> For the complete documentation index, see [llms.txt](https://interactively.gitbook.io/interactively-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interactively.gitbook.io/interactively-docs/admin/gdpr-compliance.md).
# GDPR Compliance
### Can Interactively demos withhold tracking until consent is granted?
In compliance with GDPR requirements, companies are required to ask for permission to use cookies on their websites. Cookies are commonly used to track user activities. Interactively's tracker utilizes cookes to store unique user data and identify users. Although the Interactively tracker cookie doesn't store PII, it is still considered personal data as it tracks user behavior on the website.
Websites that require cookie consent will display a user interface (UI) element prompting visitors to accept or decline cookies. This UI component can vary in complexity, offering users choices regarding marketing, analytics, or other types of tracking.
By default, Interactively tracks user interactions such as step completions, hotspot clicks, and CTA clicks to generate data for the Analytics dashboard.
However, when an Interactively demo is embedded as an iframe on an external website, it cannot automatically inherit the host site’s consent settings. Asking users for multiple consent approvals—one for the website and one for each embedded demo—would create a fragmented user experience.
## Interactively's Approach to "Do Not Track"
By default, Interactively tracks user interactions (such as clicks and step completions) to provide valuable data and analytics for our customers. We understand that there may be instances when an Interactively creator wishes to limit tracking, either by anonymizing IP addresses or completely disabling tracking. In some cases the creator may want to disable tracking until the user consents to cookie-based tracking on the host website. Which is why we provide settings to limit or disable tracking:
These settings can be found in Settings > Privacy & Access in all plans.
### Fully deactivate tracking for your Interactively demo
When **Do Not Track** is enabled, Interactively stops tracking user clicks and page views, and analytics data will no longer be available in the Interactively Analytics dashboard.
## Enable tracking upon cookie consent on the parent website
{% hint style="info" %}
This setting applies when an Interactively demo is embedded in a parent website via an iFrame. Implementing this requires technical setup.
{% endhint %}
If your website asks for cookie consent from the user, Interactively can honor this consent once it is granted. However, enabling this feature requires a small code snippet on your website to communicate the consent status to embedded Interactively demos.
If the user grants cookie consent for tracking on your website, you can notify each embedded Interactively demo by sending a message to enable tracking. Interactively will keep track of events that happen inside the demo even if **Do Not Track** is turned on, but it will only transmit event data to its tracking server once consent is received from the host site.
### How it works:
1. Users engaging with the website will see a cookie consent banner.
2. If the user approves, the website sends consent approval to Interactively.
3. Interactively receives the message and begins tracking user interactions within the demo.
### C**ode snippet for consent communication**
To send the message to the Interactively iFrames that the user has consented to the use of cookies, you need to send the following JavaScript after consent is given:
```
// Some code
```
When the Interactively iFrame(s) receive this message, all previously recorded events will be sent to the Interactively tracking server, along with all new events moving forward.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://interactively.gitbook.io/interactively-docs/admin/gdpr-compliance.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.