Privacy Policy

Effective October 2, 2026

This Privacy Policy explains what personal data Fitness collects, why, who receives it, how long we keep it, and the choices you have. It covers the Fitness website at fitness.gg.md and the Fitness apps for iPhone, Apple Watch and Android.

At a glance

We don't sell your personal data and we don't show ads.
Apple Health data is read only with your permission and is never used for advertising, marketing or other use-based data mining. Your coach sees your Apple Health workouts, readings and live heart rate only if you turn on health sharing.
Your coach sees your profile basics and the training you do with them — see Coaches and clients.
You can delete your account from Settings at any time — see Deleting your account.

1. Who we are

Fitness is operated by Eugeniu Vozoca, str. Chișinăului 26, Chetrosu, Anenii Noi, MD-6514, Republic of Moldova, the controller of your personal data ("we", "us"). Contact us about anything in this policy at devjah@gg.md.

We process personal data in line with the EU General Data Protection Regulation (GDPR) and the data protection law of the Republic of Moldova.

EU representative

We are established outside the European Union. If you are in the EU, contact us, the controller, about any privacy matter at devjah@gg.md.

2. Data we collect

Account and profile

Your name, email address and password (stored only as a one-way hash). If you sign in with Apple or Google, we receive the account identifier, email address and name that Apple or Google shares with us — with Apple this can be a private relay address — and, from Google, a link to your profile picture. You can also add a profile photo, your language, time zone and measurement units, your gym and how long it takes you to get there, your training goal, experience level and how often you train.

Body measurements

Date of birth, biological sex, height, weight and weight history, goal weight and resting heart rate — entered by you, entered by your coach, or imported from Apple Health. We treat these as health data.

Training and scheduling

Workouts you or your coach log (exercises, sets, repetitions, weights, effort, durations, distances and notes), custom exercises you create, scheduled sessions, session requests, reschedules, cancellations and their reasons, attendance and arrival updates such as "on my way" or "running late", absences and leave requests, and the session packages a coach records for you (number of sessions, date and a note). No money moves through Fitness between coaches and clients.

Coaches and clients

Which coaches you train with, and your settings for each — for example, whether a coach can see workouts your other coaches log. A coach always sees your name and photo, your profile basics — current and goal weight, height, age, BMI, biological sex, training goal, experience and how often you train — the sessions you book with them and the workouts logged with them. Only if you allow it do they also see your workouts with other coaches, and your Apple Health data and weight history.

A coach can also create a profile for a client who doesn't have their own login yet, entering the client's name, email address, date of birth, height, biological sex and weight, and logging workouts for them. For a profile like this, the coach decides what to record and is responsible for having a lawful basis for it — for health data such as date of birth, sex, height and weight, normally the client's explicit consent. We process that data on the coach's behalf, to provide Fitness to them. The coach can correct the profile in the app but can't delete it there: to see, correct or delete that data, ask the coach or email us at devjah@gg.md. Once the client claims the profile with their own login, it becomes their own account and the rest of this policy applies to them directly.

Messages and photos

Messages you send us through the in-app chat, and any photos or files you attach. We remove metadata, including when and where a photo was taken, from photos you attach and from your profile photo, both the stored file and every copy we show; other files are stored as uploaded.

Reviews

Ratings and comments you submit in the app.

Notifications

If you allow notifications: a push token for your device, a random device identifier created by the app, your platform and your device's name or model. Live Activities on iPhone use similar tokens. Notifications can contain names, session times and short message previews; a Live Activity during a workout shows heart rate.

Device, usage and log data

When you use the website or the apps we record your IP address, the browser or app version, operating system and device type, the country derived from your IP address, the pages you visit, the page that referred you and any campaign tags in the link, when and how often you sign in, and a log of some actions you take in the app. The IP addresses of your two most recent sign-ins are stored on your account, and the action log keeps the IP address and browser used; for general web visits we store the IP address with its last part removed. The country lookup uses a database kept on our own servers (MaxMind GeoLite2) — your IP address is not sent anywhere for it. Our servers also write technical logs, which can include IP addresses.

Purchases

