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.

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.

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.

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.