# How it works

When visitors accept the Umbraco Engage cookie on the website, it allows Umbraco Engage to collect and store data about browsing behavior, preferences, and interactions. This data can include pages visited, time spent on each page, actions taken on the site, and more. This data cannot be shared with 3rd parties because the data is stored in the local database of the site.

With this information, Umbraco Engage uses this information to:

* Show Analytics
* Run A/B tests
* Personalize content
* Build local user profiles

When visitors do not accept the Umbraco Engage cookie, the website's ability to collect and store this data is limited. As a result:

* Basic Analytics
* No A/B testing
* No Personalization
* No Profiling

To comply with privacy regulations like GDPR or the California Consumer Privacy Act (CCPA), websites often allow users to accept or reject cookies. This choice impacts the type and depth of data collected and consequently affects the statistical analysis and personalization capabilities of those visitors. Learn more about [cookie permissions](https://docs.umbraco.com/umbraco-engage/developers/introduction/the-umbraco-engage-cookie/module-permissions).

The diagram below provides a general overview:

![Overview](https://1498851568-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FeiQnEGdbGIoA0IQ3nJUK%2Fuploads%2Fgit-blob-4e28fa6f8fbe6a5facb426e021789ca366768ea3%2Fengage-visualization-cookie.png?alt=media)


---

# 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.umbraco.com/umbraco-engage/security-and-privacy/how-it-works.md?ask=<question>
```

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.