Privacy Policy
Last updated: [OWNER: date]. Operator (data controller): [OWNER: legal name and address]. Privacy contact: hello.censoos@gmail.com.
The short version
- You play without an account. We create a random, anonymous guest identity for your browser. We do not ask for your name, email, phone number or date of birth.
- We store your answers, guesses, points and rounds, linked to that guest identity.
- Nobody else sees your individual answers. Other players see only totals and percentages, and only after answering themselves. There are no public player profiles.
- We do not sell your data or transfer identifiable voting histories, show ads, or track you across other websites. We currently use no analytics or advertising tools.
- Our sign-in provider records the IP address and browser type of each guest session, as part of running sign-in securely. We do not use them to identify players or to analyse answers. Against abuse of statement submission we use only a scrambled, daily-changing code.
What we collect and why
| What | When | Why | How long |
|---|---|---|---|
| Guest identity (a random ID) and a session token, kept in a cookie in your browser | When you start playing | To keep your game working and to stop the same guest answering twice | [OWNER / LEGAL: retention for inactive guests. Today there is no automatic deletion.] |
| Session record kept by our sign-in provider (Supabase Auth): the session's IP address and browser type | When a guest session starts and is used | Secure sign-in and preventing abuse | While the session exists [OWNER / LEGAL: whether to shorten this] |
| Age declaration (that you confirmed 16+; no age or date of birth) | Once, on this device | To apply the Age Eligibility Policy | In your browser only |
| Bot check (Cloudflare Turnstile) | When a guest identity is created | To keep automated accounts out | Processed by Cloudflare; we receive only a pass or fail result |
| Your answers: Agree / Neutral / Disagree, your guess (0–100%) and the time | Each time you answer | To run the game and show results | [OWNER / LEGAL: retention. Today answers are kept while the statement exists.] |
| Rounds and points: points per answer, round totals, the day a round was completed | When an answer counts toward a round | Rounds, your personal best and the daily best | [OWNER / LEGAL: retention. Today they are kept with no time limit.] |
| Statements you submit: the text, its language, your own answer and guess | When you submit | To run the game, and to check the text before publication | Published or waiting: while the statement exists. Rejected: 30 days |
| Submission records: each attempt, its outcome, and a scrambled network code (a keyed hash of your IP address that changes daily) | When you submit | To prevent spam and abuse | 7 days |
| Moderation decisions: why a statement was published, held or removed | When a decision is made | Accountability and handling complaints | While the statement exists; 180 days after removal |
| Reports you make (which statement, the reason you chose) | When you report | To review possibly harmful content | Until resolved, then 180 days |
| Language cookie | When you visit or switch language | To show the game in Hebrew or English | Until you close the browser |
| Preferences and convenience data on your device (welcome seen, light or dark mode, a copy of your recent answers, which statements opened your feed, an answer still being sent) | While you play | Showing "Your answers", varying the feed, keeping an unsent answer safe | In your browser only; never sent to us as such |
| Technical logs (including IP address and browser type), kept by our hosting providers | On requests | Security and keeping the service running | Per the providers' log retention [CONFIRM: Vercel and Supabase log retention for our plans] |
We do not collect names, emails, phone numbers, contacts, identity documents, dates of birth, precise location, advertising IDs, or data from other websites.
Opinions and sensitive topics
Some statements touch politics, religion or other sensitive subjects, so your answers may reveal opinions. They are linked only to a random guest identity, never to your name. That guest identity's session record includes an IP address (see above). We do not try to identify players, we do not combine answers with IP addresses, and we do not build or publish individual voting profiles. [LEGAL: whether answers linked to a guest identity count as information of special sensitivity under Israeli law, or as special-category data under the GDPR, and the safeguards that follow.]
Who can see what
- Other players see how many people answered a statement before answering it, and the split between answers only after answering and guessing themselves. They never see who answered what.
- Moderators (named people approved by the operator) see statement texts, the reasons a statement was held, and report counts by reason. They do not see players' answers.
- The operator's technical administrators can access the database to run, back up, repair and secure the service. [OWNER: who has this access.]
How a submitted statement is checked
1. Basic rules check the text: length, and no links, email addresses or social media handles. Long numbers and some flagged words send it to a person. 2. The text, together with up to 5 similar existing statements, is sent to Anthropic's Claude AI service, which classifies it against the Community Rules. Only the statement text is sent, never your guest identity or IP address. 3. The result is published, held for a person, or rejected with a short, general reason. If the automated check cannot run, the statement waits for a person: nothing is published without passing the check.
[LEGAL: whether this is automated decision-making that requires a specific notice. A held statement is always reviewed by a person, and a rejected one can be edited and sent again.]
Service providers and where data is processed
| Provider | Role | Data | Location |
|---|---|---|---|
| Supabase | Database and anonymous sign-in | All game data above | European Union (Frankfurt, Germany) |
| Vercel | Hosting the app and its server functions | Requests, server logs, statement text in transit | [CONFIRM: region of server functions] |
| Cloudflare (Turnstile) | Bot check | Browser signals during the check | Global network [CONFIRM] |
| Anthropic | AI check of submitted statement text | Statement text only | [CONFIRM: region, and API data retention and use terms] |
[LEGAL: transfers between Israel, the EU and the US, and the safeguards to name.]
Aggregated insights
We may later publish or share aggregated statistics about how players answered, for example the share of players who agreed with a statement. Such statistics will never include individual voting histories or guest identities. [OWNER / LEGAL: minimum group sizes and other safeguards, and whether a separate notice or consent is needed.] We will update this policy before any such use begins.
Security
Players reach data only through restricted database functions, never directly. Every table is protected by row-level security. Connections use HTTPS. We use a bot check and rate limits against abuse. No system is perfectly secure. [OWNER: incident response and notification procedure.]
Backups
We keep database backups to recover from faults. Backups contain the data described above. [OWNER: where backups are stored, who can access them, how they are protected, and how long they are kept.]
Your rights and requests
You can ask to access, correct or delete your data, or object to its use, by writing to hello.censoos@gmail.com. Since you play without an account, we need a way to find your data: the "Help and reports" page shows your guest code, which you can send us. Do not share it with anyone else. Clearing your browser data ends your guest identity; after that, new play cannot be linked to the old one. [OWNER / LEGAL: response times, and your rights under the Israeli Privacy Protection Law (including Amendment 13) and the GDPR.]
Age
CENSOOS is for people aged 16 and over (see the Age Eligibility Policy). If we learn that a player is under 16, we will delete the data we can link to them.
Changes
We will update this policy when the game changes, for example before adding accounts, usage statistics or aggregated insights, and we will show the change in the game before it applies.