Privacy policy

Forma is an iPhone and Apple Watch app for logging food, training, runs and optionally body measurements and body photos. This page describes what personal data we process in the app, on this website, on the waitlist and in the partner program, why, on what legal basis, who helps us and how long we keep it. Effective 1 November 2026.

1. Controller and contact

The data controller is Tomáš Hájek, company ID (IČO) 03968944, registered at Na Křivce 1443/1, 101 00 Praha 10 – Vršovice, Czech Republic. For anything about your data, email tom@draive.online. We reply without undue delay and within one month at the latest.

2. What we process, why and on what legal basis

Account: a random account identifier and, if you sign in with Apple, the identifier from Sign in with Apple (we ask Apple for neither your name nor your email). Also language, time zone and app settings. Purpose: running your account and syncing your data between your devices. Legal basis: performance of a contract (Art. 6(1)(b) GDPR).

Email sign-in: when you sign in or sign up with email, we process the address you enter. We send a one-time six-digit code to it, valid for 10 minutes. We store the address as the sign-in credential of your account so that the account can also be opened on another device. We store the code only as a hash, never in readable form, and delete it within 24 hours at the latest. Neither the address nor the code is written to server logs. Purpose: verifying that the account is yours and letting you sign in. Legal basis: performance of a contract (Art. 6(1)(b) GDPR). Email sign-in does not turn on any marketing emails; the website waitlist is separate (section 7).

Sign in with Google: the app asks Google only for the openid and email scopes. From Google we receive the identifier of your Google account (the "sub") and your email address together with whether Google has verified it. We get nothing else from your Google account (such as contacts, photos, calendar or Drive). If Google gives us a refresh token, we store it encrypted and use it only to revoke our access at Google when you remove the Google method from your account or delete the account. Purpose: letting you sign in. Legal basis: performance of a contract (Art. 6(1)(b) GDPR). For the sign-in itself at Google, Google is an independent controller (section 8).

Several methods on one account: you can add several sign-in methods to one account (Apple, Google, email) or use the app without signing in. We match methods into one account by a verified email address only between email sign-in and a Google account whose address Google itself manages (for example @gmail.com or a Google Workspace domain). We never match an account to Sign in with Apple by email, because we do not ask Apple for an email. Two accounts that each already have a sign-in method are never merged automatically.

Health and lifestyle data (special category under Art. 9 GDPR): food and drink logs, workouts and sets, run summaries, weight, body measurements, fasting, water and the Apple Health data you allow in iOS (for example active energy, steps, heart rate, sleep and workouts). Purpose: calculating your daily targets, showing progress and building plans. Legal basis: your explicit consent (Art. 9(2)(a) GDPR), which the app asks for in the onboarding before you start logging. Without it these features do not work. Withdraw it in the app on the Me screen; the app then offers export and account deletion.

The route of a run stays on your phone and in Apple Health; only a summary (distance, time, pace, heart rate) goes to our server. The app uses your location only while recording a run.

Section 6 describes the connections with Strava and Garmin and Health Connect on Android. The route of a run leaves your phone only to Strava, and only at your request.

Food photos and food text for AI recognition: a photo of your plate or a sentence about a meal goes through our server to an AI model (Google Vertex AI, processed in the EU, not used to train models). We never store the photo permanently. If the app needs to ask a follow-up question, the server keeps it for 30 minutes at most. The result without personal data (the meal text and suggested items) may be cached for 90 days so the same request does not go to the model again. Legal basis: your explicit consent (Art. 9(2)(a) GDPR).

Buddy: when you send an invite or accept one, we link your account with one other person's account. Your Buddy then sees only your name (if you have one set in the app), whether you logged food that day, whether you finished a workout, and the length of your shared streak. They do not see what you eat, calories, macronutrients, weight, measurements, photos, the content of your workouts or any other values from your logs, so we pass them no health data under Art. 9 GDPR. An invite is a link with a random code, valid for 48 hours. We send the code to no analytics and to no one else. Remove the link in the app at any time (Me → Buddy → Remove buddy), and you can block your Buddy so they cannot link with you again. Legal basis: your consent (Art. 6(1)(a) GDPR), which you give by sending or accepting an invite and withdraw by removing the link.

