> 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/definitions/data-act/related-service-data.md).

# related service data

Definition of related service data from Regulation (EU) 2023/2854, Article 2, point (16).

|                  |                                            |
| ---------------- | ------------------------------------------ |
| **Defined term** | related service data                       |
| **Source**       | Data Act                                   |
| **Reference**    | Article 2, point (16)                      |
| **Status**       | Published                                  |
| **Refresh rule** | Regenerate after source legal-text changes |

## Definition

> (16) related service data means data representing the digitisation of user actions or of events related to the connected product, recorded intentionally by the user or generated as a by-product of the user’s action during the provision of a related service by the provider;

## Source

[Data Act, Article 2, point (16)](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02023R2854-20231222).


---

# 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/definitions/data-act/related-service-data.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.