LEGAL
Privacy Policy
Last updated: 31 October 2026 · Applies to the Android app com.atemhybrid.app and this website
Contents · 8 sections ▾
1. Controller
The controller for the processing of personal data under the General Data Protection Regulation (GDPR) is:
ORION Systems, owner Christian Müller
Weißer Hauptstraße 30
50999 Köln
Germany
Email: kontakt@orion-systems.de
Contact form: Contact
ATEM Hybrid is offered by ORION Systems. It is not connected to any employer of the owner.
2. What data is processed
ATEM Hybrid processes only what the app needs to work. There is no usage analytics, no advertising, and data is never sold or passed on for marketing.
| Data | Purpose | Legal basis |
|---|---|---|
| Google account: user ID, email address, display name, profile picture | Sign-in, linking training data to the account, blocking accounts in case of abuse | Art. 6(1)(b) GDPR (performance of a contract) |
| Training data: completed sessions, exercises, sets, repetitions, weights, duration, distance, notes, perceived exertion | The core function: logging and evaluating training | Art. 6(1)(b) GDPR |
| Body weight | Calculating training load for bodyweight exercises. Without it the calculation would produce wrong numbers. | Art. 6(1)(b) GDPR |
| Settings: language, unit system, appearance, default rest timer, pointers on or off, weight step per exercise | Adapting the app to your preferences | Art. 6(1)(b) GDPR |
| Training details, voluntary during setup or in settings: goals, type of training, where you train, equipment at home or in the gym, training week | Suggesting fitting plans, calendar and pointers | Art. 6(1)(b) GDPR |
| Nutrition, only after your own consent in the app: entries (food or brand, amount, time, calories, protein, carbohydrates, fat), favourites, chosen goal as well as year of birth, height and formula value (female, male, not specified); water drunk (amount, time) and the water goal | Showing intake next to expenditure; calculating basal metabolic rate and — only with a chosen goal — a corridor around expenditure; showing water drunk next to your usual day or your goal | Art. 9(2)(a) GDPR (explicit consent, see below) |
| AI features for nutrition, only after your own consent in the app: a photo of a plate, a menu or a recipe, a text you write; for suggestions what is left of today, the kind of goal, "I don't eat" and names and usual amounts of your own foods and meals (details under AI features) | Recognising items and amounts or suggesting a meal, which you check before saving | Art. 9(2)(a) GDPR (explicit consent, see AI features) |
| ATEM AI, only after your own consent in the app: your questions, the answers and the facts the app computes for them from your training, plan and body data (details under ATEM AI) | Answer questions about training, nutrition and your numbers, suggest or draft plans that you review before saving | Art. 9(2)(a) GDPR (explicit consent, see ATEM AI) |
| Reports of AI answers, only if you tap “Report”: reason, question or text, answer, note (details under Reporting AI answers) | Find and fix wrong, offensive or harmful AI answers | Art. 6(1)(a) and Art. 9(2)(a) GDPR (consent by sending, see Reporting AI answers) |
| Journal, only after your own consent in the app: tags per evening (e.g. alcohol with amount, stress, sick, medication, period — only if switched on), tags explicitly answered no, optionally one sentence (details under Journal) | Note what a day was like and show what went along with your next morning or next session | Art. 9(2)(a) GDPR (explicit consent, see Journal) |
| Purchase data for ATEM Pro: product, time, term and status of the purchase, the Google Play receipt, country and currency; also the account identifier as the RevenueCat identifier and the "early" flag (account from before Pro launched), details under ATEM Pro | Processing the purchase, checking the unlock, offering the thank-you price | Art. 6(1)(b) GDPR (contract) |
| Technical connection data (IP address, timestamp) arising when the servers are accessed | Operating and securing the infrastructure | Art. 6(1)(f) GDPR (legitimate interest in a working, abuse-resistant service) |
Health-related data
Body weight and training data may allow conclusions about physical condition and can therefore qualify as health data under Art. 9 GDPR. They are processed solely to deliver the function the user asked for, are not analysed further and are not disclosed. Entering them is voluntary, though using the app requires it.
Nutrition and water are a separate, optional area. What someone eats and drinks is health data; ATEM Hybrid only processes it after explicit consent in the app (Art. 9(2)(a) GDPR). One consent covers both. Before that, no nutrition or water data is read or stored. You can withdraw consent at any time under Settings › Nutrition; withdrawing deletes all your own nutrition and water entries, the goal and the details on year of birth, height and formula.
Data from Health Connect
If you choose to, ATEM Hybrid reads data from Health Connect (Android). Each data type is granted separately; you can revoke access at any time in the Health Connect settings or in the app.
| Data type | Purpose | Stored? |
|---|---|---|
| Workouts (type, start, end, device), heart rate during the workout, distance, calories | Importing workouts from your watch, time per heart-rate zone | Yes, in Cloud Firestore: workout figures, heart rate as a distribution and a curve |
| Steps | Showing today's steps next to your usual day (median of the last 28 days); also technically required to read workouts | No — read again on every open, no copy kept |
| Body weight (read and write) | Weight history; your own entries are written back to Health Connect | Yes, in Cloud Firestore |
| Resting heart rate, heart rate variability, sleep, body fat | Comparison with your own range ("Body" section, readiness) | No — read again on every open, no copy kept |
| Nutrition and water from other apps (read; only after consenting to nutrition) | Showing and counting other apps' entries next to your own | No — read again on every open, no copy kept |
| Active energy burned, basal metabolic rate, total energy burned | The day's expenditure from your watch instead of an estimate | No — read again on every open, no copy kept |
| Nutrition and water (write; only when switched on under Settings › Nutrition) | Passing your own entries to Health Connect so other apps can see them; edits and deletions follow | The entries are kept in Cloud Firestore; the copy in Health Connect is managed by Health Connect |
In addition, the answers of the optional check-in (sleep, energy, soreness on a scale of 1 to 5) are stored in Cloud Firestore.
The legal basis for this health data is explicit consent under Art. 9(2)(a) GDPR, given by granting access in Health Connect or by filling in the check-in. You can withdraw it at any time with effect for the future.
ATEM Hybrid's use of information received from Health Connect adheres to the Health Connect Permissions policy, including the Limited Use requirements: the data serves only the functions listed above, is not used for advertising, not sold and not shared with third parties.
3. Where the data is stored
ATEM Hybrid uses Google services as processors under Art. 28 GDPR:
- Firebase Authentication — signing in with a Google account.
- Cloud Firestore — storing training, profile and settings data.
The provider is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland.
Storage location: eur3 (European Union). This project's
Firestore database is pinned to the eur3 multi-region, so training
data is stored within the EU.
Access from third countries cannot be entirely ruled out in technical terms, for example during Google support or maintenance. Google bases such transfers on the European Commission's Standard Contractual Clauses and the EU-US Data Privacy Framework.
Crash reports
If the app crashes or hits an unexpected error, it sends a crash report to Firebase Crashlytics (Google, processor as above). The report contains the technical stack trace, device model, Android and app version, free memory, the time and a random Crashlytics installation ID. It contains no account ID, no email address and no training, health or nutrition data. Crashlytics also processes reports in the USA (safeguards as above: Standard Contractual Clauses and the EU-US Data Privacy Framework) and deletes them after 90 days. The sole purpose is finding and fixing bugs; the legal basis is Art. 6(1)(f) GDPR (legitimate interest in a working app). You can turn this off at any time in the app under Settings › Your data › "Send crash reports", or object via the contact form.
Usage counts
To see where getting started with the app gets stuck, the app counts a few steps as daily totals: new accounts; on which day the app was opened, including whether an account comes back after one, seven or 30 days; the onboarding steps, answered or skipped; saved workouts, including the first and the third; completed and skipped check-ins; imports from other apps and how often the ATEM Pro page was opened. Only one number per day and step is stored in Firebase Firestore (Google, processor as above), without account ID, device ID, time of day or content. So that only signed-in accounts can count, the request is tied to your sign-in; the ID is not stored. So that a day does not count twice, the app only remembers the date it was last opened on the device. The legal basis is Art. 6(1)(f) GDPR (legitimate interest in improving the app). You can turn this off at any time in the app under Settings › Your data › "Send usage counts".
Local storage on the device
The app also caches data on the device so it stays usable without an internet connection. That copy is removed when the app is uninstalled; unfinished drafts are discarded when a different account signs in. It is excluded from device backups and device-to-device transfer.
Food data, camera and microphone
The basic foods (German Nutrient Database BLS 4.0 by the Max Rubner Institute, CC BY 4.0, supplemented with values from USDA FoodData Central and, for some dishes, from McCance and Widdowson's Composition of Foods Integrated Dataset 2021 by Public Health England — contains public sector information licensed under the Open Government Licence v3.0) ship with the app; searching them never leaves the device.
For brands the app queries the open database Open Food Facts (Open Food Facts, France). Only the search term or the scanned barcode is sent, together with the technically necessary connection data (IP address, time). Your account, entries, goal or other details are not sent. The legal basis is Art. 6(1)(b) GDPR (the search you asked for). See the Open Food Facts privacy notice.
The camera is used to scan a barcode, to read a nutrition label and — only with your consent to the AI features — for food by photo, each time only after you grant access in Android. Barcodes and nutrition labels are recognised on the device (Google ML Kit text recognition, bundled with the app); the photo of a nutrition label is deleted right after reading and not transmitted. What happens to a photo for the AI is described under AI features. Images are not stored anywhere.
ATEM Hybrid no longer uses the microphone and no longer asks for it. Older versions used it only when you chose "Describe" while logging food and granted access in Android. Speech was recognised by Android's on-device speech recogniser; ATEM Hybrid only received the recognised text. No audio was stored or transmitted.
Your own products and learned words (e.g. that "bread" means a particular food for you) stay on the device only. They are deleted when you withdraw consent or switch accounts.
AI features: food by photo, text, menu and meal suggestions
These features are optional and need their own consent in the app — in addition to the nutrition consent, because they allow something else: sending to a further recipient. Without it, no photo and no text leaves your device.
| Feature | What is sent | What is not |
|---|---|---|
| Food by photo, menu or recipe | the photo — first scaled down to at most 1,568 pixels and stripped of metadata (no location, no capture time, no device) | name, email address, account ID, body weight, height, age, training, sleep and other body values |
| Read text | the text you entered (at most 500 characters) | |
| Meal suggestions | the meal (e.g. dinner), what is left until your goal as two numbers (calories, protein), the kind of goal, the words from "I don't eat", up to 40 names of your own foods with usual amount and frequency and up to 20 saved meals with their items |
How it works. The app sends the request to ATEM Hybrid's own server (Google Cloud Functions, Frankfurt region, processor as in section 3). It checks sign-in, consent and the quota and forwards the photo or text to Anthropic, which uses the AI model Claude to recognise items and amounts or to create suggestions. Names, amounts, a confidence estimate and an estimate of the nutritional values per 100 g come back. The app takes nutritional values from its food data; only when it cannot find a dish there does it use the AI's estimate and shows it as "AI estimate". Nothing is logged until you have checked and saved it.
What is stored. ATEM Hybrid's server does not store the photo or text; they are held in memory only until the reply arrives. In the app the photo stays until the sheet is closed. Only the following is stored:
- the entries you save — like any other entry, marked as estimated and with the way they came in;
- time and version of your consent and "I don't eat" in your settings;
- the number of your requests on the current day (for the quota), with your account ID;
- daily totals without personal reference (number of requests, compute used, number of users) for cost control;
- names of foods the AI recognised but the app can't find in its food data (e.g. "acai"), as a count per name — without account ID, time or amount — to fill in the food data;
- server logs with duration, status, model and error code — without photo, text or reply;
- if you report a result, the report with your text and the result, without the photo (see Reporting AI answers).
Recipient: Anthropic. Anthropic, PBC, 548 Market Street, PMB 90375, San Francisco, CA 94104, USA, processes the photo or text as a processor under Art. 28 GDPR on the basis of its commercial terms and data processing addendum. Anthropic does not use the data to train its models and deletes inputs and outputs after 30 days. Exception: if Anthropic's safety systems detect a violation of its usage policy, the content concerned may be kept for up to two years. Anthropic receives no name, no email address and no account ID. The transfer to the USA relies on the European Commission's standard contractual clauses . See Anthropic's privacy policy.
Legal basis is your explicit consent under Art. 9(2)(a) and Art. 6(1)(a) GDPR, for the transfer to the USA additionally Art. 46 GDPR. You can withdraw it at any time with effect for the future under Settings › Nutrition › "Photo, text and menu with AI"; after that no request is sent. Withdrawing the nutrition consent withdraws it too.
The results are estimates and suggestions, not nutritional or medical advice. There is no automated decision-making within the meaning of Art. 22 GDPR: only what you have checked is saved.
ATEM AI: questions about your training
ATEM AI is a chat that answers questions about your training, nutrition and numbers and can suggest or draft plans. It is voluntary and needs its own consent in the chat — separate from all other consents. Without it, nothing is sent.
| What is sent | What is not |
|---|---|
| your question and up to the last 20 messages of the chat; the facts the app computes from your data for an answer — summarised from at most one year: sets per muscle group, exercises by name, effort, best sets, sides; your workouts with date, kind and content (exercises and sets, or distance, time and pace); cardio per activity (count, kilometres, time, pace); your plans and programs (names, exercises, runs, targets, pace ranges), goal and training days, gyms with equipment, check-in and readiness, resting heart rate and HRV as a direction, body weight; nutrition (protein per kg, balance, days logged) only with your nutrition consent; from the journal only with its own permission (see Journal) | name, e-mail address, account id, session notes, photos, single readings from Health Connect such as heart-rate curves or sleep stages |
How it works. The app sends the question to ATEM Hybrid's own server (Google Cloud Functions, Frankfurt region, processor as in section 3). It checks sign-in, consent and the quota and forwards the question to Anthropic, which answers with the AI model Claude. The numbers are computed by the app on your device; the AI selects and phrases. A plan only exists once you review and save it in the plan form.
What is stored.
- your chats in your account (like your training data) so you can continue them — they are deleted 90 days after the last message; before that you delete them under Settings › ATEM AI; they are part of the data export;
- time and version of your consent;
- the number of your questions in the current month (for the quota), with your account id;
- daily totals without personal reference (number of requests without and with Pro and about the app, compute used, how often “Not right” was tapped, how often the free questions were used up, and how often that happened within 14 days of signing up) for cost control and to size the number of free questions. For the last total the server reads your account's sign-up date once; only the total is stored;
- server logs with duration, status, model and error code — without question, answer or facts;
- if you report an answer, the report with question and answer (see Reporting AI answers).
Recipient: Anthropic. Anthropic, PBC, 548 Market Street, PMB 90375, San Francisco, CA 94104, USA, processes question and facts as a processor under Art. 28 GDPR based on its commercial terms and data processing addendum. Anthropic does not use the data for training its models and deletes inputs and outputs after 30 days. Exception: if Anthropic's safety systems flag a violation of its usage policies, the affected content may be kept for up to two years. Anthropic receives no name, no e-mail address and no account id. The transfer to the USA is based on the European Commission's standard contractual clauses . See Anthropic's privacy notice.
Legal basis is your explicit consent under Art. 9(2)(a) and Art. 6(1)(a) GDPR, for the transfer to the USA additionally Art. 46 GDPR. You can withdraw it at any time under Settings › ATEM AI with effect for the future; after that no question is sent. Your chats stay until you delete them or the 90 days are over.
Answers are pointers from your own data, not medical or nutritional advice; for pain or injuries ATEM AI refers you to a doctor or physiotherapist. There is no automated decision within the meaning of Art. 22 GDPR.
Reporting AI answers
Below every ATEM AI answer and below the results of food by photo, text, menu and meal suggestion there is “Report”. With it you report an answer that is wrong, offensive or harmful without leaving the app.
What is stored: the reason, your question or the text you entered, the AI’s answer, your note if you write one, the app’s language and version and the time — with your account ID in your account. Photos are not included. The report does not go to Anthropic.
Why: ATEM Hybrid reads the report to find and fix AI errors. Google Play requires this option for apps with AI content.
How long: until it has been handled, at most six months; it is deleted with your account. It is included in the data export.
Legal basis is your consent under Art. 6(1)(a) and, where the report contains health data, Art. 9(2)(a) GDPR, which you give by sending it; the sheet says beforehand what goes along. You can withdraw it at any time by email to the address above; the report is then deleted.
Journal
In the journal you note what an evening was like: tags such as alcohol (with an amount if you like), stress, travel, sick, medication or — only if you switch it on — period, and optionally one sentence. This is health data. Nothing is stored before your own consent; the server rules reject every entry without it.
What comes of it. The app computes on your device what went along with a tag for you — the next morning's check-in and your next strength session, compared with evenings without the tag. This is a correlation from your own data, not a cause and not a judgement; there is no automated decision within the meaning of Art. 22 GDPR.
What is stored. Per evening the tags (yes or explicitly no), amounts and the sentence; plus time and version of your consent, which tags you show, your own tags, your sharing choices and whether and when you want an evening reminder (your device schedules it, not our server) — in your account like your training data, part of the data export. If you withdraw consent (Settings › Journal), the journal is deleted.
ATEM AI. ATEM AI only reads from the journal with a separate permission in the journal: permission 1 the results (tag, follow-up, difference and counts), permission 2 — separately — also your sentences. Without permission nothing from the journal goes to the server or to Anthropic. The terms are under ATEM AI.
ATEM Pro: purchases via Google Play and RevenueCat
Purchases are processed by Google Play; only Google receives payment data, not ATEM Hybrid. Which purchases belong to an account is managed by RevenueCat (RevenueCat, Inc., 1032 E Brandon Blvd #3003, Brandon, FL 33511, USA) as a processor. RevenueCat receives the account identifier (no name, no email address), the Google Play receipt and the purchase details, plus technical details about the app version and device type sent by the RevenueCat SDK, and the "early" flag. The SDK only collects an advertising ID with advertising integrations; ATEM uses none. From this the app checks whether ATEM Pro is unlocked; for this it registers every signed-in account with RevenueCat.
The transfer to the USA is based on the European Commission's standard contractual clauses (Decision 2021/914, Module 2), which are part of RevenueCat's data processing agreement. The data is stored by RevenueCat in the USA.
How long: for as long as the account exists. If you delete your account, we also delete your record at RevenueCat. The purchase itself stays with Google Play: with a new account you can bring back a running subscription or the one-time purchase via "Restore purchases". See also the privacy notices of RevenueCat and Google Play.
Contact form
If you use the contact form on this website, you send your email address, your message and optionally a name. These are stored together with the time of sending in Cloud Firestore (location eur3, see above), solely to answer your request. The legal basis is Art. 6(1)(f) GDPR (legitimate interest in answering enquiries), for questions about using the app Art. 6(1)(b) GDPR. The message is deleted once the request is dealt with, at the latest after six months. The form sets no cookies and uses no analytics or tracking.
4. Disclosure to third parties
Beyond the processors named in section 3 there is no disclosure — with three exceptions: purchases of ATEM Pro are processed by Google Play as the seller under its own responsibility (see ATEM Pro), the search term or barcode of a brand search goes to Open Food Facts (see "Food data and camera"), and only with your consent the photo, the text or the details for a suggestion go to Anthropic (see AI features). Apart from crash reports (see above), no analytics, tracking or advertising services are embedded. No profiles are built for advertising, and no automated decision-making within the meaning of Art. 22 GDPR takes place.
The figures shown in the app — such as the readiness score — are calculated from the user's own training data and have no legal or similarly significant effect.
5. Retention
Data is kept for as long as the account exists. If the account is deleted, the associated training, profile and settings data is deleted with it. Deletion can be triggered in the app or requested informally by email — the way without the app is described under Delete account.
ATEM Hybrid does not store photos or texts for the AI features (see AI features), except in a report you send yourself (at most six months, see Reporting AI answers); at Anthropic the periods named there apply. The quota counter is deleted with the account.
6. Your rights
- Access to the data processed (Art. 15 GDPR)
- Rectification of inaccurate data (Art. 16 GDPR)
- Erasure (Art. 17 GDPR)
- Restriction of processing (Art. 18 GDPR)
- Data portability in a common format (Art. 20 GDPR)
- Objection to processing based on legitimate interests (Art. 21 GDPR)
An informal message to the address in section 1 is enough.
You also have the right to lodge a complaint with a supervisory authority (Art. 77 GDPR), in the country of your habitual residence, place of work, or the place of the alleged infringement.
7. Block list
When you sign in, the app checks whether the account is blocked. The list used for this holds only an identifier, an email address and a status; it contains only blocked accounts and the provider's test accounts.
8. Changes to this policy
This policy will be updated when the processing changes, for instance with new features. The version published here is the one that applies; the date above gives its status.
↑ Back to top