Privacy Policy
What ProgressLoop collects, why it collects it, who else ever sees it, and how to make it stop.
Who is responsible for your data
ProgressLoop is a training app for iPhone and Android phones, with companion apps for Apple Watch and Wear OS watches, and this website. The controller of the personal data described below - the person who decides why and how it is processed - is Simeon Rosenov Simeonov. ProgressLoop is not a company: it is published by an individual, and no legal entity stands behind it.
For any question, request or objection about personal data, write to privacy@progressloop.eu. That address is read by the same person, and it is the only channel for data requests.
This policy covers the ProgressLoop iPhone app and the Apple Watch app that comes with it, the ProgressLoop Android app (eu.progressloop.ProgressLoop) and the Wear OS watch app that comes with it, the one account behind all of them, and the website at progressloop.eu. The apps do the same things with your data on either platform; where they differ - Apple Health on an iPhone, Health Connect on an Android phone - this policy says which is which.
The principles this is built on
Personal data is processed lawfully, fairly and transparently; for stated purposes; in the amount those purposes need; for a limited time; and with appropriate security. Four commitments are worth stating plainly, because they are the ones a training app is most often expected to break:
- Nothing is sold, and your record never reaches an advertiser. There are no ads inside ProgressLoop. What an advertising company hears from us is that a few steps in the phone app happened - installing it, signing up, finishing a first workout and the like - so that we can tell whether our own ads on Facebook and Instagram bring people who actually train. No workout, weight, measurement, photo or health reading goes with them. And if you came to the athlete survey on our website from one of those ads and say yes when it asks, our server tells Meta that you finished it - never your answers. Beyond that, our server only asks Apple which of its own ads, if any, led to an iPhone install. The section on measuring our own ads says exactly what is sent, and how Apple's tracking prompt on an iPhone, or your ad settings on an Android phone, decide what Meta may do with it. Separately, and only if you say yes, the phone apps tell Google Analytics for Firebase how the app itself is used - which screens are opened, where a sign-up or a workout was left unfinished - so that we can make it easier to use. Not for ads, and never what you recorded. And the apps tell our own server, and nobody else, when a few moments happen in them - a first-steps screen answered or skipped, a workout started or finished - so that we can see where people get stuck before they start training. A switch in the app's settings turns that off.
- The website counts visits, never visitors. It sets no cookies and loads no third-party scripts. Your chosen theme and language are saved in this browser, separately from visit counting. Its main pages tell our own server that something happened - a page was opened, a button pressed - and the server adds that to the day's totals without storing your IP address, a cookie or any identifier. If your browser sends Do Not Track or Global Privacy Control, the website counts nothing at all. That is why there is no cookie banner: the section on cookies says exactly what is counted. The one exception is a short link of ours, on
go.progressloop.eu, such as the one a QR code on a poster carries: it keeps a short record of each visit, still with no IP address or cookie, only a scrambled code that tells a returning visitor apart, and the same section says what is in it. The other is the athlete survey on the website, which saves the answers you choose to give to our own server, under a random number that names nobody; its own section says what is kept. The apps are described separately below. - Your training record is yours. It is not used to build a profile of you for any purpose other than showing you your own history. Five things widen who sees any of it, and each is yours to start: an AI reading of a week of it, recipes and estimates from the meal assistant, a personal trainer you apply to, putting your schedule into a calendar of your own, and - if you coach - sending one of your own plans, guides or recipes to a client. None of them happens until you choose it. And a workout photo you share goes only where you send it, carrying only what is drawn on it.
- Two things are public, and you choose both. A review you give a trainer is read by everyone who browses the trainer directory, and so is your trainer profile if you switch on as a trainer. Nothing else you put into ProgressLoop is.
What we process
Your account
- Your email address, and your name if you give one. An account made by signing in with Apple can have no address at all - see how you sign in, below.
- Your password, if you set one, stored only as a cryptographic hash - the original is never written down and cannot be read back. An account made by signing in with Apple or Google has no password here at all.
- Your gender, if you set one, because some body-composition figures depend on it.
- A profile picture, if you upload one.
- Account status, when it was created, and the units you prefer to read weights and lengths in.
- When you accepted the Terms of Use and this Privacy Policy - the moment you ticked the box, and nothing else about it. It is recorded whether you registered with an address and a password or made the account by signing in with Apple or Google, since the app asks either way before the account is made.
How you sign in
- If you sign in with Apple or with Google: the identifier that provider gives us for you in ProgressLoop, the email address it passes on, if you let it, and your name, if it passes one. That is the whole of what we ask either of them for and the whole of what we receive - nothing else in your Apple or Google account is read, and nothing can be done in it on your behalf. An Apple account is recognised by that identifier from then on; a Google one is found by the address Google confirms, whatever capitals it is written in. Sign in with Apple is offered in the iPhone app; the Android app offers an address and a password, or Google, through the account picker Android itself shows. Either way you reach the same account from both.
- Sign in with Apple lets you keep your address to yourself, and we hold what you chose. Hide My Email means the address on the account is the forwarding one Apple gives us, never your own - everything below about email is then about that forwarding address, and what it forwards to is between you and Apple. Sharing no address at all means the account has none: nothing can be emailed to it, and the section on emails and notifications says what that changes.
- For Sign in with Apple, the authorisation Apple issues for your account, stored encrypted. It is used for one thing: handing it back to Apple when the account is deleted, which Apple requires of an app that offers both its sign-in and deletion in the app.
- If you signed in with a provider on an address that already had a ProgressLoop account, the two are the same account: you land on the record you already had rather than a second, empty one, and it keeps the password it had, if it had one. Choosing to hide your address gives you an account of your own instead, because the address Apple forwards from is nobody else's.
What you train
- Exercises you add or edit, workouts, training programmes and the days inside them.
- Every session you run: which sets you logged, the load and reps of each, how long you rested, when you started and when you finished.
- Cardio planned before or after a workout, and the cardio logged with a session: its kind (a run, a ride, rowing and so on), minutes, distance and a note, if you give them.
- For sessions recorded with the Apple Watch app, your average and peak heart rate and the active energy you burned during the session. See the section on health and body data below.
- For sessions recorded with the Wear OS watch app, your average and peak heart rate during the session. See the section on Health Connect and Wear OS below.
- For a recent session that has no heart rate of its own, your average and peak heart rate while it ran, as Apple Health or Health Connect recorded it - from a watch's own health app, say - if you allow the app to read heart rate. And for a cardio step you logged, the distance and average heart rate of the matching workout another app recorded (on an iPhone, its active energy too), where the step has none of its own.
- Which ready-made workouts and programmes you have copied to your account, and which version of each your copy is based on, so we can show how many people use each one and offer your copy a change when we publish one. Only the total is shown; users are not identified.
- Notes you choose to write on a session, an exercise or a set in it, and whether you marked a session as a lighter day. See the section on health and body data below - these can say something about your health, and are treated that way.
- Skills you are working through and the levels you record against them.
- Habits you set, and which days you ticked them off.
- Your training goal, its targets for calories, protein, fat, carbohydrate and sessions - worked out from your body weight and body fat - and the phase it belongs to.
- The reminders you set, their scheduled days and, if you specify it, what each reminder is for: a workout, a habit, a weigh-in or a check-in.
- Your schedule: each workout you plan, with its name, when it starts and how long it lasts, any notes, the workout it is for if you link one, how long before it starts you want to be reminded, if you do, and who planned it if your trainer did. For a plan that repeats, its repeat rule - how often, on which weekdays, when it stops and the time zone it is read in - and the times of it you deleted or moved on their own.
Your body
- Body weight and the daily entries it is recorded in, with the note you write on a day, if you write one.
- Check-ins: girth measurements, skinfold readings and the dates they were taken.
- Progress photos you choose to take, and the pose each was shot in. With each photo taken in the app's camera, how it was taken: which camera, the picture's size, how the phone was tilted, the camera's exposure settings, and where your body stood in the frame, as a set of points - so the next photo can be lined up with it. See the section on health and body data below - these are treated differently from everything else.
- On an iPhone: steps, sleep, and the workouts other apps recorded with their active energy, distance and heart rate, read from Apple Health, if you allow each data type. See the section on Apple Health below.
- On an Android phone: steps, sleep, and the exercise sessions other apps recorded with their distance and heart rate, read from Health Connect, if you allow each data type. See the section on Health Connect and Wear OS below.
- Of those, kept in your account: each night's sleep (time in bed, time asleep, time in each sleep stage and awake, and when the night's longest stretch began and ended), and the workouts other apps recorded (their kind, start and end, moving time, distance, active energy, average and peak heart rate, and the name of the app that recorded them).
- How you feel on a training day, if you answer: the day, your answer from Exhausted to Fully charged, on the two lowest answers what is off (sleep, soreness, stress, energy or other) if you say, and when you answered.
Your meals
- The meals you keep as recipes: the name, your own category for it, what kind of meal it is, servings, how long it takes, whether it works cold or is vegetarian, how to store it, a substitution, the ingredients with their amounts, and the steps. Its calories and macros if you give them, and whether they were typed by a person or estimated by the meal assistant. How much it fills you up and how much you like it, if you say.
- A picture of the meal, if you upload one or the meal assistant draws one, and whether it was drawn. Where the meal came from: written by you, taken from something your trainer sent, or saved from the meal assistant.
- Your food notes, if you write them: up to 500 characters on what you dislike, what you are allergic to and what your kitchen lacks. See the section on health and body data below - an allergy is health data.
- Your food diary, if you keep one: for each thing you log as eaten on a day, its name, the kind of meal, how many portions, the calories, protein, carbohydrate and fat for what you ate, whether those figures are an estimate, and which of your meals or our recipes it came from. An entry logged from a meal assistant estimate also notes which estimate, and which of its foods, it came from.
- Which of our ready-made recipes you have starred, so we can show which are liked most. Only the total is shown; users are not identified.
The meal assistant, if you turn it on
- Whether you have turned it on. Each chat with it - your messages, any text you pasted, its replies and the recipes it wrote - for one day after the last message; each meal you ask it to estimate, with your answers to its questions and the estimate, for one day; and a record of each call it made - what kind, which model, and the tokens or seconds it used - holding none of your words. If you rate an estimate, the stars and any words you add are kept with it. When an estimate is cleared, a copy of it without your account, for 90 days, and a test example made from the foods you kept from it. Off by default; see the section on the meal assistant below for what is sent and kept.
AI training reviews, if you turn them on
- The wording of each week's verdict (or, for a week read before 18 October 2026, the written reading and the marked facts it rests on), and which model and prompt version produced it. Off by default; see the section on AI training reviews below for what is sent to produce it.
Coaching, if you use it
- If you apply to a trainer: who you applied to, the note you sent, their answer and anything they wrote with it, whether you share your progress photos with them, when the coaching started and ended, who ended it, any note left when they did, and whether you share each ended period's history; whether your trainer has marked you private, so that your sessions hold the two of you alone, and whether the others confirmed into a session with you may see your name and picture. The trainer can keep private notes about their work with you.
- Which workouts and programmes in your account a trainer put there, and which sessions a trainer started for you.
- Workouts, programmes, guides and recipes a trainer sent you: a copy of each as it was when they sent it - a guide with its recipes, pictures and any PDF attached to it - who sent it, when, the note they wrote with it, which plans or meals in your account it became, and whether you cleared a guide from your list (or, for something sent earlier, whether you added or removed it).
- Sessions booked with your trainer: each time you asked for or they booked you in for, how long it lasts, whether it is pending, confirmed, declined or cancelled, the note each of you wrote, when it was answered, and which of you cancelled it. If it was booked or moved while your trainer named a single gym, the session keeps a copy of it - its name, city, and any address and map link - as where it takes place. If a session moves, where it was before it last moved; and while a client has asked to move a confirmed session, the new time they asked for and the note they sent with it. A workout started from half an hour before a confirmed session until the session and the rest after it are over is linked to that session (the nearest one, if two are in reach).
- Reviews you write of a trainer: the stars, any comment, when you wrote it and last changed it, and whether the trainer is showing the comment.
- Payments between you and your trainer, if they record them: the packages of sessions and the prices agreed, how each session booked with them is paid for, how many sessions of a package are used and how many are left, and each payment and refund with its amount, day, the way it was paid and a note. As a trainer, how you are paid - a Revolut username, a bank account (its IBAN, holder and any BIC), cash or another way, with any note you add - and your usual price for a session.
- If you switch on as a trainer: your headline, your bio, whether you are taking clients, how you coach (in person, online or both), the gyms you name with their city and any address and map link you add, the languages you coach in, the hours you take sessions in - how long a session lasts, the rest you usually keep between clients, how many clients one session may hold, your weekly windows and your time zone - which of your clients you marked private, the days whose hours you change or take off, with any note you write on a time off, and the same record of each application, client, booking, review and plan you sent from your side, including the rest you set after each booked session. The guides you write for your clients: the title, a summary, the blocks of advice and any recipes in them, and any PDF you attach.
Steps you reach in the app
- Which of a fixed list of steps have happened on your phone - such as creating an account, picking a plan or finishing your first workout - and whether each was already reported to Meta, kept on the phone so that none is reported twice. What is sent, and what never is, is set out in the section on measuring our own ads below.
- The install the account was made on: a random install identifier the app makes up, the kind of phone and the app version, and the ad campaign it came from where Apple, Google Play or Meta can say - set out in the same section, under which ad brought you.
Your first steps, and how the app is used
- Your answers to the app's first steps: how long you have been training, your experience, how many days a week you want to train and how long a session should be, what you train for, the part of the body you want to work on most, and, where you said you were not sure, that you said so. And when you finished the first steps.
- Unless you switch it off in the app's settings, a short, fixed list of moments in the iPhone and Android apps: each first-steps screen shown, answered or skipped, the app opened or sent to the background, Today seen, a programme opened, and a workout started, finished or left unfinished. Each comes with the screen it happened on, the step and the answer chosen or the way out taken, in at most 60 characters and never words you typed, the time on your phone, whether it is an iPhone or an Android phone, the app version and the app's language, and it is kept with your account. See where we rely on legitimate interest, below.
How you use the app, if you allow it
- Your answer to the app's analytics question, kept on the phone. If you said yes: which of a fixed list of things you did in the app, the identifier the analytics software makes up for that installation, the app version, the phone's system and language, a rough location, no finer than the region, worked out from the connection, and on Android the ad or link, if any, Google Play reports the app was installed from. Held by Google for us, not by our server; see the section on how the apps are used.
Notifications and calendars
- How you want each kind of message to reach you - by email, as a notification or both - for each topic you have changed. A topic you never changed stores nothing and uses the default.
- Each phone signed in to your account that can receive notifications: the address the app on that phone is issued to deliver them to - by Apple on an iPhone, by Google's Firebase Cloud Messaging on an Android phone - whether it is an iPhone or an Android phone, for an iPhone whether it is a development or an App Store build, the app version, whether the phone lets the app show notifications, as the phone last reported it, and when it last checked in. Not the phone's name or model.
- If you connect Google Calendar: the email address of the Google account you connected, the permission Google gave us to write to it (stored encrypted), the calendar we created there, the title start, alert and colour you chose, whether Google Calendar is still connected, when it was last brought up to date, and which event in it belongs to which of your plans.
Emails
- Your answer for each of the three kinds of optional email - news and offers, tips and progress, and feedback requests - and when you last gave it. And, once you turn it off, that you turned off the emails that help you start.
- A record of each time you turned one on or off: which kind, which way, how - a box at sign-up, the app's first steps, the app's settings, the link in one of those emails, your mail program's own unsubscribe button, our staff at your request, or reporting one as spam - and when. Where it was our staff, which member of staff.
- A random code that the links in those emails carry, so the page they open knows whose choices to show without asking you to sign in.
- For each survey we email you, if you get feedback requests: when it was sent, the score from 0 to 10 you chose, the comment you wrote, if any, and when you answered. And a random code that the survey's links carry, so the page they open knows which survey it is without asking you to sign in; we keep only a one-way scrambled form of it.
- If you are sent an email that helps you start, a random code its links carry in the same way, kept for 30 days in a one-way scrambled form, and when it was answered.
- For every email we send you, optional or not: what kind of email it was, the address it went to, when, and what Amazon's mail service reported about it afterwards - delivered, bounced, reported as spam, and when it was opened and which of its links was followed. Never the words of the email itself, and never a link that carries a code of yours, such as the one that resets a password.
Technical and security data
- A session token on your device, which is what keeps you signed in, and a record of the sessions issued to your account, with when each was last used, to within an hour. Each session also records the phone app's platform, version and build number, reported with requests, so we can diagnose problems and show relevant update notices.
- Server logs: the IP address a request came from, the time, and what was asked for. These exist to keep the service working and to notice abuse.
- Crash and error reports from the apps and this website, described in their own section below.
- Website counts: when you visit the website's main pages, which page was opened in which language, and which download buttons, other buttons, questions and depths of the page were reached, each added at once to a total for the day. No IP address, cookie or identifier is kept with them. The section on cookies lists exactly what is counted.
- Short link visits: when you follow one of our short links on
go.progressloop.eu, a record of that visit - when it happened, the linking site's domain, the kind of device, its system and browser, the country and city, and whether it was the first visit to that link from your kind of device and network, told by a scrambled code rather than your IP address. The section on cookies lists exactly what is kept.
If you leave, or tell us what got in the way
- If you answer why you are leaving or did not start - before deleting your account, from the links in an email that helps you start, or when you choose to stay and send feedback instead - the reason you picked, a comment of up to 2,000 characters and the name of another app of up to 100, if you wrote them, how many days old the account was, whether it had any workout, the app's platform and version, and the language. These are kept without your account id, so they are not part of your record, though those few facts could in rare cases point back to an account. See the section on feedback about the app.
- How many accounts were deleted each week, on each platform: a count, naming nobody.
If you answer the athlete survey on our website
- Your answers about how you train, under a random response number your browser makes up for that survey, with the page's language, the campaign tags of the link you arrived by, when you started and finished, and the country your connection came from. Kept without your name, IP address, a cookie or any identifier of your device, and linked to no account. See the section on the athlete survey.
- Your email address, only if you chose to talk to us for 15 minutes at the end, kept apart from your answers.
Not on this list: a workout photo you take or pick in the app to share. It never reaches us. The section on workout photos below says what happens to it.
Health and body data, and why it is treated differently
Body weight, girths, skinfolds, progress photos, the health and fitness data you let the app read from Apple Health or Health Connect, the heart rate a watch measures while you train, the notes you write on your workouts and your days, and marking a session as a lighter day all say something about your physical condition. Data protection law treats data concerning health as a special category, which needs a stronger basis than ordinary personal data does. ProgressLoop relies on your explicit consent for it, given by choosing to record it.
In practice that means every one of these is optional and separately given. You can use the app to plan and log training and never enter a weight, never take a measurement and never take a photo. Turning any of them off, or withdrawing consent, stops future processing and does not affect your account or anything else in it.
On an iPhone, Apple Health is where this goes the other way. When you train with the Apple Watch app, the watch records that session in Apple Health as a workout. That is what lets it keep running with your wrist down, and it is what gives it your heart rate and the energy you burn while the session lasts. Writing needs a permission of its own in iOS, asked for and withdrawn separately from the ones that let the app read. ProgressLoop keeps three figures from that workout: your average heart rate, your peak heart rate and the active energy you burned during the session. These are saved with the session in your account for you to review afterwards. They are health data, processed on the basis of the same explicit consent you give when you allow the watch to read your heart rate and active energy. If you withdraw that permission in the Health app, no new figures are saved. Individual heart-rate readings remain in Apple Health. The section on Apple Health below sets out exactly what is written, what is kept, and who else can read it.
A Wear OS watch works the same way, with less kept. While you train with the Wear OS app, the watch measures your heart rate, with the permission Wear OS asks you for, and when you finish it keeps two figures with the session in your account: your average and your peak heart rate. They are health data, processed on your explicit consent, given in that permission prompt; refusing or withdrawing it means no heart rate is measured or kept. The Android phone then records the session in Health Connect, with a permission of its own, as the section on Health Connect and Wear OS below describes.
So are your food notes, where they name an allergy. What you are allergic to says something about your health, so the food notes are handled on the same basis as the rest of your health and body data: they exist only if you write them, you can clear them at any time, and they are never shown to a trainer. They are sent anywhere only if you turn on the meal assistant, as described below.
Workout notes and lighter days are part of this too. While you log a workout you can write a note on the whole session, or on an exercise or set in it - how the day went, or what you trained around, such as a sore elbow - and you can mark the session as a lighter day, meaning you deliberately trained below plan because you were injured, ill or run down. A note may say nothing about your health at all, but because it can, every note is handled on the same basis as the rest of your health and body data, and so is the lighter-day marker. Both are kept with the session in your history. The same holds for the note you can write on a whole day, on the app's "Log the day" screen: it is kept with that day's entry and handled the same way.
- Both are only ever recorded by a person: a note exists only if you write one, and a session is a lighter day only if you switch it on - or, if you have a personal trainer and they log a session with you, if they do, as part of the coaching you agreed to by applying. The app never marks a lighter day on its own. Nothing in the app reads a note for what it means, with one exception you choose: if you turn on AI training reviews, the notes on a week's sessions and days are sent to OpenAI and read by its model, as described below.
- A lighter day does two things: nothing in that session pushes the load up, and its weights are not where the next session starts from. It hides and deletes nothing - the session stays in your history, your charts and your totals exactly as you lifted it.
- Neither is used for advertising. Both are part of an AI training review only if you turn those on, and never otherwise.
- You can clear a note or switch the marker off by editing the session, at any time, without touching the rest of it. Deleting the session or your account removes them too.
So is how you feel on a training day. On a day with a planned workout the app asks "How are you today?" and you may tap one of five answers, from Exhausted to Fully charged; on the two lowest you may also say what is off - sleep, soreness, stress, energy or other. It is kept with the day and the time you answered, one answer a day, replaced if you change it. How you feel can say something about your health, so it is handled on the same basis as the rest of your health and body data: it exists only if you tap an answer, tapping is never required to start a workout, and you can hide the question in Settings. It is shown back to you beside your sleep and your own usual answer. It never changes your workout, is never part of an AI training review and is never used for advertising. To have past answers erased without deleting your account, write to privacy@progressloop.eu.
Progress photos deserve their own sentence. They are stored in a private bucket that is not readable from the internet; the app is handed a short-lived signed address each time it needs to show you one, and that address expires. They are never used for anything but showing them back to you. They are shown to nobody else, with one exception you control: while you have a personal trainer and have turned on photo sharing for them, that trainer can see them too. Sharing is off until you turn it on, and turning it off hides them again straight away during active coaching. After coaching ends, photos from a shared past period are visible only if photo sharing was on when that period ended; turning off that period's history sharing hides them. They are never part of an AI training review.
The app's camera looks for your body while you frame a progress photo, and only on the phone. So that this week's photo lines up with last week's, the camera finds where you are standing in the picture and tells you to step or tilt the phone. That is worked out on the phone itself - on an iPhone by iOS, on an Android phone by Google's ML Kit running on the device - and no picture is sent anywhere to do it. What is kept with the photo is the result described above: how the phone was held and where your body stood in the frame, as points. Nothing reads a photo once it is taken. On an Android phone you can also turn on voice commands in that camera, so you can say "photo" instead of reaching for the screen; the microphone is then listened to by the phone's own speech recogniser, on the phone, for the few command words alone, and nothing you say is recorded or sent anywhere. A phone that cannot recognise speech on its own does not offer voice commands at all. The same camera has a second, separate use in the iPhone app - a photo of a finished workout to share - and that photo is never stored; the section on workout photos below describes it.
Three uses of body data need a consent of their own. The first is having a personal trainer. Once a trainer accepts your application, they can see your body weight, your measurements and check-ins, the steps and workouts that reach your daily entries from Apple Health or Health Connect, the heart rate kept with a session, the notes on your sessions and exercises and which sessions you marked as lighter days, and how you said you feel on training days while you share it with them, alongside the rest of your record. Applying is what agrees to that - the screen you apply on lists what they will see - and ending the coaching, which you can do at any time, stops access to your ongoing record. Past-period history remains readable until you turn its sharing off under Past trainers. See the section on personal trainers below for the limits and controls.
The second is the AI training reviews. If you turn them on, your average body weight and how it moved, and a summary of your sleep, are sent to OpenAI with the week's verdict, and so are the notes on that week's sessions and days (a long note shortened, and only a limited number sent) and which sessions were lighter days. Recording a weight, letting the app read your sleep, writing a note or marking a lighter day does not agree to that; only turning the reviews on does, and the screen that turns them on says so.
The third is the meal assistant. If you turn it on, each message in a chat with it (or each request, on an older version of the app) sends OpenAI your food notes - allergies included - and, from your active goal, your body weight. Writing food notes or setting a goal does not agree to that; only turning the assistant on does, and it is a separate switch from the training reviews'. Asking it to estimate a meal you describe sends neither.
Where the data comes from
- From you, directly, when you register, set the app up, and use it.
- From Apple or Google, if you choose to sign in with them: the identifier, address and name described above, and nothing else.
- From Apple Health on your device, for the data types listed above, and only after you grant each permission in iOS. Reading is only half of that relationship: the watch writes each session you finish into Apple Health, on a permission of its own, as the section on Apple Health below describes.
- From Health Connect on your Android phone, for the data types listed above, and only after you grant each permission in Health Connect. The phone also writes the sessions your Wear OS watch measured into Health Connect, on a permission of its own.
- From your watch, if you train with one: the heart rate it measures during a session.
- From your trainer, if you have one: the workouts, programmes, exercises and sessions they create or log in your account, the workouts, programmes, guides and recipes they send you, what they put on your schedule, the sessions they book you in for, and the notes they write to you.
- From other people, if you are a trainer: the name and note of each person who applies to you or asks you for a session, whether each client cleared a guide you sent them from their list (or, for something sent earlier, added or removed it), and the reviews your clients and former clients write.
- From OpenAI, if you use the meal assistant: the replies and recipes it writes, its questions about a meal you describe and the estimate of it, the text it hears in a recording, and the pictures it draws.
- From Open Food Facts, if you scan a packaged food's barcode: the product's name, brand, pack size and the figures on its label. It is a public database of food products, and nothing it returns is about you.
- From Apple, Google Play and Meta: which ad campaign, if any, an install of the app came from, as the section on measuring our own ads describes.
- From you, if you answer the athlete survey on our website; and, kept beside your answers, from the address of the link you arrived by (its campaign tags) and from the network that carries our websites (the country your connection came from).
- Automatically from your device and the network, for the technical and security data above.
Why we process it, and on what basis
| Purpose | Data | Legal basis |
|---|---|---|
| Creating your account and signing you in | Your email address if the account has one, your password hash if you set one, your name, session tokens, and the identifier Apple or Google gives us if you sign in with one | Performance of the contract between you and us |
| Running the app: your plans, sessions and history | Exercises, workouts, programmes, sessions, sets, skills, habits, goals | Performance of the contract |
| Setting the app up for you from your first steps, and suggesting plans that fit | Your answers to the first steps, the ones you were not sure of, and when you finished them | Performance of the contract |
| Keeping your meals and recipes | Each meal's recipe, numbers and where they came from, picture and where the meal came from; your food diary; the recipes you starred | Performance of the contract |
| Keeping your food notes | What you dislike, are allergic to and cannot cook with | Your explicit consent, given by writing them |
| Writing recipes for you in a chat, reading recipes out of text you paste, estimating a meal you describe, turning a recording into text and drawing a meal's picture, if you turn the meal assistant on | For a chat, what you typed, pasted or said, with the replies and recipes before it, and the month; your gender; from your active goal your body weight, goal type and estimated daily calories; your food notes. For an estimate, what you said you ate and your answers to its questions. For a picture, the recipe's name and main ingredients | Your explicit consent, given by turning the meal assistant on - the only basis on which food notes and body weight are sent |
| Checking how good the meal estimates are and improving them | A copy of each cleared estimate, without your account: what you said you ate, its questions and your answers, the foods and figures it came to, the day, the rating and words you gave it, and what you then did with each food in your diary. A test example, without your account, made from the foods you kept from it: the name the estimate gave the meal, never your own words | Your explicit consent, given by turning the meal assistant on |
| Looking up a packaged food by its barcode, so you can log it from its label | The barcode number, sent without anything about you | Performance of the contract |
| Your schedule: planning when you will train | Each planned workout's name, start, length and notes, the linked workout, and who planned it | Performance of the contract |
| Adding a planned workout to Apple Calendar or Google Calendar from the iPhone app, when you tap it | That plan's name, start and end, notes and linked workout name | Performance of the contract, at your request, carried out on your phone |
| Keeping your phone's calendar - iPhone Calendar, or a calendar on your Android phone - in step with your schedule, if you switch it on | Each plan's name, start and end, repeat rule, notes and linked workout name; for a trainer, each booked session with the client's name and both people's notes. Written on your phone, not by our servers | Performance of the contract, at your request |
| Keeping your Google Calendar in step with your schedule, if you connect it | The same as for your phone's calendar, plus your Google account's email address and the encrypted permission to write to it | Performance of the contract, at your request |
| Telling you about coaching, sessions and plans sent to you, and reminding you of a session the next day or of requests waiting for your answer, by notification or email as you chose | Your choice per topic; each registered phone's notification address, whether it is an iPhone or an Android phone, an iPhone's build type, and the app version; the message itself - the other person's name, their note, a plan's name or when a session starts, and for a trainer how many applications and session requests are waiting | Performance of the contract |
| Body weight, measurements, check-ins and progress photos | Health and body data | Your explicit consent, given by recording it |
| Notes on your workouts, exercises and days, and marking a session as a lighter day | Session, exercise, set and day notes, the lighter-day marker | Your explicit consent, given by writing the note or switching the marker on - or, for a session your trainer logs with you, by applying to them |
| How you feel on a training day, shown back to you beside your sleep | Your readiness answer, what is off on a low day, when you answered | Your explicit consent, given by tapping an answer |
| Reading the steps, sleep, heart rate and other apps' workouts you allow in Apple Health, and keeping your sleep, the workouts other apps recorded and a heart rate filled into a session in your account | Health data from HealthKit | Your explicit consent, given in the iOS permission prompt |
| Reading the steps, sleep, heart rate, distance and other apps' exercise sessions you allow in Health Connect, and filling your daily entries and sessions from them | Health data from Health Connect: each day's steps, the activities you linked to a kind of workout, a step goal's tick, your sleep, the workouts other apps recorded and a heart rate or cardio figures filled into a session reach your account | Your explicit consent, given in Health Connect's permission screen |
| Measuring your heart rate on a Wear OS watch while you train, keeping your average and peak with the session, and recording the session in Health Connect | Heart rate during the session (health data); in Health Connect, a strength training session with its name, start and end, which Health Connect keeps on your phone, not us | Your explicit consent, given in the Wear OS prompt to measure heart rate and in Health Connect's permission screen to write exercise |
| Recording the session you just trained in Apple Health, from the Apple Watch app | A strength training workout: its start and end, how long it lasted, the active energy and the heart rate the watch measured. It is kept by Apple Health on your device, not by us | Your explicit consent, given in the iOS permission prompt that asks to write to Apple Health |
| Showing you and your trainer, if you have one, your heart rate and active energy for sessions recorded with Apple Watch | Your average and peak heart rate and active energy for the session (health data) | Your explicit consent, given in the iOS permission prompt that lets the watch read your heart rate and energy |
| Reading a week of your training back to you, if you turn AI reviews on | The week's verdict and its numbers: level and goal type, lifts by name with their direction and estimated maxes, body weight change against the goal, sessions against plan, effort ratings, sets per muscle group, and a summary of sleep. And that week's sessions: which were lighter days, movements skipped, and the session, exercise and set notes. And the note on each of that week's days. Every note cut at 500 characters, and at most 40 of them in all | Your explicit consent, given by turning AI reviews on - the only basis on which notes, lighter days and sleep are sent |
| Listing you in the trainer directory, if you switch on as a trainer | Name, profile picture, headline, bio, whether you are taking clients, how many clients you have, how you coach, the gyms you name with their city, address and map link, the languages you coach in, and while you are away, the date you are away until | Performance of the contract, at your request |
| Applying to a trainer, answering, ending it, and the emails each step sends | Both people's names, the notes each writes, where the coaching stands | Performance of the contract, at your request |
| Publishing a trainer's session hours; asking for, booking, confirming, declining, moving and cancelling sessions, and asking for a new time; putting a confirmed one on the client's schedule; and the emails each step sends | The trainer's hours and time zone, the days they changed or took off, and the note on a time off; each booking's time, length, status, place, notes and who cancelled it; a new time asked for and its note, and the time before the last move; both people's names | Performance of the contract, at your request |
| A trainer sending a client a workout, programme, guide or recipe and adding it to the client's account, the client clearing a guide from their list, the trainer withdrawing what was sent, and the email that tells the client it arrived | A copy of what was sent - with the trainer's own exercises a plan uses, or a guide's recipes, pictures and PDF; both people's names; the trainer's note; when it was sent; the plans or meals it became in the client's account; whether a guide was cleared from their list (and, for something sent earlier, whether it was added, removed or not yet answered) | Performance of the contract, at your request |
| Showing reviews in the trainer directory, and each trainer's rating | Stars and comment, the reviewer's first name and last initial, whether the comment is shown; the trainer's average and number of reviews | Performance of the contract: at the reviewer's request, and as part of being listed as a trainer |
| Letting a trainer keep a record of the packages, sessions and payments between them and each client, and showing the client their own | Packages and prices, how each booked session is paid for, the sessions used and left, payments and refunds with their amount, day, method and note; the trainer's payment details, shown only to their own clients | Our legitimate interest in giving trainers a way to run their coaching |
| Showing your record to your trainer, and shared past-period history after coaching ends | Your training, including session and exercise notes and lighter days, schedule, goals, habits, skills, meals and food diary, settings, body weight, measurements, check-ins, steps, sleep and workouts from Apple Health or Health Connect, heart rate kept with a session, how you said you feel on training days while you share it, AI training reviews already produced; your name, email address, gender and profile picture. Former-client access is limited to the records and periods described under Personal trainers. | Your explicit consent, given by applying; past-period access remains on until you turn its history sharing off, as described under Personal trainers |
| Showing your progress photos to your trainer | Progress photos | Your explicit consent, given by turning photo sharing on |
| Measuring whether ProgressLoop's own ads on Facebook and Instagram bring people who go on to train, and steering them towards those people | That one of the listed steps happened on a phone, once per account, and whether it is an athlete or a trainer step; the technical details Meta's SDK attaches to any event; an iPhone's advertising identifier only if you allow tracking, and an Android phone's unless you have deleted it in the phone's ad settings | Our legitimate interest in knowing whether our advertising works. On an iPhone, your consent, given in Apple's tracking prompt, for linking it to the advertising identifier; on an Android phone, that same interest, within the ad settings you choose for the phone |
| Counting how many people each of our ad campaigns brought, and how far they got | A random install identifier, the kind of phone and the app version, the campaign, ad group and ad the install came from where Apple, Google Play or Meta provide them, and the account it was linked to when the account was made | Our legitimate interest in knowing whether our advertising works. Meta's campaign on an iPhone is read only after your consent in Apple's tracking prompt |
| Understanding how the apps are used - which screens and features people reach, and where they leave a sign-up, a plan or a workout unfinished - to improve them | Which of a fixed list of things happened in the app, with a few fixed labels; the app-instance ID; the app version, phone system and language; a rough location, no finer than the region, derived from the IP address; on Android, the ad or link the install came from, if any | Your consent, given in the app's own question, which is also the consent the law asks for before an app stores or reads on your phone anything it does not need in order to work; withdrawn in the app's settings |
| Sending the optional emails you asked for: news and offers, tips and progress, and feedback requests | Your email address, name and language, and which kinds you turned on. For a nudge, the days since you last trained or opened the app; for a first-steps tip, whether you have set a goal, picked a plan or finished a workout. For news and offers, also what one can be sent to only some subscribers by: your language and gender, how and when you signed up, your trainer profile, trainer and clients, your first-steps answers, when you last opened the app and finished a workout, whether you are running a programme, how many workouts (and how many on a watch), programmes, check-ins, weigh-ins, tracked days, meals, skill practice and sessions with a trainer you have recorded (the counts and dates, never what they hold), your phone's system, app version and notification setting, the ad campaign your install came from, which of our earlier emails you were sent, opened or clicked, your latest answer to how likely you are to recommend us, and labels our staff gave your account. For the survey, how long you have had your account and how many workouts you have finished, and when you were last asked. For a request to review a trainer, which trainer it is about and their name, how many confirmed sessions with them are over, whether they coach or coached you, and whether you have already reviewed them | Your consent, given separately for each kind by ticking its box at sign-up or turning it on in the app, and withdrawn whenever you turn it off |
| Being able to show when and how you agreed to those emails, and when you stopped them | Each time a kind was turned on or off, how and when, and for a change our staff made at your request, which member of staff | Our legal obligation to be able to show that you consented |
| Understanding what people think of ProgressLoop, from the surveys they answer | The score and any comment you gave, when you answered, and the account they belong to | Your consent: the survey goes only to people who turned feedback requests on, and answering it is up to you |
| Knowing whether our emails arrive, keeping addresses that bounce or complain off our list, and seeing which emails are read | Which email went to which address and when, and what Amazon's mail service reported about it: delivered, bounced, reported as spam, opened, and which link was followed | Our legitimate interest in mail that works and is not unwanted; for the optional emails, the consent you gave to receive them |
| Reminders you asked for, and a notification before a planned workout | Reminder settings and weekdays; the planned workout's name and start, and how long before it you chose to be reminded | Performance of the contract, at your request |
| Seeing where new people stop before they start training, to make the first steps and the first workout easier | The moments the apps record, as listed under what we process, with their screen, step, answer, time, platform, app version and language; whether each phone lets the app show notifications | Our legitimate interest in an app people manage to start using; you can switch it off in the app's settings |
| Helping an account that has never trained to start: emails that help you start, and one notification | Your email address, name and language; that the account holds no workout and has never finished one; when the app was last used on any of your devices; whether you turned these emails off, said no to any optional email, or were already sent one of them; to send some of them only to some of these accounts, the same facts as for news and offers, other than anything about workouts and programmes; for the notification, the phones that let the app show notifications | Our legitimate interest in helping people use the service they signed up for; every email carries a link that stops them |
| Understanding why people leave, or never start | The reason you picked, your comment and the other app you named, the account's age in days, whether it had a workout, platform, app version and language, kept without your account id; a weekly count of deleted accounts per platform | Our legitimate interest in improving the service; answering is up to you |
| Being able to show that you accepted the Terms of Use and this policy | When you ticked the box at registration | Our legitimate interest in knowing what each account agreed to |
| Keeping the service working, and noticing abuse | IP address, technical logs, session records, crash and error reports | Our legitimate interest in a service that works and is not abused |
| Improving the app from feedback you choose to send | Account, topic, rating, comment, platform, app version, language and date | Our legitimate interest in finding problems and improving the service |
| Counting how the website is used, to know which pages and campaigns bring people to the app | The page and its language, what happened on it, the store a download button led to, the campaign tags of the link, the linking site's domain and the kind of device, kept only as daily totals | Our legitimate interest in knowing whether the website works for the people it is written for |
| Counting the visits through our short links and QR codes, to know which poster, post or campaign brings people to us | A record per visit: when, the linking site's domain, the kind of device, its system and browser, the country and city, and whether it was a first visit, told by a scrambled code made from the device and network | Our legitimate interest in knowing whether what we print and post reaches anybody |
| Understanding how athletes train, from the anonymous survey on our website, so that we build the product around it | Your answers, the response number your browser made up, the page's language, the campaign tags of the link you arrived by, when you started and finished, and the country your connection came from | Our legitimate interest in understanding how athletes train; you give the answers voluntarily, and they name nobody |
| Writing to you to set up a short call, if you chose one at the end of the survey | Your email address, and the language you took the survey in | Your consent, given by leaving your address |
| Telling Meta that you finished the survey, if you came to it from one of our ads and said yes | That a survey was finished and, if you chose a call, that you asked to be contacted; when; the survey's address; the click id Meta added to the ad's link; the response number; your browser's user agent, read off the request and not stored | Your consent, given by answering yes in the survey, which you can withdraw only until you finish it |
| Keeping the product's statistics steady after an account is deleted | A copy of the account's workout numbers, plan structure, star ratings and survey scores, install campaign, app usage moments and email delivery, with everything personal taken out, under a bare account number | Our legitimate interest in figures that do not change each time somebody leaves |
| Answering you when you write in | Your message and the address you sent it from | Our legitimate interest in replying; legal obligation where one applies |
Where we rely on legitimate interest
Legitimate interest is used for the purposes below and for the optional app feedback described in its own section. The first is keeping the service running and secure. That covers server logs, the IP address a request arrived from, and the record of which sessions are signed in. Weighing it up: the interest is in a service that stays up and is not abused, which is also your interest in it; the data is technical rather than about your training or your body; logs are kept briefly and session records with the account; and it is what anyone would expect a service they signed into to record.
The second is recording when you accepted the Terms of Use and this policy. It is one date on your account, kept only as long as the account, and it is what lets either of us show what was agreed if that is ever in question.
The third is measuring ProgressLoop's own advertising. ProgressLoop is free and is found largely through ads on Facebook and Instagram; without knowing which of them bring people who go on to train, the money goes to the ones that bring installs nobody opens twice. Weighing it up: what is sent is limited to a short list of steps, each once, with no name, email address, account id or anything you recorded; on an iPhone it is never linked to your advertising identifier unless you allow it in Apple's prompt, and on an Android phone it goes with the advertising identifier only while the phone's own ad settings give the app one, which you can stop at any time; and what Meta reports back to us is counts, never people. The same holds for the campaign each install came from, which our own server records: it is linked to an account only so it can be counted per campaign, it is never shown against a person, and when the account is deleted only a count of it stays, under a bare account number. The section on measuring our own ads sets it out.
The fourth is the record of the emails we send: which went to which address, and whether each was delivered, bounced, reported as spam, opened, or had a link followed. Weighing it up: without it we could not tell an email that arrived from one that did not, or stop writing to an address that bounces or that asked us to stop; it holds no words of the emails and no link that carries a code of yours; it is seen only by our own staff; and when the account is deleted the address goes from it, leaving only a count under a bare account number. An opened email is counted because the email shows a tiny image fetched from Amazon's mail service, and a followed link because it passes through that service on its way. A mail program that does not load images counts no open, and some, Apple Mail among them, load the image for every email whether you read it or not, so an open is only ever an estimate.
The fifth is counting how this website is used. Without it we cannot tell whether a page or a campaign link brings anybody to the app, or which questions people actually open. Weighing it up: nothing is stored on your device; our server keeps only daily totals, with no IP address, cookie or identifier, so nothing in them is about you; the site that linked to a page is named only by its domain; and Do Not Track or Global Privacy Control stops it in your browser, before anything is sent.
Our short links are part of the same purpose, and the one place it keeps more than a total: a short link on a poster, a post or a QR code is how we learn whether that poster or post reached anybody, and whether those people had been there before. Weighing it up: the record of a visit holds no IP address, cookie or description of your browser, only the coarse words worked out from it; whether a visit is a first one is told by a scrambled code made from the kind of device, its system and the network rather than the address; robots and a repeat within two seconds are not recorded at all; and only the people who manage our links can read the records. A short link only ever leads to a page you can also reach by its ordinary address, which counts nothing per visit, and you can object by writing to privacy@progressloop.eu; because a record names nobody, we cannot pick out your earlier visits, but we will tell you what we can do.
The sixth is the moments the apps record about how they are used. Many people make an account and never train, and without knowing which screen they stop on we can only guess what to fix. Weighing it up: the list of moments is short and fixed; none of them carries your measurements, your health or what you lifted, and the only answers that go with them are the ones you gave in the first steps - your gender, for instance, or what you train for - which the account already holds; it goes to our own server and to nobody else, no advertiser or analytics company included; our staff read it only as counts, never as one person's trail; it is kept for 13 months, without the answers that went with it once the account is deleted; and a switch in the app's settings stops it, from that moment, without changing anything else in the app.
The seventh is helping an account that has never trained to start: an email now and then, and at most one notification. Weighing it up: it goes only to accounts that hold no workout and have never finished one, which is the account somebody made and could not get going with; it carries nothing from your record but your name; every email has a link that stops them at once, and so does your mail program's unsubscribe button; the notification goes only to a phone that lets the app show notifications, once per account, ever. If you once said no to an optional email, you can still be sent the first of these emails, once in the life of the account, and never the ones that follow it.
The eighth is the answers to why people leave or never start. Weighing it up: answering is up to you, and leaving the question unanswered changes nothing, deleting an account included; the answer is kept without your account id, with only a few facts about the account, so it is not part of your record, and those facts are kept coarse so that an answer is hard to trace back; and it is read only by our own staff, as reasons and counts.
The ninth is keeping a copy, with everything personal taken out, of some of what an account held after the account is deleted, as deleting your account sets out: the numbers of your workouts, the shape of your plans, your star ratings and survey scores without their words, and the counts above. Without it, every figure about how the app is used - how many people finish a workout, which plans are taken up, which campaigns bring people who train - would change each time somebody left. Weighing it up: your name, email address, sign-in details, photos, body data and everything you wrote are deleted, and what stays is kept only under a bare account number; it is read only as counts; and it is never used to contact you or to rebuild an account.
The tenth is the athlete survey on our website. To build an app that fits how people actually train, we need to hear it from them rather than guess. Weighing it up: answering is up to you, every answer you write in your own words is optional, and a no to the first question, whether you are 16 or older, ends the survey with nothing saved; the answers are kept without a name, IP address, cookie or device identifier, and with no account, under a random number your browser makes up and forgets when the tab is closed; the country is kept only as a two-letter code; and the answers are never given to an advertiser. Telling Meta that you finished is not part of this interest: it happens only if you say yes, as the section on the survey sets out.
The eleventh is letting a trainer keep a record of the packages, sessions and payments between them and each client. A trainer who coaches for money needs to know what was agreed, what was paid and how many sessions are left, and so does the client. Weighing it up: no money passes through ProgressLoop and the record is the trainer's own, which the client can see; nobody else in the app sees it, and the trainer's payment details reach only their own clients, and only while something is owed; no email or notification carries more than an amount and a name; our staff read it without changing it and never see the payment details; and when a client deletes their account, the trainer keeps only amounts and dates, with the client's name and every note about them removed, so that their own accounts still add up.
You can object to processing based on legitimate interest - see your rights below. No body or health data is processed on this basis, and nothing about what you train beyond whether and when a workout was started, finished or left unfinished, never what was in it - except the numbers kept once an account is deleted, described in the ninth, and what you choose to tell us in the athlete survey, which names nobody, described in the tenth.
Apple Health
Apple Health is read in one direction and written in the other, and each direction is a separate permission you give in iOS and can take back there. What is read is listed first; what the watch writes is listed after it.
What ProgressLoop reads
On an iPhone, if you allow it, ProgressLoop reads only what a screen of the app uses:
- Steps - to fill in each day's step count, show it against your step target and tick a habit whose goal is a number of steps.
- Sleep - to show you each night's sleep and its stages, and so a trainer you apply to can see it.
- Workouts other apps recorded, with the active energy, distance and heart rate recorded during them - so such a workout can count towards an activity you track, fill in the cardio step of yours it matches, and be seen by a trainer you apply to. The sessions ProgressLoop recorded itself are left out.
- Heart rate, if you allow it - to fill in the average and peak of a recent session of yours that has none, from the readings Apple Health holds for the time it ran.
Permission is granted in iOS per data type and can be withdrawn at any time in the Health app, which stops future reading immediately. Earlier versions of the app also read exercise minutes, active energy and walking and running distance as daily totals, flights climbed, resting heart rate, heart-rate variability and VO₂ max; those readings never left the phone, and the current version neither reads nor shows them.
Steps and summaries derived from workouts can fill your account's daily entries. Your sleep and the workouts other apps recorded are also kept in your account, on our servers in the European Union: each night's time in bed, time asleep, time in each stage and awake, and when its longest stretch began and ended; and for each workout another app recorded, its kind, start and end, moving time, distance, active energy, average and peak heart rate, and the app's name. The sessions ProgressLoop recorded itself are left out. They are kept so you see them on any device and so a trainer you apply to can see them; deleting a night or a workout in the Health app removes it from your account at the next sync. A heart rate filled into a session is kept with the session. The app also keeps a copy of each day's steps and sleep on this device, shown on its Health data screen, which is removed from the device when you sign out, delete the account or uninstall the app. What ProgressLoop reads from HealthKit is never used for advertising or marketing, never sold and never disclosed to a third party for its own purposes. The ad measurement described below learns only that you connected Apple Health, once, and never any reading from it.
Two exceptions exist, and each only if you choose it. An AI training review includes a summary of your sleep - your average time asleep over two weeks and how many nights that covers - which may have come from Apple Health. It is sent to OpenAI solely to word that week's verdict, as described below, and no other Apple Health reading is sent. And if you have a personal trainer, the steps and workout summaries in your daily entries, your sleep and the workouts other apps recorded are part of the record they can see, solely so they can coach you.
What the Apple Watch app writes
When you train with the watch, ProgressLoop records that session in Apple Health as one traditional strength training workout. Holding a workout open is what lets a watch app keep running with your wrist down, and it is what makes your heart rate and the energy you are burning available to the watch while you train.
The workout carries what Apple Health keeps for any workout: when it started and ended, how long it lasted, the active energy burned, and the heart-rate samples the watch collected while it ran. Nothing else goes into it. No exercise names, no loads, no reps, no notes and no body data - the training itself is recorded in your ProgressLoop account, not in Apple Health.
ProgressLoop keeps only three figures from this Apple Health workout. When you finish, the watch sends our server your average heart rate, peak heart rate and active energy for the session. These are saved with the session in your account. You can review them afterwards, and your personal trainer, if you have one, can see them alongside your other session details. They are not sent for AI training reviews. Individual heart-rate readings remain in Apple Health and are never sent to us. A session logged on your phone alone has no energy figure, and has a heart rate only if the app filled one in from Apple Health, as described above. Nothing about that workout is used for advertising, sold, or given to anyone for their own purposes.
The watch asks for permission to read four types of data: heart rate, active energy, step count and your Activity summary. It also asks for permission to save workouts. Apart from the three figures above, the data it reads is displayed only on the watch and is not sent elsewhere. Step count is used only for the watch's steps ring.
Writing is asked for in iOS separately from reading and can be withdrawn at any time in the Health app, which stops future writing immediately. Once a workout is in Apple Health it is Apple Health's: it is yours to keep or delete in the Health app, and - this is Apple's model rather than ours - any other app you have allowed to read your workouts can read that one, exactly as it can read a workout written by any other app on your device. It is the one way something you did in ProgressLoop can reach an app we have nothing to do with, and the permission that decides it is given to that app by you, in iOS.
Health Connect and Wear OS
On an Android phone, Health Connect is where Android keeps health and fitness data, and ProgressLoop uses it the way the iPhone app uses Apple Health: it reads from it, if you allow it, and it writes into it only the sessions your Wear OS watch measured. Reading each data type and writing exercise are separate permissions, which you give in Health Connect when you choose to connect it - from Settings or from Today, never on its own - and can take back there at any time, which stops future reading or writing immediately.
What ProgressLoop reads, and why
- Steps - to fill in each day's step count, show it against your step target and tick a habit whose goal is a number of steps.
- Exercise sessions - so that a workout another app recorded, such as a run or a ride, can count towards an activity you track, fill in the cardio step of yours it matches, and be seen by you and by a trainer you apply to. The sessions ProgressLoop wrote itself are left out.
- Distance - only over the time of another app's workout, so its run or ride can fill in the distance of the cardio step it matches. Never as a day's total.
- Heart rate - the average and peak during another app's workout, and during a finished session of yours that has none from your watch, so they can be kept with it.
- Sleep - to show you each night's sleep and its stages, and so a trainer you apply to can see it.
- Your history. When you first connect, the app reads up to 90 days back, with the permission Health Connect asks for older data; without it, Health Connect hands over the last 30 days. After that it reads only while the app is open, and never in the background.
Nothing else is read. Earlier versions of the app also read active calories burned, floors climbed, resting heart rate and VO₂ max, and distance as a daily total; those readings never left the phone, and the current version neither reads nor shows them. The app's Health data screen lists each permission it asks for and what it fills.
What leaves your phone
These things read from Health Connect reach your ProgressLoop account, on our servers in the European Union: in your daily entries, each day's step count; for each activity you linked to a kind of workout, whether you did it, or its minutes or count; and the tick on a step-goal habit. Beside them, each night's sleep (time in bed, time asleep, time in each stage and awake, and when its longest stretch began and ended) and the exercise sessions other apps recorded (their kind, start and end, moving time, distance, average and peak heart rate, and the app's name; active energy only for a session an earlier version of the app read). Deleting a night or a session in Health Connect removes it from your account at the next sync. A heart rate filled into a session of yours, and the distance and heart rate filled into a cardio step, are kept with that session. The app also keeps a copy of each day's steps, exercise minutes and sleep on your phone, in its own storage, for up to a year; it is shown only there, and it is deleted from the phone when you sign out, delete your account or uninstall the app. It is never included in a backup or a transfer to a new phone.
They then go where the rest of your record goes and nowhere else: to a personal trainer you apply to, while they coach you, solely so they can coach you; and, if you turn on AI training reviews, a summary of your sleep - your average time asleep over two weeks and how many nights that covers - goes to OpenAI solely to word that week's verdict. No other Health Connect reading is sent to anyone.
What the phone writes
When you finish a session on your Wear OS watch, your phone records it in Health Connect as one strength training exercise session: when it started and ended, and its name - the name of the workout you trained. Nothing else goes into it: no heart rate, no calories, no exercises, loads, reps or notes. A session logged on the phone alone is not written. Once it is there it belongs to Health Connect on your phone: it is yours to keep or delete there, deleting your ProgressLoop account does not remove it, and - this is Android's model rather than ours - any other app you have allowed to read your exercise can read it, as it can any other app's.
What Health Connect data is never used for
Data from Health Connect is never used for advertising or marketing, never sold, never used to decide anything about you such as credit or insurance, and never passed to anyone for their own purposes. One fact about it does reach an advertising company, and it is not a reading: the first time you connect Health Connect, the app tells Meta that the step "Apple Health or Health Connect was connected" happened, as the section on measuring our own ads describes - without a single reading from it. ProgressLoop's use of data received from Health Connect follows Google Play's policy for health permissions.
The Wear OS watch
The Wear OS app has no sign-in of its own: your Android phone hands it your session over the connection between them, and it then talks to our server itself, over the watch's own connection. While you train it keeps the workout running in the foreground, which is what lets it carry on with your wrist down, and reads your heart rate from the watch's sensors, with the permission Wear OS asks for when you start your first workout. It also asks to recognise your physical activity, which is how it counts your steps for its steps ring.
Your live heart rate is shown on the watch. When you finish, the watch sends our server two figures: your average and your peak heart rate for the session, which are kept with the session in your account and seen by your trainer, if you have one, with the rest of it. They are not sent for AI training reviews. The watch measures no calories, and no single heart-rate reading leaves it. The steps it counts draw its ring and are never sent anywhere; your phone's reading from Health Connect is what fills your day. A session or a change to your day that the watch has not yet delivered waits on the watch until our server has it.
AI training reviews
The app reads each week of your training back to you. What the week says is decided by fixed rules on our own server - whether your lifts went up, held or fell, how your body weight moved against your goal, whether you trained as often as planned - and that verdict, with its numbers, is shown to you whatever you choose. If you turn on AI training reviews, a language model run by OpenAI also puts that verdict into one or two sentences of your own, and may mention what you wrote in the week's notes. The model decides nothing: a wording is kept only if every number in it is one the verdict already holds. Producing it means sending the verdict and the week's notes to OpenAI's servers in the United States.
It is off until you turn it on, from Settings, on a screen that says what is sent before you agree; the full list is the one below. While it is off, nothing about your account is sent anywhere. While it is on, the app asks for a reading of the week that has just finished by itself, once and without a tap, if that week does not have one yet - so a week can be sent to OpenAI without your asking for its reading. You can turn it off again on the same screen at any time, which stops any new reading being asked for. Readings already produced stay in your account unless you ask for them to be erased: write to privacy@progressloop.eu and they will be, without your having to delete the account.
What is sent
- The week's verdict as the rules worded it, in your language: what kind of week it was, how sure the rules are, its title, its next step and its sentence.
- The numbers behind it: how many weeks it looked back over, your training level and the type of your goal; for the lifts you do most, each by name, whether it went up, held or fell, by how much, and the estimated maximum it moved between, with how many sessions it was trained in; your average body weight recently and before, its weekly rate of change, and where that sits in the range your goal sets, if you set one; how many sessions you finished against how many were planned; how many of your exercises you rated for effort and how many of those were easy; and working sets per muscle group, and how they changed.
- Your sleep, in summary, if it reaches your account from Apple Health or Health Connect: your average time asleep over the week and the week before, how many nights that covers, and whether it was short. Not the nights themselves, their times or their stages, and nothing at all unless each of the two weeks has at least four nights.
- Each session you finished in the week being read: its date, whether you marked it as a lighter day, and which movements in it you skipped. Nothing from sessions you did not finish, and no lighter-day marker from earlier weeks.
- The notes written on those sessions: on the session, on an exercise in it and on a set in it, with the movement and set number each belongs to. That includes any your trainer wrote. Only notes from the week being read are sent, each cut off after 500 characters, and at most 40 from any one week, taken in the order the sessions were trained. Shortening a note is not removing what is in it: whatever you wrote in the part that is sent goes to OpenAI as you wrote it.
- The note on each day of that week, from the app's "Log the day" screen, with the date it belongs to and nothing else from that day's entry. A day's note is held to the same limits: cut off after 500 characters, and counted in the same 40 as the notes on sessions, exercises and sets. A day with no note sends nothing.
What is not sent
- Your name, email address, account id, gender or anything else from your account that identifies you, and no id of any session or exercise.
- Your photos, of any kind.
- Notes anywhere else: on a check-in, a meal, a programme, a template or an exercise in the library, on a session you did not finish, and on any day or session outside the week being read.
- Your waist, skinfold or other check-in readings, your steps, your target weight, how you said you feel on training days, the rest of your daily entries, the load and reps of individual sets, or any Apple Health or Health Connect reading other than the sleep summary above. Readings made before 18 October 2026 worked differently, as described below.
A note is your own words, and it goes as you wrote it. Nothing reads a note before it is sent, and apart from the cut at 500 characters nothing is taken out of it. So whatever is in a note on a session you finished, or on a day of that week, goes to OpenAI with the week - how you slept, an injury, an illness, a medication, or a name, a place or anything else that could identify you or somebody else. Like the lighter-day marker, a note is health data here, and it is sent only because you turned the reviews on: that consent is the whole of the basis for it. If you would rather something not reach OpenAI, leave it out of your notes, clear the note before the week is read, or turn the reviews off. The model is told to use a note only to explain what happened in the week, and never to diagnose anything or to give health, diet, injury or supplement advice.
The request carries no account id, name or email address. Apart from what your notes say, the only words of yours in it are the names of any exercises you created. All of it is sent as data for the model to read and never as instructions to it.
Under OpenAI's API terms, what is sent is not used to train or improve its models. OpenAI may keep a copy for up to 30 days to monitor for abuse of its service, and deletes it after that. ProgressLoop stores the verdict, the wording that comes back, the model that produced it and a count of tokens spent; it does not store the prompt.
Until 18 October 2026 the reviews worked differently: the model read the week itself and wrote findings about it, from a description that also included how your waist and skinfold readings moved, your average daily steps against your target, your target weight and expected weekly change, the facts our server had marked as worth reading, and the name of your programme, but not your sleep. Readings made then stay in your account as they were.
Each reading costs money, so a reading of any one week can be generated at most once every two minutes and ten times in all. Those ten count every attempt at that week, including the first reading and any retry after a failure.
If you have a personal trainer, they can read the readings already produced of your weeks. They cannot ask for one on your behalf, turn the feature on for you, or cause anything to be sent to OpenAI: that consent is only yours to give. A note they write on one of your sessions, or a lighter day they mark, is sent with the week like your own - but only because you turned the reviews on.
The meal assistant
The app can write recipes for you in a chat: you say what you want to eat, and you can ask it to change a recipe or for more like one. It can also turn a food guide or other text you paste in into recipes you can keep. It can estimate the calories and macros of a meal you describe - "two eggs and a slice of rye bread" - asking you at most one round of short questions first when something that matters is unclear. You can speak instead of typing, and it can draw a picture of a meal you saved. All of that is done by models run by OpenAI, and using it means sending what is listed below to OpenAI's servers in the United States.
It is off until you turn it on, in the app, on a screen that says what is sent before you agree. It is a switch of its own: turning on the AI training reviews does not turn it on, and turning it on does not turn the reviews on. While it is off, nothing is sent for it. You can turn it off again at any time, which stops anything new being sent; the meals you already saved from it stay yours. If you turned it on before it could chat or estimate a meal, the screen you agreed on did not describe those; this section does, and the assistant can be turned off at any time.
What a chat sends
- Your messages, as you typed them or as they were heard - what you want to eat, and whatever you say about it, such as the ingredients you have, the kind of meal or how many servings - and any text you pasted in to be turned into recipes. With each new message the chat so far goes again, the assistant's replies and recipes included, so that it can follow the conversation.
- The current month, so the recipes use what is in season.
- Your gender, if you set one.
- From your active goal, if you have one: your body weight, your goal type (losing, gaining or keeping weight) and an estimate of the calories you use in a day. The estimate is sent as a guide, not as a target to build a menu to.
- Your food notes, as you wrote them: what you dislike, what you are allergic to and what your kitchen lacks, up to 500 characters. An allergy is health data, and it is sent only because you turned the assistant on.
- On an older version of the app, which sends a single request instead of a chat: what you asked for, the ingredients you said you have, the kind of meal, how many servings and how many ideas you want - or the text you pasted in - with the same month, gender, goal figures and food notes as above.
What an estimate sends
- What you said you ate, as you typed it or as it was heard, and your answers to its questions, if it asks any.
- Not your food notes, not your goal and not your body weight, which an estimate does not need.
What else is sent
- A recording, if you speak instead of typing - a message in a chat, or a meal you want estimated. It is sent to OpenAI to be turned into text, which you can read and correct before anything is asked for. ProgressLoop does not store the recording, and neither it nor what you said is written into our logs.
- For a picture: the recipe's name and its main ingredients, and nothing about you. A picture is drawn when you ask for one, and also when you save a recipe the assistant wrote, if you have not used up the day's pictures - so saving one can send its name and ingredients without a separate tap.
- The language you use the app in, so the replies, recipes and questions come back in it.
What is not sent
- Your name, email address, account id, or anything else from your account that identifies you.
- Any health condition, measurement, photo, workout, note or anything else from your record beyond what is listed above for each use. It is not asked for, and the assistant does not write diets for a medical condition: it says a dietitian should plan those.
What you type is your own words, and it goes as you wrote it. Nothing reads your messages, your pasted text, what you say you ate, your answers or your food notes before they are sent, so anything in them - a name, a place, a condition - goes to OpenAI too. If you would rather something not reach it, leave it out.
What is kept
- Each chat - your messages, any text you pasted, the assistant's replies and the recipes it wrote - for one day after its last message, so you can go back to it and save the recipes you want. After that the chat is cleared. On an older version of the app, which sends a single request instead of a chat, the request and the recipes that came back are kept for one day in the same way.
- Each estimate - what you described, its questions, your answers and the figures it came to - for one day, after which the words and figures are cleared from it. What you log from it becomes an ordinary entry in your food diary, marked as an estimate and noting which estimate and which of its foods it came from, and is kept like any other. Once you have logged from an estimate, the app may ask you once to rate it from one to five stars, with a few words if you like; you can dismiss the question, and a rating is kept with the estimate.
- A copy of each estimate, for 90 days, without your account. When an estimate is cleared after its day, a copy of it is kept so that we can check how good the estimates are and improve them: what you said you ate, the questions it asked and your answers, the name it gave the meal, the foods and figures that came back, whether it came to figures or declined and why, any error it met, the language, and which version of the assistant made it. It also holds the rating and words you gave the estimate, if you rated it, and what you had done with each of its foods in your diary by the time it was cleared: kept it as it was, changed its amount or figures, swapped it for another food, deleted it, or never logged it - not the diary itself. Counted together across everybody, these tell us which foods the assistant keeps getting wrong, so it stops using them by itself. The copy carries no account id and no time, only the day it was made, so it is not filed under your account and cannot be found by it. That does not make it anonymous in every case: what you typed is kept as you wrote it, so if it names somebody, the copy does too, and on a day when few people asked for an estimate, the day alone could point to whose it was. For that reason it is read only by our staff who have access to account data, and it is sent to nobody. After 90 days it is deleted. Turning the assistant off stops new copies, since no new estimates are made, but does not remove the ones already kept. If you delete your account before an estimate's day is up, no copy of it is kept; a copy already made stays until its 90 days are up, because it cannot be found by your account, and for the same reason we cannot pick out your copies to delete them sooner.
- A test example, for 90 days, without your account. For each food in an estimate that the assistant matched to one of our food records, or that you picked from its choices, and that you then kept, the same clearing keeps a test example: the name the estimate gave the meal (never what you said or typed), the food's name, brand and weight, and the record it matched. We run the assistant's matching over these examples to check a change to it before it goes live; that sends nothing to anybody. Like the copy, it carries no account id, is read only by our staff, is deleted after 90 days, and cannot be found by your account to delete it sooner.
- A record of each call the assistant made - what kind of call, which model, the tokens or seconds it used, and when - so that it can be limited to a number each day. It holds none of your words, recipes, recordings or pictures.
- A recipe you save becomes one of your meals, like one you wrote yourself, marked as coming from the assistant, with any calories and macros marked as its estimate until you change them. A picture it draws is stored with that meal in the same private store as progress photos, and is only ever shown through short-lived signed addresses.
Under OpenAI's API terms, what is sent is not used to train or improve its models. OpenAI may keep a copy for up to 30 days to monitor for abuse of its service, and deletes it after that. Each call costs money, so there is a limit on how many recipes, estimates, pictures and recordings each account can ask for in a day.
The recipes are suggestions, with estimated nutrition, and an estimate of a meal is an estimate; neither is dietary or medical advice. If you have a personal trainer, they cannot use the assistant on your behalf or turn it on for you, and they never see your food notes, your chats or your estimates; they see the meals you keep, as with the rest of your record.
Scanning a packaged food
You can log a packaged food by scanning its barcode. Our server looks the number up in Open Food Facts, a public database of food products that people around the world add to, and the app shows the product's name, brand, pack size and the figures on its label, for you to log.
- Only the barcode number is sent, and it is sent by our server, not by your phone: Open Food Facts gets no name, email address, account id, address of your device or anything else about you. Nothing about you is in what it sends back.
- It needs no consent of its own and has nothing to do with the meal assistant: no AI is involved, and it works with the assistant off.
- Our server keeps a copy of the product data it got back, so the same product is not looked up again; that copy is about the product and not about anyone who scanned it. What you log becomes an ordinary entry in your food diary.
Open Food Facts's data is published under the Open Database Licence, which is why the app credits Open Food Facts wherever its figures are shown. It is a source of data for us, not a service that handles yours, so it is not among the recipients listed below.
Measuring our own ads
ProgressLoop is free, and people mostly find it through our ads on Facebook and Instagram. To know whether those ads bring people who actually train, rather than people who install the app and never open it again, the iPhone and Android apps use Meta's software development kit to tell Meta (Meta Platforms Ireland Limited) when certain steps happen. The watch apps do not, and neither does this website, which loads no Meta pixel or any other code of Meta's: the one thing it can lead us to tell Meta is that you finished the athlete survey, from our server and only after you say yes, as described below. There are no ads inside ProgressLoop, and none of this is sold.
What is sent
That one of these steps happened on your phone:
- The app was installed and opened.
- An account was created.
- A plan was picked.
- A first, a second and a fifth workout were finished.
- Two workouts were finished within the first week.
- Apple Health or Health Connect was connected.
- If you coach: a trainer profile was created; working hours were set; a first client was approved; a first plan was sent to a client; a first session was booked.
- If you are coached: an application was sent to a trainer; a session was asked for with a trainer.
Each step is sent at most once per account on each phone, at the moment it happens, and the only detail attached to it by us is whether it is an athlete's step or a trainer's. Three of them are also sent under the name Meta itself gives such a step, with its own label: creating an account as a registration by email address, a first workout as a tutorial completed, and a fifth as level 5 reached. Installing and opening the app is reported by the SDK itself, from the first time you open it, before you sign in. The SDK adds the technical details it attaches to any event it sends: the app and its version, the phone's model and system version, its language and time zone settings, the IP address the event arrived from, and an identifier the SDK makes up for that installation of the app. On an Android phone it also reads the install referrer Google Play keeps for the app, which says which ad or link, if any, the install came from.
What is not sent
- Your name, email address, account id, or anything else from your account that identifies you.
- What you train: no workouts, exercises, sets, loads, reps, notes or lighter days - only that a first, second or fifth workout was finished.
- Your body: no weight, measurements, check-ins or photos, of any kind.
- Anything read from Apple Health or Health Connect. Meta learns that you connected one, and never a single reading.
- Anything from a watch: the watch apps send Meta nothing.
- Anything about the people you coach or who coach you - not who they are, and not what was said or planned between you.
- Anything about a workout photo. Sharing one to Instagram is not one of the steps, and no photo or figure from it goes with them. The section on workout photos below says what sharing does give Meta.
On an iPhone: Apple's tracking prompt
Once you have created an account on an iPhone, the app shows Apple's own prompt asking whether it may track you across apps and websites owned by other companies. Your answer decides what Meta may link the steps to, and not whether they are sent:
- If you allow it, Meta can link the steps to your phone's advertising identifier, which is how it tells which ad, if any, you came from and shows our ads to people like the ones who went on to train.
- If you ask the app not to track, or have not answered yet - which is the case for installing, opening and creating the account - the steps are still sent, without that identifier, and Meta reports them to us only in aggregate, through Apple's privacy-preserving ad attribution (SKAdNetwork) and its own Aggregated Event Measurement. Neither can be traced back to you.
You can change your answer at any time in iOS Settings, Privacy & Security, Tracking, and it applies from the next step onwards. Turning off "Allow Apps to Request to Track" there answers no for every app at once.
On an Android phone: your phone's ad settings
Android has no prompt like Apple's, and the Android app shows none of its own in its place. The steps are sent with your phone's advertising identifier, so that Meta can tell which ad, if any, you came from and show our ads to people like the ones who went on to train - for as long as your phone's ad settings give the app that identifier. Those settings are yours, and they apply to every app at once:
- In Android's Settings, under Privacy and then Ads (on some phones, under Google and then Ads), you can delete your advertising ID. From then on no app, ProgressLoop included, is given one, and the steps are still sent, without it.
- You can instead reset it, which replaces it with a new one that nothing already sent can be linked to.
Either applies from the next step onwards.
Which ad brought you
Separately from Meta, each app tells our own server that it has been installed. It does so under a random install identifier the app makes up the first time it is opened and keeps for as long as it is installed - not your phone's advertising identifier or anything else that identifies the phone - with the kind of phone and the app version, and, where the phone can tell, the ad campaign that led to the install:
- On an iPhone, from Apple. The app asks iOS for Apple's attribution token and our server exchanges it with Apple for the Apple Ads campaign, ad group and ad behind the install, if there was one. Apple gives this to every app without the tracking prompt, because it says only whether an Apple Ads ad led to the install, so it is read whatever you answered.
- On an iPhone, from Meta - only if you allowed tracking in Apple's prompt. Meta then hands the app the link of the Facebook or Instagram ad you installed from, and the app passes on the campaign it names. If you did not allow it, nothing of Meta's is read, and where the install came from stays unknown.
- On an Android phone, from Google Play. The install referrer Play keeps for the app says whether the install came from a Google Ads click, a Meta ad or the store itself. A Meta campaign arrives in it encrypted, and is opened with a key Meta gives us for the purpose. Where Meta also hands the app the link of the ad you installed from, the campaign that link names is passed on too; Android asks no question first, as with the steps above.
Our server keeps only what that evidence says - the ad network, and the campaign, ad group and ad by their names and numbers - and never the token, link or referrer itself. When you create an account, the install is linked to it, once. That is what lets us count, per campaign, how many of the people it brought went on to reach each of the steps above. We read it only as those counts: nobody's account is shown with where it came from, and neither the campaign nor the account it is linked to is sent to Meta, Apple, Google or anyone else. When the account is deleted, the install stays only as a count under a bare account number: it is given a new random identifier, so the one your phone holds no longer finds it.
From the athlete survey on our website
If you arrive at the survey on our website from one of our ads, and answer yes when it asks whether we may tell Meta that you finished, our server tells Meta so through Meta's Conversions API - that a survey was finished, and, if you chose a call, that you asked to be contacted - with the time, the survey's address, the click id Meta added to the ad's link, the survey's random response number and your browser's description of itself (its user agent). Never your answers, your email address, your country or your IP address. Without that yes, or without having come from a Meta ad, Meta is told nothing. The section on the athlete survey sets it out.
What we see, and what Meta does with it
What reaches us from Meta is numbers - how many people a campaign brought, and how many of them reached each step - never a named person.
For collecting and sending these steps, and the finished survey, ProgressLoop and Meta Platforms Ireland Limited are jointly responsible, under the terms Meta sets for its business tools; Meta is responsible on its own for what it does with them afterwards, which includes using them to deliver and measure ads and is described in Meta's privacy policy. Questions about either half can come to us, and we will pass on what is for Meta.
How the apps are used, if you allow it
The iPhone and Android apps can tell us how the app itself is used - which screens people open, which features they find, and where signing up, choosing a plan or a workout is started and not finished - so that we can see what is hard to find or easy to give up on, and fix it. They do this with Google Analytics for Firebase, a service Google (Google Ireland Limited) runs for us. It is off until you say yes, and it is a choice of its own. The watch apps do not use it.
Only if you say yes
- The app asks you in a question of its own, with a yes and a no side by side: on the sign-in screen, and on Today for an account that has not answered on that phone. Until you answer yes, the analytics software sends nothing, and keeps nothing to send later: what you did in the app before saying yes is never reported.
- Your answer is separate from everything else you agree to or allow: the Terms of Use, the optional emails, AI training reviews, the meal assistant, Apple Health or Health Connect, and Apple's tracking prompt or your Android ad settings, which decide what Meta may do with the steps described under measuring our own ads. Saying no to analytics changes nothing else in the app.
- Your answer is kept on the phone, for your account. An answer given on the sign-in screen becomes the answer of the account you then sign in to or create, if that account has none on the phone yet; it is never carried over to another account, or past signing out.
- You can change your answer whenever you like, in the app under Settings, Your data. Turning it off stops the reporting from that moment, throws away anything the app was still holding to send, and replaces the app-instance ID described below, so nothing sent after you turn it on again is joined to what came before. Signing out does the same. Neither takes back what was already sent - see how long it is kept, below.
What is sent
That one of a fixed list of things happened in the app, in these areas:
- Moving around the app: which tab was opened - Today, Train, Progress, Meals, Clients or Trainer - and when Settings, the sign-in and sign-up screens or, for a trainer, a client's workspace were opened.
- Signing in and signing up: that it was started, and with an email address, Apple or Google; that it succeeded, created a new account, was cancelled, or failed, and which of a few kinds of failure it was.
- Plans: that a ready-made or trainer-sent workout or programme was opened and copied to your account, that you created or changed one of your own, and that a programme was made active.
- A workout: that a start was asked for and from which screen, how you answered a question that stood in the way (another workout open, a skill you cannot do today, or someone else logging it), that it started fresh, resumed or was taken over, timed or quick, and that it was paused, finished, discarded or could not be finished.
- Coaching: that an application was sent or answered, a trainer profile or working hours were saved, a plan was sent to a client or a sent plan was taken or removed, and what was done to a booking - requested, confirmed, declined, cancelled, moved or asked to move.
- Calendar sync: that syncing to the phone's calendar or to Google Calendar was started, connected, cancelled or turned off, and whether its events were then removed or kept, or that it failed and which of a few kinds of failure it was - access refused, no calendar to write to, refused by Google, the network, our server or something else.
- Notifications and emails: whether you allowed or refused notifications when the phone's own question was actually shown, and where it was asked - in Settings, while setting a reminder or for the rest timer; which channel - email, notification or both - you chose for each of the ten kinds of coaching, session and activity message, or that you switched off one of the four that can be (what a client did, or what your trainer changed), but never what the message was about; and that you turned one of the three kinds of optional email on or off, and whether on the Today card or in Settings.
- Feedback questions: that the app asked what you thought after a workout or of voice commands, and whether you sent an answer, closed the question or asked not to be asked again - and the same for the feedback form in Settings - but never the stars or the words.
Each comes with at most a few labels, each from a fixed list of its own, and never with a word or a figure you typed or recorded. The parts of the app that hold your body, your health and your food send nothing at all - not even the name of a screen inside them, because a name can say something on its own; the Progress and Meals tabs are counted only as tabs that were opened. Not measured: your meals, food diary and recipes, the meal assistant and AI training reviews, habits and the day's log, check-ins, measurements, weigh-ins and progress photos, your goal and its targets, Apple Health or Health Connect, reminders, reviews of trainers, the app's request to rate it in the App Store, and the feedback questions about the weekly review, an AI training review, the meal assistant and progress photos - and, for now, sharing a workout photo.
The analytics software also records by itself that analytics was switched on for the first time under its current app-instance ID; that a visit to the app began, and how long the app was on screen; that the app was updated; and on an Android phone, that the phone's system was updated; that the app's data was cleared, or the app was removed; that a notification arrived, was opened or was dismissed, for a notification marked for analytics, which ours are not. On an Android phone, the record of analytics first being switched on also carries which ad or link, if any, Google Play reports the app was installed from. With everything it sends, it attaches an identifier it makes up for that installation of the app (the app-instance ID), the app's version, the phone's system version and language, and a rough location, no finer than the region, that Google works out from the IP address the data arrived from. For a phone in the European Union, Google says it drops that IP address before logging the data.
What is never sent
- Anything that identifies you: your name, email address or account id, the install identifier our own server knows, Meta's identifier, or your phone's advertising identifier.
- Anything you wrote or recorded: no names you gave workouts or plans, notes, comments, messages, search text or answers, and nothing about what you lifted - no exercises, loads, reps or sets.
- Your body and your health: no weight, measurements, photos, calories, macros or heart rate, nothing read from Apple Health or Health Connect, and not whether you connected either of them.
- No pictures, recordings, or anything sent to or returned by the AI features, and nobody you coach or are coached by.
- Nothing about your calendars or reminders: not which calendar you chose, its colour, its alerts or what events are called, and nothing about a reminder or what it is about.
- No addresses: not the links in our emails or the codes they carry. Those pages measure nothing, and the website's own count, described under cookies, is not on them.
Not anonymous, and not used for ads
This data is pseudonymous, not anonymous: the app-instance ID ties together what one installation of the app did, for as long as it is kept, even though nothing in it names you and nothing we hold links it to your account. We read it in Google's console as counts and funnels - how many installations started a step and how many finished it.
Google processes it on our behalf, under its terms for Google Analytics and its data processing terms, and not for its own purposes: Google's settings for sharing the data with its other products are off. Every advertising use is off as well - the app tells the software that advertising storage, advertising use of data and ad personalisation are all refused, which Google records with the data as not for personalised ads, and we have no Google Signals, no link to Google Ads and no audiences. None of it goes to Meta, and none of the steps reported to Meta goes to Google.
How long it is kept, and what turning it off does
Google keeps what is tied to an app-instance ID for 2 months, then deletes it in its monthly clean-up; totals already counted into reports, which hold nobody, stay. Turning analytics off does not delete what was already sent, and neither does deleting your account or removing the app, because none of it is linked to your account: it goes when that period runs out. Because we cannot tell from your account which installation is yours, we usually cannot find this data for an access or erasure request; if you can give us something that identifies it, write to privacy@progressloop.eu and we will do what we can with Google.
Not the same as notifications
On an Android phone, notifications arrive through Google's Firebase Cloud Messaging, which is part of the same Firebase family but a separate service. It works the same whether you allow analytics or not: saying no to analytics does not stop notifications, and while analytics is off, nothing about a notification reaches it.
Workout photos
On iPhone and Android, you can put a finished workout's figures over a photo you take or choose. The card can show the workout's title and date, start time, duration, volume, sets, exercises, muscle groups, top sets and improvements against your history. Heart rate and active energy appear only when recorded. You can add a line of your own. Nothing is uploaded to ProgressLoop or saved to your account.
The app asks for camera access to take a photo. The system photo picker gives it only the picture you choose. Saving to Photos on iPhone asks for add-only access; on Android, saving to the gallery needs no photo-library permission. You can change camera and photo permissions in your phone's settings.
You choose whether to save the card, send it through the phone's share menu or open it as an Instagram story. The receiving app handles it under its own terms. Deleting your ProgressLoop account does not delete copies you saved or shared.
For Instagram, the photo and a separate sticker with the figures are handed to its app, along with ProgressLoop's app identifier, which identifies our app, not your account. On iPhone, this uses the clipboard with a five-minute expiry. On Android, Instagram gets read access to temporary files. Android also uses temporary files for the share menu; these can remain in the app's cache until replaced or cleared.
Instagram is operated by Meta under its privacy policy. It receives the picture and figures you chose to share, including any health figures on the card. Our server sends it nothing for this, and sharing a card is not an advertising milestone we report.
Your schedule, and your calendar
You can plan when you will train: a name of your choosing, a start time and a length, notes if you want them, and one of your workouts if you link one. A plan is stored in your account like the rest of your record.
A plan can repeat - every day, week or month, or every few of them, and on chosen weekdays when it repeats by the week - and stop on a date, after a number of times, or never. We store the plan once with its rule, including the time zone it is read in, rather than a copy of every time. When you delete one time of it, we record that time as not happening; when you move one, we record it the same way and store the moved time as a plan of its own, linked back to the series. Deleting the series deletes the times moved out of it too.
If you have a personal trainer, they can see your schedule and plan it with you - add workouts to it, and change or delete what is on it - and a plan they made says it was them. A session your trainer confirms is written onto your schedule too. That one belongs to the booking: it moves when the session is moved, stays until the session is cancelled, and is changed through the booking rather than by editing the plan. A booked session never repeats.
A booked session can also say where it takes place. When a session is booked or moved while the trainer names a single gym on their profile, that gym's name, city, and any address and map link they added are copied onto it, and the copy stays with the session if the gym is later removed or another is added. Both of you can see it with the session, the emails and notifications about the session may name it as we add it to them, and a calendar either of you keeps in step can show it as the event's location: Google Calendar sync writes it into the trainer's events.
Your schedule in a calendar
Nothing goes to any calendar unless you turn it on or send it there. There are three ways, each separate: keeping your phone's calendar in step, keeping a Google Calendar in step, and, in the iPhone app, adding one plan at a time.
iPhone Calendar sync is a switch under Settings, Calendar sync. When you turn it on, the app writes your plans - and, if you coach, the sessions booked with you - into a calendar called ProgressLoop that it creates in your phone's calendar account, or into another calendar you pick, and moves or removes them there when they change. To do that iOS makes it ask for full access to your calendars: iOS offers no narrower permission that lets an app find and update the events it wrote. With that access the app lists your calendars' names so you can pick one, and reads events only in the calendar it writes to, to recognise its own. It does not read the events in your other calendars, and nothing about your calendars is sent to our servers; the settings for it stay on your phone. Where the events go after that depends on the calendar account they are in, such as iCloud, and on that account's terms. You can withdraw the permission in iOS Settings at any time.
Phone calendar sync on Android is the same switch in the Android app, and asks Android for permission to read and write your calendars. By default it creates a calendar called ProgressLoop that lives on the phone alone and is synced to no account; you can pick another calendar instead, such as one in your Google account, and the events then go wherever that account keeps them, on its terms. With that permission the app lists your calendars - their names, the accounts they belong to and their colours - so you can pick one, and reads events only in the calendar it writes to, to recognise its own. It never reads or changes an event it did not write, nothing about your calendars is sent to our servers, and its settings stay on your phone. You can withdraw the permission in Android's settings at any time.
Google Calendar sync is the switch beside it, in either app. Turning it on opens Google's own sign-in, where you are asked to let ProgressLoop see your Google account's email address and manage only the calendars ProgressLoop itself creates. That permission cannot see or change any other calendar or any event in that account. Our server keeps it, encrypted, creates a calendar called ProgressLoop in your Google account, and from then on writes your plans (and, if you coach, the sessions booked with you) into it within seconds of a change, and once a night. The only thing it reads back is the list of events in that ProgressLoop calendar, by their identifiers alone, so it can notice one of its own that was deleted or split there and write it again. It never reads an event's title, time or notes, and never reads another calendar.
The colour you pick for these events in the app is written onto each of them, as one of Google Calendar's own event colours, so it needs no further permission. Until 27 September 2026 the same screen also asked for a second, optional permission, used only to set the ProgressLoop calendar's colour. We no longer ask for it or use it. If you gave it before then, you can remove it in your Google account's settings for third-party access; turning Google Calendar sync off and on again usually removes it too.
ProgressLoop's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Each synced event carries the plan's name (with any title start you chose), its start and end, how it repeats, the linked workout's name, the plan's notes and the alert you chose. A session booked with you as a trainer is named after the client and carries the note the client wrote and the one you wrote, and in Google Calendar the session's place where it has one. Your time off and the days you change are never written into a calendar.
Turning either sync off asks whether to remove the events it wrote or keep them. Kept events are an ordinary copy from then on, belonging to that calendar, and stop being updated. Turning Google Calendar off also withdraws the permission Google gave us, whichever you choose. Signing out of the app leaves the events on your phone where they are.
Adding one plan at a time, in the iPhone app, needs no access at all. What you add is a copy, and from then on it belongs to that calendar: changing or deleting the plan in ProgressLoop does not change it, and the app keeps no record of it.
- Add to Apple Calendar hands the event - the plan's name, its start and end, your notes, and the name of the linked workout - to your phone's own Calendar, which shows it to you before anything is saved. It does not pass through ProgressLoop's servers. Where it goes after that depends on the calendar account you save it into, such as iCloud, and on that account's terms.
- Add to Google Calendar opens Google Calendar with the event filled in. Opening it passes the plan's name, its start and end and its notes to Google, whether or not you then save it, and from that moment Google's own terms and privacy policy apply to them. Google receives them as a service you chose to open, not as a provider of ours, and ProgressLoop sends Google nothing itself.
Personal trainers
Any ProgressLoop account can switch on as a trainer and be listed in a directory that every signed-in user can browse, and any account can apply to one trainer at a time. A trainer is another ProgressLoop user: an independent person who does not work for ProgressLoop or act on its behalf, and whom ProgressLoop has not vetted.
If you apply to a trainer
- Before they answer, they see your name and the note you wrote - not your email address and nothing from your record.
- Once they accept, and for as long as the coaching lasts, they can see everything you record in the app: your workouts, programmes and every session with its sets (and the notes you wrote on it, its exercises and its sets, whether you marked it as a lighter day, and the heart rate and energy kept with it), your schedule, the exercises you created, your skills, habits, goals and meals and your food diary, settings such as your units and step target, your daily entries - including body weight and the steps and workouts that come from Apple Health or Health Connect - your sleep and the workouts other apps recorded, your check-in measurements and skinfolds, and any AI training reviews already produced. They also see your name, email address, gender and profile picture.
- They can put workouts, programmes and exercises into your account, change or delete the workouts, programmes and sessions already in it - including ones you made yourself - make a programme your active one, start and log a session with you, including its notes and whether it was a lighter day, and plan your schedule: add workouts to it, and change or delete what is on it. What they create is recorded as assigned, logged or planned by them.
- Your progress photos are not part of that. Your trainer sees them only while you have photo sharing turned on, which is off until you turn it on; turning it off hides them again straight away.
- How you feel on a training day, if you answer, is shared with your trainer while the coaching lasts: your answer, what is off on a low day, and when you answered, shown beside your sleep. It is on unless you turn it off in your coaching settings, and turning it off hides every answer from them straight away. On an answer of Exhausted or Tired your trainer is notified, at most once a day, with your name and that answer. Any other answer appears only in your trainer's notifications inside ProgressLoop, at most once a day, saying that you said how you feel and never the answer itself. A trainer cannot answer for you or make answering compulsory.
- When you log your body weight, your trainer's notifications inside ProgressLoop show that you did, at most once a day, without the weight itself, which they see in your record as described above.
If a trainer invites you
- A trainer can invite somebody they already coach by entering that person's first name and, if they choose, their last name, gender, email address and a note. ProgressLoop sends that person nothing: the trainer shares the invite's link or code with them directly.
- Opening the invite shows who sent it and what the trainer entered. The email address is only filled in for you if you sign up from the invite, and you can change it; it is never used to write to you and is never applied to an account.
- Accepting the invite in the app makes you that trainer's client at once, with no application, and they then see and do what is described above. You can end the coaching at any time.
- The invite is kept until it is accepted or expires after 30 days, and is deleted 30 days after that. The trainer can delete it sooner, and deleting either account deletes it.
Plans, guides and recipes your trainer sends you
- Besides putting plans into your account, a trainer can send you one of their own workouts or programmes, a guide they wrote - advice on training, food or anything else they coach, sometimes with their own recipes or a PDF - or a single recipe, with a note if they like. What you receive is a copy as it was when they sent it, pictures and PDF included: changing or deleting their own afterwards changes nothing you hold. It is stored with who sent it, when, and the note.
- A workout or programme your trainer sends is added to your account straight away. You are not asked to accept it first: it becomes an ordinary plan of yours, marked as assigned by your trainer, together with any exercises of the trainer's own that it uses. Your trainer decides how a programme is laid out on your calendar and can make it your active programme in the same step, which replaces the programme you were running. From then on the copy is yours: you can change or delete it like any other plan, and your trainer can change it as they can any plan in your account.
- A recipe your trainer sends, on its own or in a guide, is added to your meals the same way, as an ordinary meal of yours marked as coming from your trainer. A guide stays in your list for you to read until you clear it from there; your trainer is not notified, though their record of what they sent may show that you cleared it. Your trainer prescribes nothing by a guide or a recipe - the calorie targets you follow are still the ones on your goal.
- Your trainer keeps a record of what they sent you, and can take a plan or a recipe off it; that never touches the copy in your account. Withdrawing a guide removes it from your list too, but not the recipes already in your meals.
- A plan or recipe sent while you were still asked to accept what your trainer sent, and never accepted, is no longer offered to you; it remains only in your trainer's record of what they sent.
- Ending the coaching does not delete anything already sent, or the copies in your account.
What a trainer never gets
- Your reminders, your password, how and on which devices you sign in, how you chose to be notified, or any calendar you connected.
- The copy of your Apple Health or Health Connect readings kept on your phone.
- The ability to ask for an AI training review or to turn the feature on for you.
- The ability to change your food diary or your private food notes, including allergies and preferences. The diary is read-only for the trainer; the private food notes are not shown.
After coaching ends
Either of you can end coaching at any time. This stops the trainer from changing your account or reading your ongoing record. They can still read dated records from the period when they coached you while that period's history remains shared: training sessions, daily entries, check-ins, food diary, skill logs, goals and progress summaries. Records outside a shared coaching period are not included. Imported sleep and other apps' workouts, and how you said you feel on training days, are not available through former-client access.
History sharing stays on until you turn it off. On iPhone, open Settings, Coaching, Personal trainer, Past trainers to change it for each ended period. Turning it off stops further access to that period's records on the next request without deleting your records. Photos are included only for a shared period whose photo sharing was on when coaching ended. This cannot remove a copy the trainer already made outside the app.
The trainer's private notes about their work with you are kept separately and remain available to them when you stop sharing history. The record of sessions booked with them - times, status and notes - also stays visible to both of you, as described under retention.
Sessions with your trainer
- A trainer who takes sessions publishes the hours they take them in: how long a session lasts, the rest they usually keep between clients, how many clients one session may hold, their weekly windows and their time zone. The clients they are coaching can see those hours and which times in them are still free. A client never sees who has asked for or booked any other time, except as described below for a session they share. Each booked session also records the rest the trainer keeps after it, which starts as their usual rest and which they can change for that session alone; that is the trainer's note about their own diary, and the client does not see it.
- A trainer can also change the hours of a single day, or take days off. Those are kept with the trainer's account. Clients see that such a day is changed or a day off, and only the free times left in it, and while the trainer is away, "Away until" with the date their time off ends, on the trainer's public profile and on their own trainer's screen. A note the trainer writes on a time off is theirs alone, and no client sees it.
- While a trainer coaches you, you can ask for one of those free times, with a note if you like. Your trainer sees your name, the time you asked for and your note, and confirms or declines, with a note of their own if they like. Your trainer can also book you in directly.
- A trainer can let several clients share one session, up to the number they set. Where a time already holds clients and still has a place, you see how many hold it, never who. Once your trainer has confirmed your place in such a session, you see the first name, the initial of the last name and the profile picture of the others whose places in it are confirmed, and they see yours, unless you switch that off in your trainer settings: you are then still counted, but neither named nor shown. A trainer can also mark a client private, when approving them or at any time after; that client's sessions hold the trainer and them alone, and nobody joins them until the trainer switches it off. Changing either never cancels or moves a session.
- A confirmed session is written onto your schedule, with any note your trainer wrote when confirming it as its notes. Either of you can cancel a session that is pending or confirmed, with a note, and the record keeps which of you cancelled.
- A session can be moved before it starts. A client can move a request the trainer has not answered yet, or ask to move a confirmed session to another free time, with a note; the confirmed session stays where it is until the trainer answers, and the client can withdraw the ask. A trainer can move a session, which confirms it if it was still a request, or accept the client's ask by moving it there, or decline the ask and keep the time, each with a note. The booking records where the session was before it last moved, and keeps an ask only until it is answered, withdrawn or the session is cancelled.
- Ending the coaching cancels every session still pending or confirmed between you and drops any ask to move one.
- A trainer sees every session booked with them: which client booked which time, where each stands, and the notes on it.
- A trainer can keep their own calendar in step with their sessions. If they turn on phone calendar or Google Calendar sync, each session you have with them is written into that calendar with your name, the note you wrote and the note they wrote (and, in Google Calendar, the session's place where it has one), and it is held there under that calendar provider's terms. It stays there for as long as they keep it, including after the session is over.
If you are a trainer
- Your name, profile picture, headline, bio, whether you are taking clients and how many you have, how you coach (in person, online or both), the gyms you name with their city and any address and map link you add, and the languages you coach in are shown to every signed-in user who browses the directory, together with your average star rating, how many reviews you have, and the review comments you have not hidden - see the section on reviews below. Hiding your profile takes it out of the directory, and the clients you already have stay with you.
- The hours you take sessions in, and your time zone, are shown to the clients you are coaching, together with which times are still free.
- While you have time off, "Away until" and the date it ends are shown on your profile in the directory and to the clients you are coaching. A day you take off or change shows them that it is a day off or changed, and the free times left in it; the note on a time off stays yours.
- A session booked or moved with you while you name a single gym keeps a copy of that gym as its place, which the client sees with the session.
- A workout or programme you send a client is copied into their account at once, with your note and your name, as a plan you assigned, together with any exercises you created that it uses. That copy is theirs: taking the plan off your record of what you sent does not take it back.
- Your guides are private to you until you send one. Sending a guide or a recipe copies it to that client, with its pictures, any PDF, your note and your name, and adds each recipe in it to their meals; those meals are theirs, and withdrawing does not take them back.
- What you see of a client is shown to you so that you can coach that client, and for nothing else. If you take any of it out of the app - a screenshot, a figure written down elsewhere - that copy is yours to answer for, as the person who made it, under the data protection law that applies to you.
Payments between you and your trainer
- A trainer can keep, for each client, the packages of sessions and the prices you agreed, how each of your sessions with them is paid for (a session from a package, a single price, free, or a late cancellation they charge), how many sessions of a package are used and how many are left, any sessions they add or take off by hand with the reason they give, and the payments you made and the refunds they gave: the amount, the day, the way you paid (Revolut, a bank transfer, cash or other) and a note. Only a session booked with the trainer counts; a workout you log on your own never does.
- You can tell your trainer you have paid; it counts only once they confirm it.
- You and your trainer see it, and no other user does. Prices, packages and payments are never shown in the directory or on a trainer's profile, and an applicant, another user or another trainer sees none of them. A trainer's payment details - their Revolut username, bank account (IBAN) or how they take cash - are shown only to their own clients, and only while that client owes them something or has a package waiting to be accepted. No email or notification carries them; one about money says only the amount and the trainer's or client's name.
- Our staff who have access to account data can read these records, without changing them, to answer questions about them and look into problems. They never see a trainer's payment details: nothing we use shows the Revolut username, the bank account or the note about cash.
- ProgressLoop never processes or holds a payment. You pay your trainer directly, by transfer or in cash, outside the app; we take no commission and are not a party to what you agree. What is kept here is your trainer's own record, which they keep on our legitimate interest in giving trainers a way to run their coaching, and yours to see.
- It is kept while you have your account and the trainer theirs, also after the coaching ends, so the trainer can still see what was paid. If you delete your account, the trainer keeps the amounts and dates for their own records, with your name and every note about you removed; if the trainer deletes theirs, the whole record goes.
Notes and emails
Applying, answering and ending can each carry a note of up to 2,000 characters. It is stored with the coaching record, shown to the other person, and included in the email that tells them. Asking for, confirming, declining, moving and cancelling a session, and asking for or declining a new time, can each carry a note too, stored with the booking, shown to the other person and included in the email that tells them, along with when the session starts - and, when it has moved, when it was before. Withdrawing an ask to move a session tells the trainer nothing. A trainer sending a plan can add a note too, stored with the plan, shown to the client and included in the email that tells them it arrived; that one runs to 1,000 characters rather than 2,000. A note on a guide or a recipe runs to 2,000, and goes the same way. Every one of those emails names you by your name and never gives away your email address. Withdrawing an application before it has been answered tells the trainer nothing, and a client clearing a sent guide, or a trainer withdrawing anything sent, emails nobody.
Feedback about the app
Sending feedback is optional. We keep the topic, your rating from 1 to 5 and any comment (up to 2,000 characters), linked to your account, with the platform, app version, language and date. Our staff read these answers to find problems and improve the app. They are not published or sent to an AI provider. Please leave health details out of comments.
We rely on legitimate interest in improving the service: you choose what to send, access is limited to our staff, and you can object or ask us to delete your answer. Answers are otherwise kept while the account exists; when it is deleted, the topic and rating stay for our statistics without the comment, under a bare account number that no longer leads to your name, address or anything else about you. The phone and watch keep a local record of prompts and your choices so they do not keep asking. Muting prompts does not delete answers already sent. Email feedback requests have separate preferences.
An App Store or Google Play review is separate, handled by the store under its own rules. Its prompt is not based on the rating you gave us.
Why you are leaving, or did not start
Before you delete your account, the app asks what made you leave, and you can answer, skip the question, or stay and send it as feedback instead. An email that helps you start also lists a few reasons, each a link to a page on this website that shows the one you clicked, lets you add a comment and the name of another app you use instead, and records nothing until you press Send. Only the first answer to that email counts.
We keep the reason you picked, your comment (up to 2,000 characters) and the other app's name (up to 100), if you wrote them, with how many days old the account was, whether it had any workout, the app's platform and version, and the language - and no account id. Once stored, an answer is not kept with your account, so it is not part of your export and stays after the account is deleted. Those few facts could in rare cases still point back to an account, so we treat the answer as personal data: if you want yours erased, write to us with roughly when you answered and what you wrote, and we will find and delete it. Please leave your name, address and health details out of the comment. The code the email's links carry is kept, scrambled and with your account, for 30 days so the page knows which email it is, and goes sooner if the account is deleted. Our staff read the answers as reasons and counts, on our legitimate interest in improving the service.
We also count how many accounts are deleted each week, on each platform. That count names nobody.
The athlete survey on our website
On this website, at progressloop.eu/survey, we ask people who train how they train, so that we build ProgressLoop around how training actually goes. Answering is up to you, needs no account and is anonymous: nothing in it asks who you are, and nothing links it to a ProgressLoop account.
What it asks
It starts by asking whether you are 16 or older. If you answer no, the survey ends there and nothing is saved. After that it asks about how you train, in the past and in particular:
- when you last trained and, if you have stopped, why; what you did in that session; and how long you have trained regularly;
- how you decided what to do, how you recorded it, and the hardest part of training lately;
- whether you stopped using a fitness app, and why;
- what you did the last time your progress stalled, whether it helped, and what it cost you;
- whether you wrote down what you ate, where, or why you stopped;
- whether you asked an AI chatbot about training or food, what you asked, and whether you followed what it said;
- what you paid for to help your training in the last 12 months, and roughly how much a month for apps and for a trainer;
- what you wear on your wrist, what phone you use, and what got you training;
- your age group, from 16-24 to 55 and over, and your gender, which you can answer with "rather not say";
- and anything else we should have asked.
Every question you answer in your own words is optional. Please leave your name, how to reach you and anything about your health out of what you write: the survey does not need them.
How your answers are kept
When you start, your browser makes up a random response number for that survey and keeps it in the session storage of that tab, which the browser clears when the tab is closed, so that reloading the page carries on where you were. From the question about your age on, your answers are saved to our own server after each screen, so a survey you leave half way through still counts. Nothing links the response number to an app account, and no name, IP address, cookie or identifier of your device is stored with your answers.
With the answers, our server keeps the language of the page; the campaign tags the link you arrived by carried (utm_source, utm_medium, utm_campaign, utm_content and utm_term), as the first ones it saw; when you started and when you finished; and the country your connection came from, as a two-letter code that the network carrying our websites works out from your connection. The country is never asked, and the IP address it comes from is never stored.
The answers name nobody, and we keep them for our research into how people train. They are never given to Meta or any other advertiser. Because they name nobody, we cannot find yours from your name or email address; if you want them deleted, write to privacy@progressloop.eu with roughly when you answered and what you wrote, and we will do what we can to find and delete them. We rely on our legitimate interest in understanding how athletes train, so that what we build fits it: you give the answers voluntarily, and every answer in your own words is optional. The answers are deleted 24 months after they were last saved.
If you want to talk to us
At the end, the survey asks whether you would talk to us for 15 minutes, download the app, or neither, and then offers a link to share it. Only if you choose "I'll talk for 15 minutes" are you asked for an email address, and we use it for one thing: to write to you to set up a short video or phone call, in the language you took the survey in. It is stored apart from your answers, on your consent, given by leaving it, and is deleted after 12 months, or sooner whenever you ask us at privacy@progressloop.eu. The download buttons lead through our short links, go.progressloop.eu/survey-ios and go.progressloop.eu/survey-android, which keep the record of a visit described under cookies.
Telling Meta that you finished, if you say yes
This website loads no Meta pixel and no other advertiser's code, on the survey or anywhere else. But when you arrive from one of our ads on Facebook or Instagram, the address carries a click id that Meta adds to it (fbclid), and the survey then asks: "Can we tell Meta that you finished? Only that, never your answers. It helps the ad reach people like you." Nothing is chosen for you, and no is as easy to answer as yes.
- If you answer yes, our server - not your browser - tells Meta (Meta Platforms Ireland Limited) through its Conversions API that a survey was finished and, if you chose a call, that you asked to be contacted. What goes is only that event, an event id made from the random response number and the event's name (which lets Meta count one finish once), when it happened, the page it happened on (the survey's address), the click id, and the description your browser gives of itself (its user agent: the browser and system), which Meta requires with an event from a website and which our server reads off that request without storing it. Never your answers, your email address, your country or your IP address.
- If you answer no, or did not come from a Meta ad, Meta is told nothing.
Your browser sends the click id to our server with each screen it saves, and our server does not keep it: it is used only at the moment our server tells Meta, after your yes. The campaign tags above are kept with your answers; the click id is not.
This rests on your consent, given by answering yes. You can withdraw it only until you finish the survey: at that moment Meta is told, and it cannot be taken back. For telling Meta, ProgressLoop and Meta Platforms Ireland Limited are jointly responsible, under the terms Meta sets for its business tools, as for the steps the apps report; Meta is responsible on its own for what it does with it afterwards, which includes using it to deliver and measure ads and is described in Meta's privacy policy. Meta may transfer it to the United States, as the section on data leaving the European Union says.
Crash and error reports
When the apps or this website crash or hit an error they did not expect, they send a report of it to ProgressLoop's own server, so that we can find the problem and fix it. A report holds the app or website version, the operating system or browser and its version, the device model, the technical error itself (its type, message and where in our code it happened), the screen or page it happened on, and the id of your account when you are signed in. It holds no personal content: nothing you typed, none of your training, body or health data, no photos, and no email address.
Reports are read together with our server logs, by the people who run the service and by the automated check that groups them into problems and warns us. They are not used for marketing or advertising, and are not sent to any analytics or advertising company. The reports themselves are kept for the same short rolling window as our technical server logs; the daily summary of the problems they show, which can include a sample error and the ids of the accounts it happened to, is kept for 90 days and then deleted. There is no switch for them, because we rely on our legitimate interest in a service that works: the data is technical, it is limited to what is needed to find a fault, and you can object by writing to us.
Reviews of trainers
Anyone a trainer coaches, or has coached, can review them: one to five stars and, if they want, a comment of up to 1,000 characters. Each person has one review per trainer, and writing again changes it.
A review's comment is public. Every signed-in user who browses the trainer directory can read it on that trainer's profile, beside your first name and the initial of your last name. Your stars are added to the trainer's average rating, which the directory shows with the number of reviews, and by which it can be sorted and filtered. Write a comment only if you are content for anyone using ProgressLoop to read it.
You can change your review or delete it whenever you like. Deleting it takes the comment off the profile and the stars out of the average. Deleting your account instead takes the comment and your name off it and leaves its stars in the average, from nobody in particular.
A trainer can hide a comment, but not its stars. A trainer sees every review of them, and chooses for each one whether its comment is shown on their public profile. Hiding a comment takes only the words off the profile: the stars stay in the average either way. That is deliberate, so that a trainer cannot raise their rating by hiding the reviews they would rather nobody read.
That is the whole of the control over a review: its author can edit or delete it, and the trainer can show or hide its comment. ProgressLoop does not check reviews before they appear, and does not edit or remove them. Writing a review sends no email.
If you turned on feedback requests, you may be emailed once about a trainer, asking whether you would review them; the emails we send below say when. The review, if you write one, is written in the app as any other, and nothing is recorded from the email.
Who else touches the data
Data is passed on only where a stated purpose needs it, and only with the contractual and technical protections that purpose requires.
- Amazon Web Services - hosting, the database, backups, the private store that holds progress photos, meal pictures and guides' PDFs, and the mail service that sends the emails below. All of it runs in Amazon Web Services' Frankfurt region (eu-central-1), inside the European Union.
- OpenAI (OpenAI Ireland Ltd) - produces the wording of the weekly verdicts, only for accounts that turned AI training reviews on, from the verdict, its figures, the sleep summary and the workout notes described above; and runs the meal assistant, only for accounts that turned it on, from the chats, the meals described for an estimate, the food notes and goal figures described above. Neither carries a name, email address or account id. Processing happens in the United States; see the next section.
- Meta (Meta Platforms Ireland Limited) - learns from the iPhone and Android apps when one of the steps listed under measuring our own ads happens, with no name, email address, account id or anything you recorded, so that we can measure our own ads. Linked to an iPhone's advertising identifier only if you allow it in Apple's tracking prompt, and to an Android phone's unless you delete it in the phone's ad settings. From our server, it also learns that you finished the athlete survey on our website, only if you came to it from one of our ads and said yes, with the time, the survey's address, the ad's click id, the survey's random response number and your browser's user agent, and never your answers, email address, country or IP address. Separately, if you share a workout photo to an Instagram story, Instagram receives that picture from the Instagram app on your phone, because you posted it; we send Meta nothing for it, as the section on workout photos describes.
- Your personal trainer, if you apply to one and they accept - another ProgressLoop user rather than a provider of ours, who sees your record, your schedule, the sessions you book and the plans, guides and recipes they sent you, as the section on personal trainers describes. After coaching ends, access is limited to the past periods whose history you keep shared, with the separate notes and booking records described there.
- Other signed-in users - if you switch on as a trainer and are listed, they see your trainer profile in the directory - including how you coach, your gyms and the languages you coach in, and while you are away, the date you are away until - with your rating and the review comments you have not hidden, and the clients you coach also see your session hours, your time zone and which times are free; if you review a trainer, they see your comment beside your first name and last initial, and your stars as part of that trainer's average; once your place in a session you share with your trainer and other clients is confirmed, the others whose places in it are confirmed see your first name, last initial and profile picture, unless you switch that off. Nothing else about you.
- Apple - as the provider of Sign in with Apple if you use it, which means Apple knows you signed in to ProgressLoop and is handed the authorisation back when you delete the account; as the operator of the App Store and of your device, of your phone's Calendar if you add a plan to it or sync with it, and of the Apple Push Notification service, which carries each notification we send to your iPhone: its title and text, which can name the other person, quote their note, or give a plan's name or a session's time. On an iPhone, Apple also receives the attribution token the app hands our server, and answers with the Apple Ads campaign that led to the install, if any. Apple never receives your training record from us. The workout the watch records goes into Apple Health on your own device, and is governed by Apple's terms for it.
- Any other app you have given access to Apple Health - it can read the workout the watch recorded there, the same as any other workout on your device, because that is how Apple Health works. We send it to no one: the permission is one you gave that app in iOS, and you can take it back in the Health app. Nothing else about your ProgressLoop account is reachable that way.
- Google - only if you choose it, in one of three ways. If you sign in with Google, Google knows you signed in to ProgressLoop and tells us the identifier, address and name described above. If you connect Google Calendar, our server writes your plans (and, if you coach, your booked sessions with each client's name and notes) into your own Google account, which holds them under Google's terms as the provider of that account. If you tap Add to Google Calendar on a plan, that plan's name, times and notes go to Google as a service you chose to open, and ProgressLoop sends nothing itself. See the section on your schedule.
- Google, for Android - as the operator of Google Play, which the Android app is installed from, and of Android on your phone. As the operator of Firebase Cloud Messaging, which carries each notification we send to your Android phone: Google issues the app on your phone the address notifications are delivered to, and carries each one's title and text, which can name the other person, quote their note, or give a plan's name or a session's time. As the maker of Health Connect and of the ML Kit body detection in the progress camera, both of which run on your phone: what the app reads from or writes to Health Connect stays in Health Connect on your phone, and ML Kit sends Google no picture, only, under Google's terms for it, technical statistics about how it runs. Google never receives your training record from us.
- Google, for analytics (Google Ireland Limited) - only if you allow it in the iPhone or Android app: runs Google Analytics for Firebase for us, as our processor, receiving what the section on how the apps are used lists - never your name, email address, account id or anything you recorded.
- Any other app you have given access to Health Connect - it can read the sessions your phone wrote there from your Wear OS watch, the same as any other app's, because that is how Health Connect works. We send them to no one: the permission is one you gave that app, and you can take it back in Health Connect.
- Lawyers, accountants or a competent authority, if that ever becomes legally necessary.
Apart from Meta, for the one purpose above, and Google Analytics for Firebase in the apps, only if you allow it, there is no analytics provider, no advertising network, no email marketing platform and no data broker on this list, because none is used. The optional emails you can ask for, news and offers included, are written by our own staff and sent the same way as every other email from us, by the Amazon mail service above, and so are the emails that help you start. Your answers to our surveys, the reasons you give for leaving and the moments the apps record about how they are used are read only by our own staff, and go to nobody else.
Data leaving the European Union
Your account, your training record, your body data and your photos are stored and processed inside the European Union, and nothing about them leaves it - with the exceptions below. Each of them exists only if you use the feature it belongs to.
A notification about coaching, a session or a plan sent to you, a reminder before a planned workout, or the one notification that helps a new account start is delivered through Apple's push notification service to an iPhone, and through Google's Firebase Cloud Messaging to an Android phone. Both run worldwide, so its title and text may be processed outside the European Union on the way to your phone. That happens only for those messages. Setting a topic to email under Settings, Notifications keeps its messages from both services, and turning workout reminders off, or not asking for one, sends none; the one notification that helps a new account start has no setting, and goes only to a phone that lets the app show notifications.
If you turn on AI training reviews, the week's verdict and figures, the sleep summary and the workout and day notes described above are sent to OpenAI and processed in the United States. Under its data processing addendum, OpenAI Ireland Ltd makes onward transfers outside the EEA under agreements containing the European Commission's standard contractual clauses or an applicable adequacy decision. The safeguards described above also apply: the request carries no account id, name or email address, and it is kept briefly and not used to train models. A copy of the applicable safeguards is available on request. Turning the reviews off ends the transfer.
The meal assistant works the same way and on the same safeguards: if you turn it on, what the section on the meal assistant lists - including your chats, the meals you ask it to estimate, your food notes, a recording you speak and your goal's body weight - is sent to OpenAI and processed in the United States, with no account id, name or email address. Turning the assistant off ends that transfer.
If you sign in with Apple or with Google, the sign-in itself is an exchange between your phone, that provider and our server, and the provider may handle it outside the European Union under its own terms - which is the same relationship you already have with the account you are signing in with. What crosses is what the sign-in is made of: the token your phone was given, the request to prove it, and, when you delete your account, the authorisation handed back to Apple. None of your training record, your body data or your photos is part of it, and it happens only on the sign-ins you choose.
On an iPhone, our server also sends Apple the attribution token the app was given when it was installed, and Apple may handle that exchange outside the European Union under its own terms. The token carries nothing from your account, and what comes back is only the Apple Ads campaign that led to the install, if any.
The steps the phone apps report for measuring our ads, and the finished athlete survey our server reports after your yes, go to Meta Platforms Ireland Limited, which may transfer them to Meta Platforms, Inc. in the United States. Meta makes that transfer on the safeguards its own privacy policy sets out, which include adequacy decisions of the European Commission and its standard contractual clauses. What crosses is the list of steps and the technical details above, or the survey's finish with what the section on the athlete survey lists, never your record and never your answers.
If you allow analytics in the app, what the section on how the apps are used lists is collected through Google's servers in the European Union, which drop the IP address, and is then processed by Google wherever it keeps facilities, including the United States. Google LLC is certified under the EU-U.S. Data Privacy Framework, which the European Commission has found adequate, and Google's data processing terms provide for its standard contractual clauses where that framework does not apply. Turning analytics off ends the transfer.
A personal trainer you apply to may live anywhere, including outside the European Union. Your record stays stored in the EU either way; it is shown on your trainer's own device because you asked them to coach you. After coaching ends, the shared past-period records described above can still be shown there until you turn their history sharing off. A review you write is the same: it is stored in the EU and shown on the device of whoever reads the directory, wherever they are. A plan, guide or recipe you send a client as their trainer goes the other way, to that client's own device, wherever they live.
If you add a plan to Google Calendar, its name, times and notes go to Google, which may process them outside the European Union under its own terms. That is a transfer you make yourself by opening Google Calendar, one plan at a time; ProgressLoop does not send anything to Google.
If you share a workout photo to an Instagram story, or send it anywhere from the share sheet, the picture goes where you send it, and Instagram or that other service may process it outside the European Union under its own terms. That is a transfer you make yourself, from your phone; ProgressLoop sends nothing.
If you connect Google Calendar, our server sends the events described above to your Google account at your request, and Google may process them outside the European Union under the terms of that account. Disconnecting stops it.
How long we keep it
- Your account and everything in it - for as long as the account exists. Deleting it erases what identifies you and keeps a few things, with everything personal taken out, for our statistics, as described below.
- Progress photos - until you delete the photo, the check-in it belongs to, or the account. On an Android phone the app also keeps the photos taken on it, each as it came from the camera, in its own storage on that phone - where they stay after you sign out, and go at the latest when the account is deleted or the app is removed from the phone. They are never part of a phone backup.
- Workout photos - never received by our server. Android may keep temporary sharing files in the app's cache until replaced or cleared. A card you saved or shared is wherever you put it, and stays there under your control.
- Readings from Health Connect - the copy kept on your Android phone, for up to a year, until you sign out, delete the account or remove the app. What reached your daily entries is kept with them, as above.
- Sleep and other apps' workouts from Apple Health or Health Connect - for as long as the account exists, unless you delete the night or the workout in Apple Health or Health Connect first, which removes it from your account at the next sync. Deleting the account deletes all of it.
- How you feel on training days - for as long as the account exists, one answer a day, replaced if you change it. Deleting the account deletes all of it, and we erase past answers sooner if you ask.
- AI training reviews - one reading per week, replaced in place if you ask for it again, for as long as the account exists. Turning the feature off keeps the readings already made; asking us to erase them, or deleting the account, removes them. OpenAI's own copy of what was sent goes within 30 days.
- Meals, their pictures, your food notes, your food diary and the recipes you starred - until you delete them, or the account. Deleting a meal deletes its picture; a diary entry that came from it stays, with its own figures.
- The meal assistant - each chat for one day after its last message, and each estimate for one day, after which their words, recipes and figures are cleared (on an older version of the app, each request and its recipes for one day); a recording is not kept at all; a copy of each cleared estimate, with its rating and what was done with its foods, and a test example made from the foods you kept from it, both without your account, for 90 days after the day it was made; the record of each call, which holds no words, for as long as the account exists. Turning the assistant off deletes none of it early. OpenAI's own copy of what was sent goes within 30 days.
- Guides you write as a trainer - until you delete them, or the account.
- Coaching records - each application and coaching relationship, with the notes on it, for as long as both accounts exist, including after it was declined, withdrawn or ended. That is what lets each of you see what happened, and what the wait before applying to the same trainer again is measured from. Deleting either account removes it from both sides, and you can ask for an ended one to be erased. Turning off history sharing removes access, not your underlying records. A trainer's private notes about a client remain until the trainer deletes them or either account is deleted.
- A trainer's invites - the name, gender, email address and note a trainer entered to invite somebody, until the invite is accepted or expires after 30 days, then 30 days more, unless the trainer deletes it sooner or either account is deleted.
- Payments between a trainer and a client - for as long as both accounts exist, including after the coaching ends, so the trainer can still see what was paid. When the client deletes their account, the trainer keeps the packages, sessions and payments as amounts and dates, with the client's name and every note about them removed, until the trainer deletes theirs; when the trainer deletes their account, the whole record goes.
- Plans and sessions a trainer put into your account - they are yours, and stay when the coaching ends or the trainer's account is deleted, until you delete them. A session on your schedule that came from a booking is the exception, below.
- Plans, guides and recipes a trainer sent you - a workout, programme or recipe your trainer sent is added to your account and kept like any plan or meal of yours, until you delete it, including after the coaching ends. Your trainer's record of what they sent, and a guide in your list, are kept, also after the coaching ends, until the trainer withdraws it or either account is deleted, which takes everything sent between you with it, pictures and PDFs included; the copies in your account stay. Clearing a guide takes it off your list and records that you cleared it; you can ask for a cleared guide, or a plan or recipe you removed before sends went straight into your account, to be erased.
- Your schedule - each plan until you or your trainer delete it, or the account is deleted. A repeating plan is kept with its rule and the times deleted or moved out of it, and deleting it deletes the times moved out of it too. A plan written there by a confirmed session goes when that session is cancelled.
- Session bookings - kept with the account, including declined and cancelled ones, so each of you can see what happened, until the account is deleted. The time before a session last moved is kept with it; an ask for a new time goes once it is answered or withdrawn, or the session is cancelled. If the other person's account is deleted, a booking still pending or confirmed is cancelled, and a confirmed session is taken off the client's schedule.
- App feedback - until you delete your account, unless erased earlier following your request. After that the topic and rating stay, without the comment, under a bare account number that no longer leads to your name, address or anything else about you.
- Reviews - until the author changes or deletes one. When its author's account is deleted, the comment and the author's name go and the stars stay in that trainer's average, from nobody in particular. Every review of a trainer is deleted with the trainer's account.
- A trainer profile and session hours - until the account is deleted, or until the trainer changes them. That includes how they coach, their gyms and languages, the days they changed and their time off with its note. Nothing deletes a past one on its own: a time off stays until the trainer deletes it, and a changed day until the account is deleted. Hiding the profile takes it out of the directory straight away. A gym copied onto a booked session stays with that session.
- Sessions and sign-in tokens - tokens stop working when they expire or are revoked, including when you sign out. The session record, including the app platform, version and build, stays until the account is deleted.
- How you sign in - the identifier Apple or Google gives us for you, for as long as the account exists, because it is what gets you back in. The authorisation for Sign in with Apple is kept beside it and handed back to Apple when the account is deleted.
- Notification choices - for as long as the account exists. A registered phone, with whether it lets the app show notifications - until you sign out on it, Apple or Google tells us its notification address no longer works, another account signs in on that phone, or the account is deleted.
- Your answers about optional emails, and the record of each change - for as long as the account exists. Turning a kind off keeps the record that you once had it on, because that record is what shows the emails were asked for. Both are deleted with the account, together with the code the emails' links carry.
- A note of each scheduled message sent - which summary, nudge, tip, survey, campaign or reminder went to which account, and for which week, quiet spell, session or campaign, so that none is sent twice: for 400 days, then deleted, and with the account if that comes first. The note that you were asked to review a trainer, that you were sent an email or the notification that helps you start, and that the first of those emails reached you after you had said no to an optional email are the exception: they are kept for as long as the account exists, because they are the only thing that stops the same message being sent again.
- Your first-steps answers - for as long as the account exists, or until you change them.
- The moments the apps record about how they are used - 13 months from when they reach us, then deleted. If the account is deleted first, they stay until then without the answer that went with each, under a bare account number that no longer leads to your name, address or anything else about you. Switching them off stops new ones and keeps those already sent until then.
- Why you left or did not start - an answer, once stored, carries no account id, so it is kept with no end date and is not deleted with the account; ask us and we will find it from when you answered and what you wrote, and delete it. The code an email's links carry is deleted after 30 days, or with the account. The weekly count of deleted accounts names nobody and is kept with no end date.
- The surveys you were sent, and your answers - for as long as the account exists. When it is deleted, the scores stay without any comment, under a bare account number that no longer leads to your name, address or anything else about you. A survey can be answered, and an answer changed, for 30 days after it was sent; after that it stays as it was left.
- The record of the emails sent to you - for as long as the account exists. When it is deleted, your address goes from it and only which email went, when, and whether it was delivered or opened stays. An address that bounced or reported one of our emails as spam stays on our list of addresses not to write to, because that entry is about the mailbox rather than the account; once the account is deleted it is kept only as a one-way scramble of the address (a hash), which lets us recognise the address if it is given again; it does not store the address, though anyone who already knows an address could check it against the list.
- A Google Calendar connection - until you disconnect it or delete the account; either one deletes it and withdraws the permission Google gave us. The events already written stay in your Google account if you chose to keep them when disconnecting.
- The steps reported for measuring our ads - we keep no copy of what was sent. The phone keeps a note of which steps it has already reported for which account, until the app is deleted from it. Meta keeps what it received for as long as its own privacy policy says.
- The athlete survey's answers - they name nobody and are kept for our research, and deleted 24 months after they were last saved.
- The email address you left for a call after the survey - 12 months, then deleted, or sooner whenever you ask. The click id Meta adds to an ad's link is not kept at all; what Meta received after your yes, it keeps for as long as its own privacy policy says.
- App analytics, if you allowed it - Google keeps what is tied to an app-instance ID for 2 months, then deletes it in its monthly clean-up; totals in reports, which hold nobody, stay. Turning analytics off, removing the app or deleting the account does not shorten that, because none of it is linked to the account. We keep no copy.
- The install your account was made on, and the campaign it came from - for as long as the account exists, and after that as a count under a new random identifier and a bare account number. An install nobody made an account on holds no name, address or account, only its random identifier, the kind of phone, the app version and the campaign, and is kept with no end date, as part of the count of installs.
- When you accepted the terms and this policy - for as long as the account exists.
- Website counts - only as daily totals, which hold no IP address, cookie or identifier and say nothing about any one person. What a visit sent is not kept once it has been added in.
- Short link visits - with no end date for now, as the history of that link: we have not yet set a limit on how long they are kept, and this policy will say so when we do. They hold no IP address or cookie, only the scrambled code described there.
- Technical server logs - a short rolling window, and longer only for a specific record needed to investigate abuse or a legal claim. Logs written before an account was deleted can carry its account number, which by then names nobody, until they expire.
- Backups - deleted data can survive in an isolated database backup until that backup is overwritten on its normal rotation, which takes 7 days. Photos are not backed up, so a deleted photo is gone at once. Backups are not used for anything else, and a restore re-applies the deletion.
- What stays after an account is deleted - the copy described under deleting your account, with everything personal taken out: the usage moments until their 13 months run out, and the rest with no end date, because it is what keeps the product's statistics from changing each time somebody leaves. Our administration log keeps its record of the changes made to the account, with its name and address replaced by a bare account number.
- Correspondence - as long as it takes to answer, and after that only while it is relevant to a dispute or a legal obligation.
Cookies, and what this website stores
This website sets no cookies. When you choose a theme or language, it saves those preferences in local storage on this browser until you change them or clear site data. They contain no identifier and are not sent with visit counts. By default, the site follows your device settings. While you answer the athlete survey, it also keeps the survey's random response number in the session storage of that tab, which the browser clears when the tab is closed, so that a reload carries on where you were; it is not sent with visit counts either. It loads no fonts, no scripts and no images from anywhere else, and no Meta pixel or other advertiser's code runs on any of its pages. It does count its own visits, without cookies or browser identifiers. On the home page, the page for trainers, the Apple Watch page and the athlete survey, the page's own code tells ProgressLoop's server, in Amazon Web Services' Frankfurt region (eu-central-1), inside the European Union, when one of these happens:
- that a page was opened;
- that an App Store or Google Play button was pressed, which store, and where on the page the button was: the menu, the top of the page or its end;
- that one of the page's other buttons was pressed, such as the one to the page for trainers;
- that a question in the FAQ was opened;
- that a quarter, half, three quarters or all of the page was scrolled;
- on the athlete survey, that it was started, that one of its steps was answered - which step, by its number, never what was answered - and that it was finished;
- on the athlete survey's last screen, which of the things it offers was chosen: a call with us, downloading the app or sharing the survey,
and with each, only:
- which page, and in which language;
- the campaign name of the link you arrived by, if the link carried one (utm_source and utm_campaign);
- the domain of the website that linked to the page, such as google.com - never the address of the page you came from;
- whether you are on a phone, a tablet or a computer, which our server works out from the description your browser gives of itself, keeping the answer and not the description.
The page adds nothing else: no identifier, no screen size, no address of the page you came from, nothing that could tell your visit apart from anybody else's. Our server stores no IP address, no description of your browser, no cookie and no identifier for any of it. It adds each one to a total for the day - so many views of this page, in this language, from that campaign - and keeps only those daily totals, which say nothing about any one person. Like every request, the visit still passes through the short-lived server logs described above. If your browser sends Do Not Track or Global Privacy Control, the pages count nothing at all; turning either on in your browser is how you opt out.
Our short links are the one exception to daily totals. An address on go.progressloop.eu - printed on a poster, put in a post, or carried by a QR code, including the ones on this website's pages - takes you on to where it points, and on the way our server keeps a record of that one visit, holding only:
- when the visit happened;
- the domain of the website that sent you, such as instagram.com, if your browser named one - never the address of the page you came from;
- whether you are on a phone, a tablet or a computer, and the names of its operating system and browser, such as iOS and Safari, which our server works out from the description your browser gives of itself, keeping the answer and not the description;
- the country and city that Amazon's network, which carries our websites, places the visit in from your connection;
- whether it was the first visit to that link from your kind of device: to tell, our server joins the kind of device, its operating system and the first three parts of your IP address (the network, not the address) and keeps only a one-way scrambled code (a hash) made from them, never the address itself.
It keeps no IP address, no description of your browser and no cookie, and sets nothing on your device. A robot, such as a chat app drawing a preview of the link, is not recorded, and nor is the same visit arriving twice within two seconds. A short link made for one of this website's download QR codes also adds one to the day's total of download buttons pressed, as a button pressed through a QR code. Because our server records the visit before any page opens, a short link counts it whether or not your browser sends Do Not Track or Global Privacy Control. Only the people who run ProgressLoop and manage its links can read these records, in our administration console, and they are kept as set out under how long data is kept.
Apart from that count, and the athlete survey, which saves the answers you give to ProgressLoop's own server after each screen, the pages you read make no request to any server once they have arrived; the five pages a mailed link opens - the one that confirms your address, the one that sets a new password, the one where you choose which optional emails you get, the one where you answer our survey and the one where you tell us what got in the way of starting - send what you came to do to ProgressLoop's own server and to nobody else. If a page fails while it runs, it sends a report of the error to that same server, as the section on crash and error reports describes. The page of choices only reads them when it opens, and changes one only when you press its switch. The survey page records the score you clicked in the email, and a comment only when you send one; the page that asks what got in the way records nothing until you press Send. The page a notification email's button lands on, if the app does not open in its place, only tells you where to find it and asks for nothing. Telling Meta that you finished the survey needs no code of Meta's on the page: our server does it, and only after you say yes, as the section on the athlete survey describes. There is no consent banner because nothing is stored on your device beyond your theme and language and, while you answer the survey, its response number, each there only to do what you asked.
The administration area at /admin is a private tool for whoever runs the service, not part of the public site. It keeps a sign-in token and a couple of interface preferences in the browser's own local storage. These are strictly necessary for it to work and are never used to observe anyone.
The iPhone app stores your sign-in token and your settings on your device, which is how it keeps you signed in between launches. Your iPhone Calendar sync settings, and which event it wrote for which plan, are kept there too. So is what Meta's SDK needs to measure our ads: the identifier it makes up for that installation, your answer to Apple's tracking prompt as iOS reports it, and which steps have already been sent, so none is sent twice. And the random identifier the app reports its install to our server under, until the app is removed. So is your answer to the analytics question and, if you said yes, what the analytics software needs: the identifier it makes up for that installation and the events it has not sent yet. The watch app has no sign-in of its own: it is signed in by the phone handing it that token, and keeps it on the watch for the same reason. It then talks to our server itself, over the watch's own connection, and keeps a workout in progress on the watch until the server has it - the same sets, sent the same way, as the phone would send.
The Android app keeps the same things on your phone: your sign-in token, sealed with a key held in the phone's secure hardware, your settings, what phone calendar sync wrote, and what Meta's SDK needs, including which steps have already been sent, and the random identifier it reports its install under, your answer to the analytics question and, if you said yes, what the analytics software needs, as on an iPhone. It also keeps the Health Connect readings described above, the progress photos taken on the phone, a copy of your account's data so the app opens quickly, and what its home screen widgets show. Android's own backup and its transfer to a new phone are told to take none of it. The Wear OS app is signed in by the phone the same way the Apple Watch app is, keeps that token sealed on the watch, and keeps what it shows on its tile and watch faces, and anything not yet delivered to our server, on the watch.
Emails and notifications we send
Some emails the service needs, and they are not optional: confirming your address, a welcome once you have, resetting your password, a notice when your password changes, and replies to things you write in about. Those always come by email, whatever else you have chosen, because they are how you get into your own account.
An account made by signing in with Apple or Google needs none of those four. The address is already confirmed by the provider, so no confirmation is sent - unless the provider will not vouch for it, which is the one case where the link still goes - and there is no password here to reset or to tell you about. If you signed in with Apple and shared no address at all, nothing can be emailed to you: notifications on your phone are then the only way we reach you, and the messages below that would have fallen back to email cannot. An address cannot be added to such an account afterwards either, because the way into it is Apple rather than an address and a password of its own.
Everything else below can reach you as a notification instead. Under Settings, Notifications you choose, for each topic - an application answered, coaching ended, a plan from your trainer, session requests, session changes, and, if you coach, somebody applying to you - whether it comes by email, as a notification on your phone, or both. None of them can be switched off entirely, and until you choose, each comes as a notification. If no phone is registered to your account, or Apple or Google refuses to deliver to it, it is emailed instead. A notification carries what the email would: the other person's name, and any note, plan name or session time. Whether it shows on your lock screen is decided by your phone's notification settings.
The iPhone app asks iOS for permission to show notifications only when you ask it to - on the Notifications screen, or when you turn on a reminder. The Android app asks Android at those two moments too, and once more, at the first rest of the first workout you log, since on Android the workout in progress and its rest are shown as a notification; never when it opens. Each app tells our server the address Apple or Google gives it for your phone each time it opens, so that the choice you make later works at once. Without that permission a notification is delivered but not shown, and no email is sent in its place - so set a topic to email, or both, if you have turned notifications off on your phone. Signing out on a phone stops notifications to it.
If you use coaching, the other person is emailed each time an application is made, answered, or a coaching relationship ends - including when it ends because an account was deleted. Each email carries the name of the person who acted and any note they wrote, and never their email address.
If you coach, you can also hear when a client who shares how they feel answers Exhausted or Tired, at most once a day per client, with their name and that answer, as a notification or by email as you choose for client check-ins, which you can also turn off. If you are coached, that is what your trainer receives; turning off sharing in your coaching settings stops it.
If you coach, your notifications inside ProgressLoop - the list in the app and in the coach portal - also keep a history of what your clients do: a finished workout, a check-in, a changed goal, a weigh-in, and an answer to how they feel while they share it. A weigh-in and an ordinary answer to how they feel are only ever listed there, at most one of each per client a day, with the client's name and never the weight or the answer: they are not sent to your phone or emailed, whatever you chose for client check-ins. If your list was still empty on 6 November 2026, it was started with each of your clients' latest moment of each of those kinds from the 90 days before, and only from since you began coaching them, already marked as read.
If your trainer sends you a workout, a programme, a guide or a recipe, you are emailed that it arrived, with its name, their name and any note they wrote, and never their email address. Clearing a guide from your list, or the trainer withdrawing anything sent, sends no email.
If you book sessions, the trainer is emailed when a client asks for one, and the client is emailed when the trainer confirms one, books one directly or declines one. When a client moves a request or asks to move a confirmed session, the trainer is emailed the new time; when the trainer moves a session or declines an ask to move it, the client is emailed the time it is now at. Withdrawing an ask sends no email. When either of you cancels, the other is emailed - including for each upcoming session cancelled because an account was deleted. Each carries when the session starts, the name of the person who acted and any note they wrote, and never their email address. Writing or changing a review sends no email.
Two reminders come on top of those, by notification or email as you chose for session changes and session requests. If you train with a trainer, you are reminded about a day before each confirmed session, with the trainer's name and the time in their time zone - unless the session was confirmed less than a day before it starts, since the confirmation has only just reached you. If you coach, you are reminded once a day while a coaching application or a session request has waited more than a day for your answer, with how many of each are waiting.
A reminder before a planned workout comes only if you ask for one on that plan, at the time before it you chose - from five minutes to a day; the app's first steps suggest an hour, which you can change or remove. It is a notification and never an email, it names the workout and when it starts, and it is not sent after the workout has started or on a day you have already finished a workout - the day as the plan's time zone counts it, or as UTC counts it for a plan that does not repeat. You can turn workout reminders off entirely under Settings, Notifications. Nothing is sent to say you missed one.
Three kinds of email are optional, and you get only the ones you ask for. They are separate from everything above, and each is its own choice:
- News and offers - what is new in ProgressLoop, and offers. Each one is written by our own staff and sent on a day they choose to everybody who has this kind turned on, a confirmed address and an account that is not suspended - or only to some of them, chosen by facts we already hold about each account: only trainers, say, only readers of one language, only people who trained in the last month, or only those on an older version of the app. The full list is in the section on why we process your data. Where it is about what you recorded, we use counts and dates, never the contents: no weights, measurements, photos, notes or health readings. Our staff can also give an account a label, such as a group testing a new version, to write to that group; nobody is shown the labels on their own account, and they are deleted with it. Before one goes out, a test of it is sent only to the member of staff who wrote it.
- Tips and progress - a nudge after a quiet spell, and tips for your first steps. The nudge comes after a week in which you neither finished a workout nor opened the app, and once more after three weeks: to know when, we look at the last day you finished a workout and when the app was last used on any of your devices, which is recorded to within an hour, and the nudge itself says only how many days it has been. The first-steps tips come a day, three days and a week after you make your account, and each is skipped once you have done its step: to know that, we look at whether you have an active goal, any workout or programme, and any finished workout. None of them carries your body weight or any other figure from your record. We used to send a weekly summary of your training here, and we no longer do.
- Feedback requests - now and then, how likely you are to recommend ProgressLoop, and, if you train with a trainer, a request to review them. The survey comes at most once every 90 days, and only once you have had your account for at least two weeks and finished at least three workouts: to know that, we look at when the account was made and count your finished workouts. The request to review a trainer comes once you have had three confirmed sessions with them that are over, while they still appear in the trainer directory, if they coach or have coached you and you have not reviewed them - and only once for each trainer, ever. It names the trainer, and nothing is recorded from it: a review, if you write one, is written in the app as before.
Every one of them is off until you turn it on. When you make an account, however you make it, you are offered three separate boxes, one for each, and none of them is ticked: tick any of them, all or none, and the account is made the same way. The app's first steps may ask again, and leaving them off there changes nothing either. Afterwards you can turn each one on or off at any time in the app's settings. Using the app never depends on any of them.
Stopping them takes one step, whichever way suits you: the link in every one of those emails, which opens a page on this website where you can turn any of the three off, or back on; your mail program's own unsubscribe button, where it shows one, which turns off the kind that email belongs to; or the app's settings. Reporting one of those emails as spam turns off all three, and the emails that help you start as well. Turning one off takes effect at once and changes nothing else - the emails about your account and the messages described above carry on as before. Our staff can turn one off for you if you ask, but nobody here can turn one on for you: only you can.
The survey is answered on this website. It asks how likely you are to recommend ProgressLoop, from 0 to 10, and each number in the email is a link to a page here that records the one you clicked and offers a box for a comment, if you want to add one, of up to 1,000 characters. For 30 days after the survey was sent you can change the score, and add, change or clear the comment, from the same link. The links carry a random code instead of asking you to sign in. Your answer is kept with your account, and our staff read the answers, and the overall score they add up to, in the administration area, beside the account they belong to. It is used to understand how people find the app and what to improve; your latest score may also decide which of our own news and offers reach you, if you have asked for them. It is never published with your name and never given to an advertiser.
A record is kept of each answer - which kind, whether it was turned on or off, how, and when - because it is what shows that you asked for what we send. The page an email's link opens changes nothing when it loads, only when you press one of its switches, because some mail systems open every link in an email to check it before you do.
These emails go only to an address you have confirmed, and stop while an account is suspended. They are sent the same way as every other email from us, by Amazon's mail service in Amazon Web Services' Frankfurt region (eu-central-1), inside the European Union. No email marketing platform is involved, and your address is not given to anyone else to send them.
If you made an account and have not trained yet, we may write to help you start. These emails are about the account you made rather than news or offers, so they are not one of the three optional kinds: they go to an account with a confirmed address that holds no workout and has never finished one, until you turn them off, and some go only to some of those accounts - those the app has not been opened on for a while, say, or those on an older version of the app - chosen by the same kind of facts as news and offers, never by training, since these accounts have none. Each says how to get going, may link to the App Store or Google Play, and lists a few reasons people give for not starting, each a link to a page on this website where you can tell us yours - see the section on feedback about the app. Every one of them has a link that turns them off at once, and your mail program's unsubscribe button works too; reporting one as spam turns them off with everything optional. They stop the moment the account holds a workout or finishes one. If you ever said no to one of the optional kinds of email, you can still be sent the first of these emails, once in the life of the account, and none of the ones after it.
The same accounts can also be sent one notification that helps them start, and only ever one: only to a phone that lets the app show notifications, opening the app's first steps. It is never sent as an email instead.
Every email we send is recorded, optional or not: what kind it was, the address it went to and when, and what Amazon's mail service reports about it afterwards - that it was delivered, bounced or reported as spam, and when it was opened and which of its links was followed. An open is noticed through a tiny image in the email, and a followed link because it passes through that service on the way; a link that carries a code of yours, such as one that resets a password or opens the survey, does not, and is never recorded. The record holds none of the email's words and is kept with the account, as set out under how long data is kept. An address that bounces for good, or that reports one of our emails as spam, is not written to again.
Your rights
Under the GDPR you have the right of access to your data, and the rights to have it corrected, erased, restricted or ported; to object to processing based on legitimate interest; and to withdraw consent at any time for anything based on it. Consent to an optional email is withdrawn in one step, as set out under the emails we send, and never needs a reason. So is consent to app analytics, in the app under Settings, Your data. Two objections take one step as well: the switch in the app's settings stops the moments the apps record about how they are used, and the link in an email that helps you start stops those emails. Consent to telling Meta that you finished the athlete survey can be withdrawn only until you finish it, because that is when Meta is told.
Withdrawing consent does not make earlier processing unlawful. The right to erasure is not absolute - data can be kept where the law requires it, or where it is needed to establish, exercise or defend a legal claim, and deleting an account keeps the copy, with everything personal taken out, that the section on deleting your account describes, on our legitimate interest. You can object to that copy as to anything kept on that basis, by writing to the address below. Everything else is erased or irreversibly anonymised, except the copies of meal estimates and the test examples made from them, which are deleted 90 days after their day, as the section on the meal assistant sets out.
Two of them do not need us at all. Access and portability are built into the app: Settings will export your whole record whenever you ask, as JSON exactly as it is stored or as CSV with one file per table, and erasure is the account deletion below. Neither is rationed and neither asks a reason. The export is rows rather than pictures - it names your progress photos but does not contain them. For a copy of the photos themselves, write in and they will be sent to you. The export does not yet include your coaching records - applications, session bookings, reviews and plans a trainer sent - your schedule, or a trainer profile - how you coach, your gyms and languages, your hours, changed days and time off - either, nor the moments the apps record about how they are used; write in for a copy of those too.
The athlete survey on our website belongs to no account, so it is not in the export. Its answers name nobody, so we can look for yours only from what you tell us about them, as its section says; the email address you left for a call is deleted whenever you ask.
To exercise any of the others, write to privacy@progressloop.eu. If you think your data has been handled wrongly you may complain to a supervisory authority - in Bulgaria that is the Commission for Personal Data Protection - or to the authority where you live, and you may also go to court.
Deleting your account
You can delete your account yourself, in the iPhone app or the Android app, under Settings, Delete account. You do not need the app for it: write to privacy@progressloop.eu from the address on the account, and it will be deleted for you. The page on deleting your account sets out both ways. Removing the app from your phone does not delete the account.
Deleting your account closes it irreversibly, at once: there is no waiting period in which it can be restored. Access ends immediately and active sessions are invalidated. It works the same way whether you delete it in the app or we delete it at your request.
Deleted straight away: your name, email address and password, the way you sign in with Apple or Google, your profile picture, your progress photos and check-ins, your body measurements and weigh-ins, your goals, your meals with their pictures, your food notes and food diary and everything the meal assistant kept, your habits, reminders and notes, how you said you feel on training days, any AI training reviews, your coaching relationships and session bookings, the messages and plans sent between you and a trainer, your registered phones, your notification and email choices, and your signed-in sessions. The copies of cleared meal estimates, and the test examples made from them, are not deleted with the account, because they are not filed under it and cannot be found by it; each goes 90 days after its day, as described in the section on the meal assistant.
Kept, with everything personal taken out. A few things stay so that the product's statistics - how many people finish a workout, which plans are taken up, which campaigns bring people who go on to train - do not change each time somebody leaves. Each is stripped of anything personal and kept only under a bare account number, which no longer leads to your name, email address or anything else about you. Because those records still belong together under that number, we treat them as personal data, kept on our legitimate interest:
- your workout history as numbers only: when each session was, how long it took, which device started and finished it, and which library exercises, with their sets, reps and loads - with no title, notes, body weight, heart rate or calories;
- your workouts and programmes as structure only, with no names or notes;
- your star ratings of the app and your survey scores, without any comment, and which catalogue plans you took up and which recipes you starred, as counts;
- the install the account was made on and the ad campaign it came from, under a new random identifier, so the one your phone holds no longer finds it;
- the moments the apps recorded about how they were used, without the answers that went with them;
- whether the emails we sent you were delivered or opened, without your address;
- a bare record that an account existed: when it was made, whether it was an athlete's or a trainer's, and its language.
If your address had bounced or reported one of our emails as spam, we keep only a one-way scramble of it (a hash), so that we never write to it again; the address itself is not kept, though anyone who already knows it could check it against the hash. Our administration log keeps its record that changes were made to the account, but your name and email address in it are replaced with that bare account number, and the server logs may carry that number until they expire on their normal rotation. Copies in database backups go when those backups are overwritten, within 7 days. Signing up again with the same email address makes a new, unrelated account: nothing of the old one is brought back.
Deleting the account in the Android app also clears it from that phone: the Health Connect readings it kept, the progress photos taken on it, your reminders, what its widgets show, and the watch's sign-in. On any other phone or watch still signed in, the app stops working for the account the next time it reaches our server.
If you coach or are coached, deleting the account also ends every one of those relationships and erases the record of them from both sides, and each person you were actively coaching, or being coached by, is emailed that it has ended. A trainer profile leaves the directory, and is deleted with its gyms, languages, hours, changed days and time off. Plans and sessions you put into a client's account as their trainer belong to that client and stay with them, except a session that came from a booking, which goes as described next. Your record of the plans, guides and recipes you sent goes with yours, as does a guide still in a client's list, and your own guides; the workouts, programmes and meals a send added to a client's account stay with them. Payments between a trainer and a client go with the trainer's account; when a client deletes theirs, the trainer keeps the packages, sessions and payments as amounts and dates for their records, with the client's name and every note about them removed. Deletion cannot reach a copy a trainer made outside the app.
Your schedule and your session bookings are deleted with the account. A session still pending or confirmed with somebody else is cancelled on their side, and a confirmed one is taken off the client's schedule. Every review you wrote loses its comment and your name, and its stars stay in that trainer's average, from nobody in particular; if you are a trainer, every review of you is deleted. Your answers about optional emails and the record of them are deleted, and so are your first-steps answers and the code an email that helps you start carries. If you answer why you are leaving before you delete, that answer is stored after the account is gone and without its id, so it survives the deletion unless you ask us to erase it, and the account is added to that week's count of deletions. What app analytics already sent to Google is not linked to the account, so deleting the account cannot reach it; it goes when Google's retention period runs out, as set out under how the apps are used. If you signed in with Apple, the authorisation it gave us is handed back to Apple, which ends ProgressLoop's place in the list of apps you have used your Apple ID with. If you connected Google Calendar, the ProgressLoop calendar in your Google account is deleted and the permission Google gave us is withdrawn. Deletion cannot reach a copy of a plan you added to a calendar one at a time, or the events phone calendar sync wrote on your phone, which belong to that calendar - turn the sync off and choose to remove them first if you want them gone. Nor can it reach the workouts the watch wrote into Apple Health, which belong to Apple Health on your device and stay there, readable by any app you have allowed to read your workouts, until you delete them in the Health app. Nor can it reach the sessions your Android phone wrote into Health Connect from your Wear OS watch, which stay in Health Connect until you delete them there.
Children
ProgressLoop is not intended for children. It is meant for adults who train, and an account should be created only by someone aged 16 or over - or older, where the country you live in sets a higher age for consenting to online services. No account is knowingly created for a child. If you believe one has been, write in and it will be deleted. The athlete survey on this website is likewise only for people aged 16 or over: it asks first, and a no ends it without saving anything.
Automated decisions
No decision producing legal effects or similarly significantly affecting you is made by automated means. The app does suggest a load to try on your next set, calculated from what you lifted in earlier sessions, leaving out any you marked as a lighter day - that is a suggestion you can ignore or overwrite, it changes nothing on its own, and it is not a decision about you in the sense the law means. The same holds for an AI training review, if you turn them on: fixed rules read your own training figures into a verdict, and a model words it, with your workout and day notes, into a reading and nothing else. No setting changes because of it, no load is altered, and no access is granted or withdrawn. A recipe from the meal assistant, and the calories and macros estimated for it or for a meal you describe, are suggestions of the same kind: nothing is saved or changed until you choose to. Sorting or filtering the trainer directory by rating is ordering by the average of the stars reviewers gave, and not a decision about any trainer.
Security and incidents
Connections are encrypted, passwords are hashed, progress photos sit in a private store reachable only through short-lived signed addresses, the permission to write to a connected Google Calendar is stored encrypted, a trainer's access to a client is checked on every request against an active relationship or the permitted shared periods of an ended one, administrative access is restricted and separate from user accounts, and every administrative change is recorded in an audit trail. No internet service can promise absolute security.
If a personal data breach happens, the risk is assessed and the supervisory authority and the people affected are notified where the GDPR requires it.
Changes to this policy
This policy may be updated when the app, its providers or the law change. The new version and its date are published here. For a change that materially affects your rights or what you would reasonably expect, notice is given in advance, and where new consent is needed it is asked for rather than assumed.
Getting in touch
Any question about this policy, any request about your data, and any objection goes to privacy@progressloop.eu. See also the Terms of Use.