Privacy Policy
Last updated: 14 November 2026
Orizo ("Orizo", "we", "us") is a training app that adapts your running, lifting and nutrition to how ready your body is. To do that, it works with data that is personal, including health data. This policy explains exactly what we collect, why, where it goes, and how to get rid of it. The short version: we collect only what the features need, we never sell your data, and we don't show ads.
1. Who is responsible
Panagiotis Polymeros, the individual operator of Orizo, is the controller of your personal data. For anything privacy-related, contact us at [email protected].
2. What we collect and why
Account and profile
- Email, username, password (stored only as a salted hash) — to create and secure your account.
- Profile details you choose to add: display name, photo, training goals and answers to the setup wizard (e.g. your sport focus and experience level), and date of birth, gender and body metrics such as weight or height if you enter them — to personalise your plan and home screen.
Training and activity data
- Workouts and lifts you log: exercises, sets, reps, weights, personal records.
- Runs and walks: distance, pace, duration, and — if you use GPS tracking — your route (precise location). Location is collected only while you are recording an activity; background location is used solely so tracking continues when your screen is locked. We never track your location outside an activity you started.
- Treadmill sessions: you enter belt speed and may confirm console distance. Orizo does not currently connect directly to a treadmill or heart-rate strap over Bluetooth.
Private recovery insights and journal
Optional habit-journal tags (such as late meals, alcohol, travel or feeling unwell) are private to your account and are not shared with coaches. We compare logged habits with subsequent recovery signals only when there is enough data; associations are not diagnoses. You can delete journal entries from Readiness. To request a copy of your account data, contact [email protected]. Account erasure includes these records. Daytime stress is a device-computed heuristic: the server receives hourly low, medium and high stress-minute totals, not raw daytime heart-rate samples for this feature. Energy-bank, sleep, load, fuelling and training-status estimates are fitness guidance, not medical assessments. Fuelling prompts are optional and disabled when nutrition tracking is off.
Sleep stages and optional coach sharing
When the detailed sleep feature is enabled for your account, the existing sleep permission can supply awake, light, deep, REM and unspecified-asleep segments. We store compressed segments with your sleep episodes to provide sleep timelines, personal sleep estimates and regularity. No new health permission is requested for stages. A one-time import can read the previous 30 nights. An account data request includes these segments; deleting your account removes them.
“Share sleep with my coach” is off by default and is controlled separately for each coach. When you turn it on, that coach can see only your Sleep score, hours slept versus personal need and sleep regularity. Sleep stages, overnight vitals and habit-journal entries are never included in the coach response. You can turn sharing off at any time.
Daily summaries currently use deterministic templates, not an external AI service. Optional thumbs-up/down feedback and hidden-tip preferences are stored with your account and deleted with it. Staff can review aggregate counts by template without user details; no analytics SDK is used for this feedback.
Optional recovery widgets and personal comparisons
Recovery widgets are off until you enable them in App Settings. A limited summary (readiness, sleep estimate, training Load and a short headline) is then stored in private on-device storage shared with the widget extension. Raw sensor readings, journal text and account identifiers are not included. Lock-screen numbers are hidden by default. Turning widgets off, logging out or changing account clears the shared summary and requests a system refresh; the operating system controls refresh timing. The home-screen summary can be visible to anyone using your unlocked device.
Nightly sleeping-heart-rate and HRV summaries are calculated on your phone; raw samples are not uploaded for this feature. Existing recorded stress, temperature, sleep timing, check-ins and run-effort ratings can provide personal recovery guidance and retrospective agreement comparisons. These are explained fitness heuristics, not diagnoses or validated predictions. Missing measurements remain unavailable. Calibration does not automatically change your scoring weights. These owner-only details are not added to coach sleep summaries.
Health data (Health Connect / Apple Health)
With your permission, Android Health Connect can supply heart rate, HRV (RMSSD), resting heart rate, sleep sessions, steps, exercise sessions, distance, cadence, elevation gain, weight, skin temperature, respiratory rate, total calories burned, VO₂ max, overnight oxygen saturation and exercise routes (precise location). Apple Health supplies supported workouts and routes, distance, steps, heart rate, HRV (SDNN), resting heart rate, sleep, body mass, VO₂ max, overnight oxygen saturation, sleeping wrist temperature on supported devices and overnight breathing rate. Availability depends on the source and permissions you grant. History and background-read access let an enabled integration import earlier records and keep data current.
We use these records for readiness and recovery, training load and plans, activity history and analysis, maps, body-weight trends and nutrition targets where enabled. HRV metrics are labelled by source rather than treated as identical measurements. Self-reported fatigue, stress, soreness and sleep quality also inform readiness. Cycle tracking is optional and stays on your device; it is not sent to our servers or coaches.
Health data is not used for advertising, marketing or sale. You choose coach-sharing permissions and what to include in a social post. Imported health records are not changed; iOS may use a workout session to keep user-started treadmill coaching active. Disconnecting health permissions stops further reads, but does not automatically delete records already synced to your Orizo account.
Garmin Connect
If you choose to connect your Garmin account (Profile → Settings → Connected devices), Garmin sends us the data you allow in your Garmin Connect sharing settings: completed activities (type, time, duration, distance, pace, heart rate, cadence, elevation, laps and GPS route), and daily health summaries (steps, sleep, resting heart rate, heart-rate variability, stress and Body Battery). We receive it automatically after your device syncs. We never receive your Garmin password.
How we use it. Only to provide features to you: your activity history and maps, training load, fitness estimates and adaptive training plans, and your readiness, recovery and sleep insights. If you choose to, you can also share an individual activity to your feed or give a coach access, using the same sharing controls as the rest of your training data. Garmin activities are never posted automatically. If you use workout sync, planned workouts from your Orizo plan are sent to your Garmin account.
Who receives it. Garmin data is stored and processed only on our own servers in the EU, which only we administer. On its way between our servers and your app it passes through Cloudflare, which protects our servers from attacks; Cloudflare acts only on our instructions and may not use it for anything else (see section 4). Apart from that, Garmin data is not sent to any other company. We do not sell, rent or share Garmin data with anyone, and it is never used for advertising or marketing. Notifications about it (for example “your run has synced”) are delivered through your phone’s standard push-notification service.
AI transparency. No artificial-intelligence or machine-learning service processes Garmin data. Our training and recovery calculations are our own rule-based code running on our servers. Garmin data, and anything derived from it, is never used to train, evaluate or improve AI models.
Your control. You can see your Garmin data in the app and export it with the rest of your data. Disconnect Garmin at any time from Profile → Settings → Connected devices, or from your Garmin Connect account. Either way, imports stop immediately and our access at Garmin is revoked, which withdraws your consent. From the same screen you can also delete all data imported from Garmin, and deleting your Orizo account deletes it too. To access, correct or export your data, or for any other request, write to [email protected].
Nutrition data
- Meals, diet preferences and plans you log — to power meal tracking and daily targets.
- Faster food logging: typed meal descriptions are processed on our server to match foods and amounts. Food-name queries may be sent to our food catalogue provider, without your account identity or diary history. Usual-meal suggestions use only your own diary. If you import a recipe link, our server requests that public page; the site sees our server request, not your account. We briefly cache the public recipe data, not your personal food matches. Imported recipes remain drafts until you save them.
- Barcodes you scan are looked up against the Open Food Facts database (see section 4). If you contribute a product that isn't in the community database, the product information you submit (name, nutrition values, barcode) is shared with other Orizo users — never anything about you or your diet.
Social and community features
- Posts, photos, videos, comments and reactions you share to the feed follow the audience you select, along with your username and profile photo. “Everyone” posts may be accessible without signing in; “Followers” and “Only me” are restricted. Account privacy and per-post audience settings are separate.
- Content checks. Photos and videos you post, videos you add to exercises and profile photos are checked automatically for nudity, by a separate server that keeps nothing. Posts that are clearly explicit are hidden, uncertain ones wait until a person on the Orizo team has checked them, and a profile photo is only used once it passes. Messages are never checked: they are end-to-end encrypted.
- Leaderboards, leagues, levels and achievements display your username and training statistics (XP, distances, streaks) to other participants. Personal records may appear on your shared activities.
Messages
Direct messages in Orizo are end-to-end encrypted, including voice messages and attachments. We cannot read their content. Usable message keys are held on your devices; an encrypted recovery vault may also be stored on our server. We cannot decrypt that vault without the required recovery material. We process the minimum metadata needed to deliver messages (who is talking to whom, timestamps, delivery state).
Coaching
If you connect with a coach on Orizo, they can see the training data needed to coach you: your plans, logged workouts and progress. Your nutrition data is shared with a coach only after your explicit consent, which you can withdraw at any time in the app. Coaches are independent users, not Orizo staff.
Ideas and problem reports
Ideas. When you share an idea (a title, optional details and an area such as Running), the Orizo team checks it before anyone else can see it. Once approved it appears on the Ideas board without your name. We keep a link to your account so we can tell you when your idea is approved, merged with a similar one or not added, and when its status changes. Votes are shown only as totals; nobody else can see who voted. Notes you send about an idea are private to the team.
Problem reports. A report contains what you write, a screenshot if you add one, and the app version, device model and OS version unless you remove them before sending. Screenshots are re-encoded on our servers, which removes embedded metadata such as location. Only the Orizo team reads reports; our replies appear under “Your reports” in the app.
Notifications about ideas you voted for and replies to your reports can be turned off in Settings → Notifications. Deleting your account deletes your reports, screenshots, votes and notes; ideas you shared stay on the board with no link to you.
Help improve Orizo (optional)
Off unless you turn it on. About a week after you join, the app asks whether Orizo may learn from your data; once you answer, it does not ask again. You can change your answer at any time in Profile → Settings → Privacy → Help improve Orizo. Saying no, or not answering, changes nothing about how the app works for you.
What it is for. If you say yes, we use your data to build and test our own models that make readiness, pace targets and training plans better for everyone.
What it uses. Workouts, sets and how hard they felt; runs and walks (distance, pace, heart rate and elevation, without the route); sleep, resting heart rate and HRV; and your weight trend, age range and sex. Data imported from Garmin is never included (see Garmin Connect above).
What it never does. Before your data is used, your name, username and email are replaced with a random code, and your photos, messages and location are left out. We build these models ourselves, on our servers in the EU; your data is not sent to an outside AI service. It is never used for advertising, never sold and never shared with other companies. It is never offered to, or used for, anyone under 18.
Turning it off. One tap, with no questions. From then on your data is left out and is removed from the copies we train with; models already built are not rebuilt. Deleting your account does the same. The copies we train with are kept only as long as we need them to build and check a model. We keep a record of each answer you give (yes or no, when, and which version of this text you saw) so we can show we respected it; that record is deleted with your account.
Device and technical data
- Push notification tokens and delivery receipts — to send you notifications and to detect when a device silently stops receiving them.
- Basic device information and logs (device model, OS version, app version, error reports) — to keep the app working and fix bugs.
3. What we do NOT do
- We do not sell or rent your personal data. To anyone. Ever.
- We do not show ads and do not share data with advertisers or data brokers.
- We use health data only for the health, fitness and nutrition functions, the sharing choices and the optional “Help improve Orizo” setting described in this policy.
- We do not read your messages. We couldn't if we wanted to.
4. Service providers and third parties
We keep the list short. These are the only outside parties that handle your data for us or receive it:
- netcup — hosts, in the EU, the separate server that checks uploaded photos and videos (see “Content checks” above). That server keeps nothing.
- Cloudflare — protects our website and API from attacks and keeps them reachable. Traffic between your app or browser and our servers passes through Cloudflare, which decrypts it to check and forward it. Cloudflare acts only on our instructions. It is a US company, so this is a transfer outside the EU, covered by Cloudflare's certification under the EU–US Data Privacy Framework and by standard contractual clauses.
- Google Firebase Cloud Messaging — delivers push notifications. Receives your device's push token. Message notifications are delivered as encrypted payloads that are decrypted on your device.
- Google and Apple sign-in — authenticate you and provide the account identifiers and profile/email information you authorize.
- Google Maps — supplies maps on Android and processes map requests under Google’s terms. Web map tiles and server-generated route previews may use CARTO/OpenStreetMap-based tiles.
- Google ML Kit — reads nutrition labels on-device; label recognition does not send your image to a cloud OCR service.
- Apple Push Notification service — delivers iOS notifications via device tokens, including encrypted message payloads.
- Open Food Facts (openfoodfacts.org) — when you scan a barcode, the barcode number (nothing else) is sent to look up the product.
- Open-Meteo (open-meteo.com) — if you enable the weather widget, approximate coordinates (rounded, not your exact position) are sent to fetch a forecast. No account information is included.
- Garmin Connect — if you connect it, Garmin sends us your activities and health summaries as described above. We send Garmin only what is needed to link and unlink your account and, if you use workout sync, your planned workouts.
- Health Connect / Apple Health — the on-device health store operated by your OS; we read from it with your permission as described above.
Your media (photos, videos, voice messages) and all training data, including data imported from Garmin, are stored on our own servers in the EU, which only we administer.
5. Legal bases (GDPR)
- Performance of a contract — account, training, social and coaching features you signed up for, and the Ideas board and problem reports when you use them.
- Consent — health data, location during tracked activities, sharing nutrition data with a coach, notifications. Each of these is opt-in and can be withdrawn.
- Explicit consent — “Help improve Orizo”. Because it uses health data, it needs its own separate yes, which you can withdraw at any time without affecting anything else.
- Legitimate interest — security, abuse prevention, and keeping notifications reliable (delivery receipts).
6. Retention and deletion
Request deletion under Profile → Settings → Privacy → Delete account. Your account is hidden immediately. There is a 30-day cancellation window: sign back in and cancel the pending deletion to keep the account. After that window, scheduled erasure permanently removes identifying profile data, training history, health-derived metrics, nutrition logs, posts and media.
Messages already delivered to other people remain in their history under “Deleted account”; community food products and ideas on the Ideas board may remain without personal attribution. Restricted copyright evidence normally remains for 24 months after case closure, with exceptions for active disputes, legal holds and legal obligations. See the copyright section below and the account deletion instructions.
An account whose email address is never confirmed gets reminders on days 3 and 10. If it is still unconfirmed after 30 days, has nothing logged and hasn’t been opened for 14 days, it is removed by the same erasure. Anything you log keeps the account.
7. Your rights
You can ask us at any time to access, correct, export, restrict or delete your personal data, and you can object to processing based on legitimate interest. Write to [email protected] and we'll respond within one month. If you are in the EU/EEA, you also have the right to lodge a complaint with your local data-protection authority.
8. Security
Native release apps keep sign-in credentials and messaging keys in protected device storage. Offline sign-out retains a protected session-revocation request until delivery or expiry; reopening the app online lets it retry. Repeated unsuccessful authenticator checks can temporarily pause sign-in and trigger a security email. Staff receive an alert when a new staff authenticator is enrolled.
All traffic between the app and our servers is encrypted in transit (TLS). Passwords are stored hashed, direct messages are end-to-end encrypted, and access to production systems is restricted. No system is perfectly secure, but if a breach affects your data we will notify you as required by law.
9. Children
Orizo is not intended for anyone under 16, and we do not knowingly collect data from children. If you believe a child is using Orizo, contact us and we will delete the account.
10. Changes to this policy
If we change this policy in a way that matters, we'll tell you in the app before the change takes effect. The date at the top always reflects the latest version.
Copyright reports and disputes
Panagiotis Polymeros, the individual operator of Orizo, is responsible for this processing. Copyright contact addresses are verified before acknowledgement details are emailed. Submission and verification emails are rate-limited. Copyright submissions include contact details, work descriptions, reported URLs, signatures, statements and decisions. We use them to investigate reports, apply our rules and establish or defend legal claims, based on applicable legal obligations and legitimate interests.
Only authorised legal administrators can access case records. The uploader normally receives the claimant’s name/organisation, work description and decision reasons, not private contact details. A formal US counter-notice is forwarded in full to the claimant, including the uploader’s contact details, after an explicit warning and human completeness review. Lawful disclosure may also be required for proceedings.
Restricted evidence and records may survive account/content deletion. They are normally retained for 24 months after closure, then unnecessary identifying information and evidence are erased; active disputes, documented legal holds and legal obligations may require longer. Contact [email protected] for case enquiries or the contact below to exercise privacy rights. See Copyright.
11. Contact
Questions, requests, complaints: [email protected].
Clips recommendations
With your permission, we use what you finish, replay or skip in Clips, alongside your sport, likes, follows and planned training, to recommend clips. “Not interested” helps you see fewer similar clips. Personal viewing history is kept for 90 days; aggregate clip totals remain. You can remove your viewing history and switch to newest-first in Settings → Privacy → Personalised Clips. For people under 18, watch-based personalisation is off and watch history is not stored; recommendations use explicit choices instead. Guests are not tracked. Only the creator can see a clip’s viewing statistics. Aggregate viewer counts use per-clip keyed estimates to limit repeated votes from one account, without adding personal watch-history records. Discovery snapshots are bounded per viewer, with one shared guest snapshot.
