Skip to content
Back to policy library
European UnionIn forceRelevance to Chinese AI firms: HighData & privacy

EU ePrivacy Directive

Directive 2002/58/EC concerning the processing of personal data and the protection of privacy in the electronic communications sector, as amended by Directive 2009/136/EC

European Parliament and Council of the European Union · Directive 2002/58/EC

The sector-specific privacy law for electronic communications, applying alongside the GDPR and taking precedence on the matters it covers. Three provisions matter most for AI and digital products. Art. 5(1) protects confidentiality of communications, prohibiting listening, tapping, storage or other kinds of interception or surveillance of communications and related traffic data by persons other than users without the consent of the users concerned, except when legally authorised, and without preventing technical storage necessary for conveyance. Art. 5(3) makes storing information, or gaining access to information already stored, in a subscriber’s or user’s terminal equipment conditional on that person’s consent after being provided with clear and comprehensive information, the only exceptions being technical storage or access for the sole purpose of carrying out the transmission of a communication, or as strictly necessary to provide an information society service explicitly requested by the subscriber or user. Art. 13 restricts unsolicited communications: automated calling and communication systems without human intervention, fax or electronic mail may be used for direct marketing only in respect of subscribers or users who have given prior consent, subject to the soft opt-in for existing customers in Art. 13(2).

Verified against official sources · 2026-09-12Partly secondary sources — verify before relying

Does this apply to me?

Triggering business actions: (1) placing cookies, SDKs, pixels, local storage, device fingerprinting or any technique that reads from or writes to terminal equipment in a website or app aimed at EU users — Art. 5(3) requires consent whether or not personal data is involved, which is both different from and stricter than the GDPR; (2) sending marketing email, SMS or automated push messages to EU users; and (3) analysing communication content or traffic data in communication products such as messaging, conferencing or voice assistants, including processing communication content to train models, which must be assessed specifically against the Art. 5(1) consent requirement. Note that ePrivacy is a directive, so scope, the reading of "strictly necessary" and enforcement intensity are set by national law and differ markedly between Member States.

Key industries: All industries, GenAI & foundation models, Enterprise SaaS, AI agents

Application timeline

  1. 2002-07-31

    Directive published in the Official Journal

    The directive text is published; national effect follows transposition.

  2. 2009-12-19

    Cut-off date of the EUR-Lex consolidated text incorporating Directive 2009/136/EC

    The consolidated version cited here incorporates the Directive 2009/136/EC amendment to Art. 5(3), which changed the condition for storing information in, or gaining access to information stored in, terminal equipment from an information-and-refusal model to a consent requirement.

Obligations (3)

Each states its trigger, the evidence to retain and the clause it comes from

Confidentiality of communications and limits on training models with communication content

Severity HighArt. 5(1)-(2)

Member States must ensure, through national legislation, the confidentiality of communications and related traffic data by means of a public communications network and publicly available electronic communications services, in particular prohibiting listening, tapping, storage or other kinds of interception or surveillance of communications and related traffic data by persons other than users without the consent of the users concerned, except when legally authorised under Art. 15(1). That paragraph does not prevent technical storage necessary for the conveyance of a communication, without prejudice to the principle of confidentiality. Art. 5(2) further provides that this does not affect any legally authorised recording of communications and related traffic data carried out in the course of lawful business practice for the purpose of providing evidence of a commercial transaction or other business communication. Note that the scope qualifier — a public communications network and publicly available electronic communications services — is the first filter in any given case: internal corporate systems and features that are not an electronic communications service are not automatically caught, so the characterisation must be settled first.

Applies when
Chinese companies offering messaging, conferencing, email, customer-service or voice-assistant products. Settle scope first: whether the product is a publicly available electronic communications service under the national definition transposing the European Electronic Communications Code, Directive (EU) 2018/1972, which generally covers number-independent interpersonal communications services. If it is not, this Article does not apply directly and the analysis returns to the GDPR. Once in scope, the key judgement is that using communication content to train or fine-tune models is not "technical storage necessary for conveyance", so the consent of the users concerned is required. Note that "users concerned" in multi-party communications often includes counterparties who are not your customers, which is the hardest part to satisfy in practice.
Evidence to retain
  • · Inventory of purposes for processing communication content with the legal basis determination
  • · Design and implementation evidence for obtaining consent in multi-party communications
  • · Documented boundary between technical storage necessary for conveyance and other processing
  • · Technical controls and audit records excluding communication content from training sets

Estimated first-time effort: 8–20 person-days (estimate, not a commitment)

Penalties

The Directive itself sets no fine amounts; sanctions are laid down in national transposing law and differ markedly in practice: in some Member States the data protection authority enforces the national ePrivacy rules, in others the telecommunications regulator does, and the maximum amounts and calculation methods are not harmonised. Note that penalties under national ePrivacy law may apply independently even where the same conduct also breaches the GDPR.

Known uncertainty

Confidence is medium for three reasons. First, ePrivacy is a directive and this entry verifies only the EUR-Lex consolidated text as of 19 Dec 2009, without checking national transposing laws, which differ markedly on the scope of "strictly necessary", consent interface requirements and which authority enforces. Second, penalties are entirely national and no amounts are given here. Third, the EU-level process to replace the Directive with a regulation has remained unresolved for years, and if a new instrument is adopted this entry must be rewritten. Companies should confirm the current guidance of the local authority in each target Member State before designing an EU consent solution.

Sources (1)

Content as of 2026-09-12 · corpus 2026.09|Compiled from public official sources with links and review dates for compliance decision support. Rules change; have licensed professionals review before external disclosure, regulatory filing or contractual commitments.

Related regulations

GDPR · PIPL · CCPA control mapping
Traceable AI · cited when sourced
ISO 27001 alignment in progress
WCAG 2.1 AA accessibility target
EU ePrivacy Directive · Obligations & official sources | HaiWen HQ