If you buy a subscription: the plan, product, purchase and expiry dates, and the subscription events RevenueCat sends us. Apple handles payment; we never receive your card details.

Advertising attribution

On iPhone, the app asks Apple whether it was installed from an Apple Search Ads campaign (Apple's AdServices framework) and we store the campaign details Apple returns; when you subscribe, the app reports a conversion value to Apple's SKAdNetwork. On Android, the app reads the Google Play install referrer. We use this only to learn which of our own campaigns bring new users. Neither app collects the advertising identifier — the IDFA on iPhone or the advertising ID on Android — and the iPhone app never asks to track you across other companies' apps and websites.

What we don't collect

We don't collect your precise location or your contacts: the apps never ask for access to your location, and we remove location data from photos you attach and from your profile photo. The camera and microphone are used only while you use them — to take a photo, scan a code or dictate a message. Dictation runs on your device unless you add your own Groq API key (see Who we share data with).

3. Apple Health and Apple Watch

Fitness works without Apple Health. If you connect it, iOS asks your permission for each type of data, and you can change that at any time in the Health app or in iPhone Settings.

What the iPhone app reads

Workouts; activity rings (move, exercise and stand); heart rate, resting heart rate and heart rate variability; active energy; walking, running and cycling distance; steps; VO₂ max; body fat percentage and lean body mass; height and body weight; date of birth and biological sex. The iPhone app doesn't write anything to Apple Health.

What the Apple Watch app does

When you start a workout on Apple Watch, it reads your heart rate, active energy and walking, running and cycling distance for that workout, and saves the finished workout to Apple Health. It doesn't record a route or your location.

What we send to our servers

So that you — and your coach, if you choose — can see it in Fitness: your workouts (type, start and end time, energy, distance, and the app and device that recorded them), the readings listed above with their times, daily activity ring totals, the profile values above (used to fill in empty fields of your profile), and your heart rate during a live workout, sent every few seconds. When you delete something in Apple Health, the app tells our servers, and we mark it deleted so it no longer appears.

Who can see it

You. Your coach sees your Apple Health workouts, readings, activity rings and weight history — and your live heart rate during a workout, on their screen and in a Live Activity on their phone — only if you turn on health sharing with your coach. Sharing is off by default and you can turn it off at any time.

Your profile basics are visible to your coach either way, including values Apple Health filled in: current weight, height, age (from your date of birth) and biological sex. To keep your height, date of birth or sex from your coach, clear it in your profile and turn off Apple Health access to that type — otherwise the next sync fills it in again. Your current weight is your most recent weigh-in. If your coach created your profile and you don't have your own login, your coach manages that profile and sees everything in it.

How we protect it

We don't use health data, or disclose it to third parties, for advertising, marketing or other use-based data mining, and we don't sell it or give it to data brokers. We don't share it with third parties except as you direct — for example, by turning on sharing with your coach — or with the service providers that host and run Fitness on our behalf and under our instructions. One of them is Sentry, our error-monitoring service: if an error happens while your data is being sent to us, the error report can include that data. We don't store health data in iCloud.

Your choices

We process health data on the basis of your explicit consent (GDPR Article 9(2)(a)), which you give by connecting Apple Health or by entering the data. For a profile a coach created and manages for you, the coach is responsible for the legal basis — see Coaches and clients. To withdraw your consent, turn off Fitness's access in the Health app (your profile → Apps) or in iPhone Settings, turn off sharing with your coach, or delete your Apple Health data in Fitness under Health → Delete all data. That deletes your synced workouts, readings and activity rings, and marks weights imported from Apple Health as deleted so they aren't imported again; weights you typed in yourself are kept. Deleting your account deletes all of it.

4. How we use your data, and why

To provide Fitness — your account, training log, schedule, coach and client features, notifications and sync. Legal basis: performing our contract with you (GDPR Article 6(1)(b)).
Health data, as described above. Legal basis: your explicit consent (Article 9(2)(a)); for a profile a coach manages, the coach's legal basis, as described in Coaches and clients.
To sell and manage subscriptions. Legal basis: contract, and keeping the records the law requires (Article 6(1)(c)).
To keep Fitness secure — preventing abuse, fraud and unauthorized access, including rate limits based on IP address. Legal basis: our legitimate interest in a secure service (Article 6(1)(f)).
To find and fix bugs and understand how the app is used — error reports and usage analytics. Legal basis: our legitimate interest in a working service.
To measure which of our own ad campaigns bring new users. Legal basis: our legitimate interest in knowing what works. You can object at any time.
To translate the names of custom exercises you create into the app's other languages. Legal basis: contract.
To email you when you ask to reset your password, and to reply when you contact us. Legal basis: contract.

We don't make automated decisions about you that have legal or similarly significant effects, and we don't build advertising profiles.

People you train with

Coaches and clients see what the app shows them, as described in Coaches and clients and Apple Health.

Our staff

To answer a support request or look into a problem with your account, an administrator can open Fitness as you and see what you would see. Only our own administrator accounts can do this, and only for that purpose.

Service providers

These companies process data for us, only to provide their service:

Hetzner Online GmbH (Germany) — hosts our servers and database, where the data above is stored. Our search index (Meilisearch), which includes names, email addresses and message previews for search, runs on our own servers.
Amazon Web Services (Amazon S3) — stores profile photos and the photos and files you attach to messages.
Sentry (Functional Software, Inc., USA) — error and crash reports from the website and the apps. A report can include the error, your IP address, and device and app details; from the website, also your account ID, username and email address and the request that failed, which can contain data you entered or were syncing. Android crash reports also include a screenshot of the screen at the moment of the crash.
Datadog, Inc. (USA) — receives our server logs, which can include your IP address, browser, account ID and the pages you request, and keeps them for up to 15 days.
TelemetryDeck GmbH (Germany) — privacy-focused usage analytics in the iPhone and Android apps: technical events, such as a page that failed to load and its address, linked to a pseudonymous (hashed) form of your account ID.
RevenueCat, Inc. (USA) — manages App Store subscriptions using your account ID and purchase history; on iPhone it also receives the Apple Search Ads attribution token, and in the Android app the Google Analytics for Firebase app-instance identifier.
Apple — App Store purchases, notifications and Live Activities (Apple Push Notification service), Sign in with Apple, Apple Search Ads attribution and SKAdNetwork. Your Apple Health data stays in Apple Health on your device; we receive only what you allow.
Google — Sign in with Google; notifications to Android devices (Firebase Cloud Messaging); in the Android app, Google Analytics for Firebase, which collects app usage events, an app-instance identifier and device information but not the Android advertising ID, and which we use to understand how the app is used and which of our own campaigns bring new users (our legitimate interests, see How we use your data); the Google Play install referrer; and Google Fonts, which our web pages load from Google, revealing your IP address to Google.
OpenAI (USA) — translates the names and descriptions of custom exercises you create. Only the exercise text is sent, never your account details.
Twilio SendGrid (USA) — sends password-reset emails.
Automattic (Gravatar, USA) — if you haven't uploaded a profile photo, pages request your Gravatar picture using a hash of your email address.
Pushover (Superblock, LLC, USA) — delivers internal alerts to us, which can include your email address and the text of a review you submit.
Groq (USA) — only if you add your own Groq API key in the iPhone app's dictation settings: your recorded speech and names shown on screen are sent to Groq to transcribe it, under your own account with Groq.

Other cases

We may disclose data when the law requires it, to protect the rights and safety of our users or others, or as part of a transfer of Fitness to a new operator, who would be bound by this policy. We don't sell or rent personal data.

6. International transfers

Our servers are in Germany. We run Fitness from the Republic of Moldova, which is outside the European Union. Several service providers above are based in the United States. Where the GDPR requires it, these transfers rely on the European Commission's Standard Contractual Clauses or on the provider's certification under the EU–U.S. Data Privacy Framework.

7. How long we keep data

Your account data — until you delete your account.
Records of your visits while signed in (the pages and screens you open, with a shortened IP address, browser and device) — 13 months, and deleted with your account.
Web visits by people who aren't signed in — 32 days.
The log of some actions you take in the app (session requests and changes, and rating prompts with the IP address and browser used) — 12 months, and deleted with your account. If your coach deletes their account, your session history keeps their name until it ages out.
Subscription events from RevenueCat — 24 months, also after you delete your account, to settle purchase and refund questions. They identify you only by your account number.
A profile a coach created for you that you never claimed — deleted when that coach deletes their account, unless another coach still trains you; that coach then manages the profile.
Server logs, which can include IP addresses — up to 15 days, on our servers and at Datadog.
Read in-app notifications — one month.
Second-by-second heart rate from live workouts — 30 days; the workout's averages stay.
Guest accounts that were never set up — deleted after 24 hours without use.
Crash reports at Sentry, and purchase records at Apple and RevenueCat — according to those services' own retention.

8. Deleting your account

In the app, go to Settings → Account → Delete account and type your email address to confirm. On the website, the same option is in your account settings. Deletion is immediate and can't be undone. You can also ask us by email.

We delete your profile and photo, workouts, body measurements, Apple Health data, schedule, messages, notifications, device tokens and sign-in connections, and the records of your visits and the log of actions you take in the app. What stays, and why:

If you're a coach: past sessions your clients attended, and client packages with recorded sessions, are kept under an anonymous "Former Coach" profile so your clients keep their history. Workouts you logged for clients stay in their accounts. Profiles you created for clients who never claimed them are deleted with your account, unless another coach still trains the client — that coach then manages the profile.
Subscription events from RevenueCat, for the 24 months in How long we keep data.
Deleting your account doesn't cancel an App Store subscription — cancel it in your Apple account settings.

9. Your rights

You have the right to access your data and get a copy of it, to correct it, to have it deleted, to restrict or object to how we use it, to receive the data you gave us in a portable format, and to withdraw your consent at any time (which doesn't affect what we did before). You can edit most of your data and delete your account in the app. For anything else — including a copy of your data, which we currently prepare by hand — email devjah@gg.md. We answer within one month.

You can also complain to a data protection authority, in particular in the country where you live or work. Our local authority is the National Center for Personal Data Protection of the Republic of Moldova.

10. Cookies and similar technologies

The website, and the web pages inside the apps, use only our own cookies and browser storage:

Signing in: a session cookie (_fitness_session) that keeps you signed in and protects forms; a "remember me" cookie (remember_user_token) that keeps you signed in on that device for up to 10 years or until you sign out; and current_user_id, holding your account number, which the apps use to know who is signed in. One more, impersonating, is set only in our staff's own browser while they view Fitness as a user (see Our staff).
Analytics: ahoy_visit and ahoy_visitor, which group page views into visits.
Preferences: browser_time_zone (your device's time zone), device_measurement (metric or imperial, from your device's settings in the apps), schedule_day_count (how many days the schedule shows; it replaces an older schedule_days cookie, which we delete when we see it) and tab_prefs (the tabs you pinned or hid in the apps; it replaces an older tab_overrides cookie, which we delete when we see it).
Rating prompts: ratingSnoozed, unperfectRating and lastReviewRequest, which keep the app from asking you to rate it too often.
Browser storage, which stays on your device: your theme, unsent message drafts, the schedule's zoom level, which sections you expanded, and error reports queued until they can be sent to us.

We don't use advertising or third-party tracking cookies. Our pages do load fonts from Google Fonts and, if you have no profile photo, a picture from Gravatar; those requests reveal your IP address to Google and Automattic.

11. Children

Fitness is not directed at children. You must be at least 16 years old to use it. We don't knowingly collect data from anyone younger; if you believe a child under 16 has given us personal data, contact us and we'll delete it.

12. Security

All traffic uses HTTPS. Passwords are stored only as one-way hashes, the iPhone and Apple Watch apps keep their sign-in token in the device Keychain, and tokens from third-party sign-in are encrypted in our database. No system is perfectly secure; if a breach affects your data, we'll tell you as the law requires.

13. Changes to this policy

We'll post any change on this page with a new effective date. If a change is significant, we'll tell you in the app or by email before it takes effect.

14. Contact

Eugeniu Vozoca
str. Chișinăului 26, Chetrosu, Anenii Noi, MD-6514, Republic of Moldova
devjah@gg.md