Privacy
Last updated 25 August 2026
Visitors do not have accounts, so there is not much to collect.
What we store about visitors
We do not store raw IP addresses for analytics, and we do not fingerprint devices.
- A random identifier in a cookie. It is not linked to your name, email or device fingerprint.
- What you cooked, voted on and answered, tied to that identifier.
- Page views and outbound clicks, tied to that identifier.
- A hashed key derived from your network address, used only for rate limiting.
What we store about claimants
If you claim a page, we store your email address, whatever evidence you submitted, and a record of the decision. Sign-in links are stored only as hashes and are single-use.
What we store for verified hiring reports and trust requests
We encrypt contributor and case contact addresses and retain a keyed hash only for secure lookup. A verified hiring report records the contributor relationship, declaration and policy versions, review decision, and a version history.
Evidence is held in private storage, scanned for malware, and never served from the public upload path. Reviewer access requires a recorded purpose and creates an access log. Evidence is deleted after the configured retention period unless a documented legal hold applies.
Cookies
No advertising cookies and no third-party trackers.
- A visitor identifier, so your votes persist and limits can be applied.
- A CSRF token, so forms cannot be submitted from other sites.
- A session cookie, only if you sign in as a claimant or an operator.
Deleting your data
Ask and we will remove cooks tied to your visitor identifier where we can identify them. Aggregate counts that no longer identify anyone may remain.
Editions
Each edition is a separate market with its own pages. Which edition you use depends only on the address you open. We never redirect you based on where you appear to be.