> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-engage/security-and-privacy/security-and-privacy.md).

# Security and privacy

When using a tool like Umbraco Engage, security and privacy are important considerations due to the involvement of user data.

Security is a first-class citizen in the Umbraco Engage. Besides performance and all the features, security is important in all parts of Umbraco Engage.

Umbraco Engage is made secure and safe allowing you to have full control of all data of your visitors.

In this section, you can dive deeper into the following aspects.

## Security settings

When you have [locked down access to your Umbraco folder](https://docs.umbraco.com/umbraco-cms/reference/security/security-hardening#lock-down-access-to-your-umbraco-folder-iis), ensure the `/umbraco/engage/\*` path is allowed for all clients. You should also ensure it is not blocked based on an IP. This is needed to collect [client-side events](/umbraco-engage/developers/analytics/client-side-events-and-additional-javascript-files.md).

## Privacy settings

Umbraco Engage stores a lot of data, but because it is stored in your database(s) you have full control over this data. The data is never stored in a central data center and no visitor data is ever transmitted to Umbraco.

Umbraco Engage can be [configured](/umbraco-engage/developers/settings/configuration.md) to store the data in whatever database you specify. This can be the same database as the Umbraco installation, or a different database.

Aside from full control, Umbraco Engage also gives you tools to anonymize and [fully delete](/umbraco-engage/security-and-privacy/retention-periods-of-data.md) the data.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.umbraco.com/umbraco-engage/security-and-privacy/security-and-privacy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.