The complete list of what this site stores in your browser, what we deliberately don't, and what has to happen before that list is ever allowed to grow.
This site sets only cookies it cannot work without: one to keep you signed in, and one to remember that you have seen the cookie notice. There are no analytics cookies, no advertising cookies, and no third-party tracking of any kind.
That is why the notice has one button. Nothing optional is being set, so there is nothing to decline — and the essential cookies continue whether or not you dismiss it. Dismissing it records that you have read this. There is nothing optional to agree to.
If we ever add a non-essential category — analytics is the likely candidate — it will be opt-in through the cookie notice before the first byte of it is set, and this page will be updated before the notice asks. We will not treat a past dismissal of this notice as consent to a category that did not exist when you clicked it.
Cookies are a website mechanism; the mod and coordinator don't use them. What the platform collects while you play — what the mesh needs to run, what map sharing sends when you turn it on, what a bug report or log share includes when you ask for one, and the VBF_PHONE_HOME=off switch that stops everything optional — is listed in the privacy policy, §03 “What the mod sends, and when”. The same list is shown in-game under "What Fragments sends".
Your browser can list, block, or delete cookies for this site at any time. Deleting the session cookie simply signs you out; deleting the acknowledgement brings the notice back. Blocking cookies entirely leaves every public page readable — you just won't be able to stay signed in.
This document describes what the site does honestly. It is not a formal legal contract. If Fragments scales to meaningful volume in the EU, UK, or California, a lawyer should review the cookie and consent wording alongside the privacy policy.