Privacy Policy

Last updated: October 25, 2026

Data controller

Sebastian Ślączka

Tax ID (NIP) 9880296433

1. Who we are (Controller)

The data controller for personal data processed through the Airon web and mobile application is the person named at the top of this document ("we"). Contact: support@airon.coach.

2. What we collect

  • Account data — email address and display name, provided when you sign in.
  • Profile data — age, gender, height, weight, goals, activity level, dietary preferences and language — all optional and entered by you.
  • Training data — workouts, exercises, sets, cardio activities, plans and body measurements you log.
  • Nutrition data — meals, portions, water intake, supplements, recipes, shopping lists and any food photos you upload.
  • Camera & photos — meal, fridge and progress photos you choose to capture or upload, and camera access for barcode scanning. The camera is active only while those features are open.
  • Voice & audio — when you tap the microphone to dictate in a chat or to log by voice, your speech is transcribed into text — usually directly in the browser; if browser dictation is unavailable, the recording is sent to our transcription service, which runs through Base44 (section 6). The text of a voice log is then read by OpenAI through OpenRouter (section 6). Recording starts only when you press the microphone button.
  • Content you create — chat messages with the assistant, team messages, posts, comments and support tickets.
  • Error reports — when something crashes, we automatically send the error message, the technical stack trace, the name of the screen where it happened (never the query string or any ID in the address), your screen size and browser version. So that the report can be acted on, it also carries the app version, whether the app was running in a browser or inside an app, the app language, your account type (athlete, coach or admin) and plan, a pseudonymous account code (derived from your account ID so that we can find your reports if you tell us something broke — it is not your name or email), a random code for that visit, whether your device was online, the names of the last 10 screens you opened and the internal names of the buttons you tapped there (never their labels or anything you typed), and the names and error codes of the last 3 requests to our servers that failed. This contains no screen recording, no screenshot, nothing you typed and none of your training, nutrition or health data, and nothing is stored on your device to do it. It runs for everyone, because a diagnostic report is our legitimate interest in keeping the app working (section 4) — not something we ask cookie consent for. We remove email addresses and tokens from these reports before they are sent.
  • Technical data — application logs (errors, actions) and analytics events — analytics only if you consent to analytics cookies.
  • Push notifications (iPhone app) — if you allow notifications in the iPhone app, we store the push token of your device with its language, time zone and app version, so that we can tell you about a new message from your coach or a reminder. Apple (Apple Push Notification service) delivers the notification, and it carries only generic text such as "New message from your coach" — never the message itself, a name, or any training, nutrition or health data; the app shows the content after you open it. You can turn notifications off at any time in your iPhone settings, and signing out unlinks the device. The token is deleted with your account; a technical log of sent notifications, linked to your account (type, result and internal record ids only, no content), is kept for 30 days and removed in a weekly clean-up.
  • Funnel counts — when you finish a sign-up step — completing onboarding, asking to join or joining a team, or generating your first plan — our server records a count of that step: which step, which path (athlete, coach or team invite) and how old the account is in broad bands (under a day, a week, a month, older). The count holds no name, email, account ID, team or device details, and nothing is read from or stored on your device to make it. It is our legitimate interest in seeing where people get stuck signing up (section 4), so it is counted whether or not you accept analytics cookies. Each count is deleted after 13 months.
  • Payment data — handled entirely by our payment providers; we store only the subscription status and a provider customer id, never card numbers.

3. Health-related data (special category)

Weight, body measurements, nutrition and training logs can reveal information about your health. We process this data only on the basis of your explicit consent, given by choosing to enter it, and only to deliver the features you use. You can withdraw consent at any time by deleting the data or your account.

4. Why we process it (legal bases)

  • Contract (Art. 6(1)(b)) — to provide the app: storing your logs, plans, teams and coaching features.
  • Consent (Art. 6(1)(a), Art. 9(2)(a)) — health-related data, analytics cookies, optional messaging channels (Telegram) and marketing emails.
  • Legitimate interest (Art. 6(1)(f)) — security, abuse prevention, error logging and counting how many people complete each sign-up step.
  • Legal obligation (Art. 6(1)(c)) — accounting records for paid subscriptions.

5. AI processing

