Privacy Policy
DRAFT for the owner to review before launch. This text was written by an AI assistant, is not legal advice, and contains [OWNER: ...] placeholders that must be filled in or removed. Have it checked for your country before enabling sign-in for the public.
Crokinole Club is a free browser game. You can play every mode as a guest without an account, and as a guest nothing about you leaves your device. This page explains what happens if you choose to sign in with Google to save your progress.
Who we are
Crokinole Club is run by [OWNER: your name or company] ("we"). Contact: [OWNER: contact email address].
What we collect when you sign in
From Google (through Supabase Authentication): your Google account name, email address and profile picture address. We use the name to suggest your first display name and the email only to identify your account. We do not show your email or picture to other players, and the game does not display your Google picture.
From the game: the display name and portrait you choose, your career progress (stars and best score), your game statistics (matches, wins, twenties, clean contacts), a capped list of your last 50 finished matches (date, opponent, score), a few synced settings (sound, ambience, cue sliders, turn board), and a short label for each device you sign in on (for example "Chrome on Android") with a random device number. The device number is not linked to anything outside this game.
Automatically: our hosting and database providers see your IP address and technical request data in their server logs, as every web service does.
Anonymous analytics and crash reports
To fix bugs and see which parts of the game are used, the game sends anonymous events to PostHog, our analytics provider (EU cloud): that the app opened and how fast it loaded, which screen was shown, tutorial steps, when a level or online match started and ended (the level, the rival, the result, score, stars and how long it took), per-match totals such as shots, fouls, takeouts, twenties, average power and how long you took to shoot, how fast the computer rival thinks, online queue, disconnect and rematch events, which settings you change, whether the app was installed or updated, whether a sign-in or sync worked, simple performance figures (frame rate bucket, slow frames, load times, a rough memory bucket) and crash reports (the error type, a message with web addresses removed, the code location and the screen and level you were on). Each event also carries coarse device facts: app version, screen size class, pixel ratio, CPU core and memory buckets, graphics chip family, language, reduced-motion and connection type. These are never tied to your name, email, account or Supabase user id.
To keep this working with ad blockers, the events go to our own address first (/ingest on this site), which passes them on to PostHog without your IP address or any cookies. If that path is unavailable, the browser sends them to PostHog directly.
Screen recordings: a small share of visits (about 15 in 100), and every visit in which an error or a Report a problem happens, is recorded as a short replay of the game's menus and screens so we can see what went wrong. Recordings never include the game board picture (the 3D canvas is blocked), what you type (all input boxes are masked), names, emails or anything in the account, privacy and report sheets, and no network contents. They are kept by PostHog under its retention settings (our plan keeps them about a month).
This uses no cookies and nothing stored on your device: each visit is a separate anonymous visitor, so a returning player counts as new. We turn off IP address use, autocapture and heatmaps. If your browser sends Do Not Track or Global Privacy Control, we send no usage events and no recordings, only anonymous crash reports. You can turn all of it off in Settings > Privacy & data > Share anonymous diagnostics (on by default). If you use Report a problem, the text you write is sent with your app version, device and graphics type and recent game log lines; please do not include personal details. Events are limited per visit.
What we do not do
No advertising, no ad networks, no selling or sharing of your data for marketing, and no cookies or tracking across other sites. The game stores a few items in your browser (local storage) so that it works offline and remembers your progress and sign-in; it does not set advertising cookies.
The older optional crash-report switch in Settings is off by default. If you turn it on, only an error type and message are sent, never gameplay or personal data.
Why we use it
To let you keep your progress when you change device and to restore it if you clear your browser data (performing the service you asked for by signing in). We do not use your data for anything else.
Who processes it
Supabase (database and authentication) stores your account data. Google handles the sign-in. Cloudflare hosts the game files. Their locations and terms are described on their websites; data may be processed outside your country, using the safeguards those providers offer. [OWNER: state the Supabase region you selected.]
How long we keep it
Until you delete your account. Match history is capped at your latest 50 matches. Backups made by our provider, if any, expire on the provider's schedule. [OWNER: confirm backup retention.]
Your choices and rights
You can see everything we hold with Export my data (Account in the game). You can change your display name and portrait at any time. You can delete your account in the game (Account, Delete account), which removes your login and all stored rows. Local progress on your device is kept unless you reset it. Depending on where you live you may also have the right to ask us to correct or restrict processing, to object, or to complain to your data protection authority; contact us at the address above.
Children
Crokinole Club is not directed at children under 13 (or under 16 where your country sets a higher age for consent). We do not knowingly collect data from them. If you believe a child has signed in, contact us and we will delete the account.
Security
Data is sent over HTTPS and every table is protected by row level security so that an account can only read and change its own rows. No system is perfectly secure; if we learn of a breach affecting you we will tell you as the law requires.
Changes
If this policy changes in a meaningful way we will update the date at the top and tell you in the game before the change applies to accounts.