RunMentor is built to keep your training data yours. The app has no accounts, no ads, and no analytics-for-sale. This policy describes exactly what data the app touches, where it goes, and why.
RunMentor is developed and operated by Andrei Simedre ("we", "us"). For anything in this policy, contact support@runmentor.app.
Health and fitness data (HealthKit). With your explicit permission, RunMentor reads the following from Apple Health: workouts and runs (including route, duration, and calories), heart rate, distance and pace, cadence, elevation, sleep, and body metrics such as weight. RunMentor never writes to Apple Health or changes your existing Health data — it only reads. When you send a planned session to your Apple Watch, that is scheduled through WorkoutKit, not written into Health. You can change or revoke these permissions at any time in Settings → Privacy & Security → Health.
Training profile. Information you enter in the app — your goal race, race date, experience level, weekly availability, and chat messages to the coach.
Meals you log. In the Nutrition tab, whatever you record about what you ate — the food name, portion, calories and macros, and the time you ate it. Logging by hand stays on your device. If you ask the coach to estimate a meal for you, that description (and any photos you add) is sent for that one request as described in section 4. Your week's meals are also included in coach prompts so it can advise on fuelling around your sessions.
Photos you choose to send. Two places, both opt-in per photo: attachments you add in chat, and up to three photos of a meal when you ask for an AI calorie estimate. Before a photo leaves your device it is re-encoded (and downscaled if it is large), so the original file's metadata — including any location tag — is not sent. Photos are used only to answer that one request and are never stored on our servers. We never access your photo library on our own — you pick each photo, or take it with the camera.
What we do NOT collect: no name, email, or account; no contacts; no photos beyond the ones you attach yourself as described above; no location tracking outside of workout routes you share via HealthKit; no advertising identifiers.
Your training plan, run history, conversations, and settings are stored on your device. We do not operate servers that store your health data or your conversations.
Our servers keep only what's needed to run the service, tied to a random identifier generated on first launch (never your name, email, or Apple ID): subscription status, free-tier usage counters, promo-code redemptions, and short-lived technical logs (timestamps, request sizes, error codes — never message or workout content).
RunMentor's coaching is powered by large language models. To generate your plan, analyse a run, answer a chat message, or estimate a meal, the app sends the relevant workout metrics and your training profile (e.g. distances, paces, heart-rate summaries, race goal, your message) through our relay service — hosted on Cloudflare — to our AI provider over an encrypted connection. The relay does not store this content.
Two kinds of request carry more than metrics. Any photo you attach — in chat, or up to three of a meal for a calorie estimate — is relayed the same way, for that request only. And because the coach advises on fuelling, a summary of the meals you logged this week (food names, calories, and the times you ate) is included in coach prompts. Logging a meal by hand never sends anything on its own; it is stored on your device until a coaching request needs that context.
Our current provider is Google (Gemini API). We may add Anthropic (Claude) and OpenAI (ChatGPT) as providers in future versions; this policy will be updated before any change takes effect.
Requests carry the random identifier from section 3 — never your name or account details. We use API terms under which providers do not use your data to train their models. AI requests are processed transiently to produce a response and are not used to build a profile of you. We never send raw HealthKit database contents — only the derived metrics needed for the specific coaching task.
Subscriptions are sold and processed by Apple through the App Store — we never see your payment details. We use RevenueCat to validate purchases and manage subscription state; RevenueCat receives purchase records tied to the random identifier above. Manage or cancel any time in Settings → Apple ID → Subscriptions.
As required by Apple's guidelines: we never use HealthKit data for advertising or marketing; we never sell HealthKit data or share it with data brokers; HealthKit data is used solely to provide the coaching features you asked for; and it is only shared with the AI provider as described in section 4, with your knowledge.
The app may share anonymous crash reports and usage statistics with us via Apple's built-in analytics, only if you opted in to "Share with App Developers" in iOS settings. These contain no health data.
You can erase the server-side records yourself, in the app: Me → Your data → Erase server records. It deletes everything our servers hold for your install — the random identifier, usage counters, subscription state, and promo redemptions — and issues a new identifier with no link to the old one. Your training data stays on your device, because that is not what the server holds.
Deleting the app removes everything stored on your device, and revoking Health permissions stops all HealthKit access immediately. If you would rather we did the erase for you, or you have already deleted the app, email support@runmentor.app.
RunMentor is not directed at children under 13 (or the minimum age in your jurisdiction) and we do not knowingly collect data from them.
If we change this policy, we will update the effective date above and, for material changes, notify you in the app before they take effect.
Questions or requests: support@runmentor.app.