Last updated: September 21, 2026
This page explains what information Cussator actually collects and how it's used. Cussator is a small, independently built project — this is meant to be a plain, accurate description of what happens, not a generic template.
You don't need an account to use Cussator. You can play every round as a guest, without signing in or giving us your name or email. If you'd like your progress to follow you between devices, you can optionally sign in with Google — see "Optional Google sign-in" below.
When you submit an argument during a round, the text you typed, the debate motion, and the recent conversation history for that round are sent to Anthropic — the provider of the AI model Cussator uses — in order to generate the AI opponent's reply and judge your turn. This happens each time you submit an argument. We don't store this text on our own servers; it's used only to generate that round's response, and Anthropic processes it under its own privacy and data-use terms.
Some small pieces of data are saved locally in your browser using localStorage, so they persist between rounds and visits:
If you play as a guest, this data stays in your own browser. It isn't sent to us, isn't tied to any account, and disappears if you clear your browser's site data for Cussator. We don't have access to it.
Signing in with Google is entirely optional. If you choose to, Cussator uses Supabase, our authentication and database provider, to sign you in. Supabase receives the name, email address and profile picture from your Google account.
While you're signed in, your Bag, Vocabulary Scars and Connector Log (together with the word definitions and round history that go with them) are saved to Supabase and linked to your account, so your progress follows you between devices. Only you can read or change your saved progress. When you sign in, it's merged with whatever is already in your browser, and it's saved again after each round. Signing out removes this data from the browser you signed out on; your saved copy stays in your account.
Nickname: signed-in users can choose a nickname (we suggest not using your real name). Your nickname is public to other signed-in users; your Google name and email are not shown to anyone through Cussator. If you skip choosing one, the app simply shows "Player". When you create an account, the nickname you type is kept in your browser's localStorage until Google sign-in finishes (for up to an hour), then saved to your profile and removed from the browser. Anyone can check whether a nickname is already taken, without signing in.
Deleting your data: email cussator.app@gmail.com from the address on your account and we'll delete your account and everything saved to it.
Cussator is hosted on Vercel. Like most web hosts, Vercel's infrastructure may automatically log basic technical information (such as IP address and request timestamps) as part of normal operation. We don't use this for tracking, profiling, or analytics.
Cussator does not use cookies, analytics scripts, advertising, or third-party trackers. If you sign in, your sign-in session is kept in your browser's localStorage so you stay signed in; it's removed when you sign out.
We don't sell your data, and we don't share it with third parties for marketing. The third parties involved in running the app are Anthropic (to generate the AI's replies, as described above) and, only if you choose to sign in, Google (to sign you in) and Supabase (to store your account and progress).
Cussator is not directed at children under 13, and we don't knowingly collect personal information from children.
We may update this policy as the app changes. The "Last updated" date above reflects the most recent version.
Questions about this policy can be sent to cussator.app@gmail.com.