Privacy
Last updated: Nov 17, 2026
Who we are
Arguewise is run by Joe Ball. For privacy questions, takedown requests, or reports, use the Requests & reports form. If you have an account, you can also download or delete your data yourself.
Fairview, a separate professional service run by Joe Ball, has its own privacy policy and terms. Nothing you do on Arguewise is shared with it.
What we collect
We keep what we need to run the service:
- Email, if you sign in, plus sign-in session records. We send a one-time code through Cloudflare Email. We store a hash of the code, not the code itself, and it expires quickly.
- Breakdown content — the text or links you paste, titles, the AI breakdown, later push-backs and expansions, and any comments or sources you add.
- Screenshots — sent to xAI so the model can read them. Arguewise does not keep the image file. We only store a flag that an image was used, plus the text transcript the model returned.
- Usage counts used to enforce daily caps, including a hashed IP address, optional account id, and event type. After you delete your account we strip the account id and hashed IP from those rows, but the anonymous counts can remain so caps and cost tracking still work.
- Monthly spend totals — a site-wide estimate of AI cost, not tied to your name or email.
- Hashed IP addresses on sign-in sessions, usage events, password-guess logs, problem reports, and Requests & reports submissions, so we can limit abuse. We do not store raw IP addresses in our database.
- Password-share guess logs (a hashed IP, time, and whether the guess was right) so we can lock a shared breakdown after too many wrong passwords.
- Turnstile signals — when you paste a breakdown, request a sign-in code, or send a problem report, your browser talks to Cloudflare Turnstile, a bot check. We send the one-time token to Cloudflare to verify you’re a person. We do not keep that token.
- Problem reports from the Report a problem button on a shared breakdown — the reason you chose, an optional note, the breakdown id, an optional account id if you are signed in, a hashed IP address, timestamps, and the report’s status (open, hidden, blocked, or dismissed). We may email the operator a short, throttled digest when a new report arrives (at most one email every ten minutes).
- Requests & reports forms, including what you tell us and an optional contact method.
- LightDrawer stamp receipts we store next to a breakdown (the hash, time, and receipt). See below for what LightDrawer itself keeps.
- Progress, if you are signed in: experience points, level, the current and best streak, the days you qualified, badges, and the event keys that keep a reward from counting twice. Guests keep the same kind of record in this browser only, until they sign in and choose to merge it. A merge is capped, and badges that need a graded attack stay on the server.
- Survive the attack runs for 24 hours: which round you are on, the map hash, and the objections in that run. A guest run stores a hash of a random browser token, not the token itself. Signed-in runs store the account id. Expired runs are deleted when the site next tidies up.
- Arguewise Plus interest — if you ask at /plus/notify to be emailed when Arguewise Plus is available, we store that email address, the consent sentence you agreed to, and the time. If you are signed in, we also store your account id. Downloading your data includes this row. Deleting your account deletes it. You can also ask us to delete the address from Requests & reports.
- Plan — if an operator grants Arguewise Plus, or a store later confirms a purchase, we store the plan, the source (web, Apple, Google, or a manual comp), the status, and the start and end. We do not store a card number.
- Today's comparison stores anonymous counts: how many maps landed in each score band, and how many objections those maps answered. It does not store who submitted, and there is no leaderboard and no names. A hash of the account or browser is kept for 2 days so the same person is not counted twice. That hash holds no score. If you are signed in, your own progress can include a +25 daily experience event, which says that you took part and not what score you got. The topic itself is a fixed list, not something written per person.
- Offline maps — when you are signed in and open or save a map, this browser keeps a copy on your device so you can view it without a connection. The copy holds the map id, title, boxes, version, the time it was saved, and your account id. Signing out, deleting your account, or signing in as someone else clears those copies. You can also clear them by removing this site’s data in your browser settings.
Where your content is sent
Before your text goes to the AI (Grok, from xAI), we hide emails, phone numbers, SSNs and card numbers. Names and other details are sent as written, and screenshots are sent as-is. We don't log your text. We've turned on xAI's zero data retention for our account, so xAI doesn't store your text or the breakdown it writes, and it doesn't train on them.
Please read xAI’s legal terms as well. We don’t use your content for ads.
Your breakdowns are private to your account. We keep them until you delete them, delete your account, or 365 days after you last opened one, whichever comes first. We don't sell them or share them with anyone except xAI, which writes the breakdown. We don't look at them except to fix a problem you report, to handle an abuse report about something you shared, or when the law requires it. A breakdown is visible to others only if you turn on sharing or create a share link.
Who can see a breakdown
- Private — only you, when you’re signed in or still have the original guest cookie in that browser.
- Password — anyone who has the link and the password.
- Secret link — anyone who has that unguessable link.
- Public — anyone who has the ordinary link.
Admins can see breakdowns when needed to run the service, handle a report, or take an account down. If an admin suspends or closes an account, that account’s public, password, and secret links are turned off (they return “not found”) and the breakdowns are set private and hidden.
LightDrawer stamps
A stamp sends only a hash of a snapshot of the breakdown to LightDrawer — not the text. The stamp at LightDrawer is public and permanent. A receipt can’t be undone. Deleting the breakdown on Arguewise deletes our stored copy of the receipt, but it does not remove the stamp at LightDrawer. If the same snapshot is stamped again, we reuse the receipt we already have for that exact hash; a later edit gets a new hash and, if stamped, a new receipt.
Cookies we set
- fv_session — keeps you signed in.
- fv_own_… — a guest-owner cookie so you can reopen a breakdown you created without an account, from the same browser.
- fv_unlock_… — remembers that you already entered the password for a password-protected share.
These are first-party cookies used to run the site, not advertising cookies.
How to delete things
You can delete a single breakdown from its page, or delete your account from Account. Deleting a breakdown removes it from the live database, along with its comments, sources, and Arguewise’s copy of any stamp receipts. Guest users can ask us to delete a breakdown through Requests & reports.
If you left an email to be notified about Arguewise Plus and you do not have an account, use Requests & reports, choose Delete my data, and put that email in the target field. We remove that notify-me address.
Deleting your account removes your email, sign-in sessions, breakdowns, argument maps, sources, progress, badges, experience events, and Survive runs from the live database, and strips your account id from usage and report rows. Anonymous daily counts stay, because they were never tied to you. We keep:
- Anonymous usage and site-wide spend totals, so we can still enforce caps and understand costs.
- Abuse-report records with your account id removed.
- Any LightDrawer stamp of a hash, which we cannot undo.
- Database backups we may have taken to recover from mistakes or outages. There is no automatic backup expiry built into the product, so a backup can still contain your content until that backup is removed.
If an admin closes an account, we hide and unshare its breakdowns so shared links stop working. We may keep the underlying records rather than erase them outright.
No ads, no selling your data
We don’t run ads, we don’t sell your data, and we don’t use third-party advertising or analytics trackers.
The site is hosted on Cloudflare (Workers, D1, and Email). Cloudflare may keep standard request logs and worker traces we use to run and debug Arguewise, which can include IP addresses and request metadata. Cloudflare Turnstile is a bot check, not an ad tracker. If you stamp a breakdown, LightDrawer receives only the hash, as described above. xAI receives the content needed to generate a breakdown.
Children
Arguewise is not for anyone under 18. Don’t create an account or submit personal information if you are under 18.
AI output
Breakdowns are generated by an AI. They can be wrong, incomplete, or biased. They are not legal, medical, financial, or other professional advice.
Requests we receive
Forms sent through Requests & reports are kept so Joe can act on them. Optional contact details are wiped 30 days after a request is marked done. Done requests are deleted after 90 days. Open requests nobody touched are deleted after 90 days.
If you appear in someone else’s shared breakdown, you can also use the Report a problem button on that page. Reports go to an admin queue. The operator can hide the breakdown (its share link then returns “not found”), block the owner’s account, or dismiss the report. Report records are kept so Joe can act on them and review past decisions. After you delete your account, your account id is stripped from report rows, but the report itself may remain.
You can also use the Requests & reports form to ask for a takedown. An admin can block accounts and remove shared links.
Changes
If this policy changes, we’ll update the date at the top.