Documentation
Straight answers about what Let's Consent supports
What the platform does, what it deliberately doesn't, and the reasoning behind it.
Looking for compliance answers?
Everything on data retention, information security, hosting locations, GDPR compliance and our subprocessors lives on the Compliance page.
Does Let's Consent support Cross-Domain Consent Sharing?
No.
Consent is shared automatically across all subdomains of one domain: a visitor who
decides on www.acme.com
is not asked again on
shop.acme.com,
because the consent cookie is set for the whole domain. Consent does not carry over to a
different domain: a visitor who decides on
acme.com is asked
once more on
acme.de.
This is not a product choice. Cross-domain consent sharing for unidentified visitors relied on a piece of third-party storage (a cookie, local storage, or a hidden iframe) that every site of a group could read. Established browsers have removed exactly that capability, so there is no longer browser support for cross-domain consent sharing for unidentified users.
Browser support
- Safari blocks all third-party cookies and partitions all third-party storage (Intelligent Tracking Prevention, fully enforced since 2020). No shared storage of any kind works across domains. Because every browser on iOS must use Apple's WebKit engine, this also covers Chrome, Firefox and Edge on iPhone and iPad.
- Firefox ships Total Cookie Protection by default (since 2022): every website gets its own isolated cookie and storage jar. A helper domain embedded on acme.com and on acme.de sees two different, empty storages.
- Chrome partitions all third-party storage (local storage, IndexedDB, iframe storage) per top-level site since version 115 (July 2023), which broke storage-based sharing between different registrable domains. Third-party cookies are still allowed in the default configuration, but are blocked in Incognito mode and whenever the user or an extension disables them, so cookie-based sharing works only for part of the Chrome audience.
- Edge is Chromium-based and inherits Chrome's storage partitioning. Its built-in Tracking Prevention (default "Balanced") additionally blocks storage access for known tracking domains, which consent helper domains can fall under.
- Brave blocks third-party storage by default and makes what remains ephemeral and partitioned. Nothing survives across domains or sessions.
How the market implements it
| Vendor | Technical approach | Limitations |
|---|---|---|
| Cookiebot | Third-party local storage item on a shared origin, read by every site of the domain group | Blocked by Safari, Firefox and Brave; broken between different top-level domains since Chrome 115 (per Cookiebot's own docs). No working cross-domain consent. |
| Usercentrics | Hidden iframe on a shared Usercentrics origin, consent exchanged via third-party storage | Vendor states it no longer works between different root domains since Chrome 115 and not on iOS at all. Only subdomains of one root domain remain. No working cross-domain consent. |
| Didomi | Consent cookie on a shared helper domain (e.g. privacy.your-domain.com), read as a third-party cookie by all sites | Depends on third-party cookies: blocked by Safari, Firefox, Brave and Chrome Incognito. Works only for the shrinking share of visitors whose browser still allows them. No reliable cross-domain consent. |
| OneTrust | Server-side consent profile in the OneTrust cloud, keyed to a user identifier the website passes in (typically from a login) | Works across domains and devices, but only for identified users. The website must recognize the visitor before the banner loads; anonymous visitors get no sharing. Requires storing per-person consent profiles centrally. |
The bottom line: for visitors who are not logged in, no technique is left that reliably works across registrable domains in current browsers. Let's Consent therefore asks once per registrable domain and shares that answer across all of its subdomains via a first-party cookie, which every browser fully supports. Should a first-party, identification-free mechanism become practical, we will evaluate it; we will not build sharing on visitor identification or hidden iframes.
Browser and vendor behavior per their public documentation, verified July 2026. Offerings change. Spotted an error? Tell us at hi@letsconsent.eu and we'll correct it.