Shared plans: a plan you share by link is visible to anyone you send the link to. You can stop sharing at any time. Legal basis: performance of a contract.

Subscription: the status of Plus, the trial and App Store purchase receipts (no payment details, only Apple has those). Purpose: unlocking Plus. Legal basis: performance of a contract and, for accounting records, a legal obligation (Art. 6(1)(c) GDPR).

Code from a partner: when you get Plus with a code from a Forma partner (for example a gym, coach, running club, shop, creator or employer), we can tell from the App Store purchase whose code it was. RevenueCat passes us which code was used together with the purchase. We store your account identifier, the partner, the date of the attribution and the App Store purchase events that belong to it (purchase, renewal, refund, price, currency and storefront country), with no payment details. Purpose: calculating and settling the partner's reward. Legal basis: our legitimate interest in fulfilling our contracts with partners (Art. 6(1)(f) GDPR) and, for accounting records, a legal obligation (Art. 6(1)(c) GDPR). A partner only receives monthly totals from us (for example how many people redeemed the code and how many pay), never your name, email, identifier or anything from the app. An employer gets totals only when at least 10 people redeem its code in a month. Health data is not used for the attribution and is never passed to a partner. Gift codes do not attribute you to a partner.

Notifications: the push token from Apple and your notification settings. Notifications on the lock screen show no numbers unless you turn that on. Legal basis: performance of a contract.

Security and abuse prevention: server logs (time, request type, errors, without the content of your logs and without health data) and device checks via Apple App Attest and DeviceCheck so that nobody bypasses limits or forges requests. Legal basis: our legitimate interest in secure operation (Art. 6(1)(f) GDPR).

App analytics: anonymous events and counts only (for example that a measurement was saved or a screen opened), no health data, no body measurement values, no food content and no images. Legal basis: legitimate interest in improving the app (Art. 6(1)(f) GDPR).

Support: when you write to us, we process your email and message to reply. Legal basis: legitimate interest, or performance of a contract for questions about it.

We do no profiling and no automated decision-making with legal effects. We do not sell data and do not use it for advertising in the app.

3. Body measurements (circumferences)

Body measurements are circumferences of your waist, hips, chest, thigh, upper arm, neck and calf in centimetres. You enter them yourself after measuring with a tape, and you can also import your waist from Apple Health. You can fill in any of the places. With every measurement we store the date and the source: tape, Apple Health or body scan (section 5).

Like weight, body measurements are health data under Art. 9 GDPR. We process them on the basis of your explicit consent, which you give in the app. You can withdraw it at any time in the app settings.

Your measurements are stored on your phone and on our server in the EU (Railway, EU West, Amsterdam). We use the server for syncing between your devices and as a backup. We use them for nothing else: they do not appear on the watch, in widgets, in notifications with numbers or to your Buddy, they do not count towards your streaks, and they are hidden by default on share cards. You can hide the Body section in settings, which does not delete any data.

If you grant permission in iOS, Forma writes a waist measured with a tape to Apple Health and reads the waist you already have there. A waist read from Apple Health is stored as a measurement with the source Apple Health. We never write a scan estimate to Apple Health. You can change the permission at any time in iOS Settings. When you delete a measurement in Forma, we also delete the sample Forma wrote to Apple Health.

You can correct or delete a measurement in the app at any time. A deleted measurement stops being shown and is marked as deleted on the server. It disappears from our servers completely at the latest when you delete your account. Until then the server keeps only a marker of the deleted record, which syncing between your devices needs. Measurements are part of the data export (CSV and JSON).

4. Body photos

Body photos are an optional feature. You take a photo of yourself in the app (or pick one from your gallery) so that photos from two different days can be compared. The app can show a translucent outline of your previous photo in the viewfinder so that the pose matches.

Body photos stay only on this phone. We do not send them to our server, to an AI model or to analytics, and we have no access to them. The app does not upload them to iCloud on its own (it uses neither iCloud Drive nor CloudKit) and does not write them to your Photos library. If you pick a photo from your gallery, the app receives only that one photo and stores its own copy.

