Privacy & community data

This build collects only the limited information needed to support voting, anonymous profiles, competition and moderated discussion.

Anonymous profile

When a reader creates a profile, the site stores the alias and selected allegiance they provide. The browser creates a random participation token; the server stores only a one-way hash of that token as the profile key. There is no password, email address or attempt to discover the reader’s real identity. The same profile does not automatically follow a reader to another browser or device.

Local progress

XP, rank progress, unlocked achievements, timeline exploration, Score Lab weights and share-card preferences are stored in the browser’s local storage. They can be removed by clearing this site’s browser data. Clearing local storage also breaks the link to the anonymous server profile and creates a fresh participation identity.

Predictions, votes and reactions

Prediction choices, confidence values, votes and reactions are associated with the anonymous participation hash to calculate points and discourage repeat submissions. Public responses contain aliases, allegiance, aggregate totals and competition statistics; they do not expose the browser token, request address or internal hash.

Evidence challenges, arguments and comments

Submissions contain the alias, text and optional public source supplied by the reader. They remain in a private moderation queue until approved. Temporary hashes derived from the participation token and request address are used for abuse prevention. Do not submit private information or confidential material.

News and external links

The site requests a cached index of publisher metadata and sends readers to the original publisher to read a story. External publishers apply their own privacy and cookie policies.

Briefing waitlist and analytics

If a reader joins the Battle Briefing waitlist, the site stores the email address they submit and the time of opt-in in a private server-side file so the list can later be migrated to a mailing provider. This build does not send marketing email or share the address with a third-party mailing service. A reader can request removal at the contact address below. No analytics script is included.

Deletion and contact

A reader can clear local progress through browser settings. Requests to remove a known public alias, approved submission or anonymous profile should include enough detail to locate it: admin@muskvbezos.com.