# Privacy opt-in
Privacy opt-in adds a consent modal before the recorder opens.
Use it when you need explicit consent before a customer shares a recording that may contain personal or sensitive information.
Once accepted, Screendesk remembers the choice in that browser so repeat visitors are not asked again.
{% hint style="info" %}
**Plan availability:** All plans.
{% endhint %}
***
### How it works for customers
When Privacy opt-in is enabled, a modal appears before the recorder loads.
The modal can include:
1. your workspace **logo**
2. a customizable **consent message**
3. an optional **privacy policy link**
4. **Decline** and **Accept** buttons
When the customer clicks **Accept**, Screendesk stores the consent in the browser and opens the recorder.
If the customer clicks **Decline**, they cannot continue to the recorder.
Once accepted, the modal does not appear again in that browser unless browser data is cleared.
***
### Enable Privacy opt-in
{% stepper %}
{% step %}
#### Go to Security settings
Open **Settings** → **Security** in your Screendesk workspace.
{% endstep %}
{% step %}
#### Find Privacy opt-in
Scroll to the **Privacy opt-in** section.
{% endstep %}
{% step %}
#### Enable the toggle
Turn on **Privacy opt-in**.
A live preview appears below the setting so you can see what customers will see.
{% endstep %}
{% step %}
#### Customize the consent message
Enter the message shown before the customer starts recording.
Example:
> We need your consent before you can start recording.
If you leave it blank, Screendesk uses the default message.
{% endstep %}
{% step %}
#### Add a privacy policy link
Set:
* **Link text** — for example, **Privacy Policy**
* **URL** — the destination of your privacy policy
Leave both fields empty if you do not want to show a link.
{% endstep %}
{% step %}
#### Save
Click **Save**.
{% endstep %}
{% endstepper %}
***
### Add translations
If your workspace supports multiple locales, locale tabs appear at the top of the preview.
Switch to a locale and enter the translated consent message and link text.
If a field is blank, Screendesk falls back to English.
Supported languages:
* 🇬🇧 English
* 🇫🇷 French
* 🇪🇸 Spanish
* 🇵🇹 Portuguese
* 🇩🇪 German
* 🇳🇱 Dutch
* 🇧🇷 Brazilian Portuguese
{% hint style="info" %}
If a translation is empty, Screendesk shows the English version by default.
{% endhint %}
See also [Internationalization](/request-screen-recording/branding-and-customization/internationalization.md).
***
### Disable Privacy opt-in
Turn off **Privacy opt-in** in **Settings** → **Security**.
Click **Save**.
Customers will go directly to the recorder without seeing the consent modal.
Your message and privacy policy link stay saved, so you can enable the feature again later.
***
### What counts as consent
Consent is stored in the customer's browser.
It is not tied to a customer account or email address.
This means:
* clearing browser data resets consent
* a different browser requires consent again
* a different device requires consent again
* Chrome extension users do not see this modal
***
### How Privacy opt-in works with Recorder Flow
If both features are enabled, Screendesk shows them in this order:
1. Privacy opt-in
2. Recorder Flow
3. Recorder
Use **Privacy opt-in** when you need an explicit **Accept** step before recording starts.
Use **Recorder Flow** when you want to guide the customer before recording starts.
See [Recorder flow](/request-screen-recording/branding-and-customization/recorder-flow.md).
***
### Best practices
**Keep the consent message simple.**
Say what the customer is agreeing to in one or two short sentences.
**Link your privacy policy.**
This gives customers the context they need before accepting.
**Translate the message.**
Localized consent text reduces confusion and increases completion rates.
**Test in a private window.**
This avoids using a previously stored consent state.
**Review with your legal team if needed.**
Browser-level consent storage may not meet every compliance requirement.
***
### Troubleshooting
The consent modal does not appear
Check these first:
* **Privacy opt-in** is enabled
* you clicked **Save**
* you are testing the browser-based recorder
* the browser already has a stored consent state
Try again in a private or incognito window.
The wrong language is shown
Screendesk uses the browser locale.
If the translation for that locale is blank, Screendesk falls back to English.
The privacy policy link is missing
Make sure both **Link text** and **URL** are filled in.
If either field is empty, the link may not appear as expected.
A customer clicked Decline
The customer stays blocked from the recorder until they click **Accept**.
There is no separate redirect or decline page.
***
### FAQ
Does the consent modal appear for Chrome extension users?
No.
Privacy opt-in applies to the browser-based recorder only.
Chrome extension users are authenticated workspace members and do not see this modal.
Can I customize the button labels?
The **Decline** and **Accept** labels follow the locale used by the recorder.
They are not configured as separate custom fields in this setting.
What happens if a customer clicks Decline?
The recorder does not open.
The modal stays on screen until the customer accepts or leaves the page.
Is consent logged in Screendesk?
Consent is stored in the customer's browser.
It is not stored as an audit event in Screendesk.
Can I link to my own privacy policy?
Yes.
You can set both the link text and the destination URL.
Does the customer need to accept every time?
No.
After acceptance, Screendesk remembers the choice in that browser.
If cookies or local storage are cleared, the modal can appear again.
***
### Related pages
* [Recorder flow](/request-screen-recording/branding-and-customization/recorder-flow.md)
* [Customize recorder](/request-screen-recording/branding-and-customization/customize-recorder.md)
* [Hide sensitive data](/security/hide-sensitive-data.md)
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.screendesk.io/security/privacy-opt-in.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.