# 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.

<figure><img src="https://3820804400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfW6XSzJSKsNyZnOkSJPt%2Fuploads%2FAwNQ8prUsOvO0EjvOxDn%2FScreenshot%202026-03-17%20at%2009.43.47.png?alt=media&#x26;token=2dc2d233-837a-4d7e-a701-dd16a9926145" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://3820804400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfW6XSzJSKsNyZnOkSJPt%2Fuploads%2Fyqr5HFOPkcwRkbJmh0Pk%2FScreenshot%202026-03-16%20at%2016.15.15.png?alt=media&#x26;token=5c138f3f-b494-4a6a-8647-1c9a92d1264f" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://3820804400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfW6XSzJSKsNyZnOkSJPt%2Fuploads%2Fyrwdl1X125qolwbWkUpy%2FScreenshot%202026-03-16%20at%2016.15.14.png?alt=media&#x26;token=dfad6074-6ce5-46dc-99b5-3c1803030222" alt=""><figcaption></figcaption></figure>

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](https://docs.screendesk.io/request-screen-recording/branding-and-customization/internationalization).

***

### 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](https://docs.screendesk.io/request-screen-recording/branding-and-customization/recorder-flow).

***

### 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

<details>

<summary>The consent modal does not appear</summary>

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.

</details>

<details>

<summary>The wrong language is shown</summary>

Screendesk uses the browser locale.

If the translation for that locale is blank, Screendesk falls back to English.

</details>

<details>

<summary>The privacy policy link is missing</summary>

Make sure both **Link text** and **URL** are filled in.

If either field is empty, the link may not appear as expected.

</details>

<details>

<summary>A customer clicked Decline</summary>

The customer stays blocked from the recorder until they click **Accept**.

There is no separate redirect or decline page.

</details>

***

### FAQ

<details>

<summary>Does the consent modal appear for Chrome extension users?</summary>

No.

Privacy opt-in applies to the browser-based recorder only.

Chrome extension users are authenticated workspace members and do not see this modal.

</details>

<details>

<summary>Can I customize the button labels?</summary>

The **Decline** and **Accept** labels follow the locale used by the recorder.

They are not configured as separate custom fields in this setting.

</details>

<details>

<summary>What happens if a customer clicks Decline?</summary>

The recorder does not open.

The modal stays on screen until the customer accepts or leaves the page.

</details>

<details>

<summary>Is consent logged in Screendesk?</summary>

Consent is stored in the customer's browser.

It is not stored as an audit event in Screendesk.

</details>

<details>

<summary>Can I link to my own privacy policy?</summary>

Yes.

You can set both the link text and the destination URL.

</details>

<details>

<summary>Does the customer need to accept every time?</summary>

No.

After acceptance, Screendesk remembers the choice in that browser.

If cookies or local storage are cleared, the modal can appear again.

</details>

***

### Related pages

* [Recorder flow](https://docs.screendesk.io/request-screen-recording/branding-and-customization/recorder-flow)
* [Customize recorder](https://docs.screendesk.io/request-screen-recording/branding-and-customization/customize-recorder)
* [Hide sensitive data](https://docs.screendesk.io/security/hide-sensitive-data)