> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/help-and-support/security-and-privacy/information-storage.md).

# Information storage

Find out how and where Coupler.io stores your data. Learn about data retention policies, storage locations, and what information is kept after imports.

To learn more about the Privacy and Security of our product, please read our [Privacy Policy](https://www.coupler.io/privacy-policy).

* Our product is designed to store data for a period of time required to provide users with stable integrations with different applications in a secure and encrypted state, prioritizing the protection of sensitive information. With robust encryption protocols in place, we ensure that your data remains confidential and its integrity remains intact.
* Coupler.io securely encrypts importer settings and credentials provided by users when setting up an importer.
* User data is automatically deleted within 7 days upon a user's request for account deletion. Users can also request full data deletion earlier by contacting our support team.


---

# 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.coupler.io/help-and-support/security-and-privacy/information-storage.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.