Privacy Policy
Last updated: 8 November 2026
Who we are
INQON ("the app") is made by Yevhenii Sereda, a sole trader based in the United Kingdom, who is the data controller for everything described here.
Yevhenii SeredaLytchett House, 13 Freeland Park, Wareham Road, Poole, Dorset BH16 6FA, United Kingdom
support@inqon.app
Registered with the Information Commissioner's Office (ICO) as a data controller, registration number ZC280365.
This policy explains what the app collects, why, where it is kept, who else handles it, and how you remove it.
The short version: the app is built to work on your phone first. Your training and food journal is stored on the device and backed up to your account, so it survives a new phone. We do not sell your data, we do not share it for advertising, we do not show ads, and we do not track you across other companies' apps or websites. If you turn on Share usage data (off unless you do), the app sends counts of which parts of it are used, with a random number — never what you log, never your name or account (section 1, "Usage data"). Crash reports are sent so faults can be fixed, without your account or your journal. The routes of your runs, rides and walks are part of your journal and are backed up to your account with it, unless you turn sync off; the meal photos you keep never leave your phone unless you share a picture yourself. A plate or label you scan, or a photo you attach to a question, is sent once to be read: we do not keep it, and the AI provider may hold it for a limited period for safety monitoring before deleting it (sections 4 and 6).
If you are in the United States, two more documents apply alongside this one: the California section at the end, and — because training, food and body data count as consumer health data there — a separate Consumer Health Data Privacy Policy written for Washington State and Nevada.
1. What the app collects
Account
- Email address and a user ID, when you sign in with Apple, with Google, or with a one-time code or link sent to your email. With Sign in with Apple you can choose to hide your email; we then receive a private relay address.
- Ways to sign in. You can add more than one way back into the same account (Profile → Settings → Email and sign-in): an email address of your own, added or changed with a six-digit code sent to it; a password, if you set one; and Apple or Google, linked to the account. We keep the email address, which sign-in methods the account has, and when each was added and last used. A password is never stored as you typed it: our sign-in provider (Supabase, section 5) keeps only a hashed form of it, one-way, and we cannot read it. The codes, and the emails for confirming an address or resetting a password, are sent by that sign-in provider through Resend (section 5). We do not use this address for marketing, and we give it to nobody except the providers in section 5.
- You do not need a full account to start. You can sign in, or choose "Try without an account" (below). Either way what you log belongs to one account, which backs your journal up and keeps it apart from anyone else's on a shared phone; a full account also brings it back on a new phone. The app still works without a connection — in a gym with no signal, for example — and what you log is sent when there is one.
- Trying the app without an account (guest). If you choose "Try without an account", the app makes an anonymous account for you: a user ID — no email and, unless you add them yourself, no name, no nickname and no photo. Like every account, it identifies itself to RevenueCat with that ID (section 5). Your journal is kept on your phone and synced to that anonymous account in the same way as for any account (unless you turn sync off), so the rest of this policy applies to it in full, the assistant included (with your consent, on the free weekly allowance). A training plan, Pro and using INQON on another phone need a full account. If you later save your progress with Apple, Google or an email, that sign-in is added to the same account and nothing moves. If you sign in to an account you already had, the app asks what to keep and never deletes anything without asking. A guest account cannot be brought back on another phone, and signing out of it removes its journal from the phone; the app warns you before it does.
- An unused guest account is removed after 30 days. Each time you open the app with a connection, it tells our server, which keeps the time of the last opening. If a guest account is not opened while connected to the internet for 30 days (opening the app offline does not reach our servers to reset the timer), the account and the journal stored with it on our servers are deleted, as in "When you delete your account" (section 6), together with a profile photo, if you added one. Because a guest has no email, the reminders come from the app: a "Save your progress" card, a line in Profile and Settings, a card when you come back with a week or less left, and — if you allow notifications — a notification three days before. Opening the app, or saving your progress, keeps the account. What is on the phone is not deleted with it: it stays until you sign out or delete the app, and the app offers to put it into a new account (a full one, or a new guest) so it is backed up again.
- Your name and a nickname: a first name, a surname if you want to give one, and a nickname that no other INQON account can have. They are asked for the first time you share your profile or invite a friend, or when you add them in Profile. If you sign in with Apple, the name Apple shares is filled in for you. Nobody else can see them in the app in this version, beyond what you choose to share yourself; if a later feature shows them to someone else — a coach you invite, for example — the app will say so before it does.
- A city and a one-line bio, if you add them in Edit profile.
- A profile photo, if you add one: kept in a private folder of your account (United Kingdom) and on your phone. Nobody else can see it in this version. Removing it, or deleting your account, deletes it from our storage.
- We never see or store your Apple or Google password.
Your journal (stored on your phone and in your account)
- Your chats with the assistant, while sync is on: each chat's title, times and pins; your questions and its answers; reminders you set in a chat; and the changes it proposed, with their outcome. A photo you attached is not stored, only the fact that there was one. What you type is free text, so it can hold anything you choose to write. The assistant's consent screen says this first.
- Routes you plan to follow: name, points and distance.
- A few assistant and route settings: whether it adds entries without asking, suggested questions, how much of a route is hidden when you share it, and when you agreed to send your plan settings, note or scans to Anthropic; that answer follows your account to your other phones.
- Training: your goal, experience, available days and equipment, the plan built for you and its changes with their reason, and the sessions you log — exercises, sets, weights, reps, effort ratings, duration, distance and notes — and exercises you created.
- Routes of runs, rides and walks you record with your location, with the times of the session's pauses and rests: kept with the session they belong to, so its splits and charts come back on another phone. A very long route is thinned before it is sent (fewer points, the same line). Visible only to you; turning sync off (Profile → Settings → Your data) keeps your journal, routes included, on the phone. Your name, nickname, city, bio and profile photo still go straight to your account when you set them. Sync comes back on after you sign out, so turn it off again after signing in if you want it off.
- A note about what to avoid in training, if you write one (for example "sore shoulder").
- Your body: body weight entries, and body measurements you add (body fat, chest, waist, hips, thigh, arm, neck).
- About you: your year of birth, sex and height, if you give them, used to set your food targets. The goal screen accepts ages of 18 and over.
- Shoes, if you add them: the name you give a pair, when you started using it, its starting distance and limit, what it is used for, and which runs and walks were done in it. A photo of a pair stays on your phone.
- Food: meals, the foods and amounts you log, products and dishes you create or scan, day notes, and nutrition goals with what you told us to set them: daily activity, training load, everyday stress level and weekly pace.
- Settings: units, your daily step goal, exercises you chose to always swap for another, and similar preferences. Theme, app icon and first day of the week stay on the phone.
- Invitations, if you invite someone or use an invite: which account invited which, when the invite was used, when the reward was given, and the Apple offer codes given to each account. We ask RevenueCat whether an account has had Pro before, and RevenueCat tells us when an invited friend's first paid period starts. The friend you invited sees only your nickname, which they typed in.
- Movement breaks: when each reminded break was due, the move, and whether you took it, put it off or walked instead; breaks you log yourself; and your break days, hours and interval.
Much of this is data about your health in the legal sense — not only what comes from Apple Health, but your weight, what you eat, how hard you train and anything you write about what your body cannot do. Section 2 says what that means and what we ask of you because of it.
Kept only on your phone — never uploaded by the app
- Photos of your meals that you keep, and photos of your shoes.
- Health-store readings other than imported workouts (see below).
- What the Lock Screen and Home Screen widgets show — the workout in progress, today's movement breaks. The app hands this to its own widget on the phone; it is not sent anywhere.
- If you sign out of a full account, these stay on the phone under that account and come back when it signs in here again; another account on the phone cannot read them. Photos are kept as files in the app's private folder; what shows in the widgets is cleared. Deleting your account from this phone, or deleting the app, removes them. A guest's are removed when the guest signs out.
- If you have device backups (such as iCloud Backup) turned on in your phone's own settings, iOS may include the app's local files in your personal device backup under Apple's terms; we never receive or have access to those backups.
Age check
- Where the law requires it and iOS says so, pressing "Agree and continue" on "Before you start" asks Apple for your age range (Apple's Declared Age Range). If Apple reports that you are under 18, you cannot go on. If you decline to share it, or the check does not apply, the app relies on the box you ticked. The answer is used at that moment on the phone: it is not stored and not sent to us.
Location
- Used to record a run, ride or walk, from the moment you press Start until you press Finish, and to centre the map on where you are: on the screen before Start, and while you draw a route to follow. For centring, the app reads the phone's last known position; it is not saved or sent to us. While you draw a route, iOS also keeps your position up to date on the map; that is not saved or sent to us either. Once you have pressed Start, recording continues while the screen is locked; iOS shows a blue location indicator while it does. The app does not read your location at any other time.
- The route, and the distance and pace calculated from it, are part of the session in your journal, stored on the phone and in your account (see "Your journal" above). Nobody else can see it.
- When you share a route in a picture, the start and finish are hidden by default (Profile → Settings → Profile & route privacy).
Apple Health (optional)
- If you allow it, the app reads: workouts, active energy, resting energy, steps, walking and running distance, cycling distance, swimming distance, flights climbed, sleep (including its stages), body weight and body fat percentage, and heart rate during a workout (from Apple Health — a watch or another device that writes to Apple Health, including a workout you recorded in INQON while wearing one). The app does not write to Apple Health, and it does not read resting heart rate, body mass index, blood pressure or water.
- Workout heart rate stays on your device. It is read from Apple Health for the time of one workout, when you look at it, and shown as an average, a highest value and a line. It is not saved in your journal, not uploaded to our servers, not sent to Ask INQON and not shared.
- It reads only while you are using the app — when you open it and when you return to it. Nothing wakes the app up in the background to read your health data.
- Each account connects for itself. The phone's Health permission belongs to the app, so the app adds its own step: an account reads nothing from the health store until you connect it in that account (Profile → Settings → Apple Health, under Health & devices). Another account signed in on the same phone reads nothing of yours, and you can disconnect at any time.
- Imported workouts become sessions in your journal and are synced with it like any other session: the kind of activity, when it started and ended, its duration, distance and energy, which app or device it came from, and the health store's reference for it.
- Everything else read from the health store stays on your device. Your steps, distances, floors, energy, sleep, weight and body fat from the health store are held in a local cache so the screens can show your day. They are not uploaded to our servers and are not part of the sync between your devices. Deleting the app deletes them; they can always be read again from the health store.
- With Pro, movement breaks use your recent steps on the phone, or a walking workout that has just ended, so a walk you already took counts as a break. The steps and workouts are read on the phone and not uploaded, but the result is: the break is saved in your journal as walked instead and syncs with it. That result is not sent to the assistant.
- The app reports these figures and nothing more. It does not diagnose, does not give medical or recovery advice, and does not calculate any readiness or recovery score.
Steps counted by your iPhone (optional)
- If you turn on Count steps with this iPhone (and allow Motion & Fitness), the app reads the daily step count your iPhone's motion sensor keeps, for days the health store has no steps for. It is used for the Walking view, your step goal, the evening walking reminder and movement breaks.
- Those counts stay on the phone, in the same local cache as the health readings above: they are not uploaded and not synced. Turning the option off deletes them.
Evening walking reminder (optional)
- Off unless you turn it on. It is a notification scheduled on the phone, worked out from the steps the phone already holds; nothing about it is sent to us.
Health data is never used for advertising
- Health data is never used for advertising or marketing, never sold, and never shared with third parties except the service providers in section 5 that store or process your journal on our behalf, and except where the law compels us (section 5, "When the law requires it").
Camera
- Used to read barcodes, to photograph nutrition labels and to photograph a plate so its foods can be estimated (all in Pro). Barcode images are not stored. A label or plate photo (stripped of location and time metadata) is sent once to be read (section 4) and is not kept by us. The app deletes its temporary copies on your phone once the answer is back.
- Used for meal photos only when you choose to take one; those stay on the phone.
- Used, with your photo library, for a photo you choose to attach to a question to the assistant: it is sent with that one question (section 4) and not kept.
Microphone and speech recognition (optional)
- When you turn the microphone on in the assistant, what you say is turned into text on your phone, by the phone's own speech recognition. No sound is recorded, kept or sent — by us or by the app to anyone. Only the text, which you see and can change before sending, goes with your question.
Calendar (optional)
- If you turn on "Whole plan in Calendar" (Profile → Settings → Calendar), the app makes a calendar of its own named "INQON" on your phone (which your phone may sync with your own iCloud or default calendar account) and writes your planned sessions into it, keeping them in step with your plan. It reads no other calendar and no other event, and nothing from your calendar is sent to us. Turning it off takes the plan out of that calendar.
Feedback
- If you send feedback (Profile → Settings → Send feedback), we receive the message, its type (idea, problem, praise), the app version and the update it runs, the platform, the device model and system version, the app's language, and an email address only if you enter one. If you are signed in it is linked to your user ID. Nothing from your journal or health data travels with it.
- A note written without a connection waits on the phone and is sent when the connection is back. Each note is stored in our database, where we read it, and may also be forwarded by email to our support inbox.
Business enquiries
- If you write to partners@inqon.app about working with us, we keep your name, your email, the company you write for and what you send, to answer and to follow up.
Purchases
- Payments are taken by Apple, who is the seller. We receive confirmation of your subscription status, never your card details. Subscription status is managed through RevenueCat (section 5).
Crash reports
- When the app stops unexpectedly, or meets an error it can recover from, a report is sent to Sentry (section 5) so the fault can be found and fixed. It contains the error and where in the code it happened; the app version and the update it runs; technical details of the phone at that moment, such as its model, system version, memory and language and time-zone settings; and a short list of the last steps before the error — which screens were open and which services the app contacted, by name of the service and nothing after it.
- You can turn crash reports off in Profile → Settings → Your data.
- Reports are built to exclude your name, email address, account ID and journal: no meals, weights, health readings, routes or photos. An error message could rarely quote something you entered. Sentry receives your IP address, as any internet request does, and is set not to store it. A report may carry a random number Sentry makes on the phone to count how many phones a fault affects; it is not linked to your account.
- There is no session recording and there are no screenshots. Reports are sent only when something fails, and they are separate from usage data (below).
Usage data (optional, off unless you turn it on)
- Your choice, off unless you agree. You are asked on the "Before you start" screen, in a box of its own that is not ticked and is not needed to use the app; if you were already using the app, a card on Today asks once each time you sign in ("Not now" leaves it off). You can change your answer at any time in Settings → Your data → Share usage data. The app records on your phone when you answered and which version of this text you answered. Nothing is sent while it is off, and nothing that happened before you agreed is ever sent: an event is dropped at the moment it happens unless you have already said yes.
- What is sent when it is on: counts of which parts of INQON are used — the name of an event (for example "a screen was opened", "the first meal was logged", "a plan was built", "a scan was used", "the Pro screen was shown") and a few fixed details of it, each one a choice from a short list, a count, or a yes or no (for example which screen, barcode or label, monthly or yearly). With them go whether the account has Pro or is a guest, the app's language, and the time of the event.
- What is never sent: what you log or write — no food, dish or product names, no barcodes, no weights, measurements, calories or other body figures, no heart rate, no routes or places, no notes, no questions, answers or messages, no search words, no photos; and nothing that says who you are — no name, nickname, email or account ID. The app checks every event against a fixed list before it is sent and drops anything not on it.
- The only identifier is a random number made on your phone the first time an event is sent, used for nothing else in the app; it is replaced with a new one when you sign out or delete your account. It is not linked to your account, so we cannot tell which person an event came from — which also means we cannot find, show or delete one person's events on request (section 7).
- Who receives it: PostHog (section 5), on its servers in the European Union. It is set to discard your device's IP address, not to work out where you are from it, and not to build a profile of any person. No session recording and no screenshots.
- Why: to see which parts of the app help people and which get in their way, and to fix what does not work — never for advertising.
What we do not collect
No advertising identifiers, no tracking across other companies' apps or websites, no session recordings, no contacts, no microphone recordings (speech is recognised on your phone, see above), and no data from other apps beyond what you allow from Apple Health. Usage data is sent only if you turn it on (above).
The website
inqon.app is a set of static pages. It sets no cookies and remembers your light or dark choice in your own browser. It counts visits with Cloudflare Web Analytics: the page opened, the page you came from, your country (worked out from your IP address, which is not kept) and your browser and type of device. Cloudflare's script stores nothing on your device, does not fingerprint it and does not follow you to other websites. We see only totals, and nothing from the app is joined to them. To stop it, use Don’t count my visits at the foot of any page: your browser remembers that, and the script is no longer loaded. It is not loaded either when your browser sends Global Privacy Control. The site does not act on the older Do Not Track signal, because it does not follow you to other websites in the first place. Our host keeps ordinary server logs for security and troubleshooting.
2. Why we use it, and on what legal basis
Under UK and EU GDPR two things must be true before we may use data about your health: a general lawful basis (Article 6) and a separate condition for special category data (Article 9). They are set out apart below, because they are not the same thing and one does not stand in for the other.
| Purpose | Data | Article 6 basis | Article 9 condition |
|---|---|---|---|
| Running your account and syncing your journal between devices | Email, user ID | Performance of our contract with you | — |
| Signing you in by email or password, and sending the codes for it | Email address, sign-in methods, the password's hashed form | Performance of our contract | — |
| Your profile: telling accounts apart, and later showing you to people you choose | Name, nickname, profile photo | Performance of our contract | — |
| Keeping your training journal | Sessions, plans, effort, distances, shoes and their distance | Performance of our contract | Your explicit consent |
| Keeping your food diary and nutrition goals | Meals, foods, amounts, goals, day notes | Performance of our contract | Your explicit consent |
| Keeping your body measurements | Body weight, body fat, body measurements | Performance of our contract | Your explicit consent |
| Setting food targets | Year of birth, sex, height, daily activity, training load, everyday stress level, weekly pace | Performance of our contract | Your explicit consent |
| Building and adjusting your training plan around what you cannot do | The "what to avoid" note | Performance of our contract | Your explicit consent |
| Importing workouts and showing your day | Apple Health data | Performance of our contract | Your explicit consent (the Health permission) |
| Recording runs, rides and walks | Location while recording | Your consent (the location permission) | Your explicit consent |
| Reminding you to move during the day | Movement breaks and their settings | Performance of our contract | Your explicit consent |
| Keeping your assistant chats in your account | Chats, questions, answers, reminders, proposed changes | Your consent (the assistant's own consent screen) | Your explicit consent (the same screen) |
| Answering your questions in the assistant | Your question, the chat so far, the journal summary (section 4) including your own foods, saved dishes and foods logged in the last 60 days, what the phone reads back from your journal when the assistant asks for more, and a photo if you attach one | Your consent (the assistant's own consent screen) | Your explicit consent (the same screen) |
| Reading nutrition labels and plates, finding foods by barcode | Label or plate photo, barcode number | Performance of our contract | Your explicit consent |
| Answering and learning from feedback | Feedback message, app version, platform, device model, system version, language | Our legitimate interest in improving the app | Your explicit consent (the box on the feedback screen, or your written confirmation by email, if your message has health details) |
| Keeping the app up to date (over-the-air updates) | App and update version, random installation number, IP address | Our legitimate interest in an app that works and stays secure | — |
| Answering business enquiries | Name, email, company, message | Our legitimate interest in running the business | — |
| Counting visits to the website | Page, the page you came from, country, browser and type of device (section 1, "The website") | Our legitimate interest in understanding how the website is used and improving it | — |
| Finding and fixing crashes | Crash report: the error, app and phone details, the last steps before it (no account, nothing from the journal) | Our legitimate interest in an app that works | — |
| Learning which parts of the app are used | Usage events and a random install number (section 1, "Usage data") | Your consent (the Share usage data switch) | Your explicit consent (where an event name relates to health or fitness) |
| Protecting the AI features from misuse | Request counts per account; a scrambled code per network | Our legitimate interest in keeping the service affordable and available | — |
| Subscriptions | Purchase status | Performance of our contract | — |
| Applying the 18+ rule where the law requires a check | The age range Apple reports, read on the phone and not kept | Legal obligation | — |
| Meeting a legal duty: a court order or a regulator's demand, and records of rights requests, complaints and breaches | Only what that duty needs | Legal obligation | Where health data is involved, legal claims and courts (Article 9(2)(f)) or another condition the law gives |
| Bringing or defending a legal claim | Only what the claim needs | Our legitimate interest in protecting our legal rights | Legal claims and courts (Article 9(2)(f)) |
| Protecting someone's life when they cannot consent | Only what is needed | Vital interests | Vital interests (Article 9(2)(c)) |
| Passing the app to a new owner | Your account and journal | Our legitimate interest in the app continuing | Your explicit consent, asked where the law requires it, after notice in the app (section 5) |
What "explicit consent" means here. You give your explicit consent when you tick the consent box and confirm our health data and AI notice on the "Before you start" screen at the beginning of the app — which covers keeping your journal and backing it up to your account. Sending your plan settings, your "what to avoid" note, or a label or plate photo, to Anthropic needs separate consent, asked at first use; refusing keeps your journal, and you can turn it off in Profile → Settings → Your data. You also give it when you turn on a system permission (such as Apple Health, Motion & Fitness or Location), and when you accept the Ask INQON's own consent screen, which names its provider. Beyond that, nothing is taken from you in the background, and data about your health is used only for the purposes in the table above.
Withdrawing it. You can withdraw any of these consents at any time — turn the permission off in your phone's Settings (Location, Health, Motion & Fitness, Camera), turn the assistant off in Profile → Settings → Ask INQON or movement breaks off in Profile → Settings → Movement breaks, delete individual entries, or delete your account in Profile → Settings → Your data → Delete account. Withdrawal stops future processing; it does not make what was already done unlawful. Because keeping a training and food journal is the core of INQON, withdrawing your consent to the processing of your health and fitness data means we can no longer provide the journal, and you will need to delete your account.
Legitimate interests. Where we rely on legitimate interest — feedback, crash reports, the limits on the AI features and the website's visit counts — we have weighed it against your interests. Each carries little or no personal data, none is used to build a profile of you, and none is shared for any other purpose. You can object at any time (section 7). A legal claim or a change of owner (section 5) relies on it too, and is weighed when it arises, using only what it needs.
Usage data is sent only with your consent — the Share usage data switch, off unless you turn it on. Turning it off withdraws that consent: nothing more is sent.
3. Automated decisions
We do not make decisions about you solely by automated means that produce legal effects or similarly significantly affect you. The app's AI features suggest; they do not decide. A scanned label is shown to you to confirm before anything is saved, and changes to a plan follow fixed training rules written into the app rather than the model's judgement. What the assistant suggests shows on a card for you to confirm; if you turn on "Add new entries without asking" (Profile → Settings → Ask INQON), new entries go in at once with Undo, and a change or a removal still waits for you. No profiling is used to decide anything about your access, your price, or your rights.
4. Where AI is used
Your training plan itself is built on your phone, by fixed training rules written into the app. Four features send a small piece of text or one image to an AI model provided by Anthropic, through our own server, when you have a connection (the optional assistant, below, uses Anthropic too):
- Reading a nutrition label (Pro): the label photo, stripped of location and time metadata, is sent once so the nutritional values can be read from it.
- Reading a plate (Pro): a photo of a meal, stripped of location and time metadata, is sent once so the foods on it can be named and their weights estimated. Every line is shown to you to correct before anything is added, and the app says that weights from a photo are estimates.
- Understanding your "what to avoid" note: if you write an optional note about movements or soreness to work around, its text is sent so the model can match it to exercises or equipment to leave out of your plan. Without a connection, the app matches the note against keywords on your phone instead.
- Writing a short explanation of your plan: only the plan's settings are sent — goal, kinds of training, experience level, training days, session length, cycle length, split, weekly set counts and running or riding minutes. No name, no email and no health history.
Anthropic processes this data under contract, only to return the result to us, and does not use it to train its models. The app never gives medical advice and never makes a diagnosis.
Ask INQON, the assistant (optional; three questions a week free, up to 50 a day with Pro)
- The assistant answers questions about your own training, food and progress and, when you ask, adds or changes or removes entries in your journal, and saves dishes: food, sets, a workout, your weight, a movement break, your food goal, body measurements or break reminders. It can also open a screen in the app, which changes nothing. Each change shows on a card first, unless you turn on "Add new entries without asking", which applies to new entries only and leaves an Undo. Nothing is sent until you accept its consent screen, which names the provider.
What is sent, and when. Nothing is sent until you have accepted the assistant's consent screen, and then only when you ask a question (or tap "Explain this workout for me"). With each question go: your question; the earlier messages of that chat (the last few in full, older ones shortened to a line), including the lines under an answer that say whether a suggested change was applied; and a summary of your journal worked out on your phone:
- the last 14 days — for each day, whether food was logged, the day's calories, protein, fat and carbohydrate and how they compare with your goal, the number and minutes of workouts, and the title of any planned session;
- the last 12 weeks — for each week, workouts done and planned, minutes, strength sets, running and riding distance, days with food logged and average calories and protein;
- up to ten workouts from the last 14 days — date, kind, title, minutes, effort, distance, and for gym sessions the names of the exercises with their sets and best set — and, if a workout is running, its exercises and sets so far and how long it has been going;
- your best lifts — the heaviest set of up to eight exercises, with its date;
- today's meals, with the name, grams and calories of each food in them;
- your plan and goals — your training goals, training days and session length, your food goal (calories, protein, fat, carbohydrate), the plan's week, the titles of planned sessions, and today's and the next three planned sessions;
- your body — your latest body weight entered in the app and its weekly averages, and your latest body measurements and body fat, if you added them;
- your foods — up to 24 foods you can ask for by name: your saved dishes, foods you created or scanned, and foods you logged in the last 60 days, each with its name, its calories, protein, fat and carbohydrate per 100 g, and up to three of its portions (for example "1 serving 350 g");
- movement breaks, if you use them: your interval, days and hours, and this week's breaks done and due, not counting one recorded as walked instead;
- the app's language and units, the time and your time-zone offset, the screen you asked from, whether you have Pro and, without it, how many free questions are left this week; and internal numbers that point at the rows above, so the assistant can refer to one of them.
When the assistant needs more to answer, it can ask your phone, which reads it from your journal and sends back only this: one day's meals and foods with their values, workouts and weight; one workout in more detail (each set's weight and reps, the distance of each part, and whether it has a note — never the note); one exercise's sets for a period; totals of training, food and body weight for a period of up to a year; or up to eight foods matching a word, from your own foods and the app's food list, with their values per 100 g and portions.
Never sent: your name, nickname, email, account ID, profile photo, routes or places, the text of any note (workout, day or "what to avoid"), meal or shoe photos in your diary, heart rate, and anything imported from Apple Health — imported workouts, weights and body fat, steps, sleep and energy.
Guests can use the assistant in the same way, on the free weekly allowance, after accepting the same consent screen.
- A photo, only if you attach one: sent with that one question, re-encoded on your phone first so it carries no location, time or device details. It is not kept by us, and the re-encoded copy on your phone is deleted once the question is sent, and so is the temporary copy from the camera or photo picker once the clean one is made. A question with a photo counts like any other question.
- Speaking a question: recognised on your phone; only the text is sent, as if you had typed it.
- "Explain this workout for me": when you tap it, the app asks the assistant on your behalf. It sends the same summary, and with it the session on screen — its title, its week in the plan and its exercises with their sets and reps, or its minutes or distance, and whether you are on easy days or coming back after a break. It counts as one of your questions, and the answer is kept only on your phone.
- Who answers: Anthropic, using its Claude models, through our own server. Anthropic processes it for us only to write the answer, under its commercial terms, and does not use it for advertising or to train its models. To answer the next question faster, it may hold the summary for a few minutes. Before 5 November 2026, answers came from Google's Gemini model; the app asks for your permission again when this changes.
- What we keep: the fact that you gave or withdrew permission (and when), and how many questions you asked each day (with Pro) or each week (without), for the limits. Our server does not keep the summary. While sync is on your chats are stored in your account, like your journal, so they come back when you sign in and show on your other phones. They go to Anthropic only as described above, one chat at a time. You can delete a chat or all of them in the app.
- You can turn the assistant off at any time in Profile → Settings → Ask INQON. Nothing more is sent after that.
- The assistant gives general information about training and food. It is not a doctor, a dietitian or a personal trainer, and it does not give medical advice.
Protecting the AI features from misuse
To stop anyone running up the cost of these features, our server counts how many AI requests come from each account and each network, and how many invitation codes are claimed from each network. For a network we keep only a one-way scrambled code made from its address, never the address itself, and the counts are deleted after about two days. The times of your plan changes are kept in your account, without their content, to apply the free limits.
5. Who handles data for us
| Provider | What for | Where | Transfer safeguard |
|---|---|---|---|
| Supabase | Account sign-in and the sign-in emails it sends, database for your synced journal, storage for your profile photo, your assistant chats and planned routes, feedback, server functions | United Kingdom (London; operated by companies in the United States and Singapore) | Stored in the UK; UK Addendum to the EU Standard Contractual Clauses for any access or processing elsewhere |
| Anthropic | The AI features in section 4, including Ask INQON if you turn it on | United States | UK International Data Transfer Agreement / EU Standard Contractual Clauses |
| Sentry | Crash and error reports (no account ID, nothing from your journal; section 1) | European Union (operated by a US company) | UK adequacy regulations (EEA); UK Addendum to the EU Standard Contractual Clauses |
| PostHog | Usage events with a random number, only if you turn on Share usage data (section 1) | European Union (PostHog's EU cloud, Frankfurt; operated by a US company) | UK adequacy regulations (EEA); UK Addendum to the EU Standard Contractual Clauses |
| RevenueCat | Subscription status. The app identifies itself to RevenueCat with your user ID, guests included, whether or not you buy | United States | UK International Data Transfer Agreement / EU Standard Contractual Clauses |
| Apple | Sign-in; payment, as the seller of the subscription; the age check (section 1); Apple Maps, which draws the map and receives the map area shown and your device's IP address | Their own terms apply | Their own safeguards |
| Sign-in, if you choose it | Their own terms apply | Their own safeguards | |
| Open Food Facts | Looking up a scanned barcode (Pro). Your phone connects to Open Food Facts directly and sends only the barcode number (never in-store codes), a short app label in the request header, and your device's IP address, as any internet request does. Never account data, your name or journal entries. Products found are kept on your phone. | France (open database) | UK adequacy regulations (EEA) |
| Expo | Delivering app updates: the phone asks whether a newer version exists, sending a random installation number made for this, the app's version and current update, and its IP address, as any internet request does. Never account data or journal entries | United States | UK Extension to the EU-U.S. Data Privacy Framework |
| Cloudflare | Serving the inqon.app website and counting its visits | Global network | UK International Data Transfer Addendum |
| Resend | Sending sign-in emails (codes, address and password confirmations). Holds your address and the email's text for 30 days | Sent from Ireland; records kept in the United States | UK Addendum to the EU Standard Contractual Clauses |
| Google (Workspace / Gmail) | The notice before an unused account is deleted, feedback notes, and holding mail you send to support@inqon.app and partners@inqon.app | United States and other countries where Google processes data | UK Addendum to the EU Standard Contractual Clauses |
Local food database (USDA). The core list of 378 basic foods comes from the public-domain USDA Standard Reference Legacy dataset (CC0) and is built into the app. Searching it happens entirely on your phone and never sends a request to the USDA or anyone else.
Supabase, Anthropic, Sentry, PostHog, RevenueCat, Resend, Expo, Cloudflare and Google Workspace act on our instructions under a written contract. Expo also uses device information from update checks (IP address, crash traces) on its own account, for aggregate trend analysis, as an independent controller. Apple, Google sign-in and Open Food Facts are independent and follow their own terms. Data sent to the European Economic Area is covered by the UK's adequacy regulations. Where data goes elsewhere, we rely on the UK International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses, together with the checks those require; for Expo, on the UK Extension to the EU-U.S. Data Privacy Framework. You can ask us for a copy of the safeguard used for any transfer — write to support@inqon.app.
We do not sell or rent personal data, we do not share it for advertising, and no provider acting on our instructions is permitted to use your data for its own purposes.
When the law requires it. We disclose data to a court, the police, a regulator or anyone else only where the law requires it, or where it is needed to protect someone's life or safety or to bring or defend a legal claim. We check that a request is valid, give only what it requires, and tell you first unless the law stops us or telling you would put someone at risk. What stays only on your phone is not ours to give.
If the app changes hands. If INQON moves to someone else, whether a buyer or a company set up to run it, your account and journal may move with it, and whoever takes over must keep to this policy. We will tell you in the app first, in time for you to export your journal or delete your account.
6. How long we keep it
- Your journal and account: for as long as you have an account.
- An entry, chat or planned route you delete: it disappears from the app on all your phones. A deleted activity loses its route, notes and times on our servers as soon as the deletion reaches them. The record stays, marked as deleted, for 30 days so your other phones learn it is gone, and is then removed for good (from encrypted backups within a further 30 days). A phone that stays offline for longer keeps showing the entry until you delete it there too.
- When you delete your account: it is removed from our live systems immediately (if a file cannot be removed at that moment, the nightly job removes it), and from our encrypted backups within 30 days, when the backups that contain it expire. Backups cannot be edited one record at a time, which is why deletion from them takes as long as it does. RevenueCat keeps your subscription record, under your user ID, until you ask us to have it deleted; Apple keeps its own purchase records.
- If you stop using the app: we delete an account that has not been opened with a connection or signed in to for 24 months, along with everything in it and its profile photo. If the account has an email address, we send a notice to that address at least 30 days before, and opening the app or signing in keeps it; an account with no address is deleted at 24 months. An account with an active Pro subscription is not deleted for this reason. A guest account follows its own rule, below.
- A guest account: deleted, with the journal stored with it on our servers, after 30 days in which the app is not opened on its phone (an opening with no connection does not reach us and does not count); the app reminds you before then. Because a guest has no address to write to, we do not write first. What is on the phone stays until you sign out or delete the app.
- Feedback: until the issue is dealt with, and no longer than 24 months, in our database and our support inbox. If you delete your account, notes sent from it are deleted with it. Copies in our inbox, and a note sent without an account, are deleted when you ask.
- Business enquiries: for as long as the conversation is active, and no longer than 24 months after the last message.
- Label photos, plate photos, photos attached to the assistant, and AI requests: not stored on our servers once the answer is returned. Under its commercial terms, Anthropic does not use what is sent to it to train its models, and keeps API inputs only for a limited period for safety and abuse monitoring (or where required by law) before deleting them. To answer the next question faster, it may hold the summary for a few minutes.
- Your profile photo: until you remove it, or your account is deleted by you or under the rules above.
- The assistant: the record of when you gave or withdrew permission, the question counts and, while sync is on, your chats, for as long as you have an account or until you delete them; a deleted chat loses its words on the phone at once and on our servers when the phone next syncs, and its empty record after 30 days.
- Invitations: the record of who invited whom goes when either account is deleted. An offer code given to you stays on our list, without your account, so that it is not given twice.
- Crash reports: no longer than 90 days.
- Usage data: 12 months in PostHog, then deleted. Because the events carry no account ID, they cannot be picked out and deleted with your account; turning the switch off stops new ones.
- Requests and complaints you send us: 24 months after they are closed; a short summary without health details for up to 6 years, if needed for legal claims.
- If the law requires us to keep something, or we need it for a legal claim: we keep only that, for only as long as needed, even where a period above would otherwise have ended.
- On your phone: until you sign out (the journal, routes included, is then removed from that phone and comes back from your account when you sign in again. Signing out first sends anything still waiting; if something could not be sent — no connection, or sync turned off — the app says so and asks before removing it. Routes that had not reached your account, with the rest times of their sessions, are kept on that phone, encrypted and under that account, so they are not lost; they are put back, and sent to your account unless you have turned sync off again, when the same account signs in on that phone again, another account cannot read them, and deleting the account removes them. A guest account cannot sign in again, so its routes stay encrypted on the phone until you delete the app. Meal and shoe photos, kept only on the phone, stay there under that account in the same way, as do chats and planned routes not yet sent; a guest's photos are removed), until you delete your account in the app (which wipes the phone, routes included), or until you delete the app.
7. Your rights
- Delete your account: Profile → Settings → Your data → Delete account. This removes your account and the journal stored with it from our servers and wipes the app's data on the phone. If you signed in with Apple, we ask Apple to revoke the app's link to your Apple ID at the same time, so it no longer appears under the apps using your Apple ID. It cannot be undone.
- Export your data: Profile → Settings → Your data → Export gives you a JSON file of your journal: your profile, goals, plans and their changes, sessions with their routes, body measurements, foods, meals, day notes, shoes, movement breaks, your own exercises, assistant chats and planned routes. Photos, a few settings and invitation records are not in the file; write to support@inqon.app for those.
- Under UK and EU GDPR you can ask to access your data, correct it, delete it, restrict or object to its use, and receive it in a portable form. Where we rely on consent you can withdraw it (section 2).
- Your right to object: you can object at any time to processing based on legitimate interests. Write to support@inqon.app.
- Providing this data is not a legal requirement; without it, the feature using it cannot work.
- Write to support@inqon.app. We answer within one month, and will tell you if we need longer because a request is complex. There is no charge unless a request is manifestly unfounded or excessive. A guest account has no email or name, so we may not be able to tell from a message which account is yours: delete and export in the app, as above.
- Usage data: turn it off in Profile → Settings → Your data → Share usage data, and nothing more is sent. The events already sent carry no account ID or name, so we cannot tell which are yours to show you or delete them (UK GDPR Article 11); they are deleted when their retention period ends (section 6).
- We may ask you to confirm who you are before we act, so that nobody else can reach your data by asking for it.
If you are unhappy with how we handled your data, please tell us first at support@inqon.app. We will acknowledge your complaint within 30 days, look into it without undue delay, and tell you what we find. You can also complain at any time to the UK's Information Commissioner's Office — ico.org.uk/make-a-complaint, helpline 0303 123 1113 — or, if you are elsewhere, to the data protection authority where you live.
8. Security
Data travels over encrypted connections. In our database every row is tied to the account that owns it and is protected by row-level security, so one account cannot read another's — a rule enforced by the database itself rather than by the app asking nicely. The key that could bypass it exists only on our server and is never in the app. Access to our systems is limited to the people who run and repair the service, who look at your data only to answer a request from you, fix a fault, keep the service secure or do what the law requires. No system is perfectly secure; if a breach is likely to put you at risk we will tell you and the Information Commissioner's Office within the time the law allows.
9. Children
The app is not for anyone under 18, and we do not knowingly collect their data. If you believe a child has given us data, write to support@inqon.app and we will delete it.
10. Changes
If we change this policy in a way that matters, we will say so in the app before the change takes effect. The date at the top shows the current version.
11. California
This section is for residents of California and uses the words the CCPA, as amended by the CPRA, uses. It describes the same handling as the rest of this policy.
Categories collected in the last 12 months: identifiers (email address, user ID, name, nickname, city, bio and profile photo); commercial information (subscription status); internet or network activity (crash diagnostics, and — only if you turn on Share usage data — counts of which parts of the app are used); geolocation data (while you record an activity, and on the phone only to centre the map; the route is kept with your journal, on your device and in your account); and health and fitness information (training, food, body measurements, and anything imported from the health store).
Sources: you, your device, and Apple or Google when you sign in or subscribe.
Purposes: running the app and your account, the features you ask for, support, and fixing faults.
Disclosures and retention: we disclose these categories only to the service providers listed in section 5 to run the app for you, and as section 5 says where the law requires it, and we keep each category for the periods set out in section 6.
Sensitive personal information. Health and fitness information and precise geolocation are sensitive personal information. We use them only to provide the app to you — one of the purposes Section 7027(m) of the CCPA regulations allows without an opt-out — and never to infer anything about your character or preferences. We do not use or disclose them for any other purpose, so the "Limit the Use of My Sensitive Personal Information" right does not arise.
We do not sell your personal information and we do not share it for cross-context behavioural advertising. We have not done so in the last 12 months, and we do not do it with the data of anyone under 16.
Your rights: to know what we collect and why, to a copy of it, to correct it, and to delete it. Exercise them in the app (Profile → Settings → Your data → Export or Delete account) or by writing to support@inqon.app. We will not discriminate against you for asking. You may use an authorised agent; we will ask for proof of their authority.
12. Washington, Nevada, Connecticut and other US states
Training, food, body measurements and anything read from the health store are consumer health data under Washington's My Health My Data Act and Nevada's SB 370. How we handle them, and the rights those laws give you, are set out in our separate Consumer Health Data Privacy Policy, as those laws require.
Connecticut residents may access, correct, delete or obtain a copy of their personal data, revoke consent and appeal; write to support@inqon.app. We do not use or sell personal data to train large language models, and our AI provider may not train on it under its terms.
If you live in another state with a consumer privacy law, such as Colorado, Delaware, Iowa, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Tennessee, Texas, Utah or Virginia, you can ask the same of us in the same way, and appeal a refusal by replying to our answer. We do not sell personal data, use it for targeted advertising or use it for profiling that decides anything about you, so there is nothing of that kind to opt out of.
13. Contact
Yevhenii Sereda Lytchett House, 13 Freeland Park, Wareham Road, Poole, Dorset BH16 6FA, United Kingdom support@inqon.app