Data categories
SideQuest processes account identifiers and authentication records, profile and character choices, saved game and learning events, earned-entitlement ledgers, player-submitted feedback, and redacted operational telemetry. Saved Life records contain the validated action and resulting game state; saved Learn assessments contain the submitted answer records. Raw Life free-text intent, optional reflection text, and generated mature scenes are not written to game history or application logs. Passwords, IP addresses, and credentials are not written to the application log path.
Why data is used
Account and state records provide sign-in, save/resume, progression, support, security investigation, and reliability functions. Feedback reports help triage bugs and safety concerns. Product analytics are limited to documented, minimised events and do not attach narrative content.
Optional OpenRouter features
Play uses the server-side OpenRouter service for optional adaptive responses when the owner has configured a key, an allowlisted model, and that feature’s usage policy. Without that configuration, local previews, authored choices, and local reflection continue to work. Submitting a saved Life free-text action may send the text and the current fictional scene/action list to OpenRouter for interpretation. Submitting a saved Learn reflection may send its prompt, published source excerpt, and response for unscored feedback. Explicit text scenes send only the fictional age and content exclusions. Graphic Life illustrations send the fictional age, saved visual appearance recipe, and content exclusions to the configured OpenRouter image provider; the generated image and topic exclusions are then sent to a separately configured vision-review provider. These requests do not include the account name, character name, saved identity labels, account ID, or a player photograph. Each relevant screen explains the data transfer before the player submits it. Provider/model routing is selected by the site owner, not the player; OpenRouter and the selected underlying providers process the data under their own terms.
Adult content and local previews
Graphic Life text and images are optional, private, and unavailable unless adult access, the graphic preference, the current eligible chapter, explicit per-scene intent, route configuration, and the matching usage quota all pass server checks. The text response or reviewed image is returned with private no-store handling and is kept only in transient browser memory; it is not added to Life history. Anonymous previews and local Learn reflections stay in the browser unless a screen explicitly offers and the player submits an enabled OpenRouter request. Turning content preferences off prevents later graphic deliveries.
Retention and choices
Players can use the account export and deletion tools for supported account-backed records. Saved game history follows the product’s account lifecycle and ruleset-preservation requirements; ephemeral mature output is excluded from that history. Backup and legally required record schedules, response times, and jurisdiction-specific privacy rights must be finalized before a public service launch. Classroom records require separate school retention and student-rights policies.
Sharing and security
Supabase stores the product’s account-backed database records in the configured SideQuest project. OpenRouter and the selected model providers receive only the content described above for an enabled request. The application uses access-scoped database policies, server-authoritative mutations, and least-privilege observability, but no security system can promise absolute security. Final processor, retention, and legally required disclosure details must be reviewed for the jurisdictions the service supports.