When you use AI features (chat with the assistant, the assistant on Telegram, voice logging, plan generation, photo meal analysis, fridge analysis, progression forecasts), the relevant content — your message and a limited context of your recent training and nutrition data — is sent to the AI providers named in section 6 to generate a response. It is not used to train public models. AI output is informational only and is never medical advice.

  • Who receives it — Base44 (our platform and AI gateway); Anthropic (Claude) and Google (Gemini) for the assistant chat and meal analysis; OpenRouter, which routes voice logging and the assistant on Telegram to OpenAI (GPT), and progression forecasts to DeepSeek; and ElevenLabs for spoken workout cues. What each one receives, and why, is in section 6.
  • You are talking to an AI — the assistant chat in the app and the assistant on Telegram are AI systems, not human coaches, and they say so in the chat itself (EU AI Act Art. 50).
  • AI-generated content — plans, meal estimates, fridge suggestions and the assistant's replies are generated automatically. They can be inaccurate or incomplete — always check anything that affects your health.
  • Human coaches are separate — messages with a real coach or team happen in team chat and direct messages, which are never answered by AI on your coach's behalf.
  • No automated decisions about you — we do not use AI to make legally significant decisions about you, and no emotion recognition or biometric categorisation is performed.

6. Who we share data with (processors and recipients)

  • Base44 — application hosting, database, file storage and the AI gateway: it relays the assistant's and the AI features' requests to the model providers below and selects the model itself for some features, including AI features (for example speech-to-text for dictation, and meal or plan analysis) that Base44 runs for us through its own model providers. It stores Airon's data on servers in the United States.
  • Anthropic (Claude) — AI model provider for the assistant chat, reached through Base44. It receives your messages, any photo you attach, and the limited context of your training and nutrition data the assistant needs to answer.
  • Google (Gemini) — AI model provider. It analyses the meals you describe (through Base44), can power the assistant chat when we select a Gemini model, and can serve features behind OpenRouter when we select it. It receives the content of the feature it serves.
  • OpenRouter — AI model routing for voice logging, the assistant on Telegram (including preparing its context) and progression forecasts. It passes each request to the model selected for that feature, whose provider then receives it: today OpenAI (GPT) for voice logging and the assistant on Telegram, and DeepSeek for progression forecasts (an exercise name and your recent sessions of it). If we select a different model for a feature, that model's provider receives the request instead, and we update this section.
  • OpenAI (GPT) — AI model provider, reached through OpenRouter. For voice logging it receives everything you say or photograph there: entries (workouts, meals, water, body weight, habits), app commands, questions it answers, and any message you dictate to a client, with that client's name. With it go your exercise, habit and supplement names, the running workout's exercises with their last set, your last body weight, today's water and calorie totals, entries still waiting for your confirmation, and today's date. We do not attach your name, email address or account identifier. It also runs the assistant on Telegram and prepares its context: your message and recent conversation, your profile (goal, body data, nutrition targets, coaching notes), facts the assistant has saved about you, and the records it selects; for a coach, also clients' names and email addresses and the records of the client asked about.
  • ElevenLabs — text-to-speech for spoken workout cues in the workout player. It receives only the short phrase to be spoken (an exercise name and a time, for example "Plank. 30 seconds."), never your account details; the generated audio is stored and reused.
  • Cloudflare (AI Gateway) — and the model it routes to: used only by an internal administrator tool that matches exercise names people typed to our exercise library. They receive the exercise names only — no personal data, no account identifier and no other account data. They are not recipients of your account data.
  • Stripe / PayU — payment processing for subscriptions and top-ups.
  • Email and messaging providers — transactional email and, if you connect it, Telegram.
  • Analytics — consent-gated Google Analytics 4 and Base44 platform analytics, loaded only after you accept analytics cookies (where applicable).
  • AI assistants you connect yourself — if you mint an API token, pair an assistant, or approve an app at /AuthorizeApp (for example ChatGPT, operated by OpenAI; Claude, operated by Anthropic; or a script of your own), everything the connection permits is sent to whoever operates that assistant, each time it asks. Depending on the permissions you tick, that is: your profile (first name, goal, units, height, weight, age, gender, activity level, diet type and daily targets; not your email address); your workouts and planned sessions (dates, completion times, titles, sport, total volume and notes) and their sets (exercises, activity type, reps, weights, RPE, rest, durations, distances, heart rate, power, pace, elevation, superset labels, whether each set was done, and notes); your meal entries (dates, meal types, names, calories and macros); and your body measurements, including the dates and notes of progress-photo entries. The write permissions also let it log workouts, meals, water and measurements, edit workouts, remove workouts and measurements (removed ones are archived and hidden, not erased) and permanently delete meal entries. An app you approve at /AuthorizeApp never receives progress photos; a token you mint or an assistant you pair receives their image links only if you grant it the photo permission, and anyone who holds such a link can open the image. They are recipients you chose rather than processors acting for us (a different role from any AI model provider listed above, even where it is the same company), so their own privacy terms govern what they then do with it; section 5 does not cover them, so whether they train models on it is set by their terms and your settings with them. Their operators may be outside the EEA (OpenAI and Anthropic are in the United States); the data goes there because you send it there. We keep a record of each call a connection makes (which connection, the tool, the time, whether it worked, and a shortened copy of what was sent and returned, such as a measurement value, the first 120 characters of a note, or record titles and dates), so that what an assistant did in your account can be traced. The record is kept for 30 days and removed in a weekly clean-up; it is part of your data export (section 9) and is deleted with your account. Every connection made this way is listed and revocable at /ApiAccess.
  • Apple (Apple Push Notification service) — delivers the notifications of the iPhone app, if you allow them. It receives the push token of your device and the notification itself, which carries only generic text such as "New message from your coach" — never a message, a name, or any training, nutrition or health data (section 2).

