> Portal Navigation:
> 
> - Append `.md` to any URL under `https://dev.wix.com/docs/` to get its markdown version.
> - Pages are either content pages (article or reference text) or menu pages (a list of links to child pages).
> - To get a menu page, truncate any URL to a parent path and append `.md` (e.g. `https://dev.wix.com/docs/sdk.md`, `https://dev.wix.com/docs/sdk/core-modules.md`).
> - Top-level index of all portals: https://dev.wix.com/docs/llms.txt
> - Full concatenated docs: https://dev.wix.com/docs/llms-full.txt

## Resource: Implement Cookie Consent Requirements

## Article: Implement Cookie Consent Requirements

## Article Link: https://dev.wix.com/docs/build-apps/launch-your-app/legal-and-security/gdpr-compliance/implement-cookie-consent-requirements.md

## Article Content:

# Implement Cookie Consent Requirements

Meeting cookie consent requirements is critical for GDPR compliance and the success of your app. To prevent your app from being uninstalled by customers striving for compliance, ensure your app complies with the requirements and test it thoroughly.

Make sure to:

1. Check the visitor's consent policy at the start of each session, and comply completely with the set policy.
2. Listen to changes in the policy during the session, and comply with any changes.

## Access the consent policy

The method you use to access and monitor the consent policy depends on the type of extension. The following table provides the relevant methods for each extension type.

| Extension | Get consent policy | Listen for changes |
|--|--|--|
| Custom elements, Embedded scripts, Wix Blocks apps | **JavaScript SDK** [`getCurrentConsentPolicy()`](https://dev.wix.com/docs/sdk/host-modules/site/consent-policy-manager/get-current-consent-policy.md) | **JavaScript SDK** [`onConsentPolicyChanged()`](https://dev.wix.com/docs/sdk/host-modules/site/consent-policy-manager/on-consent-policy-changed.md) |
| iframe apps (Deprecated) | **wix.utils** [`getCurrentConsentPolicy`](https://dev.wix.com/docs/client/api-reference/deprecated/iframe-sdk-deprecated/wix-utils.md) | **wix.utils** [`onConsentPolicyChanged`](https://dev.wix.com/docs/client/api-reference/deprecated/iframe-sdk-deprecated/wix-utils.md) |
| Worker iframe apps (Deprecated) | **wix.worker** [`Utils.getCurrentConsentPolicy`](https://dev.wix.com/docs/client/api-reference/deprecated/iframe-sdk-deprecated/wix-worker.md) | **wix.worker** [`Utils.onConsentPolicyChanged`](https://dev.wix.com/docs/client/api-reference/deprecated/iframe-sdk-deprecated/wix-worker.md) |

> **Note:** For worker iframe apps, the consent policy is also passed as a query param in the iframe URL.

## Guidelines for embedded scripts

Embedded scripts are automatically rendered or blocked based on the site visitor’s approval or denial of the cookie type, which corresponds to the [script type selected during setup](https://dev.wix.com/docs/build-apps/develop-your-app/extensions/site-extensions/embedded-scripts/about-embedded-scripts.md).

![Embedded Script Setup](https://wixmp-833713b177cebf373f611808.wixmp.com/images/041a741c1522287e14e5fcbec428d6f0.png)

If your script falls into more than one category, always select the more restrictive category. For example, if the script is **Functional**, but also collects **Analytics** data, it should be marked as **Analytics**.

If your script has marketing or analytical functionalities but needs to be listed in one of the less restrictive categories in order to carry out its main functionalities, you should do one of the following:

- Create two embedded script components, each one containing the relevant script for its category.
- Write conditional code to check the policy before running code that requires a more permissive policy.

Your script or functionality should load only if the user has granted consent.