“Your data stays on your phone unless you choose to share it.”
It’s a reassuring promise. For a health app, it may be the most important promise a company can make. It only holds if the privacy policy says the same thing.
When the Promise and the Policy Don’t Match
A recent LinkedIn post caught our attention. A founder of a women’s health app announced that users’ data stays on their phones. A reader then opened the app’s privacy policy and found a very different picture.
According to that reader, the policy described practices that sit far from “on your phone”:
- Data stored on cloud servers in a specific AWS region, not locally on the device
- Display names, symptoms, weekly check-ins and questionnaire scores sent to AI model providers
- That sharing happening whether or not the app’s memory feature was turned on
- Data retained after a person deletes their account
- Access available to internal staff
- Data shared with employers
This is a clear example of the gap that can exist between what a company says in its marketing and what it discloses in its privacy policy. It’s one of the most common issues we find when we review healthtech products.
It’s rarely a single dramatic failure. More often, a marketing team describes the product as it was designed to work early on, while the infrastructure, vendor contracts and business model quietly evolve. The policy gets updated. The tagline doesn’t.
Why Health Data Demands a Higher Bar
Health information is among the most personal data a person can share. Symptoms, cycle tracking, mood check-ins and mental health questionnaire scores can reveal pregnancy, menopause, gender identity or a diagnosis someone hasn’t told their family or employer.
Many consumer health apps also sit outside traditional health privacy rules. An app that isn’t working on behalf of a doctor or insurer often isn’t covered by HIPAA. That leaves people relying almost entirely on what the company tells them, and on whether the company follows through.
The stakes rise further when an app is built for communities that already face higher risks when their information is exposed. For these users, an employer learning about a health condition, or a vendor holding identity-related data indefinitely, can carry real consequences for their safety, work and access to care.
When a product is designed for people who need privacy most, its privacy practices are part of the product itself.
What Health Tech Companies Can Do Differently
- Make your marketing match your policy. Every privacy claim on your website, app store listing and social posts should trace back to a specific line in your privacy policy. Build a review step so privacy and legal teams see marketing copy before it ships, and revisit claims whenever infrastructure or vendors change.
- Be precise about where data lives. “Stays on your phone” and “encrypted in the cloud” are very different promises. If some data syncs to a server for backup or features, say which data, where it goes and why. Precision builds more trust than a broad claim that later falls apart.
- Disclose AI providers and what they receive. If symptoms or check-ins are sent to an AI model provider, name the provider and list the data types. Share only what each feature truly needs, strip identifiers like display names where possible, and state whether vendors may use the data to train their models.
- Make settings mean what they say. If a user turns off a feature like memory, data tied to that feature should stop flowing. A toggle that changes nothing behind the scenes undermines every other promise you make.
- Make deletion mean deletion. Publish a clear retention schedule. When someone deletes their account, explain exactly what is removed, what is kept, for how long and why, including backups.
- Limit internal access. Restrict staff access to sensitive health data by role, log that access and review it regularly. Tell users in plain language who inside the company can see their information.
- Treat employer relationships with extra care. If your app is offered through employers, share only aggregated, de-identified insights, with minimum group sizes so individuals can’t be singled out. Make this boundary explicit to both the employer and the employee.
- Design for the people you serve. If you build for communities facing elevated risk, set your defaults to match. Collect less, keep it for less time and give people meaningful control. Laws such as Washington’s My Health My Data Act reflect a broader regulatory focus on consumer health data, but the higher bar starts with the people using your product.
- Invite independent review. A fresh set of eyes, outside your marketing and product teams, is often the fastest way to find gaps between what you say and what you do.
Earn Trust with Your Users
Regulators, advocates and everyday users continue to look more closely at how health apps handle personal information. AI features add new vendors and new data flows, which makes clear disclosure even more important.
The companies that earn lasting trust will be the ones whose public promises and written policies tell the same story. That consistency is something any team can build, starting with a careful read of its own fine print.
If your team would like an independent look at how your privacy practices line up with your public claims, book a Privacy Assessment.

