Privacy
Reading this site, and voting on the arguments in it, require no account and no personal data. Here is precisely what is stored, and why.
Effective [effective date — NOT CONFIGURED]. Data fiduciary: [operator legal name — NOT CONFIGURED], [registered address — NOT CONFIGURED].
Draft — not yet reviewed by a lawyer
This page was drafted from how the platform actually works. It has not been reviewed by a qualified lawyer and is not legal advice. BRD 14.3 makes that review a launch dependency. Set NEXT_PUBLIC_LEGAL_REVIEWED=true once it is done, and fill in the operator details.
Reading
Nothing is collected. There are no advertising trackers, no analytics cookies and no third-party scripts on any public page. Pages are served as static HTML wherever possible.
Voting on an argument, or disputing one
To stop one person voting a hundred times, the site needs to recognise a repeat visitor without knowing who they are. It combines your network address and browser user-agent string with a secret salt, hashes the result with SHA-256, and stores only that hash.
The hash cannot be reversed into an address. It is never returned by the API and never appears on a page. Changing the salt discards every association at once. Your address itself is not written to the database.
Submitting evidence
This is the only place personal data is collected.
- Display name — required, and published beside your evidence if it is accepted. Use whatever name you want credited.
- Email address — optional. Used only to come back to you about that submission. It is never published, never used for marketing, and never shared.
- What you submitted — the observation, its date, and any source or proof link. If accepted, this becomes part of the public evidence base.
Removing what you sent
Write to the address below and your email will be deleted and your display name removed from any page crediting it. Accepted evidence itself stays on the record: verdicts were reached using it, and removing it would make the published reasoning unexplainable. It can be deprecated so no future debate cites it, and corrected if it is wrong.
The operator console
The console at /admin sets a single session cookie after sign-in. It is not part of the public site and sets no cookie for readers.
What is sent to AI providers
Debates are generated by sending the subject and its evidence base to a model through OpenRouter. Nothing about a reader is ever sent. If your submitted evidence is accepted it becomes part of that evidence base and is sent with it — your email address is not. The methodology page names which model does what.
How long things are kept
- Vote and dispute fingerprints — kept while the argument they relate to is published. They identify nobody.
- Submitter email — kept until the submission is decided and any follow-up is done, then deleted on request at any time.
- Display names on accepted evidence — published for as long as that evidence is on file, because contributors are credited. Removed on request.
- Rejected submissions — retained briefly so the same item is not re-reviewed repeatedly, then discarded.
Your rights under the DPDP Act, 2023
Where we hold personal data about you — in practice, only if you have submitted evidence — you may ask us to:
- tell you what we hold and what we have done with it;
- correct anything inaccurate or incomplete;
- erase it, subject to the limit described below;
- nominate someone to exercise these rights if you cannot;
- raise a grievance with us, and escalate to the Data Protection Board of India if we do not resolve it.
The one limit: accepted evidence itself stays on the record even after your name and email are removed. Verdicts were reached using it, and deleting it would make published reasoning unexplainable. It can be deprecated so no future debate cites it, and corrected if wrong.
Who else sees anything
- OpenRouter and the model providers behind it receive the subject and its evidence base in order to generate a debate. Accepted evidence goes with it; email addresses never do, and nothing about a reader is ever sent.
- Our hosting provider processes traffic in the ordinary course of serving the site.
We do not sell personal data, and we do not share it for advertising.
Security and children
The site is served over HTTPS, secrets are held outside the codebase, and the operator console is separately authenticated. No system is perfectly secure; we keep the amount of personal data we hold small precisely so a breach would matter less.
The site is not directed at children and we do not knowingly collect data from anyone under 18. Tell us if we have, and we will delete it.
Contact and grievances
For anything on this page, write to [privacy email — NOT CONFIGURED].
[grievance officer name — NOT CONFIGURED], Grievance Officer[operator legal name — NOT CONFIGURED]
[registered address — NOT CONFIGURED]
[grievance email — NOT CONFIGURED]
We acknowledge within 24 hours and aim to resolve within 15 days. See also our terms and corrections policy.