Privacy Policy

Last updated November 6, 2026

The short version: we collect what Coachh needs to coach you, we use AI providers that don’t train on your data (and, for replies, plans and meal estimates, only endpoints that don’t keep it), we never sell your data or use it for ads, and you can request an export or account deletion from the app. Retention exceptions and provider cleanup are explained below.

This policy explains how People In Tech LLC ("Coachh", "we", "us") handles information in the Coachh apps for iPhone and Apple Watch, the Coachh app for Android phones (in testing now, coming to Google Play) and its Wear OS companion once released, and on this website. Where the Android apps work differently, this policy says so. If you live in Washington, Nevada, Connecticut or another state with a consumer health data law, also read our Consumer Health Data Privacy Policy.

What we collect

Category	What	Where it comes from
Account	Email address, name, and an account ID. With Sign in with Apple you can hide your email behind an Apple relay address. With Sign in with Google we receive only your name, email address and profile photo; we never get your Google password or access to your Gmail, Drive or other Google data.	You, Apple, Google
Profile and goals	Height, birth year, sex if you give it, training experience, where you like to train, equipment, training days, the areas you want help with, your goals in your own words, limitations or injuries you mention, and your plan. If you connect Apple Health during setup, height, birth year, sex and weight can be filled in from it for you to confirm (on Android, height and weight from Health Connect).	You, Apple Health or Health Connect
Health and fitness	Weigh-ins, body measurements and body-fat readings, workouts and sets, meals and nutrition estimates (and the foods you rename, fix or stop Coachh suggesting in My foods, and the meals you save in My meals), water, sleep quality, energy, pain and mood check-ins, and the badges, streaks and personal bests worked out from them.	You
Apple Health	If you allow it: daily totals of steps, distance, exercise minutes, active energy, resting heart rate, heart rate variability (HRV), VO2 max, sleep, workouts, weight, body fat and lean body mass (for example from a smart scale), and your biological sex. We upload daily activity totals, each weigh-in (weight and time), each body-fat reading (at most one a day), and a summary of each workout (type, start time, duration and calories). Lean body mass is shown in the app and isn’t saved to your account. HRV is used for your daily readiness and is part of the health summary sent to the AI for coaching; it isn’t stored in your daily summaries. Biological sex can be filled in from Health for you to confirm, and is then saved to your profile. Individual Health samples are processed on-device rather than uploaded as your log history. During enabled live workout sharing, current heart rate can pass from the Watch through the phone and our private realtime channel to signed-in devices following the session. Those live readings are broadcast, rather than stored as heart-rate history. Apple TV support is coming soon. If you allow it, Coachh also writes to Apple Health: workouts, weigh-ins, waist and body-fat measurements, water, meal nutrition and your mood check-ins.	Apple Health, with your permission
Health Connect (Android)	On Android, Coachh uses Health Connect instead of Apple Health, with the same rules. If you allow them (each one can be turned on or off in Health Connect), it reads steps, distance, active calories burned, exercise sessions (workouts, runs and walks other apps record), sleep, resting heart rate, heart rate variability (Health Connect measures it as RMSSD), heart rate (for the average of a run or ride), VO2 max, weight, body fat, lean body mass and height. Health Connect has no birth date or biological sex, so those aren’t read. Coachh uploads the same daily totals, weigh-ins, body-fat readings and workout summaries as on iPhone, and keeps raw samples on your phone. With background access on, it checks Health Connect for new data about once an hour while the app is closed, and with past-data access it can read further back than 30 days for your recaps. If you allow it, Coachh writes to Health Connect: the workouts you finish, the walks you record on your watch, weigh-ins, body fat, water, and the nutrition of meals you logged with exact numbers or confirmed. Coachh asks only for the Health Connect permissions its features use, and never sells Health Connect data, transfers it to advertising platforms or data brokers, or uses it for advertising.	Health Connect, with your permission
Photos	Meal photos you send to Coachh, and the photos you share on a voice call with the camera button (below, under Voice). Progress photos stay on your phone unless you turn on Back up progress photos (Settings), which stores them privately so only your account can open them, and lets you restore them on a new phone. Turning backup off lets you delete the backed-up copies. Coachh’s AI never sees your progress photos.	You
Chat	Your messages to Coachh and its replies, in one ongoing conversation, and short weekly and monthly summaries of it that Coachh writes so it remembers what happened before your latest messages. Settings › Memory › Clear chat history deletes the conversation and its summaries (your logs stay).	You, Coachh
Memory	Coachh remembers what you tell it so it can coach you over time; you can see and delete it in Settings › Memory. Things you tell Coachh that matter for coaching you over time, in your own words: your schedule, diet and allergies, injuries, supplements, events and goals with their dates, how you like to be coached, and health notes. Health notes (for example a diagnosis, a medication or something your doctor said) are only used after you tap “Keep this”. You can add, edit or delete anything there, pause remembering, or forget everything; your logs stay. Memory is used only to coach you in the app: never for emails, ads or analytics. Settings that follow your account (like your coaching style, reply length and nutrition targets) are kept with it so a new phone has them.	You
Feature requests	The requests you send, in the chat (when you ask Coachh for something it doesn’t do yet) or in Settings › Request a feature: the text you send, which app you sent it from (iPhone or Android), and which roadmap items you asked for. They’re stored with your account to count votes, and so we can tell you when something you asked for ships on your phone. To match a request to the roadmap, its text goes through the same AI providers as your chat messages (see AI processing). Only item titles and vote counts are public, at coachh.app/roadmap; never your name, account or words. Deleted with your account.	You
Founder survey	If you’re a founding member, two optional questions on day 14 of your founding month. Your answer to the first is kept as private feedback for us. Your answer to the second is counted on the public roadmap the same way as a request from Settings › Request a feature (see Feature requests above), never shown with your name.	You
Voice	If you use voice mode, your audio is streamed to Google (the Gemini API), or to xAI (Grok voice) when we use it instead (see AI processing), for transcription and a spoken reply. We don’t store the recording. The mic in the message box and in setup (speech to text) uses your phone’s own speech recognition: Apple’s on iPhone, and on Android the phone’s on-device recognizer where it has one for your language. Otherwise Android uses its speech recognition service, usually Google’s, which may process the audio on Google’s servers under Google’s terms. Only the text reaches Coachh, and only when you send it. Workout cues are spoken by your phone’s own voice and never leave it. Replies read aloud use your phone’s voice too, unless you have Coachh Pro and keep Settings › Voice on “Coach voice”: then the words of the coach’s reply (only the reply, nothing else about you) are sent to xAI, or to Google when xAI isn’t available, to be spoken in the coach’s voice, and the audio is kept on your phone so you can play it again. xAI doesn’t keep the request, and we ask Google not to store it. On a voice call that uses Google, a camera button lets you share a photo (a meal, equipment, the move you’re doing) so the voice can see it: after a notice the first time, the photo is sent to Google, resized to at most 1024 pixels, for that call only. Coachh doesn’t keep it. It’s saved only if you ask Coachh, on the call, to log it as a meal, and then it is that meal’s photo, like a photo you send in the chat. Calls that use xAI have no camera button.	You
Notifications and in-app messaging	When enabled, OneSignal links messaging subscriptions to your Coachh account ID across your devices. It processes push subscription identifiers, device and app information, permission and subscription status, and message delivery or interaction events. For email, it also receives your verified email address and the content of the email you asked for or agreed to receive. Apple Push Notification service delivers iPhone push; Firebase Cloud Messaging delivers Android push when configured. OS permissions remain specific to each device. Coachh also stores notification preferences, candidate and dispatch records, suppression reasons and expiration times to avoid duplicate or stale messages. Lock-screen copy is discreet by default. Optional in-app messages can be deferred during a conversation or workout. Turn categories off in Settings › Notifications; OS permission is controlled in your phone’s settings.	You, Coachh, OneSignal, Apple, Google
Purchases	Your subscription product, transaction and entitlement status, and Coachh account ID so we can verify Pro access and restore purchases. Apple (or Google Play, on Android) processes payment; Coachh and RevenueCat do not receive your card number. If you installed Coachh from an ad on the App Store (Apple Ads), which ad campaign the install came from: Apple tells RevenueCat through Apple’s own attribution service, without an advertising identifier and without tracking you across apps.	Apple or Google, RevenueCat, Coachh
Device checks	To give each device one founding month and a limited number of free plan builds, Coachh checks whether a device has already had them. On iPhone we use Apple’s DeviceCheck, which stores two bits for the device with Apple and never gives us a device identifier, and Apple’s App Attest, which confirms the request comes from the real Coachh app on a real iPhone (we keep the app’s App Attest public key, not a device identifier). On Android, Google Play Integrity confirms the request comes from Coachh installed from Google Play on a genuine device; nothing from Google’s answer is stored. We also keep a one-way hash of an identifier for the device or app install (on Android, the Android ID), with when it was used and, for a founding month, which founder code was redeemed. The hash lets us recognise a device that already had a founding month or its free plan builds, but can’t be turned back into the identifier. These records are kept after you delete your account, no longer linked to it (see How long we keep it).	The app, Apple, Google
App usage	On by default, unless you turn it off (Settings › Share anonymous usage data), on iPhone and Android: which features you use and how you move through the app, for example that you opened it, finished a setup step, logged a meal by photo or barcode, started or finished a workout, or saw the Pro screen. Events carry only rough counts (like “6-15 sets” or “31-45 minutes”), your app version, operating system (iOS or Android) and its version, device type, country or region setting, whether you have Pro and your coaching style. They’re sent under a random ID created for this purpose, not your account ID, email or name, and a new one is made when you sign out. Never weights, calories, meals, what you type or say, notes, goals, Apple Health or Health Connect data or anything else you log. The same events include short reports of crashes, freezes and errors the app showed you (see Crash reports below). Nothing is sent before you sign in except which setup screens were seen and crash reports, under a separate random ID that is discarded at sign-in.	The app, PostHog
Crash reports	On by default, unless you turn it off (the same switch, Settings › Share anonymous usage data). When the app crashes, freezes or shows an error, a report of what went wrong in the code: the error type, where in the app it happened (the code’s call stack), the app and operating system versions and the device model, and on iPhone what the app was doing just before (for example, that it came to the foreground or which screen was open). On iPhone and Apple Watch it goes to Sentry; on Android to Firebase Crashlytics (Google), with the crash, device model, Android version and build number; and on both, a shorter version goes to PostHog with the usage events. Each is sent under random IDs made for that install (Crashlytics adds its own), not your account ID, email or name, and can be sent before you sign in. Never what you type or say, anything you log, your health data, or pictures of the screen.	The app, Sentry, Google (Firebase Crashlytics), PostHog
Coaching emails	Optional coaching, education and lifecycle emails require your email and topic preferences. We select them using explicit interests, supported features, lifecycle stage and messaging choices. Where enabled and consented, independently verified actions logged in Coachh, such as a first workout, can make a milestone email eligible; imported Health workouts do not. The email uses general recognition rather than exercise details. We do not use Apple Health or Health Connect data, health measurements, private chat or remembered health notes to select promotional emails. Detailed personal progress stays inside authenticated Coachh views. You can unsubscribe or change topics without losing access to your account. Providers receive the recipient address, subject and email body, delivery identifiers, unsubscribe state and available delivery or interaction events. An open event does not prove you read a message. If you explicitly request a recipe or meal-plan email, that copy can contain recipe names, ingredients, preparation instructions, portions, estimated nutrition and planned meal or cooking dates. Those details pass through the email provider and your mailbox provider. This is separate from optional promotional email and does not log a meal or confirm that you ate it. Do not request an emailed copy if you do not want those details in email. Necessary account or service emails have a separate purpose and delivery owner.	You, Coachh, OneSignal or Resend
Invite links	If you share a badge from the app, the link includes a random invite code made for your account (not your name, email or account ID). The page it opens shows the badge and, only if you switch it on in the app, your first name; nothing else about you. You can get a new code at any time, which turns the old link off, and the code is deleted with your account. The shared image is made on your phone and shows the badge and the link, never your body weight, measurements, Apple Health or Health Connect data.	You, Coachh
Website	Your email if you request website release updates: we save signup intent, platform interests, confirmation and opt-out evidence in Supabase. Resend delivers transactional confirmation during the provider transition. Confirmed website subscriptions and permitted launch emails can use a separate OneSignal app; website identities are not automatically joined to mobile accounts. Tokens are encrypted and expire; opening a confirmation link alone does not subscribe you. Failed or uncertain provider outcomes are retained for safe retry or review, and provider acceptance does not prove inbox delivery. When you join, Vercel’s bot protection (BotID) runs a check in your browser and on our server to tell people from automated sign-ups, from signals about your browser and the request, never your email. Anonymous, cookieless measurements of which pages are visited and how fast they load (Vercel Web Analytics and Speed Insights: the page, the referring site, country, device and browser type, load times, and a count when someone joins the waitlist, never the email; invite codes and link tokens are removed from page addresses before they’re sent; it doesn’t identify you, set cookies, or track you across sites). To show the right store (App Store or Google Play) or mark a waitlist sign-up as Android, the site reads the kind of phone from your browser’s standard User-Agent header; it doesn’t set a cookie or run a script for this, and stores only the platform interest you select (iPhone, Android or both where available), not calculator results or health information. While we test two versions of the home page’s headline, the site sets one first-party cookie (coachh_hero) that holds only the letter of the version you saw, so you keep seeing the same one; it lasts 60 days, identifies nothing and isn’t shared. On invite pages and the waitlist, anonymous events (that an invite page was opened, which badge it showed, whether a signup was saved, a confirmation was requested or completed, or an official store link was tapped, and whether that was on an iPhone, an Android phone or a computer) go to PostHog under a random ID kept only for that browser tab; never the invite code, your email or IP-based location. Our host keeps standard server logs (IP address, browser) for security for a short time.	You, Vercel, PostHog

