Privacy policy

Last updated: 8 October 2026

The German version is the primary text.

1. Controller

Maximilian Schlecht
Peter-Jakob-Schober-Str. 8
71717 Beilstein
Deutschland
E-Mail: max.schlecht2000@gmail.com

2. What data Tracki processes

• Account: e-mail address and sign-in identifier; when you sign in with Google or Apple, the identifier provided by that service. On the first signed-in request, the Tracki server creates an internal Tracki account with a pseudonymous account number for this identifier – even if you do not use Tracki afterwards (it then remains an empty Tracki account).
• Participation and consent: self-declared date of birth, age band, accepted text versions, consent and withdrawal times. Exact birth dates and consent records remain in the private account record and are not returned as AI-assistant profile fields.
• Profile and goals: preferences, equipment, nutrition and training goals, day types, check-ins and breaks.
• Nutrition: meals with nutrition values, saved foods, recipes and recipe drafts, meal photos, and barcodes and search terms of food research.
• Meal plan: if you use it, your meal times (weekday, label, time and meal kind) and your weekly meal plans with the planned content and its state (open, checked off, skipped, logged), plus drafts for a week that a connected AI assistant or the app saves for you; they only change your plan once you apply them and are deleted after 14 days. All of it is included in the data export and is deleted with „Alle Daten löschen“, the withdrawal of the health consent and „Konto löschen“.
• Body and daily life: water, weight, height, age, sex, activity level and fasting times.
• Training: plans, sessions and results; for workouts imported from Apple Health also duration, distance, active energy, elevation gain and average heart rate.
• Apple Health: weight, workouts with heart rate and energy, only while sharing is on steps, distance and active energy, and only with a separate opt-in sleep, HRV, resting heart rate, VO₂max and body fat (details in section 6).
• Jobs: recipe imports with their link and food research with search term or barcode, each with its result, plus a daily counter for photo analysis.
• Connections: connected AI assistants and access keys you created (stored only as a hash, with the time of last use).
• Technical data: server logs with IP address, time, requested path and error messages for secure operation.

3. Health data

Data such as weight, body fat, heart rate, resting heart rate, heart rate variability (HRV), sleep or nutrition can be health data and therefore a special category of personal data under Art. 9 GDPR. The public participation flow requires a separate, explicit consent to processing it for the Tracki features you choose (Art. 6(1)(a) and Art. 9(2)(a) GDPR). It is collected separately from accepting the terms and is not selected by default. Confirming that you read the privacy policy or registering an account does not replace it.

The consent covers your recorded nutrition, body, water, fasting and training information and processing necessary for the features you trigger. Apple Health, sharing activity and recovery and assistant connections remain separate additional permissions. You can withdraw health consent for the future. Health-related use is then blocked, and Tracki deletes everything stored for your account: besides nutrition, body, water, fasting and training data and meal photos also the profile and settings, recipes, recipe folders, recipe drafts, favorites, training plans and the change and account-link history. The account with its sign-in, the necessary private participation evidence and the daily counters of the AI features (photo analysis, recipe imports, food research) remain. Assistant connections and personal access keys are ended. Account management remains available. If part of deletion fails, affected features stay blocked; you can retry deletion, and Tracki does not report completion prematurely. Processing before withdrawal is not retrospectively invalidated.

Minimum age

Tracki is for people aged 18 and over. You declare your own date of birth during participation setup. This is self-reporting, not identity verification using official documents. If the declared date of birth shows an age under 18, Tracki does not accept a consent; public health-related app and assistant features then remain blocked.

4. Purposes

• daily summary, goals, fasting and training planning in the app;
• AI features you trigger (photo analysis, voice entry, recipe import, food research, AI meal times and AI weekly plan);
• the connection with your AI assistants;
• security, troubleshooting and recovery (backups).

Tracki contains no advertising and does not include advertising or analytics services.

Legal bases and optional information

Account data necessary to sign in and provide the service you choose is processed to perform the contract (Art. 6(1)(b) GDPR). Health data additionally requires the explicit consent described in section 3. Security and error logs serve the legitimate interest of protecting the service and resolving failures (Art. 6(1)(f) GDPR). Necessary consent evidence supports the statutory accountability obligation (Art. 7(1) GDPR); Tracki keeps it until your account is deleted (section 7).

You supply optional information such as meal photos, Apple Health values and recipe links for the respective feature. Without it that feature cannot work or is limited. Features depending on required health consent remain blocked without that consent. Tracki does not make automated decisions with legal or similarly significant effects; calculated goals and suggestions are not diagnoses or binding decisions.

