Local-first, by default.
Your workout, habit, meal, body and profile data is stored only on your device. The AI features send summaries of some of it to Google to write their answers, and our server keeps none of it. The one exception is a feature you switch on yourself: add a training partner, and a small summary of your streak is kept on our server so they can see it.
US residents, including Washington and Nevada: read our Consumer Health Data Privacy Policy.
Eight things worth knowing.
- Your workout, habit, meal, body and profile data is stored only on your device. The AI features send summaries of some of it to Google to write their answers, and our server keeps none of it. The one exception is a feature you switch on yourself: add a training partner, and a small summary of your streak is kept on our server so they can see it.
- Some features send a summary of your training to Google's Gemini API to generate a result. Those features are listed below. Apart from them, the app talks only to Apple and RevenueCat for your subscription (and, if you answer it, where you found the app), to Apple and our own server to show it is the genuine app (App Attest), and to our own server for anonymous setup counts and, if you add one, your training partner's page (section 05).
- Diet Scanner photos are analyzed and then discarded by our server, and Google keeps them only in the request logs it holds for a limited time to detect abuse (section 07). The only lasting copy is the one your phone keeps in your meal history, if you log the meal.
- Health data (steps, sleep, active energy) is read from Apple Health only if you turn it on, stays on your device, and is never included in any AI request.
- Screen Time blocking happens entirely on your device. We never learn which apps you chose.
- We don't run ad tracking, third-party analytics or crash reporting. The only counting is anonymous daily totals for setup and the subscription screen, linked to no one. There's no behavioral profile of you anywhere.
- The AI features are restricted to users 18+. The rest of the app is available from age 13.
- Deleting the app deletes the data on your device, apart from a few small values iOS can keep in its Keychain (section 11). If you added training partners, use Reset all data first, with your phone online, to delete their copy from our server; otherwise it expires 90 days after the app last updated it.
Data stored on your device.
SENTINEL is local-first. Your workouts, habits, streaks, personal records, weight log, training days, age, profile details, scanned meals and their photos, and body check-in photos and waist measurements are all stored only on your device. Body check-in photos are never uploaded or sent to any AI service.
Uninstalling the app removes this data along with it. The single exception is the training-partner summary described in section 05, which exists only if you add a partner.
What we send to Google, and when.
Several features use Google's Gemini API to generate a result. Rather than list features that may change, here is every category of data that can leave your device, and what asks for it. Your app language is sent with each request so answers come back in it.
All of these features are restricted to users 18 and older — see Age restrictions.
A photograph of your food
When you scan a meal, the photo is sent through our server to Google's Gemini API for analysis, and the estimated calories and macros are returned to the app. Location and camera details are removed from the photo on your phone before it is sent. Our server discards the photo after analysis, and Google keeps it only in the request logs it holds for a limited time to detect abuse (section 07). If you log the meal, your phone keeps a copy with it in your meal history (not in your camera roll), which Reset all data deletes. We do not keep a history of your meals or nutrition data on any server.
Your habit and workout summaries
For the AI Coach: habit names with completion counts and current streaks; session counts, average session rating, average set completion, how many sessions were strength, muscle-building or endurance style, and how many days it has been since you started. The Weekly Recap sends the week's totals instead — sessions trained against sessions scheduled, sets, which days you trained, average session rating, habits kept — with the previous week's totals for comparison, your current streak, and your weakest training-balance area with its score out of 100.
Your training profile
Your fitness goal, experience level, training days, weight, target weight, age, and sex, and, if your goal is Build Muscle, what you are working toward. The AI Coach also sends your self-reported outlook and stress level from setting up your plan, if you provided them — used only to calibrate the tone of the answer (for example, more supportive pacing for higher stress), never treated as a clinical assessment. If you answered them when setting up your plan, it also sends what has derailed you before (for example, not enough time, or injury or pain), how active your days are outside training, and the part of the day you train.
It also sends the sets, reps and rest your sessions are built from, the date a recovery week ends if one is running, and, for any muscle group you have trained much harder than usual in the past week, its name and its sets that week against its usual weekly sets, so the coach does not add work to a muscle that is already tired.
It also sends how you eat (for example vegetarian) and any food allergies you chose to list, so that every food the coach names is one you would and can eat. Allergies are used only as foods to leave out. SENTINEL cannot check labels or menus, so it never tells you a food is safe for your allergy.
It also sends your daily calorie and macro targets, the same ones the app shows you, so the coach quotes your real numbers. They are worked out on your phone from your profile.
Your progress summaries
Used by: AI Coach (coaching questions)
So the coach can answer from your real progress and today's plan, each question also sends a few short summaries, worked out on your phone:
- Weight: your latest logged weight, how much it changed over about 4 and 12 weeks, and how many times you weighed in over about 4 months, from your weight log.
- Lifts: for up to six lifts you trained recently, an estimated one-rep max now and one from about 2 to 4 months earlier; whether the lift is progressing, holding or stalled, and for how many weeks; and, if you tapped one of the app's suggestions for it (a reset, a hold, an easier target or a recovery week), which one, how many sessions since, and whether it has worked yet. All of it is worked out from the lifts you logged.
- This week: how many sessions you have done against this week's target, on how many days you checked off every habit against your habit-day target, how many days are left, and whether you are on track.
- Today: today's date and weekday, whether your plan makes it a training or rest day and the name of that day's session, and whether you have logged a session today.
- Meals: for the last 7 days, the number of days you scanned meals and your average calories, protein, carbs and fat on those days.
- Today's session: the exercise names, their type and planned sets, the planned minutes, and whether you have started it, so the coach can shorten or change today's session when you ask.
- Today's food: how many meals you have scanned today and their total calories and protein.
- Weak spot: when one area of your training is under half its weekly target, that area's name and its score out of 100.
Only these totals, averages and today's plan are sent. Your meal photos, dish names, individual meals, the sets you logged, and the dates in your history stay on your phone; the only dates sent are today's and, during a recovery week, the day it ends. Like everything the coach receives, the summaries are used to write that one answer and are not stored on our server.
Your lifts, milestones, and bodyweight change
Personal records set during the week — the exercise name, the weight, and the reps — plus the names of any milestones earned, and how much your bodyweight moved across the week, in the unit you chose (pounds or kilograms).
This is more specific than the summaries above, and we call it out separately for that reason. It is limited to records you set in the week being reviewed. We do not send your full set-by-set training history.
Your training-balance scores
Six numbers describing how your training is distributed across push, pull, legs, core, mobility and cardio, and — for push, pull, legs and core — the name of the one muscle inside each your training currently feeds least, such as “chest” for push. The weak-spot fix finds your weakest area and asks Gemini for a short workout that trains that specific muscle. Every exercise it can prescribe is chosen from a fixed, pre-approved list built into the app, narrowed to the ones that train the muscle in question — Gemini cannot introduce new or unrecognized exercises. The app also sends each area's average, so our server breaks a tie between two areas the way the app does; the averages are not passed to Google. No set, rep, weight or date from your training history is sent — only these figures derived from it.
An anonymous install identifier
A random identifier is created the first time you open the app and stored in your device's Keychain. It is sent with each request to our server so it can limit how many requests a single installation makes.
It is not your name, your email, your Apple ID, or your device's identifier — it is a random value with no meaning outside our rate limiter, and it is not used to build any profile of you. Because it lives in the Keychain, iOS may keep it after the app is deleted, so reinstalling the app does not always replace it.
Each request to our server also carries your time zone's offset from UTC, so weekly free-plan limits turn over on your own Monday, and the anonymous identifier RevenueCat creates for your app (section 10), so our server can confirm a subscription with RevenueCat. It also carries a free-or-premium flag: Diet Scanner and Weekly Recap requests set it from your subscription so our server can choose the AI model, and every other request says “free”. Each AI request also carries your age, so our server can check you are 18 or older (section 08). None of these is passed to Google, except your age as part of your training profile for the AI Coach.
What you type
A question you ask the coach is sent as the question. Before it goes, the server strips invisible control characters, caps its length, and marks it clearly as your words rather than as instructions to the AI. The same trimming is applied to habit names you wrote yourself.
We should be precise about what that last part is worth: it makes the AI far less likely to treat something typed in a question as an order, but it is guidance to the model rather than a hard guarantee. It is also not really a protection of your data — a question only ever travels with your own information, so there is no one else's for it to reach.
We do not store your questions or the answers. They exist for the length of the request.
What we never send
Your name is never included in any request to Google. Nor is your email or any contact information — we don't collect it. Nor is your Apple Health data, your Screen Time selections, your body check-ins, or your full set-by-set workout history.
Apple Health.
If you turn on Automate tracking, SENTINEL reads three things from Apple Health: your step count, sleep analysis and active energy burned. It uses them to check off habits you've already completed — a step goal you've already walked — and to estimate the calories you have burned today.
Three things about this:
- Read-only. SENTINEL requests read access only. It cannot write to, change, or delete anything in Apple Health. The permission sheet reflects this: it offers no write toggles.
- It never leaves your device. Health data is read on-device and used on-device. It is never sent to our server, never included in any AI request, and never shared with Google or anyone else.
- It's off until you turn it on. The permission is never requested while you set up your plan or at launch. It is only ever requested when you tap "Automate tracking" in Settings, and the app works fully without it.
We do not request access to clinical health records.
Screen Time blocking.
The Shield uses Apple's Screen Time (Family Controls) framework to block the apps you choose until you have done the day's work in SENTINEL: the day's session, or on a rest day your habits.
We never learn which apps you picked. Apple deliberately makes these selections opaque to third-party apps: the app receives anonymous tokens, not app names or identifiers. When SENTINEL displays your blocked apps back to you, Apple's own system draws each name and icon — the information is rendered on screen without ever being handed to the app.
Your app selections, your usage data, and the blocks themselves never leave your device and never reach our servers.
Our server, and training partners.
For the AI features, our server exists only to relay requests to Gemini and return the response. It does not retain a copy of anything that passes through it — no images, no prompts, no responses are stored. Each request is processed and discarded.
Training partners, only if you add one
A training partner is someone you choose to see your streak. Adding one creates a private link for that person, which opens a web page showing your first name and goal, your current and best streak, and this week day by day: which days you trained (including extra sessions), missed, covered with a streak save, have still to come, or rest, and how many of the week's planned sessions are done; and when the app last updated it.
That is the complete list. Your weight, meals, photos, body check-ins, habits and everything else stay on your phone. To keep the page current, your phone sends this summary to our server when you open the app, and the server stores it with a random identifier it created when you added your first partner, which your phone keeps. Each partner's link is separate, and our server counts how many times each link is opened and when it was last opened (not who opened it), so the app can show you whether your partner has looked.
Removing it. Removing a partner turns their link off at once, when the request reaches our server. Settings → Reset all data deletes the summary and every link from our server, again when the request reaches it. The app does not retry either one: if your phone is offline at that moment, a removed partner can still open the page (and, while you have other partners, still sees it update) until the summary expires. If you stop opening the app, the page says so, and everything expires on its own 90 days after the app last updated it. Removing your last partner turns their link off but leaves the summary on our server, where no one can open it, until it expires. Deleting the app does not reach our server either, so use Reset all data first if you want the summary gone straight away.
The partner page loads the app's two typefaces from Google Fonts, so the browser of whoever opens it contacts Google to fetch them, as it would for most websites.
What else the server holds
In a small key-value store (Upstash Redis):
- Rate-limit counts — how many requests each anonymous installation identifier, and each internet (IP) address, has made recently, so no one can overload the AI features. Opening a partner's page is counted the same way, by address. They expire on their own within a day.
- App Attest keys — the public key Apple issues so our server can tell requests from the genuine SENTINEL app apart from anything else, with when it was registered and Apple's count of recent App Attest keys from your device for the app, which is a sign of abuse. To get that count, our server sends Apple the receipt that came with the key, once, when the key is registered. The first time our server checks a subscription for that installation, it also keeps the anonymous RevenueCat identifier the installation sent, so no other installation can use it. A key identifies an installation of the app, not you, and has no set expiry. Our server also keeps running totals of how these checks turn out, with no identifier.
- Free-plan use counts — how many free scans, coach messages and weak-spot fixes each App Attest key has used. They expire after a day, a week, or for the weak-spot fix a year.
- Anonymous setup totals — per-day counts of how many times people reached each setup step, met a free-plan limit, or saw the subscription screen or the gift offer, and what they chose there, and how many answered each option to “Where did you find us?” at the end of setup (TikTok, Instagram, YouTube, App Store search, a friend, or somewhere else). No identifier is stored with them, so they cannot be traced to anyone. They are kept for 30 days and used only to see where setup and the subscription screen lose people.
Apart from the training-partner summary above, none of these contain your training data, your photos, your questions or anything you typed.
How a request travels.
Every AI request leaves your device over HTTPS, and on top of that the app pins the connection: it ships knowing which certificate authorities are allowed to vouch for our server, and refuses to send anything when the server that answers is vouched for by anyone else.
This matters for one specific situation. On a network configured to inspect traffic — a corporate device profile, a public network running an interception proxy — ordinary HTTPS can be read by whoever set it up, because your device has been told to trust their certificate. Pinning is what stops that: the app would rather fail the request than hand your data to something vouched for by an authority it does not recognize.
If a pin check fails, the feature returns an error. It does not quietly fall back to an unverified connection.
Google's handling of this data.
SENTINEL uses the paid tier of the Gemini API. Under Google's terms for paid API usage, Google does not use this data to train its models. Google retains request logs for a limited period for abuse detection, per its API terms. Google's own terms are the authoritative source for their retention practices.
Age restrictions.
SENTINEL is intended for users aged 13 and older. The Diet Scanner, AI Coach, Weak-spot fix, and Weekly Recap are restricted further, to users 18 and older, since they send data to a third-party AI service.
Your age is asked when you set up your plan and stored on your device. The restriction is enforced twice: on your device before the feature runs, and again on our server before any request reaches Google.
What we don't do.
- No third-party analytics or behavioral tracking (the anonymous setup totals in section 05 are the only counting, and they are not linked to anyone)
- No advertising or ad networks
- No third-party trackers
- No crash reporting services
- No selling of data, ever
- No push notifications from our servers. Reminders are scheduled locally on your device; we do not collect a push token and could not message you if we wanted to
- No collection of your email or other contact information. Setting up your plan asks for a first name to personalize the app. It stays on your device and is never included in any AI request; it reaches our server only if you add a training partner, as the name on their page
Third parties we use.
- Google (Gemini API) — powers the AI features described in section 02, and nothing else.
- RevenueCat — handles subscriptions and purchase verification. When you subscribe or restore a purchase, RevenueCat receives an anonymous identifier it generates, along with purchase and subscription details from Apple. If you answer “Where did you find us?” at the end of setup, RevenueCat also receives that one answer (for example “TikTok”) with the same anonymous identifier, so we can see which posts bring people who subscribe. Apart from that, it does not receive your name, your training data, or anything else described in this policy. If you never subscribe, it holds nothing about you beyond an anonymous app installation record. Our server also asks RevenueCat whether that anonymous identifier has an active subscription when you use an AI feature (section 02).
- Apple — processes all payments. We never see or handle your payment details. Apple also confirms App Attest keys (section 05).
- Expo / EAS — the build and hosting infrastructure that runs the app and its server routes.
- Upstash — the key-value store described in section 05: rate-limit counts, App Attest keys, free-plan use counts, anonymous setup totals, and, if you add a training partner, the partner summary.
- Google Fonts — only on a training partner's page, which loads the app's typefaces from Google.
Your data, your control.
Because your data lives on your device rather than on a server we control, you hold it directly. There's no account to delete. Deleting the app removes your local data, apart from a few small values iOS can keep in its Keychain after an app is deleted: the anonymous install identifier, the app's App Attest key reference, its count of free uses, and the keys for training-partner links. None of them holds your training data.
You can also reset everything you logged from inside the app: Settings → Reset all data. It leaves only the install identifier, the App Attest key reference, the count of free uses, and your Screen Time app selection, which stays on your phone. That also deletes the training-partner summary and every partner link from our server, if you had added partners and the request reaches our server (section 05). To remove one partner, with your phone online, long-press them in Settings → Training partners.
To revoke Apple Health access, go to the Health app → Sharing → Apps → Sentinel. To revoke Screen Time access, go to iOS Settings → Screen Time.
If you live in California.
California's privacy laws (the CCPA, as amended by the CPRA) give residents specific rights. They apply whether or not a company is required to comply, and we would rather answer them plainly than argue about thresholds.
The right to know what is collected. Everything is listed in the sections above. There is no hidden category: your training data is on your device, and the only things that leave it are the ones named there.
The right to delete. There is no account, profile or history of yours on our servers, only the counts and the App Attest record for your installation described in section 05. The one thing of yours we keep is the training-partner summary, if you added a partner: Settings → Reset all data deletes it along with everything you logged on your phone, and removing a partner turns their link off, as long as the request reaches our server (section 05). If you want confirmation of that in writing, email us and we will give it.
The right to correct. Your data is yours to edit directly in the app. The partner summary is rebuilt from it each time you open the app.
The right to opt out of sale or sharing. We do not sell personal information and never have. We do not share it for cross-context behavioral advertising. There is no opt-out link below this paragraph because there is nothing to opt out of — not as a technicality, but because the app has no advertising, no third-party analytics, and no trackers at all.
The right to non-discrimination. Exercising any of these changes nothing about what the app does for you. There is no worse tier for people who ask questions.
Sensitive personal information. Health and fitness data can count as sensitive under the CPRA. Ours is stored on your device; the parts the AI features send to Google (section 02) are used only to write the answer you asked for, and Apple Health data is never transmitted at all. We do not use it to infer characteristics about you, and there is no secondary purpose to limit.
To exercise any of these rights, email support.sentinelapp@gmail.com. We will verify a request by replying to the address it came from, since that is the only identifier we could possibly have.
Changes to this policy.
If SENTINEL's data practices change — for example, if a new feature sends a new category of data off-device — we'll update this policy and revise the "last updated" date above. We encourage you to check back periodically, especially before using a new feature for the first time.