How Privacy Center Hosting Works
Learn what serves your Privacy Center on a Transcend subdomain and on your own domain, and what each stage of a domain move changes.
After you read this page, you can explain to your DNS and security teams what serves your Privacy Center. You can also tell what each DNS record does, and what each stage of a domain move changes. For the steps, see Launch or Move Your Privacy Center Domain.
The Transcend subdomain
Transcend creates your Privacy Center when it creates your organization. Its first URL is a Transcend subdomain built from your organization's URI. A shared AWS CloudFront distribution with a wildcard certificate serves these subdomains. The Domain card on the Deployment tab shows your current URL.
Your own domain
The default hostname is privacy. plus your organization's domain. When you select Request certificate, Transcend does two things:
- It requests a certificate for your hostname from AWS Certificate Manager (ACM). ACM validates the certificate through DNS.
- It creates a CloudFront distribution for your Privacy Center.
If your root domain has Certification Authority Authorization (CAA) records, one of them must allow AWS. Otherwise the certificate request fails.
The DNS records on the Deployment tab do two jobs:
| Record | Job |
|---|---|
| Validation CNAME | Lets AWS validate that you own the hostname and issue the certificate |
| Routing record | Points your hostname at your CloudFront distribution |
Transcend checks every minute whether AWS has issued the certificate. When it has, Transcend attaches the certificate and your hostname to the distribution. Launch Privacy Center then sets your Privacy Center URL to your hostname and republishes your Privacy Center.
How requests are routed
Your distribution redirects HTTP to HTTPS, requires TLS 1.2 or later, and supports IPv6.
| Request | Goes to | Cached |
|---|---|---|
/privacy/graphql | Transcend backend API | No |
/privacy-center-modules/* | Transcend backend API | No |
| HTML pages | Privacy Center app files | No |
| Other files | Privacy Center app files | Yes |
The Privacy Center sends its API calls to /privacy/graphql on its own hostname. A path that matches no file returns the app page, and the app handles the route in the browser.
What a domain move changes
A move keeps the same distribution. Only its certificate and hostnames change.
| Stage | What Transcend does | Hostnames on your distribution |
|---|---|---|
| You start the move | Requests one certificate that covers the old and the new hostname | Old |
| AWS issues the certificate | Attaches it to your distribution with both hostnames | Old and new |
| You switch | Confirms the new hostname returns your Privacy Center over HTTPS, then sets your URL to it and republishes | Old and new |
| You remove the old domain | Requests a certificate for the new hostname only. When AWS issues it, Transcend removes the old hostname | New |
Transcend runs the certificate steps on the same one-minute check. After the move, it deletes the certificates that the move no longer needs.
You can undo a move until you remove the old domain:
- Cancel move returns your distribution to the old hostname only.
- Switch back to old domain sets your URL back to the old hostname and republishes. Both hostnames stay on the distribution.
Related pages
- Launch or Move Your Privacy Center Domain: the steps to launch or move.
- How Privacy Center Publishing Works: what a publish includes.
- Troubleshooting Privacy Center Publishing and Custom Domains: errors during a publish, a launch or a move.