> For the complete documentation index, see [llms.txt](https://cmp.docs.sirdata.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cmp.docs.sirdata.net/en/install/cache-systems-exclusion/sirdata-script-cache-management.md).

# Sirdata Script Cache Management

Sirdata CMP scripts are **geolocated**: the version served depends on the user's country, because consent collection rules differ from one country to another. Caching therefore cannot be delegated to a third-party system that ignores this geographic dimension.

Sirdata manages caching end to end, using a **two-tier** system.

***

## 1. Browser cache (private)

Scripts are served with a `Cache-Control: private` directive and a **10-minute** lifetime.

* **`private`** means only the end user's browser is allowed to keep a copy of the script. No shared cache (proxy, third-party CDN, cache plugin, server-side cache) is allowed to store or re-serve it.
* **10 minutes** of browser-side lifetime: long enough to avoid redundant requests during a browsing session, short enough for any update to propagate quickly.

{% hint style="info" %}
The `private` directive exists for a specific reason: it prevents public cache systems from taking over delivery and serving **the wrong version** of the script — for example, country A's version to a user in country B, or a version predating a regulatory change.
{% endhint %}

## 2. Public cache managed by Cloudflare

On top of that, a public cache is used, **entirely managed by Sirdata through Cloudflare**, with a **3600-second (1 hour)** lifetime.

This cache is segmented **by country**: each point of presence serves the variant matching the applicable regulation. This is exactly what a generic public cache cannot do, hence the need to control it at the CDN level.

## 3. All other caches are deliberately disabled

Any other caching layer — third-party CDN, reverse proxy, application cache, CMS cache plugin — is **deliberately disabled** and must not be re-enabled. See the other pages in this section to exclude Sirdata scripts from the main WordPress cache plugins.

***

## Special case: loading the CMP through your own CDN

Some integrations unblock CMP loading by routing it through the client's own CDN. In that case:

* **The rules are identical**: 10-minute private browser cache, country-aware public cache, no other cache allowed.
* The only difference: the cache system is managed at **Bunny** instead of Cloudflare.

{% hint style="danger" %}
In all cases, do not cache or modify Sirdata's CMP script yourself. Delivery and updates are handled by Sirdata, as stipulated in our T\&C.
{% endhint %}


---

# 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://cmp.docs.sirdata.net/en/install/cache-systems-exclusion/sirdata-script-cache-management.md?ask=<question>&goal=<endgoal>
```

`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.