Usage & privacy

Updated October 8, 2026 — Build 276 reporting revision. This supplements the game's existing privacy information for accounts, billing and ads.

Basic game totals

Basic reporting is on by default for new players and players who have not made a reporting choice. Earlier reporting refusals remain off. Basic reports send event types, Android or browser platform, approximate event times and relevant product types: sessions, first reporting launches, new dynasties, completed games and seasons, guide and feature use, shop visits, checkout outcomes, ad presentation callbacks and separate native ad impression callbacks, app build numbers, ad entry locations, bounded ad-load times, numeric weekly/season resource balances, spending and sponsor grants, visible reward offers, school prestige tiers, difficulty, scenario types, and fixed technical failure categories. No exception messages or stack traces are uploaded. They do not contain a persistent installation ID. A separate random ID for each event prevents retries from counting it twice; it is not reused for other events.

Optional ID tracking

ID tracking is off unless you enable it. It adds a random installation ID to future activity so we can measure unique and returning players. Earlier basic events are not assigned the ID when you enable this setting. Players who previously allowed reporting with a random ID keep their existing choice. The ID is hashed before storage. This linked data is pseudonymous, not completely anonymous.

Your controls

In Settings → Usage & privacy, you can switch off Share basic game totals to stop all usage reporting, or switch off Allow ID-based usage tracking while continuing to contribute basic totals. Declining does not change gameplay, purchases or access to features. Ad privacy choices are separate.

What stays out of usage reports

This feature does not send dynasty saves, player names, account emails, payment details or advertising identifiers. Basic requests still use ordinary internet connections: hosting providers may process IP addresses and keep operational logs. We do not store IP addresses as reporting identifiers or use fingerprinting to reconstruct an installation ID.

Purpose and service providers

Supabase receives and stores activity to help us understand and improve the game. Resend delivers aggregate daily reports to the developer. Emails do not contain device or event IDs. Usage reporting does not track you across other apps and is not used for personalized advertising. It is separate from Google Play, Stripe and AdMob provider records.

Storage and retention

Up to 500 events can wait on your device while offline. Events older than seven days are not accepted. Raw server events are removed after 35 days; aggregate totals are retained for long-term reporting. Report snapshots are retained for 90 days. For ID-enabled players, a hashed installation record is retained to distinguish first and returning activity.

Turning off ID tracking deletes the local installation ID and removes it from unsent events. Basic totals can continue. Turning off basic reporting clears the pending queue and stops future uploads. Neither setting retracts events already received or erases existing aggregate totals. Enabling ID tracking again creates a new ID. Clearing app/browser storage can also start a new reporting history. First reporting launches are not verified Google Play installs.

Contact ctoolis@gmail.com with questions about these statistics or your privacy choices.

Return to Saturday Dynasty

Optional browser visits and campaign attribution

Updated October 15, 2026. When both basic reporting and ID-based usage tracking are enabled, browser funnel events can connect a landing-page visit, Play click, dynasty creation, first recruiting action, completed games, community actions and returning visits. This uses a random browser cohort ID and a tab session ID, which are hashed before server storage. It is pseudonymous, not anonymous. Source is limited to validated utm_source, utm_medium and utm_campaign tags. No complete URL, account ID, email, password, token, save file, player name or precise device information is included. Community impressions count only when visible; canceled shares are not completed shares.

A session expires after 30 minutes of inactivity. A returning browser is observed on a later UTC day, within the consenting cohort only. Raw funnel events are kept for 90 days; up to 100 pending events can wait locally, and events older than seven days are rejected. Global Privacy Control prevents linked funnel collection. Disabling either reporting choice clears local funnel identifiers and queued funnel events; it cannot retract activity already received. Basic game totals remain separate. Not opting in does not affect gameplay, saves, purchases or community access.