> For the complete documentation index, see [llms.txt](https://digifortune-1.gitbook.io/digifortune-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://digifortune-1.gitbook.io/digifortune-docs/vehicle-identity-information.md).

# Vehicle Identity Information

We may collect:

* vehicle make and model  
* model year  
* fuel type and mileage  
* period of ownership/use  
* optional plate number or VIN (Vehicle Identification Number) entered by the user  

 

Purposes: To create and manage the requested vehicle profile and associate driving records.

 

Legal basis: Necessary for the performance of a contract (Article 15(1)(4) of the Personal Information Protection Act) / Your consent for optional identifiers (Article 15(1)(1)).

Retention period: Until the user deletes the information or deletes the account.

Full text available in the app settings - Privacy Policy.


---

# 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://digifortune-1.gitbook.io/digifortune-docs/vehicle-identity-information.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.