Photos are kept in the app's storage, which iOS protects with encryption and which is available only while the phone is unlocked. Stored photos contain no location and no other EXIF data.

You control your device backup. If it is turned on (to iCloud or to a computer), iOS creates it from the whole phone including app data, so it may contain your body photos. Deleting a photo in Forma does not remove it from an older backup that already contains it. That backup keeps it until a newer backup replaces it or you delete it. You manage backups in iOS Settings.

Only you can send a photo out. A body photo gets onto a share card only after you explicitly select it and confirm that everyone you send the card to will see it. The card is created on your phone and is not sent to our server. We cannot influence what a recipient does with a card you send.

You can delete one photo, selected photos or all of them at any time, even offline. When you delete your account, the app also deletes all body photos on your phone. Uninstalling the app deletes the photos with it (subject to the backup caveat above). Because we have the photos nowhere else, we cannot restore them.

Body photos are not in the data export, because we do not have them. You grant camera access in iOS and can withdraw it at any time.

5. Body scan and outlines (coming soon)

Body scan is a feature that is yet to come to the app. We describe in advance how it will handle your data.

From the outline of your figure on two camera frames (front and side), the scan estimates the circumference of your waist, hips, thighs and chest. The whole calculation runs on your phone. Scan values are an estimate and do not replace a measurement by a professional.

Camera frames are not stored at all. They stay only in the phone's working memory for the duration of the calculation, a few seconds, and are then discarded, even if you interrupt the scan or it fails. The camera runs only during the scan and iOS shows its indicator. We use the frames for nothing but the calculation.

The outline of your figure (a silhouette only, without colours) and auxiliary calculation data stay only on your phone, stored with the same protection as body photos. We do not send them to a server or to iCloud on our own, and the same backup caveat applies to them. You delete an outline by deleting the measurement, all scans or your account. We do not use the outline to identify a person, yet we protect it as health data.

Only numbers go to the server: circumferences, date, the source "scan", the version of the calculation and whether a tape calibration was used. They are stored like other body measurements (section 3).

6. Strava, Garmin and Health Connect (coming soon)

Connections with Strava and Garmin, and the Android app with Health Connect, are still to come. We describe in advance what will happen to your data. Connecting Strava or Garmin is optional, only you can turn it on, and each connection has its own consent.

Strava: when you connect Forma to your Strava account (by signing in at Strava, OAuth), Forma uploads a finished run to it at your request: time, distance, route, heart rate, cadence and laps. You give the instruction with the button on a run, or by turning on automatic upload of new runs (off by default). You can turn off sending heart rate. The run goes from your phone straight to Strava; neither the route nor the heart rate passes through our server. Before the upload the app applies your privacy zones to the route (by default it leaves out the first and last 200 m). Strava, Inc. (USA) is an independent controller of the uploaded runs and processes them under its own policy (strava.com/legal/privacy). Who can see a run on Strava depends on your Strava settings. Legal basis: your explicit consent, given when you connect (Art. 9(2)(a) GDPR for heart rate, Art. 6(1)(a) GDPR for the route and other data).

We read and store nothing from Strava, not your activities, routes or profile. For the connection and uploads we keep on our server in the EU only your Strava account identifier, encrypted access tokens and, for each uploaded run, the upload and activity identifiers on Strava and the upload status. Nothing from Strava goes to an AI model. If you delete a run on Strava, we mark it as deleted and keep the activity identifier so that the same run is not uploaded to Strava again. You can disconnect at any time in the app, or on Strava by removing Forma's access. Disconnecting withdraws your consent: we revoke access at Strava and delete the tokens and the upload records. Runs already on Strava stay there; you delete them on Strava.

