[DRAFT - CLIENT LEGAL REVIEW REQUIRED]
This page is a structure, not a finished legal document. URU Forge is publishing the section order and what each section must establish, so the shape can be reviewed. The operative wording is written by the site owner and their counsel before launch, and this notice is removed at that point.
Nothing on this page is a commitment, and no sentence here should be relied on until counsel has signed it off.
What a cookie is
One short plain-English definition covering cookies and the similar technologies actually in use, such as local storage where the consent choice is kept. Definition-first, in the same register as the rest of the site: a cookie is a small file a site asks your browser to keep, so it can recognize the same browser later.
How we use them
Must match what the site actually does. The consent sheet already states our position in microcopy.md §10 and this page must not contradict it: essential cookies for security, the consent choice itself and form submission; analytics only with permission; no advertising cookies and no third-party trackers.
The cookie table
The operative content of this page. One row per cookie, with these columns and no fewer:
Analytics
Must name the analytics provider, say what it collects, say whether the data is shared or sold (it is not), and say where it is processed. This is the same fact as the analytics entry in the processor list on the privacy policy, and the two must agree.
Managing your choices
Must explain three routes: the consent sheet on first visit, the “Cookie settings” control in the footer, and the reader’s own browser settings. Must also say what happens if analytics are refused, which is: nothing changes about the site.
Changes to this policy
Must say how changes are notified and that the last-updated date at the top is authoritative. Worth stating that a new cookie category requires fresh consent rather than a quiet table update.