Privacy notice
Version: 2026-10-12-v1
Controller
Erdem Winnicki · Intempore AI Solutions, Traute-Martin-Weg 1, 30457 Hannover, Germany. Privacy contact: winnicki@intempore.de.
Your choices
Academy and example data do not require Health consent. Personal imports require explicit consent to health-data processing and storage. Signed-in account storage needs its own account choice. AI and voice are separate optional permissions. Declining or withdrawing permission blocks the relevant features. Reading this notice or accepting the terms does not constitute consent.
Health data and personal learning
The original Health file stays on this device and is not uploaded. Parsed Health data is saved in your account only when you are signed in and have given permission. Apple Health imports may contain activities, heart rate, sleep, nutrition, body measurements and GPS routes. Health Connect imports may include supported activities, heart rate, asleep stages, steps and body measurements. On Android 14 or newer, you can separately grant Android read permissions to manually import workouts, measured distance, heart rate and steps for up to four weeks. No write, background or extended-history permissions are requested. Android permission does not replace your Runnizer Health data consent. ZIP/XML files and Health Connect database files are parsed locally. Imported records, notes, preferences, conversations and reports are stored on your device and, with account consent, in your signed-in profile. Personal relationships and interests are used for your own insights and Academy recommendations; they remain personal data. Legal basis: GDPR Articles 6(1)(a) and 9(2)(a).
Optional COROS connection
You may authorize your COROS account through COROS sign-in. Runnizer stores access tokens in your private server storage and automatically retrieves runs while you use the app after connecting. You can also request training and recovery status. Supported runs are saved in your activity history under your existing Health and AI consent choices. Raw files and GPS traces are not sent to the AI coach. COROS processes sign-in under its own privacy policy. Disconnecting, withdrawing Health consent, or deleting the saved profile removes tokens from Runnizer. Legal basis: GDPR Articles 6(1)(a) and 9(2)(a).
Automatic AI and voice
After separate explicit AI consent, derived health summaries, selected metrics, notes, saved context and conversations go through the Intempore AI service to OpenAI. New or changed data may trigger analyses automatically. Raw exports and GPS traces are excluded from coach requests. Free text may still identify you: avoid unnecessary names or other people’s health information. Voice requires additional consent and a call you start; microphone audio goes directly to OpenAI during the call and transcripts join the conversation. Legal basis: GDPR Articles 6(1)(a) and 9(2)(a). Microphone and HealthKit device permissions do not replace these choices.
No general training on personal data
Runnizer does not use personal health data, conversations or pseudonymous participant records for general model training. Global cohort collection, new participation and public community hypotheses are paused pending a documented anonymisation review. Removing names, hashing identifiers or minimum cohort sizes alone do not establish anonymity. Existing research contributions can be deleted by withdrawing participation. Any future global use requires a separately reviewed process and updated information, not a blanket licence under these terms.
Sign-in, hosting and device storage
ChatGPT Sites and Cloudflare provide delivery, database and private object storage. Requests include necessary connection information such as IP address, time and requested resources. Google/email sign-in uses the shared Intempore service with Supabase. Provider/account identifiers and, where applicable, email/profile information are processed. Account features: GDPR Article 6(1)(b). Security and abuse prevention: Article 6(1)(f), our legitimate interest in safe operation. Necessary sessions/device settings support the feature you request (§25(2) TDDDG). Health data is stored locally only after consent. Displaying a route loads external OpenStreetMap map tiles with necessary connection data.
App Store subscriptions
Apple processes payments through your Apple account. Runnizer stores a random Apple purchase token linked to your Runnizer account, transaction and product identifiers, expiry and verification status to confirm purchases, renewals and restoration. Runnizer does not receive payment details or Apple passwords. Health data is not sent to Apple for purchase verification.
Recipients and international processing
Recipients are the hosting, sign-in and AI providers used, including Cloudflare, OpenAI and, for the selected sign-in method, Supabase and Google. Providers may process outside the EEA, including the USA. Their published privacy/data-processing terms describe standard contractual clauses and, where applicable, adequacy decisions. Contact the controller for applicable contracts, configuration and transfer evidence; general provider information does not prove individual implementation. Consent to a feature is not blanket consent to inadequately protected international transfers.
Retention and deletion
Imported profile content remains for your history until you delete it under Profile → Account & data or request erasure. The original ZIP/XML is not kept in the profile. Remove local copies there or through browser/device settings; other devices must be cleared separately. Withdrawal stops new processing and cloud access for the disabled features; withdrawing Health consent also deletes the stored Health profile and local data on this device; requests already sent cannot be recalled. Stored content can be deleted separately, including without active Health consent. Consent choices and minimal receipts are retained for accountability/legal claims; historic entries are removed after three years when permissions are next managed. Statutory records such as future invoices do not justify retaining all health profiles. Providers may keep security/abuse logs: OpenAI states a default of up to 30 days with justified exceptions. store:false does not guarantee zero retention.
Your rights
Subject to GDPR conditions, you can request access, rectification, erasure, restriction and portability. Withdraw consent at any time in Profile → Privacy & permissions, with effect for the future. Earlier lawful processing is unaffected. You can object to legitimate-interest processing on grounds relating to your situation. Profile backup and deletion are available in the app; other requests: winnicki@intempore.de. You may complain to a supervisory authority, including the Lower Saxony authority. Runnizer does not make solely automated decisions with legal or similarly significant effects; its guidance supports your own decisions.