By default, whether used to load a consent notice, a preference center, or a privacy request widget, the Didomi Web SDK, including its assets (JavaScript files, images, etc.) and API requests, relies on the privacy-center.org domain.
Alternatively, you can use your own domain to load the SDK and its assets.
A custom domain can be used for:
- Sharing consents across domains
- Serving the Web SDK and API requests from your own domain by redirecting all requests to your domain instead of the domain used by Didomi (privacy-center.org). This ensures that Didomi does not appear as a third-party on your websites.
- Preventing adblockers from blocking the Didomi SDK.
Setup options available
We offer two solutions for setting up your domain:
| Didomi default domain (privacy-center.org) |
NS Delegation (subdomain)
|
Reverse proxy (subdomain)
|
Reverse proxy (main domain)
|
|
|
Increase Adblocker resilience |
❌ | ✅ | ✅ | ✅ |
|
Safari ITP |
❌ | ❌ | ✅ | ✅ |
|
Implementation complexity |
🟢 Low | 🟢 Low – NS record only | 🔴 High – Requires reverse-proxy setup | 🔴 High – Requires reverse-proxy setup + Path transformation |
|
Recommendation |
Best for low-budget, non-technical clients, or non-critical setups |
Best for low-budget, non-technical clients, or non-critical setups |
Best for technical teams with strong infra and ITP concerns, and allows subdomain branding |
Best for technical teams with strong infra and ITP concerns |