Garmin, importing from Garmin Connect: when you connect your Garmin account (by signing in at Garmin, OAuth) and consent to importing, we receive only summaries from it on our server in the EU. For strength workouts recorded on a Garmin device these are the time, workout type, energy, average heart rate, device model and sets (exercise, reps, load); for each night, heart rate variability (HRV) and resting heart rate. Sleep and other workouts from Garmin come only through Apple Health, or Health Connect on Android, if Garmin Connect writes them there. We store no FIT files and no routes. Purpose: showing your completed sets in your training history and including your recovery in the training readiness calculation. We send no Garmin data to an AI model. Legal basis: your explicit consent to importing from Garmin, given when you connect (Art. 9(2)(a) GDPR). Importing also needs your consent to health data from section 2.

You can turn importing off in the app, which withdraws that consent. You can disconnect Garmin in the app or in Garmin Connect. Disconnecting withdraws your consent: we revoke access at Garmin and delete the tokens. When you disconnect in the app, it offers to delete the workouts and recovery data already imported. The default is to keep them. They then stay with your other logs under your consent to health data from section 2, as they do after you disconnect in Garmin Connect, and are deleted when you delete your account or withdraw that consent. Imported workouts and recovery data are part of the data export.

Garmin, your plan on the watch: when you connect Garmin and consent to sending your plan, Forma sends workouts from your plan to your Garmin account at your request, so that they appear in the Garmin Connect calendar and on your watch: exercises, sets, reps, load, rest and, for runs, steps with a target pace or a target heart rate zone. For a step with a heart rate zone we send the zone number and the target heart rate range, which comes from your maximum heart rate (HRmax): the one you enter, or the one the app measures or estimates. Because the range comes from your maximum heart rate, we treat it as health data. You give the instruction on a workout, or by turning on automatic sending of your plan (off by default). We send no other health data, such as your body weight, measured heart rate, sleep or food. Garmin International, Inc. (USA) is an independent controller of the workouts you send, not our processor, and processes them under its own policy (garmin.com/privacy). Legal basis: your explicit consent, given when you connect (Art. 9(2)(a) GDPR for the target heart rate range, Art. 6(1)(a) GDPR for the other data). For the workouts sent we keep only the Garmin identifier, the day and the sending status. You can turn sending off in the app, which withdraws that consent. We delete the records of sent workouts when you disconnect. Workouts already in your Garmin Connect calendar stay there; you delete them in Garmin Connect.

Health Connect (Android): the Android app is still to come. Once it is released, it will use Health Connect wherever the iPhone app uses Apple Health, to the same extent. In Health Connect each type of data is a separate permission. The app asks for it when a feature needs it, and you can remove it at any time in the Health Connect settings. The app will read weight, body fat percentage and height, steps, active energy and workouts, sleep, heart rate variability (HRV) and resting heart rate and, for runs, distance, speed, heart rate, cadence, power, elevation gain, VO2 max and the route (the route only with your additional consent). It will write weight entered in Forma, workouts and runs from Forma, food (energy, macronutrients, fiber and micronutrients) and water. Health Connect has no body circumferences; those stay only in Forma.

Data from Health Connect stays on your phone. Only what the iPhone app sends from Apple Health goes to our server, in the same way (section 2), and never the route of a run. The legal basis is the same as for Apple Health: your explicit consent to health data (Art. 9(2)(a) GDPR). We use data from Health Connect only for the app features that need it. We do not use it for advertising, we do not sell it and we pass it to no one else, except our processors (section 8) and what you send to Strava or Garmin at your request under this section. Our use of data from Health Connect follows the Google Play policy on Health Connect permissions, including its Limited Use requirements.

7. Website, waitlist, advertising and partners

We measure website traffic with Umami (Umami Cloud, data in the EU) without cookies and without storing anything in your browser. Umami stores no IP address or other identifier that would let us recognise you; we only see aggregate numbers (pages, where visitors came from, device type, country) and counts of clicks on the App Store link, language switches and form submissions. On partner pages (/c/…) we also see, as totals, which partner and which source (for example a QR code) visits came from and how often someone tapped download or redeem. Legal basis: legitimate interest in knowing how the website is used (Art. 6(1)(f) GDPR).

