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

# Data security

Read JOIN's Data Processing Agreement and list of subprocessors on join.com, and see how JOIN protects your and your candidates' data.

JOIN processes your candidates' data on your behalf under our Data Processing Agreement (DPA). The current version of the DPA, including the list of subprocessors, is published on our website.

<a href="https://join.com/en/data-processing-agreement" class="button primary">Read the Data Processing Agreement on join.com</a>

***

## FAQs

<details>

<summary>How secure is my data on JOIN?</summary>

All data on JOIN is encrypted and stored in the EU. JOIN complies with GDPR (General Data Protection Regulation) and other relevant data protection laws for your personal and candidate data.

Here's how we keep your data safe:

* Consent management: We actively manage candidate consent, notifying recruiters when a candidate withdraws an application or rejects consent. (Note: It's also important for you to manage candidate data responsibly if stored outside of JOIN.)
* Platform integrity: We conduct regular checks to remove fraudulent jobs, candidates, and companies.
* Ongoing security: We apply security measures and regular updates to protect your information.

Read more: [Candidate consent](https://help.join.com/privacy-and-security/candidate-consent.md).

</details>


---

# 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://help.join.com/privacy-and-security/data-security.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.
