Domains

The domain determines from where the Didomi SDK and assets are served. In this section we cover the options available to your organization for determining which domain is utilized to serve the SDK and assets.

• Default domain

• Custom domain

---

Default domain

By default, Didomi relies on the privacy-center.org domain when serving assets- whether that is to load a consent notice, a preference center, or a privacy request widget, Didomi's SDKs and integrations, including their assets (JavaScript files, images, etc.) and API requests.

Utilizing the default domain is a fast and easy way to launch a consent notice on your organization's property.

Custom domain

As an alternative to the custom domain that Didomi provides, your organization can also configure a custom domain. While using a custom domain your organization can:

Serve SDK and API requests	All requests are redirected to your organization's custom domain instead of the default domain used by Didomi (privacy-center.org). This ensures that Didomi does not appear as a third-party on your websites. See the links below for more information: Serve Didomi assets from your domain (web) Serve Didomi assets from your domain (mobile)
Share consents between domains	Click here for more information.
Reduce reliance on browsers	This ensures an end-user's consent is captured and ads served comply with the end-user choices.

Once a custom domain is configured it can be used for one or more of the purposes listed above.

Didomi supports the following methods when configuring your custom domain. Please visit our dedicated resources for more information.

• Domain delegation

• Reverse proxy

For your convenience, Didomi has compiled some benefits and considerations in the matrix below:

	NS Delegation (subdomain)	Reverse proxy (subdomain)	Reverse proxy (main domain)
Resilience	Robust against Adblockers until subdomain is blocked	Robust against Adblocker until subdomain is blocked	Robust against Adblocker.
Increase Adblocker resilience	✅	✅	✅
Safari ITP	🟡 Cookie maintained only 7 days	🟡 Cookie maintained only 7 days	🟡 Cookie maintained only 7 days
Implementation complexity	🟢 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 technical teams with strong infra and allows subdomain branding	Best for technical teams with strong infra and Adblocker concerns.