Privacy Policy

Last updated: August 4, 2026.

Data we collect

When you submit a Genesis Registry request, we collect your email address, source page, optional preferred Throne and membership interest, the submission consent record, an internal Registry identifier, and a one-way hash of the browser management key. The checkbox records the requester's action, not verified ownership of the email; the identifier is not disclosed before verified delivery launches.

Analytics

We collect event-level page engagement such as landing page, traffic source, scroll depth, time on page, CTA and conversion-step events, plus a coarse browser and device category. New events do not store a raw user-agent string or an IP address in the analytics table. An automated retention window must be active before paid acquisition begins.

Local storage

The site may store your selected Throne and raw browser management key. The key is a bearer capability for a pending request; it is not a login, proof of email ownership, or paid entitlement. Voting limits are enforced on the server at a visitor/network level.

Email

No email verification or Chronicle campaign is active today. New and existing emails receive the same public response. A browser-managed pending record can be removed below with its email and management key; legacy records without a key require a future verified or reviewed manual process.

Remove a Registry entry

Enter the email and browser management key together. A removal is confirmed only when both values match the same browser-managed entry; a wrong key and an unknown email return the same no-match result.

Contact

A public privacy contact address has not yet been configured, so new Registry collection remains paused. The self-service control applies only when you hold the browser management key; legacy-key requests remain an explicit activation blocker until a verified contact or claim process exists.