# 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. As a default the \_crbx cookie is set as a temporary “*session*” cookie, meaning that it is automatically removed after the browser is closed. It is necessary in order to keep a consistent experience for the visitor, also in case our client uses subdomains. Visitors will be able to see and use the Crobox functionality, but will not be included in analytics data, will not see any AB test variants, and no data will be persisted in connection to that session.

If consent is given by the visitor, or not needed according to our client's cookie policy, the cookie will be 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. A returning visitor will not see any pre-filled information or content based on information given in a previous session.

**Temporary Local & Session Storage**

Crobox makes use of *necessary*, non-persistent local and session storage. Local storage is needed for when the visitor uses multiple browser tabs, but is treated as *temporary*. Once the visitor closes their browser, both storage types will expire, and no data connected to the session, excluding explicit opt-out information, 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: 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.crobox.com/security-and-compliance/legal/cookie-policy.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.