Usage and crash reports use random identifiers rather than your account ID, name or email. This reduces direct identification; it is not a promise that technical data is irreversibly anonymous. Reports already received by those providers are not automatically removed by deleting your Coachh account. You can turn off future optional reporting in Settings and contact us about an access or deletion request.

With expanded Health access enabled, imported workouts can also include distance, available aggregate heart rate and source-app information. Readiness and coaching can use relevant sleep, breathing rate, activity and nutrition summaries when authorized and available. We do not read workout routes or infer a diagnosis from these records.

We don’t use advertising SDKs, don’t track you across other companies’ apps or websites, and don’t collect precise location.

How we use it

To coach you: log what you tell it, build and adjust your plan, estimate meals, and answer questions.
To keep you safe: messages are checked for signs of a medical emergency or crisis so the app can point you to real help.
To run the service: sign-in, sync between your devices, reminders you turn on, support, fraud and abuse prevention (including one founding month per device).
To decide what to build next: we count feature requests, and tell you when something you asked for ships.
To improve Coachh: we look at anonymous app usage (see “App usage” above) to see which features get used and where people get stuck, at crash reports (see “Crash reports” above) to fix what breaks, and at replies you choose to report, to fix mistakes. A support report can contain the conversation excerpt you agree to include; it is account-linked support data, separate from ordinary usage analytics.

