> For the complete documentation index, see [llms.txt](https://docs.userlane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.userlane.com/security-and-privacy/eu-data-act-data-categories-and-portability.md).

# EU Data Act: data categories and portability

What data Userlane makes available under the EU Data Act, which categories are excluded, and how to request an export.

The European Union Data Act (Regulation (EU) 2023/2854) places obligations on providers of data processing services. Because Userlane processes data generated by and about end users inside customer applications, the Act's data portability and switching obligations apply. This article sets out which data categories are exportable, which are excluded, and how to request an export.

Userlane GmbH is incorporated in Germany. All production infrastructure runs on Microsoft Azure in European Union regions, under EU jurisdiction. Userlane applies technical and organizational measures against unlawful third-country government access, in line with the standard contractual and regulatory framework for EU-hosted services.

## Exportable data categories

The following data categories can be exported at any time, either through the Userlane portal or through the REST API[^1].

<table><thead><tr><th width="184.25445556640625">Category</th><th width="387.7110595703125">What it contains</th><th width="86.3333740234375">Export method</th><th width="79.6796875">Format</th></tr></thead><tbody><tr><td>HEART data</td><td>Daily scores per dimension (Happiness, Efficiency, Adoption, Risk, Task Success), plus user and session counts</td><td>API</td><td>JSON</td></tr><tr><td>Net Promoter Score (NPS) responses</td><td>Score (0 to 10), optional free-text comment, timestamp, user ID</td><td>API</td><td>JSON</td></tr><tr><td>Survey responses</td><td>Score (1 to 5), optional free-text comment, timestamp, user ID</td><td>API</td><td>JSON</td></tr><tr><td>Tag interaction data</td><td>Per-user, per-tag, per-day click counts on tagged elements</td><td>API</td><td>JSON</td></tr><tr><td>Task adoption data</td><td>Per-user starts, completions, time to complete; step-level event stream</td><td>API</td><td>JSON</td></tr><tr><td>Guide interaction data</td><td>Guide progress events, completions, step-level events</td><td>API</td><td>JSON</td></tr><tr><td>Announcement interaction data</td><td>Views and clicks per announcement</td><td>API</td><td>JSON</td></tr><tr><td>Guide texts and translations</td><td>Full guide content across all configured languages</td><td>API</td><td>JSON</td></tr><tr><td>User profile data</td><td>User attributes, audience membership, last-seen dates</td><td>API</td><td>JSON</td></tr><tr><td>Content analytics (portal export)</td><td>Guide health scores, tooltip and beacon interaction counts, announcement reach, validator compliance rates</td><td>Portal download</td><td>CSV</td></tr></tbody></table>

Each API endpoint is documented in the Developer Reference, including request parameters, pagination, and a live test button. See [Export HEART data](/developer-reference/export-heart-nps-survey-tag-and-task-data-via-api.md), [Export Guides and Announcement data](/developer-reference/export-guides-guide-progress-and-announcement-data-via-api.md), and [User profile data export](/developer-reference/user-profile-data-export.md). The portal comma-separated values (CSV) export is available under the analytics views for each content type.

Data retention varies by category. NPS, survey, and tag data are available for the last two years. Task step-level events are available for the last 31 days. For longer history, schedule a regular pull into a local data store.

## Excluded data categories

The following categories are not exportable under the Data Act and are excluded from its portability obligations.

<table><thead><tr><th width="245.2803955078125">Category</th><th>Reason for exclusion</th></tr></thead><tbody><tr><td>Internal system algorithms and proprietary AI models</td><td>Protected as trade secrets. These are the computational methods Userlane uses to produce scores and recommendations, not customer data.</td></tr><tr><td>Aggregated, anonymized data that cannot be attributed to a single customer's deployment</td><td>This data has been irreversibly de-identified and aggregated. It does not constitute personal data or customer-specific Service Data.</td></tr><tr><td>Raw infrastructure and application logs</td><td>Operational telemetry used for system reliability and debugging. Not generated by or about end users in the meaning of the Act.</td></tr></tbody></table>

Excluded categories either cannot be isolated to a single customer's deployment or are protected as trade secrets.

## How to request an export

For API-based exports, generate an authorization token in the Userlane portal under **Settings** > **API Token**, then call the relevant endpoint. See [Your Userlane API token](/developer-reference/your-userlane-api-token.md). The Developer Reference has step-by-step instructions for each API, including the HEART, NPS, survey, tag, task, guide, and announcement endpoints.

For portal-based CSV exports, open the analytics view for the content type you need, then use the export option on that page.

If you need a data export that is not covered by the self-service options above, contact Userlane through the support channel described in your service agreement. See [Contact and escalation](/support/contact-and-escalation.md).

## Relevant articles

{% content-ref url="/pages/TcXdqgybeGLnS1EODhcN" %}
[Your Userlane API token](/developer-reference/your-userlane-api-token.md)
{% endcontent-ref %}

{% content-ref url="/pages/pFJIN3rpdCcXyo6ifg4j" %}
[Export HEART, NPS, Survey, Tag, and Task data via API](/developer-reference/export-heart-nps-survey-tag-and-task-data-via-api.md)
{% endcontent-ref %}

{% content-ref url="/pages/0XiPZYLLfKewriq8G6Av" %}
[User profile data export](/developer-reference/user-profile-data-export.md)
{% endcontent-ref %}

{% content-ref url="/pages/h4XuR33OT54sP0N63SOo" %}
[Hosting and certifications](/security-and-privacy/hosting-and-certifications.md)
{% endcontent-ref %}

## FAQ

<details>

<summary>What data can I export from Userlane under the EU Data Act?</summary>

HEART scores, NPS and survey responses, tag and task interaction data, guide texts and translations, guide and announcement interaction data, user profile data, and content analytics summaries. Exports are available in JavaScript Object Notation (JSON) through the API or in CSV through a portal download.

</details>

<details>

<summary>How do I request a data export?</summary>

Generate an API token in the Userlane portal under **Settings** > **API Token**, then call the relevant endpoint documented in the Developer Reference. For CSV exports, use the export option on the analytics page for the content type you need. If you need something beyond self-service, contact Userlane support.

</details>

<details>

<summary>Why are some data categories excluded?</summary>

Internal algorithms and AI models are protected as trade secrets. Aggregated, anonymized data cannot be attributed to any single customer and falls outside the scope of the Act. Raw infrastructure logs are operational telemetry, not data generated by or about end users.

</details>

[^1]: The REST API is the application programming interface (API) for exporting Userlane data. Each endpoint returns JSON and is documented in the Developer Reference.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.userlane.com/security-and-privacy/eu-data-act-data-categories-and-portability.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.