We never sell your personal data. Transfers of personal data to our processors outside the EEA rely on the EU Standard Contractual Clauses.

7. Coaches and teams

When you join a team as an athlete, the team's owner and trainers ("your coaches") get access to your data so they can coach you. This applies to coaching teams and community teams alike. Before you join, the app shows you what they will be able to see and change and asks you to confirm it by ticking a box.

  • What they can see — your workouts, training calendar and cardio, your nutrition log, your body measurements and progress photos, your strength goals and your habits; your profile details, including age, gender, height, weight, goals, diet settings and any health notes you entered; the answers you give in the team's intake and check-in forms; your messages with them; and when you last trained.
  • What they can change — by default they can create, plan and edit your workouts and training calendar, and edit your nutrition log and meal plans. Through Airon's coach assistant (for example in Telegram), a coach can also log entries such as meals, workouts or body measurements for you. What the coach assistant on Telegram reads about you to answer your coach is sent to OpenAI through OpenRouter (section 6).
  • Your switches — Settings → Privacy & Safety → Coach access lists each team you belong to as an athlete, with a switch for each of these permissions. You can turn any of them off at any time, and a switch you turn off stays off. The switches control only some of the coach views: your profile details, form answers and messages stay visible to the team's owner and trainers while you are a member, the coach's calendar still shows your workouts and meals, and Airon's coach assistant still reads your workouts, meals and body measurements when a switch is off.
  • Leaving a team — leaving the team ends its owner's and trainers' access to your account through the team from then on. They keep what they already have: your messages with them, the form answers you submitted to the team, and the workouts and plans they created for you, including results you later log on those plans.

8. How long we keep it

We keep your data for as long as your account exists. Data held in accounts that have been inactive for an extended period may be removed, or reduced in detail, to preserve storage; we give reasonable advance notice to your account email before that happens, and signing in again resets the inactivity period. You can export your data at any time (section 9). When you delete your account, your personal data and content are deleted; anonymised or aggregated records and legally required accounting records may be retained. Application error logs are kept for a limited period for security and debugging. Funnel counts (section 2) are not tied to your account, so they are not removed with it; each is deleted after 13 months.

  • Files you upload — on a Free plan account we may remove them under section 6 of the Terms of Service: case by case, never automatically, after at least 30 days' notice and with a way to download them. On a paid plan we keep them for as long as the plan is active.

9. Your rights

You have the right to access, rectify, erase, restrict and object to processing, and the right to data portability and to withdraw consent at any time.

  • Export — available in the web app (airon.app → Settings → Privacy & Safety → export your data, a machine-readable file) or by email to support@airon.coach.
  • Delete — Settings → Privacy & Safety → Danger Zone → delete account, which removes your data. Public instructions: https://airon.app/AccountDeletion
  • Complaint — you may lodge a complaint with your supervisory authority (in Poland: Prezes Urzędu Ochrony Danych Osobowych, uodo.gov.pl).

10. Cookies

We use essential cookies and local storage to keep you signed in and remember your preferences — these are always on because the app cannot work without them. Analytics cookies and the support widget load only if you accept them in the cookie banner, and you can change your choice at any time. Automatic error reports and funnel counts (section 2) are not covered by this choice, because sending one stores nothing on your device and reads nothing from its storage — no cookies, no local storage.

11. Children

The Service is not intended for children under 16. We do not knowingly collect data from children; if you believe a child has provided us data, contact us and we will delete it.

12. US State Privacy Rights

If you live in a US state with a privacy law (e.g. California, Virginia, Colorado, Washington), the rights in section 9 apply to you, and in particular:

  • We do not sell your personal data, and we do not share it for cross-context behavioral advertising.
  • Consumer health data — we collect health-related data only with your consent, only to provide the features you use, and we never sell it. You can withdraw consent and delete this data at any time (Settings → Privacy & Safety → Danger Zone → delete account).
  • We do not discriminate against you for exercising any of your privacy rights.

13. Changes and contact

We may update this policy; material changes will be announced in the app. Questions or requests: support@airon.coach. See also our Terms of Service.

We use cookies for sign-in, analytics and core features. Privacy Policy