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

# Cookie Policy

### Storage Types & Purpose <a href="#storage-types-and-purpose" id="storage-types-and-purpose"></a>

**First Party Cookie**

The cookie \_crbx is a **first party cookie**, and will not be used outside of our client’s domain.

If your cookie policy requires explicit consent (the setting “Opt-in needed to persist visitor data” is turned on), **Crobox sets no cookies at all before that consent is given**. Visitors will be able to see and use the Crobox functionality, but will not be included in analytics data, will always be shown the default variant of any AB test, and no data will be persisted in connection to that session.

Once consent is given by the visitor, or if it is not needed according to our client's cookie policy, the \_crbx cookie is set as a “*persistent*” cookie, which will expire after the set time by our client (default 180 days). It is then used for *aggregated* analytics & AB testing and to remember a given consent. It is in no way used for tracking or marketing purposes. The cookie keeps a returning visitor in the same AB test variant across visits, but it is not used to pre-fill or personalise content: information the visitor gave, such as product finder answers, is kept in temporary local storage only (see below) and is not restored once that has expired.

If a visitor revokes consent, the \_crbx cookie is removed. Where explicit consent is not required, the cookie is instead reduced to a marker that records the opt-out itself, so that the choice survives into the visitor’s next visit; it no longer holds a profile identifier.

**Temporary Local Storage**

Crobox makes use of *necessary*, non-persistent local storage. Local storage is used rather than per-tab session storage so that the experience stays consistent when the visitor uses multiple browser tabs, but it is treated as *temporary*: it is reset and removed after 30 minutes of inactivity (configurable by our client). It is scoped to a single domain, so this state is not shared between subdomains.

Before consent is given, this storage holds functional state only — such as the answers a visitor gave in a product finder, and messages or campaigns the visitor dismissed — so that the visitor is not asked the same thing twice within a session. No analytics or AB test assignment data is stored before consent. Apart from an explicit opt-out, no data connected to the session is persisted without proper consent.

### Website Integration Instructions

Please follow our [Visitor's Consent - Website Integration Instructions](/getting-started/first-steps/cookie-wall-settings.md#visitors-consent-website-integration-instructions) to implement Crobox according to your cookie policy.


---

# 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.crobox.com/security-and-compliance/legal/cookie-policy.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.