5. Where the data is stored and who receives it

• On your iPhone: sign-in information in the keychain and a local copy of Tracki data for display and synchronization. Server deletion and device-managed data are distinct; the app synchronizes when connected again.
• Supabase (Frankfurt region): database (PostgreSQL), sign-in (Supabase Auth) and private photo storage.
• Sign-in services Google and Apple: only if you sign in with them. Their privacy policies apply in addition; Tracki receives the identifier and, if provided, the e-mail address.
• Google Cloud Run (europe-west3, Frankfurt): the Tracki server that connects the app and assistants with your data; its logs are stored in Google Cloud Logging.
• Google Cloud Storage (Frankfurt): a daily, encrypted backup of Tracki data and photos in private storage.
• Google (Gemini Developer API), age 18 and over only: If the server offers Gemini, it is the preset AI provider for accounts with a stored age of 18 or over; in the app you can choose OpenAI or, if offered, Anthropic (Claude) instead under Profil → KI-Anbieter (Profile → AI provider). Tracki then processes photo analysis, meal and training voice entry, AI meal times and the AI weekly plan, and recipe-link analysis with Gemini. For recipe imports, the Tracki server may also use Gemini instead of OpenAI for these accounts, for example when OpenAI is not available for the import. The same content needed for each feature described below is sent; recipe videos may include their audio track. Tracki sends no account data. The microphone recording for Tracki voice entry stays on your iPhone. Food research uses Anthropic (Claude), otherwise OpenAI. Accounts without a stored age of 18 or over do not use Gemini. The key stays on the server. Tracki uses Gemini only as a paid API service; under Google's terms, this content is not used to improve its models. Google may retain content temporarily for abuse detection and process it outside the EU, including in the USA. Exclusive EU processing or complete immediate deletion is not promised.
• Anthropic (Claude API): for food research and, age 18 and over only, as a selectable AI provider – in each case only when you use the feature. This is independent of whether you connect Claude as an AI assistant.
  • Food research (“Search the Web with AI”): Tracki uses Anthropic (Claude) with Anthropic's web search when available, otherwise OpenAI. Only the product name or search term or the barcode is sent, no account or diary data. Tracki may add the product data it finds, with the link to its source, to its shared food catalog, which all users can search – regardless of which provider did the research. The catalog entry contains no information about your account.
  • Selectable AI provider: if the server offers Anthropic, you can explicitly choose Anthropic (Claude) in the app under Profil → KI-Anbieter (Profile → AI provider) for an account with a stored age of 18 or over. Only then does Tracki process meal voice entry, photo analysis, voice for training, AI meal times and the AI weekly plan, and recipe import from links with Claude. The same content needed for each feature described below is sent. For recipe videos, no audio track is sent to Anthropic, only text (page text, captions and description) and individual still frames from the video. The microphone recording for Tracki voice entry stays on your iPhone. Without this choice, Anthropic receives no content from these features.
  Tracki sends no account data. The key stays on the server. Tracki uses Anthropic only as a paid API service; under Anthropic's commercial terms, Anthropic does not train its models on this content. According to Anthropic, API inputs and outputs are generally deleted within 30 days, and kept longer for example where the law requires it or where needed to enforce Anthropic's usage policy. Requests go to the Anthropic API (api.anthropic.com). Anthropic processes the content in the USA; the model may also run in other countries. Exclusive EU processing or complete immediate deletion is not promised.