Waitlist: when you sign up on the website, we process your email, the website language, where you came from (for example an ad on Facebook), and the time and wording of your consent (the version of the text at the checkbox) as proof of consent. The form sends the data directly to our processor Brevo, which sends you a confirmation email. We add you to the list once you confirm the address with the link in that email. Purpose: sending you the confirmation email and one email about the app launch. Legal basis: your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time with the link in the email or by writing to tom@draive.online.

Ads on Facebook and Instagram: when you sign up through a Forma form directly in Facebook or Instagram, Meta Platforms Ireland passes us your email, the time and your consent from the form. We store them like a website sign-up (source "Meta") and send you a welcome email. Meta is responsible as an independent controller, under its own policy, for showing the ad and for the data it holds about you. We use no Meta Pixel or other social media tracking code on the website or in the app.

New sign-up alerts: Brevo emails us about every new sign-up (address, language, source) so we keep track of the list. We pass the addresses to no one else.

Partnership enquiries: when you fill in the form on the Partner with us page, we process the business, club or brand name, the kind of partner, city, website or profile, your name, email, phone (if you fill it in), message, website language, and the time and version of your consent. The form sends the data directly to our server (Railway, data in the EU), where we store it in our partner records (next paragraph). Through Brevo we send you a confirmation that we received your message, and an alert to us. Purpose: replying to you and sending a partnership offer. Legal basis: your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time by writing to tom@draive.online, and steps prior to entering into a contract (Art. 6(1)(b) GDPR).

