Privacy

Playing without an account

The game stores your career in this browser (for example localStorage and, when needed, IndexedDB). That data stays on your device unless you use optional cloud backup below. We do not receive your save file unless you upload it.

Optional cloud backup account

If you choose Club → OS Config → Cloud account and sign up or sign in, we use Supabase (authentication and storage) so you can upload and download a private backup copy of your career save tied to your user id. Processing includes:

• Account identifiers: email address and authentication artefacts Supabase issues (for example session tokens in your browser). We do not run our own password database alongside Supabase Auth.
• Save data: your compressed career blob as you sync it — only for backup and restore, not for selling or profiling.
• Access: storage is scoped so each account can reach only its own backup (see Supabase Row Level Security / bucket policies in the project configuration).

Supabase acts as a processor under their terms and privacy policy: supabase.com/privacy.

Global leaderboard

When you are signed in and playing an active career, the game may automatically synchronize your trophy count and seasons managed (derived from your current save) to our leaderboard database in Supabase, alongside your user id and a display name (your manager name or a name you set under Club → Settings → Global leaderboard). We also store whether you are hidden from the public list. If you are hidden, your row is not shown on the public board but may still be updated in storage when stats change. You can turn on hide in Settings, or stop syncing by signing out of the cloud account or not using the signed-in leaderboard feature. You can also use Publish now in Settings to force an immediate update. For metrics and storage detail, see the project file docs/GLOBAL_LEADERBOARD_PLAN.md.

Site analytics and hosting

Public pages may load Google Analytics (measurement id used in the app bundle), Vercel Analytics, and PostHog for aggregate traffic and product analytics (for example when a career is started or a save is loaded). Those providers receive technical data such as page views, coarse device/network signals, and those gameplay events under their policies. The game shell does not require analytics to run locally.

The site may show Google AdSense or similar ads on some surfaces; those networks may use cookies or identifiers as described in their own policies.

Cookies and local storage

We use browser storage for gameplay (save data, preferences) and, when you use cloud backup, Supabase may store session-related tokens so you stay signed in. You can clear site data in your browser; clearing storage removes local saves unless you restore from the cloud again.

Retention and deletion

Local saves remain until you delete them or clear browser data. Cloud backups remain until you delete your Supabase user / project data or we remove them as part of service operations. To request deletion of cloud data associated with your account, use Feedback so we can coordinate with the account email on file; you can also delete your account through Supabase where your deployment exposes that flow.

Children

The game is not directed at children under 13 (or the age required in your region). Do not create an account for cloud backup if you do not meet your region's minimum age for consenting to online services.

Changes

We may update this page when features or providers change. The "Last updated" date at the top will move when we do.