Console: regulatory content

Draft and publish a site’s Privacy Policy and Cookie Policy from a GDPR/CCPA/LGPD/PIPEDA template.

Per site, there is one multi-framework document per type (Privacy Policy and Cookie Policy): the frameworks it covers show up as labeled sections inside the same document, not as separately geo-served versions.

Start from a template

Pick a framework (GDPR, CCPA, LGPD or PIPEDA) and click Insert template to replace the current draft text with it. It’s a starting point — not legal advice — review and adapt it before publishing.

Multiple languages

Each document supports multiple locales (en, es…), each with its own title and HTML body. The {{PREFERENCE_CENTER_URL}} placeholder in the body is replaced with the site’s preference center URL — set it above the document editor, or via PATCH /admin/sites/{siteId} (preferenceCenterUrl). Left unset, it is served as the static [Preference center URL] bracket instead, same as every other unfilled placeholder in the starter templates ([Organization Name], [Effective Date]…) — those are never resolved dynamically; replace them by hand before publishing.

Body format

The body is sanitized HTML, not Markdown, and it is edited in a plain text area. Up to 50,000 characters per language. Only these tags survive: p, br, strong, em, u, h1–h4, ul, ol, li, a (with href and title, on http, https or mailto links) and blockquote. Anything else — scripts, styles, images, tables, inline attributes — is removed when you save, so the text you see after saving is exactly what visitors get.

Publishing

Every publish lands in the version history with its status (DRAFT / PUBLISHED / SUPERSEDED), label and date. The published version is reachable at a public URL signed with the site’s publishable (pk_) key.