> For the complete documentation index, see [llms.txt](https://www.headlesslaw.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.headlesslaw.com/eprivacy/readme.md).

# ePrivacy

*In force · Consolidated version of 19 December 2009 ·* [*Official source*](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02002L0058-20091219)

**Directive 2002/58/EC** — of the European Parliament and of the Council of 12 July 2002 concerning the processing of personal data and the protection of privacy in the electronic communications sector (Directive on privacy and electronic communications)

The full text is available article by article, one page per article (`articles/<number>`). Every numbered paragraph and point carries a stable anchor (`#p-3` for paragraph 3, `#p-3-a` for its point (a)), so any provision can be cited with a direct link. The English consolidated manifestation from CELLAR is reproduced verbatim; the official text remains the EU publication at [EUR-Lex](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02002L0058-20091219).

### Contents

#### [Chapter I — General provisions](/eprivacy/chapters/i.md)

* [Article 1 — Scope and aim](/eprivacy/articles/1.md)
* [Article 2 — Definitions](/eprivacy/articles/2.md)
* [Article 3 — Services concerned](/eprivacy/articles/3.md)
* [Article 4 — Security of processing](/eprivacy/articles/4.md)

#### [Chapter II — Specific provisions](/eprivacy/chapters/ii.md)

* [Article 5 — Confidentiality of the communications](/eprivacy/articles/5.md)
* [Article 6 — Traffic data](/eprivacy/articles/6.md)
* [Article 7 — Itemised billing](/eprivacy/articles/7.md)
* [Article 8 — Presentation and restriction of calling and connected line identification](/eprivacy/articles/8.md)
* [Article 9 — Location data other than traffic data](/eprivacy/articles/9.md)
* [Article 10 — Exceptions](/eprivacy/articles/10.md)
* [Article 11 — Automatic call forwarding](/eprivacy/articles/11.md)
* [Article 12 — Directories of subscribers](/eprivacy/articles/12.md)
* [Article 13 — Unsolicited communications](/eprivacy/articles/13.md)
* [Article 14 — Technical features and standardisation](/eprivacy/articles/14.md)
* [Article 14a — Committee procedure](/eprivacy/articles/14a.md)
* [Article 15 — Application of certain provisions of Directive 95/46/EC](/eprivacy/articles/15.md)
* [Article 15a — Implementation and enforcement](/eprivacy/articles/15a.md)

#### [Chapter III — Final provisions](/eprivacy/chapters/iii.md)

* [Article 16 — Transitional arrangements](/eprivacy/articles/16.md)
* [Article 17 — Transposition](/eprivacy/articles/17.md)
* [Article 18 — Review](/eprivacy/articles/18.md)
* [Article 19 — Repeal](/eprivacy/articles/19.md)
* [Article 20 — Entry into force](/eprivacy/articles/20.md)
* [Article 21 — Addressees](/eprivacy/articles/21.md)

### Level 2 and Level 3

* [Level 3](/eprivacy/level-3.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.headlesslaw.com/eprivacy/readme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.