ePrivacy compliance for a health app
ePrivacy Directive (Directive 2002/58/EC, as amended by 2009/136/EC). This page applies it to one kind of product (health app), so you get the obligations that are actually yours instead of a summary of the whole statute.
Does it apply to you?
Anyone storing or reading information on a user's device — cookies, localStorage, SDK identifiers.
What a health app typically processes
- health and wellbeing data, which is sensitive in most jurisdictions
- explicit consent as the usual lawful basis
- data shared with practitioners or providers
Each of these is processing you have to disclose. Adding an SDK later adds to this list — which is why a policy written once goes stale.
Documents you need
The intersection of what ePrivacy requires and what a health app actually does:
- Privacy policy
Rights you must honour
ePrivacy gives people in the European Union the right to:
- Withdraw consent at any time
Cookies and trackers
Nothing non-essential may load before the visitor agrees. Analytics and marketing scripts must be blocked until then — a banner that only informs is not enough.
See what your site is actually missing
Paste your URL. We fetch the live page, detect the trackers, payments and AI calls that really ship to visitors, and tell you which documents and consent you need. No signup.
No signup · result in seconds
Primary sources
- ePrivacy — ePrivacy Directive (Directive 2002/58/EC, as amended by 2009/136/EC) · official text
- Art. 5(3) — Prior consent for storing or accessing data on a device
ePrivacy for other kinds of product
Other frameworks for a health app
This page is an engineering summary of publicly available regulatory requirements, generated from LexVibe's framework registry — not legal advice. Every framework links to its official text so you can check it yourself. For decisions about your own compliance posture, consult the primary sources and a lawyer qualified in the relevant jurisdiction.