We do not sell your personal information, share it for cross-context behavioral advertising, or use Apple Health or Health Connect data for advertising, marketing or data mining.

AI processing

Coachh’s replies, plans and meal estimates are written by AI models. To do that, the relevant parts of your data (your message, a compact summary of your recent logs and daily health totals, including heart rate variability, your body measurements and body-fat readings, and any meal photo; never your progress photos) are sent to:

OpenRouter, a gateway that routes each request to a model from OpenAI, Anthropic or Google. Those models may be served by Microsoft (Azure), Amazon (Bedrock) or Google Cloud (Vertex AI) rather than by the company that made them. On every request, we tell OpenRouter to use only providers that don’t train on your data, and only endpoints that don’t keep your requests (OpenRouter’s zero data retention: a request may be held in memory while it’s processed, never stored). OpenRouter itself doesn’t store the content of requests or replies; it keeps metadata such as the number of tokens and how long a request took.
Google (the Gemini API: Gemini Live and Gemini text to speech): voice mode, to transcribe your speech and speak the reply, and reading the coach’s replies aloud in the coach’s voice when that’s on. On a call, your audio, and a photo if you share one with the call’s camera button, goes to Google with the same summary the coach uses in chat (including what Coachh remembers about you, your recent conversation and, when you ask, your plan), on a call a Coachh server sets up; for replies read aloud, only the reply’s words. We use Google’s paid service: Google doesn’t use what we send to improve its products, and keeps prompts and responses for a limited time (up to about 55 days) only to detect abuse and meet legal requirements, then deletes them. For replies read aloud we also ask Google not to store the request.
xAI (Grok voice and xAI text to speech): we may use it for voice mode and replies read aloud instead of Google, with the same data, through a Coachh server that sets up the call. Our xAI account has Zero Data Retention on (since October 9, 2026): xAI doesn’t keep the requests, the conversation or the audio, and doesn’t train on them.

