ePrivacy compliance for an AI writing tool
ePrivacy Directive (Directive 2002/58/EC, as amended by 2009/136/EC). This page applies it to one kind of product (AI writing tool), 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 an AI writing tool typically processes
- user text sent to a model provider for completion
- drafts and history stored per account
- usage metering for billing
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 an AI writing tool 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.
The EU AI Act angle
A product like this that puts a model in front of users falls under the transparency duties of Article 50: you have to tell people they are interacting with an AI system, and machine-readable marking of generated content is required. Those duties apply from 2 August 2026; the high-risk obligations of Annex III were pushed to 2 December 2027.
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 an AI writing tool
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.