• OpenAI: if OpenAI is your AI provider or Tracki uses neither Gemini nor Anthropic for your account or the respective feature, and for food research when Anthropic is not available for it – in each case only when you use the feature.
  • Photo analysis: the meal photo.
  • Voice entry: the spoken or typed text of a meal description, only when you use voice entry. Your iPhone recognizes the speech itself; the recording never leaves the device and is not stored. If your description refers to earlier meals (e.g. “the same as yesterday”), the meals of the day or of a nearby day you refer to are sent as well, with amounts and nutrition values (at most two days, each at most a week from the day of the entry). If you refer to them, the names of your saved recipes and favorites are also sent to OpenAI, with servings and nutrition per serving (at most two searches with six matches each; no ingredients or recipe text). Tracki only saves once you tap “Log”.
  • Voice for training: the spoken or typed request and the necessary parts of your training profile, availability and selected plan or workout and its result. Meals, recipe names, account identifiers and GPS routes are not sent as training context. The recording stays on your iPhone. The model only reads; a plan, adjustment, break or feedback is saved only after your explicit confirmation in the app. Your request and a result note may contain health information, for example about a sick break; they are sent as described.
  • AI meal times and AI weekly plan: if you describe your break and meal times in the app by voice or text, or have a weekly plan created, your spoken or typed text and, for the weekly plan, only the data you select for it are sent to your AI provider (OpenAI, Google or Anthropic): the places of your meal times in that week with their status (planned dishes only for places that are still open and not for free suggestions), diet type, preferences, exclusions, allergies, cooking time and budget per serving, depending on your selection the names and nutrition per serving of your recipes and favorites, patterns of your meals from the last 14 days, the week's workouts without start times and your daily goals. No body data, photos or account identifiers. The model only reads; Tracki saves meal times or a draft only once you confirm them.
  • Recipe import from TikTok, Instagram and website links: the content of the link; the audio track of videos is sent to OpenAI to be transcribed.
  • Food research when Anthropic is not available for it: search term or barcode. OpenAI uses its web search for this, and the Tracki server fetches the product pages it finds.
  Tracki sends no account data. For photo analysis, voice entry, recipe analysis and research, Tracki does not request that responses are stored (store: false); transcription has no such setting. In any case, the retention rules of the OpenAI API apply. Requests go to the OpenAI API in the USA (api.openai.com); exclusive EU processing is not promised.
• Open Food Facts: for barcode lookup and food search. The Tracki server sends the barcode or search term, without account data.
• Public websites: for recipe import and food research, the Tracki server fetches the pages itself, not your device.
• Connected AI assistants (ChatGPT, Claude, Grok): only after you signed in and agreed, via OAuth or with a personal access key. The assistant receives the data it requests for your request; its provider's privacy policy governs further processing. You can disconnect at any time in the app under Profil → KI-Assistenten (Profile → AI assistants).
• Timetable in the chat: if you upload a timetable in ChatGPT or Claude to take meal times from it, the chat platform processes the file under its own rules. Tracki receives no file and only stores the times and labels of the meal breaks you confirmed; subjects, rooms and names are not taken over – labels containing such details are rejected.
• ZITADEL: sign-ins from before the switch to Supabase are still verified through this sign-in service during a transition period.

6. Apple Health

Tracki only reads Apple Health data if you connect Apple Health in Tracki and iOS allows access. Health data reaches your Tracki account on the server in three ways:

1. Weight: „Gewicht aus Apple Health übernehmen“ (import weight from Apple Health) is on by default once Apple Health is connected. Tracki then transfers weight measurements from up to the last 90 days (the last one per day) and later new measurements. You can switch this off in Tracki.
2. Workouts: Tracki transfers running, cycling, swimming and multisport workouts from Apple Health as training results – when you import them by hand or switch on „Trainings automatisch übernehmen“ (import workouts automatically, off by default). Duration, distance, active energy, elevation gain and average heart rate are transferred.
3. Activity and recovery: Only if you switch on „Aktivität aus Apple Health teilen“ (share activity from Apple Health) under Profil → KI-Assistenten does Tracki transfer day values: steps, distance, active energy and workouts. Recovery values (sleep, HRV, resting heart rate, VO₂max, body fat) are only transferred with the additional opt-in „Erholungswerte teilen“ (share recovery values), which is off by default. „Erholung lesen“ (read recovery) only controls the recovery card in the app and shares nothing. If you switch sharing off, Tracki deletes these day values on the server; if you only switch „Erholungswerte teilen“ off, Tracki deletes the recovery values and keeps steps and workouts. Recovery values transferred before this opt-in existed were deleted once for all accounts without the opt-in.

After you switch sharing off, the day type of past days that was calculated from shared workouts is recalculated without them. The day type, daily goal and calorie budget of past days can change as a result. Day types you set by hand and workout results recorded in Tracki stay.

Tracki only takes over your height if you deliberately use it for your goals. GPS routes of your workouts stay on the iPhone and in Apple Health.

In the other direction, Tracki writes meals with calories, macros and fiber, water, weight and workouts recorded with Tracki into Apple Health on your iPhone. You can switch meals, water and weight off individually in Tracki, and saving a recorded workout for each session („In Apple Health speichern“, save to Apple Health). Overall access to Apple Health is controlled in the iOS settings.

7. Retention