Partner contacts: we keep records (a CRM) on our server in the EU of the businesses we work with or are talking to about a partnership (gyms, coaches, clubs, shops, creators, employers). For contact persons they hold the name, role, work email and phone, the history of our communication (emails, calls, meetings, notes) and the acceptance of the partnership terms. We find businesses we approach ourselves, and their work contacts, in public sources (the business's website, a public profile). The records hold no bank or invoicing details; invoices arrive by email and we keep them as accounting law requires. Purpose: agreeing, running and settling partnerships in the partner program. Legal basis: our legitimate interest in approaching businesses and running partnerships with them (Art. 6(1)(f) GDPR), your consent for an enquiry through the form, and the performance of the contract once a partnership is agreed (Art. 6(1)(b) GDPR). You can refuse further contact at any time by writing to tom@draive.online: we delete the contact and keep only a fingerprint of your address (an HMAC from which the address cannot be read), so we never approach you again. Writing to us through the form later cancels that refusal.

Partner portal: contact persons of a partner whom we have given access sign in to the partner portal with their email and a one-time code that we send through Brevo (valid for 10 minutes, at most 5 attempts). To prevent abuse we keep only fingerprints of the email, the code and the IP address while the code is valid. A sign-in lasts at most 12 hours: our server keeps only a fingerprint of the sign-in token and the times of sign-in and last use; your browser keeps the token only in that tab (sessionStorage) and forgets it when you sign out or close the tab. The portal shows totals for the partner only, never data about individual app users, and uses no traffic measurement and no third-party scripts. Legal basis: performance of the partnership contract (Art. 6(1)(b) GDPR) and our legitimate interest in a secure sign-in (Art. 6(1)(f) GDPR).

8. Processors and other recipients

These processors help us run Forma. Each processes data only on our instructions and under a data processing agreement.

Railway Corporation (USA): hosting of the app server, database (including the partner records) and this website. Servers and data are in the EU (EU West, Amsterdam).

Google Cloud (Google Ireland Limited): the Vertex AI model for recognising food from photos and text, processed in EU member states, not used for training.

Google Ireland Limited (Sign in with Google): the provider of sign-in with Google. For the sign-in itself it is an independent controller under its own policy (policies.google.com/privacy). From Google we receive only the data in section 2 (your Google account identifier and verified email). You can also withdraw Forma's access to your Google account in your Google account settings.

Brevo (Sendinblue SAS, France): waitlist emails (confirmation, welcome, launch announcement), new sign-up alerts, confirmations and alerts for partnership enquiries and transactional emails with a one-time sign-in code for the app and the partner portal (sent from ahoj@mail.forma.draivemobile.com; for these Brevo receives your email address and the text of the message with the code). Data is in the EU.

Umami (Umami Software, Inc., Umami Cloud, EU region): website traffic measurement without cookies and without personal data.

RevenueCat, Inc. (USA): management of the Plus subscription and trial based on App Store receipts. It receives a random account identifier, no health data.

TelemetryDeck GmbH (Germany): anonymous app analytics without health data.

Apple Distribution International Ltd. (Ireland) and Apple Inc.: the App Store and payments, Sign in with Apple, push notifications (Apple Push Notification service), App Attest and DeviceCheck. For the App Store, payments and Apple Health, Apple is an independent controller under its own policy. Data in Apple Health stays on your phone under your control.

Meta Platforms Ireland Ltd.: only for ads and the waitlist form on Facebook and Instagram, as an independent controller (section 7).

Partners in the partner program (gyms, coaches, clubs, shops, creators, employers) receive none of your personal data from us, only aggregate numbers that do not identify you (section 2).

Strava, Inc. (USA): only if you connect Strava. At your request it receives the runs you send to it and is an independent controller of them under its own policy, not our processor (section 6).

Garmin International, Inc. (USA): only if you connect Garmin. At your request it receives the workouts from your plan that you send to it and is an independent controller of them under its own policy, not our processor (section 6). We process the data we import from Garmin at your request as the controller.

We may also disclose data to authorities where the law requires it.

9. Transfers outside the EU

We store and process health data, food photos and account data in the EU. Railway, RevenueCat, Umami and Apple are companies based in the USA or with a US parent company, so their staff outside the EU may access data. Such transfers are covered by the European Commission adequacy decision (EU-U.S. Data Privacy Framework) for certified companies, otherwise by the European Commission standard contractual clauses and further safeguards (encryption in transit and at rest).

Sign in with Google: Google may process data in the EU and the USA under its own policy. Transfers within Google are covered by the EU-U.S. Data Privacy Framework and standard contractual clauses. Brevo sends the emails with the sign-in code from servers in the EU.

Strava and Garmin: the runs and workouts you send to them at your request (section 6) are also processed in the USA. Garmin International, Inc. is certified under the EU-U.S. Data Privacy Framework, so transfers to Garmin are covered by the European Commission adequacy decision. Strava, Inc. is not certified, and we have no standard contractual clauses with Strava, because we do not entrust it with processing data for us; you send the data to your own account. For the data you send to Strava, protection of personal data at the EU level is therefore not guaranteed in the USA, for example as regards access to data by US authorities. Transfers to Strava rely on your explicit consent, given when you connect (Art. 49(1)(a) GDPR). We store the data we import from Garmin in the EU.

10. Retention

Account data, logs and health data: for as long as you have an account. When you delete your account in the app, we delete them from the server right away, and they disappear from database backups as those rotate, within 3 months at the latest.

Buddy link: until one of you removes it or deletes their account. A block: for as long as you have an account. An invite is valid for 48 hours.

A food photo on the server: 30 minutes at most, and only when the app asks a follow-up question. A recognition result without personal data: 90 days.

Server logs: 30 days at most. They contain neither an email address nor a sign-in code.

Email address and Google account identifier as sign-in credentials: for as long as you have the account. We delete them when you remove that method in the app (Me → Account) or delete the account.

The encrypted Google token: until you remove the Google method or delete your account, when we revoke it at Google.

One-time sign-in codes: valid for 10 minutes, stored only as a hash and deleted within 24 hours at the latest.

Strava: your Strava account identifier, encrypted tokens and records of uploaded runs until you disconnect (in the app or on Strava) or delete your account, then we delete them at once. Until then, the record of a run you delete on Strava stays, marked as deleted (section 6).

Garmin: encrypted tokens and records of sent workouts until you disconnect or delete your account. Data arriving from Garmin waits for processing, encrypted, for 72 hours at most. Imported workouts and recovery data: like other health data, unless you delete them when you disconnect (section 6).

Waitlist: until we send the launch email, at most 2 years from sign-up. After you unsubscribe we send you nothing more and delete the address within 30 days. The proof of consent (text version and time) is kept as long as the address.

Accounting and tax records about subscriptions: as long as the law requires (usually 10 years).

Code from a partner: the attribution to a partner for as long as you have an account. Records for settling the partner's reward (purchase events and the reward calculation) for as long as accounting and tax law requires (usually 10 years). When you delete your account, we delete the attribution and anonymise the settlement records: only the partner, dates and amounts remain, without your account identifier.

Partnership enquiries and partner contacts: a contact at a business with which no partnership followed, which ended or which declined, is deleted 12 months after the last contact (with no contact, 12 months after it was created). During a partnership we keep the contact for its duration, contracts and invoices as long as the law requires (usually 10 years). The fingerprint of an address after a refusal of further contact is kept without a time limit, otherwise we could not respect the refusal.

Partner portal: sign-in codes (valid for 10 minutes) and sign-ins (valid for 12 hours) are deleted after they expire, at the latest within 24 hours.

Aggregate website statistics and anonymous app analytics contain no personal data and are kept without a time limit.

11. Your rights

You have the right to access your data, to rectification and erasure, to restriction of processing and to data portability (CSV and JSON export right in the app on the Me screen, including body measurements; body photos and outlines are not in it because they exist only on your phone). You can object to processing based on legitimate interest. You can withdraw consent at any time without affecting processing before the withdrawal: consent to health data in the app on the Me screen, consent to a reply to a partnership enquiry by writing to tom@draive.online, consent to the waitlist with the link in the email, consent to sharing with your Buddy by removing the link.

You withdraw consent to the Strava and Garmin connections by disconnecting or by turning their features off in the app (section 6). You manage access to Apple Health and Health Connect in your phone's settings. The export also includes your connections (without access tokens), records of runs uploaded to Strava and of workouts sent to Garmin, and the workouts and recovery data imported from Garmin.

You can delete your account and all server data yourself in the app on the Me screen. Send any other request to tom@draive.online.

You manage sign-in methods in the app under Me → Account: you can add another method or remove one (not the last one, so the account is not left without a sign-in; to leave completely, delete the account). Removing a method deletes the address or identifier stored for it and revokes the Google token. Deleting your account deletes all methods including the email address and revokes access through Apple and Google. You manage your Google account and its permissions for Forma at Google (myaccount.google.com).

You also have the right to lodge a complaint with the Czech Office for Personal Data Protection (Úřad pro ochranu osobních údajů), Pplk. Sochora 27, 170 00 Praha 7, www.uoou.cz, or with the supervisory authority in the country where you live.

Living in the United States? Our Consumer Health Data Privacy Policy describes the health data we process under US state laws (Washington My Health My Data Act, Nevada, Connecticut), who receives it, your rights and how to use them.

12. Cookies and similar technologies

This website uses no cookies and stores nothing in your browser, except the partner portal: while you are signed in, your browser keeps the sign-in token there (sessionStorage, until you sign out or close the tab, at most 12 hours), without which the sign-in would not work. Fonts are self-hosted. Traffic measurement (Umami) works without cookies. The app does not use the advertising identifier (IDFA) and does not track you across other companies' apps and websites.

13. Children

Forma is not intended for children under 16. Body photos are available from 18. If we learn that a child under 16 gave us data without a parent's consent, we delete it.

14. Changes

When we change this policy, we update the date below. We tell you in the app in advance about any material change, such as a new purpose or a new recipient of health data, and ask for new consent where needed.

On 20 October 2026 we added sign-in with email and with Google (today sections 2, 8, 9, 10 and 11).

On 31 October 2026 we added codes from partners, the partnership enquiry form, partner contact records and the partner portal (today sections 2, 7, 8, 10, 11 and 12).

On 1 November 2026 we changed section 8: Vertex AI processes food photos and text in EU member states rather than in one named region.

Section 6 on Strava, Garmin and Health Connect applies from the app version that brings each connection, for Health Connect from the Android app. Adding section 6 raised the numbers of the following sections by one.

The Buddy paragraph in section 2 applies from app version 1.0.1, which brings Buddy.

Effective from 1 November 2026.