> 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/candidate-consent.md).

# Candidate consent

See how JOIN asks candidates you add manually for consent, check each candidate's consent status, and delete candidate data when you need to.

When you add a candidate manually, JOIN sends a consent request and tracks the response. You can check whether the candidate has agreed to data processing for your company.

<figure><img src="https://1825767176-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEdFjOFlkC1DEfDv3nGRh%2Fuploads%2FNuYIBbXVGZubJf8dNxO8%2Fconsent-request-email-template.png?alt=media&amp;token=403012be-30f5-4f7b-bacd-47034e6a15a4" alt=""><figcaption></figcaption></figure>

{% 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

Consent status appears on the candidate card and in the candidate profile. To check the status across candidates, use the `GDPR status` column in the `Candidates` table.

The profile shows `Consent requested` while the request is pending and `Consent given` when the candidate accepts. If the candidate declines a pending request, JOIN deletes their candidate profile and applications from your company’s account.

***

## Manage candidate data

Withdrawing a single application and deleting candidate data are separate actions. As a recruiter, you can delete a candidate from your company’s account.

### Delete a candidate

You can also permanently delete a candidate from your account. This removes 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`

<figure><img src="https://1825767176-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEdFjOFlkC1DEfDv3nGRh%2Fuploads%2FSRjrAKtBIkNxBHG3jlEI%2Fdelete-candidate.gif?alt=media&amp;token=fc4cd419-467c-4162-8a07-eb095e206107" alt=""><figcaption></figcaption></figure>

This action is permanent and erases the candidate’s profile and all associated job applications from your JOIN account. For the full steps, including bulk deletion, see [Delete a candidate](https://help.join.com/review-candidates/reject-delete-or-block.md#delete-a-candidate).

### Candidate-initiated deletion or withdrawal

* **Withdrawing an application** changes the status of that application. JOIN retains the withdrawn record for audit. Withdrawing the application alone does not delete the candidate’s data from your company’s account.
* **Declining a pending consent request** removes the candidate profile and applications from the company that requested consent.
* **Deleting their JOIN account** removes the candidate’s linked profiles and applications from the affected company accounts.

{% 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](https://help.join.com/privacy-and-security/privacy-policy.md)
* [Terms & Conditions](https://help.join.com/privacy-and-security/terms-and-conditions.md)

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/privacy-and-security/candidate-consent.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.