To coach you over time, each reply can also use what Coachh remembers about you (see Memory), the summaries of your conversation, and a summary of your progress over everything you’ve logged, and Coachh can look up your earlier messages, meals, workouts and weigh-ins to answer a question about them. Health notes are used only after you keep them.

Extraction (picking weights, meals and sets out of what you type) runs on our servers with the AI providers above. On an iPhone with Apple Intelligence you can switch on Extract logs on this iPhone (Settings › Privacy); it then runs on the phone where it can, and that part never leaves the device. AI output can be wrong; see our Terms.

Who else processes your data

We use these service providers, under contracts that limit them to processing data on our behalf:

Supabase: database, sign-in and file storage, including meal photos and, if you turn on backup, your progress photos (United States).
OpenRouter, OpenAI, Anthropic, Google, Microsoft (Azure), Amazon (Bedrock): AI processing for replies, plans and meal estimates, on endpoints that don’t keep your requests, as above.
Google (Gemini API): voice mode and replies read aloud, as above.
xAI: voice mode and replies read aloud when we use it instead of Google, with Zero Data Retention, as above.
RevenueCat: manages Coachh Pro subscriptions. It receives your Coachh account ID, purchase and subscription status, and basic device information from the App Store or Google Play, never your card or health data. For installs from Apple Ads, it also receives which campaign the install came from (from Apple, without an advertising identifier).
Apple: Sign in with Apple, App Store payments, Apple Push Notification service (notifications, as described under “Notifications” above), and DeviceCheck and App Attest (see “Device checks”). Apple Health data is read on your iPhone; the totals, weigh-ins, body-fat readings, workout summaries and optional live workout sharing described above are transmitted.
Google: Sign in with Google, if you choose it, and on Android: Google Play payments, Firebase Cloud Messaging (notifications), Firebase Crashlytics (crash reports, as described under “Crash reports”) and Google Play Integrity (see “Device checks”). Health Connect data is read on your phone; the totals, weigh-ins, body-fat readings, workout summaries and optional live workout sharing described above are transmitted.
PostHog: anonymous in-app usage analytics and short crash and error reports from the iPhone and Android apps, as described under “App usage” and “Crash reports” above, and the anonymous invite-page events described under “Website” (United States). It receives feature-use events under a random ID, never your name, email, account ID, health data or anything you log, type or say. We ask PostHog not to look up a location from your IP address. It keeps no recordings of your screen: we don’t use its automatic capture or session replay.
Sentry: crash and error reports from the iPhone and Apple Watch apps, as described under “Crash reports” above (United States). It receives what went wrong in the code under a random ID, never your name, email, account ID, health data or anything you log, type or say, and no pictures of the screen.
Vercel: hosting, anonymous analytics and load-time measurements for this website, and the bot check on the waitlist form.
OneSignal: push, in-app messaging and supported email delivery when enabled. When enabled, OneSignal links messaging subscriptions to your Coachh account ID across your devices. It processes push subscription identifiers, device and app information, permission and subscription status, and message delivery or interaction events. For email, it also receives your verified email address and the content of the email you asked for or agreed to receive. Apple Push Notification service delivers iPhone push; Firebase Cloud Messaging delivers Android push when configured. OS permissions remain specific to each device. If you explicitly request a recipe or meal-plan email, that copy can contain recipe names, ingredients, preparation instructions, portions, estimated nutrition and planned meal or cooking dates. Those details pass through the email provider and your mailbox provider. This is separate from optional promotional email and does not log a meal or confirm that you ate it. Do not request an emailed copy if you do not want those details in email. We do not put private health records, chat or memory into messaging tags or promotional segments.
Resend: continues to deliver sign-in and account email, waitlist confirmation and supported lifecycle flows that have not been migrated. It receives the verified recipient address and the applicable email content and delivery information. Each flow has one delivery owner; an ambiguous provider response does not cause a second send through another provider. Unsubscribe or change optional topics using the email footer or Settings.
GitHub: the exercise demo pictures in the apps load from GitHub (the open free-exercise-db project). Like any website, GitHub sees your IP address and which pictures your phone loads; nothing from your account is sent.
Open Food Facts and the USDA FoodData Central database: when you scan a barcode, only the barcode number is sent to look up the product. When you scan a product’s label because they don’t have it (or their numbers look off), its nutrition numbers and name go on Coachh’s shared food list so the next person who scans it gets them: never the photo, and never who scanned it.

