Privacy
Summary
We collect a small amount of data needed to run puzzles, remember guest progress on this device, optionally record signed-in history, and understand reliability through minimal telemetry.
What we collect
- Session and identity: A session identifier for guests and authenticated players, derived from cookies or headers as implemented in this deployment.
- Gameplay progress: Puzzle attempts (for example in-progress, completed, score, and timing) stored server-side for rollups and history features.
- Telemetry: Allow-listed client events (such as page views and errors) sent to the application for diagnostics; payloads are size-limited.
- Simulated sign-in fields: In development, optional HTTP headers (such as subject, provider, email, display name) may be read to mimic an identity provider.
How we use data
We use this information to operate puzzles, show streaks or history where enabled, debug issues, and improve product quality. We do not sell personal data as part of this MVP shell.
Storage and retention
Data is stored using the server’s configured data directory for this instance. Retention policies are environment-specific and should be defined for production deployments.
Cookies and local storage
The app may use cookies or equivalent mechanisms for sessions. Browser local storage is not required for core MVP paths described in this repository but may be introduced by future features.
Third parties
If advertising tags or external analytics are enabled in a deployment, those vendors may collect data under their own policies. The on-page ad slot is a placeholder until such integrations are configured.
Your choices
You can clear cookies to reset guest session state in the browser. Signed-in users should use account controls provided by the eventual identity platform.
Children
The service is not directed to children under 13, and we do not knowingly collect personal information from children for this MVP pilot.
Changes
We may update this page as the product matures. Material changes in production should be communicated according to your organization’s policy.
Related
See Terms of Use and About.