A small data footprint.
A good time.
You can play every experiment without an account, email address, payment, or tracking cookie.
What stays in your browser
By default, anonymous activity events stay on this device: page visits, game starts, completions, share clicks, referral opens, and return visits. We keep up to 500 events for seven days and use a random session ID per browser tab. We store a last-visit timestamp to recognize a visit after 30 minutes.
Storage is optional. If your browser blocks it, the games still work. We do not record your name, raw predictions, IP address, or a device fingerprint in the application analytics. Hosting providers may separately retain standard operational request logs.
Your controls
Optional growth measurement
The footer control separately opts you into first-party growth measurement when the operator enables it. We assign a random signed browser cookie for up to 90 days, use sessions separated by 30 minutes of inactivity, and keep minimal event history for 90 days. First-acquisition and first-completion metadata remains while this consented identity is active; inactive identities expire 90 days after their last measured activity. No fingerprinting or cross-device matching. Do Not Track, Global Privacy Control and global opt-out prevent collection. Anonymous browser counts are estimates, not a census of humans.
Gameplay is available without measurement. Only the operator can access aggregate reports. Cookies cleared or separate devices may count the same person twice. Standard hosting logs follow the hosting provider’s separate retention policy.
What a challenge link reveals
Links contain an anonymous challenge ID, game seed, game mode, and score. Humanity links also contain your five percentage predictions so friends can compare. These links are public to anyone you send them to and aren’t encrypted. CAST ME links send a casting invitation; your generated story stays out of the URL.
Optional published creator challenges
If you choose to publish a creator pilot, the operator must obtain your permission to display your public creator name, recorded score, game seed and shared predictions. This public challenge is separate from your private browser activity. Deleting browser measurement does not remove an intentionally published page; ask the operator to remove that page. No account or publication is needed to play.
AI is optional
CAST ME works locally without AI. If you turn on the AI option and a provider is configured, only your three fictional character choices are sent through our server to that provider. No account or identity is attached. If the provider fails or isn’t configured, a local story generator takes over.
Optional audience measurement and purchases
Live monetization and audience collection are disabled by default. When configured, optional audience measurement uses a signed anonymous first-party cookie to count active devices, sessions, returns, and activated referrals. No fingerprinting or cross-device matching. Published creator leaderboards use only a nickname you explicitly choose to publish.
Optional purchases and creator ownership use an essential signed cookie. Ad messages appear only by choice after a result; rewarded ads need an explicit opt-in. No payment or advertising is needed to play. Sandbox reports and purchases are always labelled demonstrations.
Shared activity has a 35-day reporting retention window. Financial and credit-consumption records have a separate required retention policy; deleting audience activity does not revoke a purchase. Premium story retries may cache fictional text on the server for up to 24 hours. Core local stories remain on your device.
For whoever runs the lab
Growth measurement is disabled until the operator configures the durable first-party repository and reviews this notice. Shared event history has a 90-day logical retention window, with scheduled cleanup targeting removal within one further day at pilot size. Operators must monitor cleanup and review hosting backups separately. Owner reports are aggregate and protected. The legacy log sink is not used by current browser instrumentation. Monetization remains separately disabled; its public revenue preview is clearly simulated.