• Your entries are stored until you delete them, delete all data or delete your account.
• Meals and saved foods and recipes can be restored after you delete them; they are only marked as deleted. Deleted water entries, weight measurements, fasting times and breaks are also first only marked as deleted, so that other devices pick up the deletion. All of these entries are permanently removed with „Alle Daten löschen“ (delete all data) or „Konto löschen“ (delete account).
• Removed permanently right away: day types you reset, shared Health day values when you switch sharing off, recovery values when you switch „Erholungswerte teilen“ off, revoked access keys and the still planned sessions of a replaced training plan (the plan itself stays archived).
• For every write, Tracki stores the result under its operation key so that a repeated request does not create a duplicate. These results contain the stored data and are kept until „Alle Daten löschen“ or „Konto löschen“. Exceptions: for shared Health day values Tracki only stores that the day was transferred, without the values. When you switch sharing or „Erholungswerte teilen“ off, Tracki removes all results that still contain such values.
• Recipe imports, recipe drafts and food research are kept until „Alle Daten löschen“ or „Konto löschen“. Product data that food research added to the shared food catalog contains no information about your account and stays there afterwards as well.
• Photos that are not attached to a meal are deleted after 24 hours.
• The daily cloud backup has an automatic deletion rule starting at an age of 30 days. Google Cloud Storage performs lifecycle deletion asynchronously; no exact deletion time is promised. Until deletion, data you deleted may still be contained in a backup. Additional soft-delete retention is disabled for the backup storage.
• In addition, the operator can create an encrypted backup of the same data by hand, stored on the operator's own computer. These backups have no automatic deletion rule; until they are removed, they may also still contain data you deleted.
• Health consent withdrawal deletes the content described above; age and consent records remain private for handling that process. Account deletion also removes those records. Exact birth dates are not included in model responses.
• Access tokens of a connected assistant are valid for 15 minutes, refresh tokens for at most 30 days. Personal access keys are valid until you revoke them in the app or under „Manage account“.
• After „Konto löschen“, a disabled, pseudonymous mapping of your sign-in identifier to the internal account number remains. It prevents an old sign-in from creating the account again.
• Google Cloud Logging: the regular log bucket _Default is configured for 30 days of retention. Administrative audit and system-event logs in Google's required bucket _Required have 400 days of retention.
• A sign-in on „Manage account“ is stored encrypted with the account, e-mail address and times until you sign out, at most 30 minutes without activity and at most 2 hours in total.

8. Your rights

• Access and data portability (Art. 15 and 20 GDPR): Profil → Daten exportieren (export data) gives you all stored entries as a JSON file (endpoint /v1/export). The export also contains stored consent evidence. Other people’s health data are separate; your own access rights remain unaffected. Without the app you download the same file on the web under Manage account; if your sign-in there is more than 15 minutes old, you sign in again first.
• Erasure (Art. 17 GDPR): Profil → Alle Daten löschen removes all entries, photos, operation results and access keys and disconnects all assistants. Konto löschen additionally removes your sign-in account at Supabase. Deleting the account also works without the app under Manage account: there you confirm with your e-mail address, and your sign-in may be at most 5 minutes old. If Konto löschen is not yet offered for your sign-in method, please contact support.
• Withdrawal: you can end assistant connections and access keys at any time in the app or under Manage account. You end sharing of Apple Health activity and recovery values and the import of weight and workouts in the app. These permissions can only be changed in the app, not through an AI assistant.
• You also have the right to rectification, restriction of processing, objection and to lodge a complaint with a data protection supervisory authority.

You can withdraw consent independently of closing your account. Withdrawal does not retrospectively invalidate processing based on consent before withdrawal. Where no other legal basis remains for stored data, the statutory right to erasure applies (Art. 17(1)(b) GDPR). Deletion on withdrawal and account management support these rights; other statutory rights remain unaffected.

Privacy requests are answered without undue delay, generally within one month. The GDPR allows an extension by up to two further months for complex or numerous requests; you are informed within the first month. If there are doubts about identity, necessary additional information may be requested.

Contact for privacy questions: max.schlecht2000@gmail.com

9. These pages

The public Tracki pages use no cookies, no scripts and no analytics services. The only exception for cookies is „Manage account“ (/en/account): after you sign in, Tracki sets a strictly necessary session cookie there that applies only to this page and becomes invalid after 30 minutes without activity, at the latest after 2 hours. Signing in with Google or Apple adds a cookie for the return for at most 10 minutes.