Legal pages
Your site needs a privacy policy, terms and a cookie notice. Giant Context keeps them as versioned documents rather than words pasted into a page, so you always know which wording was live and when.
Versioned documents
Every legal document in your project carries a type and a version history. You edit a draft, publish it when it reads right, and your pages show whichever version you published last.
Three modes for the LegalDocument block
Legal content reaches your site through the LegalDocument block, which works in one of three modes depending on where the text comes from.
Whichever mode you use, the block fills in your organization's name where the text calls for it, and it renders in the visitor's language.
The seeded legal pages and the cookie list
You do not set this up from scratch. A new site arrives with published Privacy Policy, Terms of Service and Cookie Policy pages, built from the templates and carrying your organization's name.
The cookie notice itself uses the Cookie List block, which lays your cookies out in three categories. Necessary cookies are essential for website functionality and are always enabled. Statistics cookies help understand how visitors interact with the website, for example Google Analytics. Marketing cookies are used to track visitors across websites for advertising.
The built-in templates are a starting point, not legal advice. Read them, make them your own and have a lawyer review anything you rely on.
Frequently asked questions
Frequently asked questions
The three listed above, already published. Edit them or replace them with your own.
Template renders a document the platform maintains. Custom renders markdown you write in the block. Project binds to one of your own published documents.
A published version is frozen and cannot change. Editing it creates a new draft and a new version.
No. They are a starting point, not counsel. Have a lawyer review anything you rely on.