How your Privacy Center works
Your public trust page at your workspace's own address: what visitors see on it, what decides each part appears, and the tabs you run it from.
The Privacy Center is the public page your customers and their users read: the policies in force, the certifications you hold, what you disclose from your compliance registers, and the forms people use to exercise their rights or report illegal content. You run it from Privacy Center in the sidebar.
Its address
Every workspace's Privacy Center is served at an address built from the workspace's handle: the workspace with the handle acme is at acme.prvcy.center. You choose the handle when you create the workspace, and an admin can change it in the Handle field under Settings › Organization. See Edit your company and workspace details.
Changing the handle moves your Privacy Center to the new address the moment you save. Links already shared to the old address, in a privacy policy, an email footer or a data subject's inbox, stop working, and nothing redirects them.
Nothing is served at the address until you publish the page: until then a visitor gets a page that isn't found. On Pro you can also serve the page at a domain you own, and run a hub for each brand at a path under your address. See Connect a custom domain and Add a brand hub.
What visitors see
From the top of the page down:
- Your logo in the header, or your display name until you add one, with a link to your website.
- Buttons for Exercise a right, Report illegal content and Check request status. They open the forms described in What visitors can do on your Privacy Center.
- What we disclose: the AI systems you mark for the page, the product recall notices you've published and your published transparency reports.
- Learn how your data is handled: each policy in force, with its version and the day it came into force.
- Privacy rights we honour: the laws a visitor can file a privacy request under, each with the time you have to respond.
- Independently verified: the certifications you list.
- Sub-processors: the active sub-processors you mark for the public list in your Privacy register.
- Talk to us: your privacy contact address, when you've set one.
Apart from the policies, a section with nothing in it is left out rather than shown empty.
What decides each part appears
The page as a whole appears once you publish it. Most of its parts also belong to a compliance register, and are shown only while that register is open: subscribed, which still holds while Stripe retries a failed renewal, and with its representation mandate signed. See Open a register.
| Part of the page | Shown while |
|---|---|
| Privacy request form, Privacy rights we honour, Sub-processors | Privacy is open |
| Illegal content form, transparency reports | Content Safety is open |
| Request status page | Privacy or Content Safety is open |
| AI systems | AI Governance is open |
| Recall notices | Product Safety is open |
| Policies, certifications, Talk to us | The page is published |
The two forms and the status page are served only while at least one of your hubs is published, your own or, on Pro, a brand's. Links that have already been emailed to someone, such as a status link or an identity upload link, keep working either way.
The five tabs
| Tab | What it's for |
|---|---|
| Overview | The Go-live checklist; What's live now, with the page's address, what's on it and the addresses of its forms; and Recent submissions from the last 30 days. |
| Policies | Your policies and every version of each. See Publish a policy. |
| Certifications | The certifications you hold and whether the page shows them. See Add a certification. |
| Brand | The page's details and look, publishing, brand hubs and custom domains. See Set up and publish your Privacy Center. |
| Subscriptions | Where each register stands, in the same rows as the Subscriptions card on Home, each with the button that moves it on. |
Who can change what
- Anyone in your workspace other than a DPO can edit the page's details and look, publish it or take it offline, and manage policies, certifications and brand hubs.
- Only an admin can add, check, change or remove a custom domain, or add a brand straight onto a domain of its own.
- A DPO you've hired can work on your policies and certifications. They can see the page's details, whether it's published and its brand hubs, but can't change them, and they don't see the Subscriptions tab or the go-live checklist.
See Roles and permissions for everything each role can do.