> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/policies/privacy-and-security/data-processing-agreement-model.md).

# Data Processing Agreement

Where to find the Data Processing Agreement (Article 28 GDPR) between Neostore SAS (The Wallet Crew) and its clients.

The Data Processing Agreement is an annex to the General Terms and Conditions of Sale. It is published, versioned, and dated on The Wallet Crew official website, which is the single source of truth. This documentation no longer hosts a copy of the contractual text.

{% hint style="info" %}
The DPA in force is DPA 2026.2. It describes the processing operations, security measures, data breach notification commitments, authorised sub-processors, and international transfer rules.
{% endhint %}

Read the [English version](https://www.thewalletcrew.io/en/legales/dpa-2026-2) or the [French version](https://www.thewalletcrew.io/legales/dpa-2026-2).

For personal data matters, contact <privacy@thewalletcrew.com>.

See also [Contractual documents](/policies/terms-and-conditions.md), [Data Protection FAQ](/policies/privacy-and-security/data-protection-faq.md), and [Security overview and trust model](/policies/privacy-and-security/security-overview-and-trust-model.md).


---

# 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.thewalletcrew.io/policies/privacy-and-security/data-processing-agreement-model.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.