> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/user/guide/devices-and-settings/tachograph-and-compliance.md).

# Tachograph and compliance

Manage tachograph compliance for your fleet by downloading DDD files on demand and routing them automatically to the right recipients.

For tachograph-capable vehicles, these blocks let you **remotely retrieve digital tachograph data as DDD files** and have them emailed automatically, supporting compliance with driving-time and rest-period regulations.

## What are DDD files?

DDD files store detailed information from a digital tachograph about driver activities, including driving hours, rest periods, and potential compliance violations. The frequency of downloading and the retention period are regulated by law. In the EU, for example, DDD files are typically downloaded about every month from the driver's card and about every three months from the vehicle unit, with a mandatory storage period of about one year.

{% hint style="warning" %}
Navixy supports the **download functionality** of DDD files. Navixy doesn't process them in any way and doesn't read any data from them.
{% endhint %}

<table data-view="cards"><thead><tr><th>Block</th><th>Purpose</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4>DDD files download</h4></td><td>Request and download DDD files on demand from the device.</td><td><a href="/docs/user/guide/devices-and-settings/tachograph-and-compliance/ddd-download.md">DDD files download</a></td></tr><tr><td><h4>DDD files recipient email</h4></td><td>Email each downloaded DDD file to up to 5 recipients when the device delivers it.</td><td><a href="/docs/user/guide/devices-and-settings/tachograph-and-compliance/ddd-emails.md">DDD files recipient email</a></td></tr></tbody></table>


---

# 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://navixy.com/docs/user/guide/devices-and-settings/tachograph-and-compliance.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.