Refund requests. Only when you ask Apple for a refund, we may share information about your use of Coachh, for example how much of the subscription you used, with Apple to help it decide. It doesn’t include what you log or your health data.

We may disclose information if the law requires it, to protect someone’s safety, or as part of a merger or acquisition, in which case this policy continues to apply.

How long we keep it

A successful in-app deletion removes your account, account-linked records and private uploaded photos from active Coachh storage. We request deletion from messaging and subscription providers separately. Those requests can take longer or need another attempt if a provider is unavailable; account deletion does not mean that every provider copy or backup disappears immediately.

Deleted data may remain in restricted, rolling backups until those backups expire under the hosting provider's configured retention period. Backups are for recovery, not active coaching. Security and operational logs have separate retention based on security, troubleshooting and legal requirements. Contact us for the retention applicable to your request.

A restricted cleanup queue can temporarily retain your account ID and messaging-app identifiers so we can retry provider deletion and reconcile previously issued login credentials. It contains no chat, health records or email content. Providers may separately retain records they are legally required to keep. Purchase records held by Apple or Google remain subject to their policies. Data already saved to Apple Health or Health Connect stays there, where you control it.

We also retain limited fraud-prevention data after account deletion: the device check records described under Device checks (a one-way hash of a device or install identifier, when it was used, which founder code was redeemed on it and, on iPhone, the app’s App Attest public key). They’re no longer linked to any account and can’t be turned back into the identifier; we keep them so deleting and signing up again doesn’t give the same device another founding month or more free plan builds. You can also ask us to delete your account without the app; Delete your account explains how, and what’s deleted and kept.

