> 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/legal-and-data-privacy/candidate-consent.md).
# Candidate consent
This article explains how candidate consent works in JOIN and what it means for your recruitment process and data privacy compliance.
Candidate consent is required to ensure compliance with GDPR and similar data protection regulations. JOIN automates the consent request process for candidates that are manually imported, and tracks their status to ensure recruiters only engage with candidates who have explicitly agreed to data processing.
{% hint style="info" %}
JOIN checks for duplicate candidates by email. If a manually imported candidate already exists for the same job, a validation error is shown. If they later apply directly, their manual application is deleted in favour of the direct one.
{% endhint %}
***
## Where to view consent status
JOIN makes it easy to identify whether a candidate has given consent. Consent status appears on the candidate card, and in the candidate profile. To make it easier for you to monitor consent across all applications, you can also see a dedicated `GDPR Status` column in the applications table.
If consent is still pending, the profile will display `Consent requested`. Once the candidate responds, the status updates to either `Consent given` or `Consent rejected`, as shown in the left panel of the candidate profile.
***
## Managing candidate data
Candidates have the right to withdraw their application or delete their application at any time. If they do, JOIN will automatically and permanently delete all of their data from your account, in accordance with GDPR regulations.
As a recruiter, you can also delete candidate data manually:
### Delete candidate
You can also permanently delete a candidate from your account. This will remove all applications submitted by that candidate across jobs.
To do this:
1. Open the candidate’s profile
2. Click the `...More` menu in the top-right corner
3. Select `Delete candidate`
This action is permanent and will erase the candidate’s profile and all associated job applications from your JOIN account.
### Candidate-initiated deletion or withdrawal
Candidates can take action on their own data by:
* **Withdrawing their application** to a job
* **Deleting their JOIN profile**
If either occurs:
* JOIN automatically deletes all relevant data from your account
* You’ll be notified when this happens
{% hint style="warning" %}
If you’ve stored this candidate’s data outside of JOIN, it's your responsibility to ensure it is deleted or managed according to your local data protection regulations.
{% endhint %}
***
## Legal background and responsibilities
JOIN provides automated tools to help you comply with data protection laws, but it’s important to note:
> The information provided in this article does not constitute legal advice. Always consult your legal counsel for compliance guidance relevant to your jurisdiction.
Candidates are shown and must agree to JOIN’s Privacy Policy and Terms when applying:
* [Privacy Policy](/legal-and-data-privacy/privacy-policy.md)
* [Terms of Service](/legal-and-data-privacy/terms-and-conditions.md)
You can decide, based on your local legal requirements, when to remove candidate data from your account if no consent is given.
JOIN automatically handles consent for candidates who apply directly through a job posting on the JOIN platform or via partner job boards.
---
# 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/legal-and-data-privacy/candidate-consent.md?ask=&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.
