When a fitness app asks for health permissions, it's asking for some of the most personal data you generate: where you run, when you sleep, how fast your heart beats. Most people tap "Allow" without reading, because the alternative is the app not working.
You don't need to become a privacy lawyer to protect yourself. You need a short checklist and the discipline to run it before granting access. Here's what actually matters.
What fitness apps can actually see
On iOS, apps request health data through Apple Health; on Android, through Google Health Connect. Both platforms are permission-based — an app only sees the categories you grant. But those categories can be broad: workout sessions, heart rate, GPS routes, step counts, and more.
GPS routes deserve special attention. A history of your runs isn't abstract data — it's a map of where you live, where you work, and when you're predictably away from home. Any app that uploads route data should be able to tell you exactly why it needs to.
The questions worth asking
- Where is the data processed — on your device, or on the company's servers? On-device processing means raw data never has to leave your phone at all.
- What is uploaded? There's a world of difference between uploading your full workout history and uploading a derived number computed from it.
- Is data sold or shared with third parties? Look for a plain-language answer, not a maze of "trusted partners" language.
- Can the app do its job with less? An app should request only the categories its features genuinely require.
- What happens when you leave? Deleting your account should mean your data goes with it.
On-device processing: the gold standard
The single most protective architecture is one where analysis happens on your phone and only a result leaves it. If an app computes what it needs locally and transmits nothing but an aggregate, there's no raw-data honeypot on a server to breach, subpoena, or quietly monetize. What was never uploaded can't leak.
This is the model Gritvit uses. The app reads workouts from Apple Health or Google Health Connect and does all processing on-device. Raw workouts, heart-rate readings, GPS routes, and step counts are never uploaded — the only things its servers receive are two aggregated numbers, a Trust Level and a Fitness Score. Nothing is sold or shared. It's proof that an app can verify your training without warehousing your health history.
Practical habits that cost you nothing
Grant permissions per category, not wholesale — both Apple Health and Health Connect let you approve workouts while denying, say, heart rate. Audit your granted apps a couple of times a year and revoke access for anything you no longer use; a dead app with live permissions is pure downside.
And apply one simple smell test: does the data requested match the feature delivered? A running app asking for GPS makes sense. Vague requests for everything, justified by nothing specific, are your cue to look closer or walk away. Your training data tells the story of your daily life — it's worth two minutes of scrutiny before you hand it over.