> For the complete documentation index, see [llms.txt](https://www.mica.wtf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.mica.wtf/eprivacy/chapter-i-general-provisions-art.-1-4/2.md).

# Art. 2 — Definitions

ePrivacy Article 2 — Definitions. Directive 2002/58/EC, Chapter I — General provisions.

Save as otherwise provided, the definitions in Directive 95/46/EC and in Directive 2002/21/EC of the European Parliament and of the Council of 7 March 2002 on a common regulatory framework for electronic communications networks and services (Framework Directive) shall apply.

> The following definitions shall also apply:
>
> > **(a)**user means any natural person using a publicly available electronic communications service, for private or business purposes, without necessarily having subscribed to this service;
> >
> > **(b)**[traffic data](https://headlesslaw.com/definitions/eprivacy/traffic-data/) means any data processed for the purpose of the conveyance of a [communication](https://headlesslaw.com/definitions/eprivacy/communication/) on an electronic communications network or for the billing thereof;
> >
> > **(c)**[location data](https://headlesslaw.com/definitions/eprivacy/location-data/) means any data processed in an electronic communications network or by an electronic communications service, indicating the geographic position of the terminal equipment of a user of a publicly available electronic communications service;
> >
> > **(d)**communication means any information exchanged or conveyed between a finite number of parties by means of a publicly available electronic communications service. This does not include any information conveyed as part of a broadcasting service to the public over an electronic communications network except to the extent that the information can be related to the identifiable subscriber or user receiving the information;
> >
> > **(e)**call means a connection established by means of a publicly available telephone service allowing two-way communication in real time;
> >
> > **(f)**consent by a user or subscriber corresponds to the data subject's consent in Directive 95/46/EC;
> >
> > **(g)**[value added service](https://headlesslaw.com/definitions/eprivacy/value-added-service/) means any service which requires the processing of traffic data or location data other than traffic data beyond what is necessary for the transmission of a communication or the billing thereof;
> >
> > **(h)**[electronic mail](https://headlesslaw.com/definitions/eprivacy/electronic-mail/) means any text, voice, sound or image message sent over a public communications network which can be stored in the network or in the recipient's terminal equipment until it is collected by the recipient;
> >
> > **(i)**[personal data breach](https://headlesslaw.com/definitions/eprivacy/personal-data-breach/) means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data transmitted, stored or otherwise processed in connection with the provision of a publicly available electronic communications service in the Community.


---

# 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.mica.wtf/eprivacy/chapter-i-general-provisions-art.-1-4/2.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.