> For the complete documentation index, see [llms.txt](https://kai-eco.gitbook.io/terms/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kai-eco.gitbook.io/terms/privacy-statement/how-long-do-we-hold-private-information.md).

# How Long Do We Hold Private Information?

How long will KAIECO keep the data?

Your personal data will be kept strictly for the purposes of which it is collected, and, in any case, following the principle of data minimization provided for in any applicable regulations.

If you are a KAIECO user, your data will be kept for the entire duration of your relationship with KAIECO and or our partners. This includes from the moment you exercise your right to cancel your data or sell your digital assets related to KAIECO.

Your data will be kept discretely for a period of seven years in order to meet the legal responsibilities that may arise from the services provided and ten years in the case of conservation of personal data in compliance with the rules of prevention of money laundering or otherwise required to by law.


---

# 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://kai-eco.gitbook.io/terms/privacy-statement/how-long-do-we-hold-private-information.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.