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 Sereda
Lytchett 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

Your journal (stored on your phone and in your account)

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

Age check

Location

Apple Health (optional)

Steps counted by your iPhone (optional)

Evening walking reminder (optional)

Health data is never used for advertising

Camera

Microphone and speech recognition (optional)

Calendar (optional)

Feedback

Business enquiries

Purchases

Crash reports

Usage data (optional, off unless you turn it on)

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.

PurposeDataArticle 6 basisArticle 9 condition
Running your account and syncing your journal between devicesEmail, user IDPerformance of our contract with you—
Signing you in by email or password, and sending the codes for itEmail address, sign-in methods, the password's hashed formPerformance of our contract—
Your profile: telling accounts apart, and later showing you to people you chooseName, nickname, profile photoPerformance of our contract—
Keeping your training journalSessions, plans, effort, distances, shoes and their distancePerformance of our contractYour explicit consent
Keeping your food diary and nutrition goalsMeals, foods, amounts, goals, day notesPerformance of our contractYour explicit consent
Keeping your body measurementsBody weight, body fat, body measurementsPerformance of our contractYour explicit consent
Setting food targetsYear of birth, sex, height, daily activity, training load, everyday stress level, weekly pacePerformance of our contractYour explicit consent
Building and adjusting your training plan around what you cannot doThe "what to avoid" notePerformance of our contractYour explicit consent
Importing workouts and showing your dayApple Health dataPerformance of our contractYour explicit consent (the Health permission)
Recording runs, rides and walksLocation while recordingYour consent (the location permission)Your explicit consent
Reminding you to move during the dayMovement breaks and their settingsPerformance of our contractYour explicit consent
Keeping your assistant chats in your accountChats, questions, answers, reminders, proposed changesYour consent (the assistant's own consent screen)Your explicit consent (the same screen)
Answering your questions in the assistantYour 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 oneYour consent (the assistant's own consent screen)Your explicit consent (the same screen)
Reading nutrition labels and plates, finding foods by barcodeLabel or plate photo, barcode numberPerformance of our contractYour explicit consent
Answering and learning from feedbackFeedback message, app version, platform, device model, system version, languageOur legitimate interest in improving the appYour 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 addressOur legitimate interest in an app that works and stays secure—
Answering business enquiriesName, email, company, messageOur legitimate interest in running the business—
Counting visits to the websitePage, 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 crashesCrash 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 usedUsage 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 misuseRequest counts per account; a scrambled code per networkOur legitimate interest in keeping the service affordable and available—
SubscriptionsPurchase statusPerformance of our contract—
Applying the 18+ rule where the law requires a checkThe age range Apple reports, read on the phone and not keptLegal obligation—
Meeting a legal duty: a court order or a regulator's demand, and records of rights requests, complaints and breachesOnly what that duty needsLegal obligationWhere health data is involved, legal claims and courts (Article 9(2)(f)) or another condition the law gives
Bringing or defending a legal claimOnly what the claim needsOur legitimate interest in protecting our legal rightsLegal claims and courts (Article 9(2)(f))
Protecting someone's life when they cannot consentOnly what is neededVital interestsVital interests (Article 9(2)(c))
Passing the app to a new ownerYour account and journalOur legitimate interest in the app continuingYour 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):

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)

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:

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.

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

ProviderWhat forWhereTransfer safeguard
SupabaseAccount 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 functionsUnited 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
AnthropicThe AI features in section 4, including Ask INQON if you turn it onUnited StatesUK International Data Transfer Agreement / EU Standard Contractual Clauses
SentryCrash 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
PostHogUsage 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
RevenueCatSubscription status. The app identifies itself to RevenueCat with your user ID, guests included, whether or not you buyUnited StatesUK International Data Transfer Agreement / EU Standard Contractual Clauses
AppleSign-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 addressTheir own terms applyTheir own safeguards
GoogleSign-in, if you choose itTheir own terms applyTheir own safeguards
Open Food FactsLooking 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)
ExpoDelivering 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 entriesUnited StatesUK Extension to the EU-U.S. Data Privacy Framework
CloudflareServing the inqon.app website and counting its visitsGlobal networkUK International Data Transfer Addendum
ResendSending sign-in emails (codes, address and password confirmations). Holds your address and the email's text for 30 daysSent from Ireland; records kept in the United StatesUK 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.appUnited States and other countries where Google processes dataUK 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

7. Your rights

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