Your choices and rights

Export: Settings › Export my data gives you your logs as spreadsheet files, and your conversation, what Coachh remembers, its summaries and your synced settings as JSON files.
Memory: Settings › Memory shows everything Coachh remembers. Edit or delete any of it, pause remembering, forget everything, or clear your chat history.
Correct: edit or delete any log in the app.
Delete: Settings › Delete account, or email us (how to delete without the app).
Permissions: turn off Apple Health, camera, microphone or notifications in iOS Settings at any time; on Android, in Settings › Apps › Coachh, and Health Connect access in Health Connect.
AI: you can use Coachh without voice mode; logging works without Coachh replying.
Usage data: on by default; turn off Settings › Share anonymous usage data and the app stops sending usage events and crash reports (to PostHog, Sentry and Firebase Crashlytics), and deletes any usage events (and, on Android, crash reports) waiting to be sent.
Notifications: choose which kinds you get in Settings › Notifications, or turn them off in your phone’s settings.

Depending on where you live (for example California, Colorado, Virginia, the EU or the UK), you may have the right to know, access, correct, delete or port your data, to withdraw consent, to opt out of sale or targeted advertising (we do neither), and to appeal our decision or complain to your data protection authority. Email hello@peopleintech.io and we’ll respond within 30 days (45 where the law allows). We won’t discriminate against you for using these rights. Where the EU or UK GDPR applies, we process your data to provide the service you asked for (contract) and, for health data, on your explicit consent, which you give in the app and can withdraw by deleting your account.

Children

Coachh is for adults 18 and over. We don’t knowingly collect data from anyone younger. If you think a minor has an account, email us and we’ll delete it.

Security

Data is encrypted in transit and at rest, access is limited per account by database rules, and AI keys never live in the app. No system is perfectly secure; if we learn of a breach affecting you, we’ll notify you as the law requires.

International transfers

We’re based in the United States. Our providers may process data in the United States and other countries where they operate. Where applicable law requires transfer safeguards, those safeguards must be in place before the relevant processing.

Changes

If we change what we collect or who processes it, we’ll update this page and ask for your agreement again in the app before the change applies to you.

Contact

Questions or requests: hello@peopleintech.io, People In Tech LLC.