Arguedly

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

There are no advertising trackers on any public page, nothing about you is sold or shared with advertisers, and pages are served as static HTML wherever possible.

We do measure how the site is used, with Google Analytics 4. It records which pages are opened, roughly where in the world the request came from, what kind of device and browser made it, and which site — if any — linked you here. Where you arrive through a search on this site, the words you searched for are part of the page address and are recorded with it.

It sets cookies in your browser to recognise the same visitor across pages. Google does not receive your full network address: GA4 truncates it before it is logged, and it is never stored. We have not enabled Google Signals, advertising features or cross-device tracking, so the data is not used to build an advertising profile of you. The operator console is excluded from measurement entirely.

If you would rather not be counted, any browser setting or extension that blocks third-party scripts or cookies will stop it, and the site works exactly the same without it. Global Privacy Control and Do Not Track headers are not currently acted on.

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, and requesting a verdict below, are the only places 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.
  • Request email — kept until that verdict is published and you have been told, or until you ask for it to go.
  • The request itself — the words typed, kept as a record of what readers wanted. It names nobody.
  • 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.

Asking for a verdict

If you search for something we have not covered, you can ask for it. We record the words you typed and, so that one device cannot inflate the count, the same salted fingerprint described above — not your address.

You may leave an email address. That is optional, and it is used for exactly one thing: telling you when a verdict on that request is published. It is never shown on a page, never used for marketing, never shared, and you can have it deleted at any time by writing to the address below. Leaving it blank does not affect whether the request is counted.

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.
  • Google, as the provider of Google Analytics, receives the usage data described above. Google is based outside India and processes it on servers abroad.

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.