ePrivacy compliance for a mobile app
ePrivacy Directive (Directive 2002/58/EC, as amended by 2009/136/EC). This page applies it to one kind of product (mobile 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 mobile app typically processes
- device identifiers and advertising IDs
- device permissions such as camera, location or contacts
- crash reporting and mobile analytics SDKs
- in-app purchases through the store
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 mobile 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.
On mobile, the store asks too
There is no cookie banner in a native app, but Apple App Privacy and Google Play Data Safety both make you declare the same processing — and a declaration that contradicts your privacy policy is the version reviewers notice. The policy has to be reachable at a public URL before you submit.
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 mobile 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.