KEGILLION FIELD NOTES

Privacy and your saved games

This notice describes the current build, reviewed on November 12, 2026. Cloudflare Pages serves this site and a dedicated SQLite-backed Cloudflare Durable Object stores game and account records. External account email delivery must be configured before registration is offered.

Browser identity and saved play

The game creates a random kegillion_player cookie to associate this browser with its games. It is HttpOnly and SameSite=Lax, has a one-year lifetime and uses the Secure flag over HTTPS. There is no name, email or login requirement to play. Clearing it disconnects a guest browser from its saved games; it does not delete the server records.

What is stored

The project’s SQLite file stores the game identity, frozen question versions, attempts, original submitted answers, normalized answers, scores, deadlines and completion times. Request identifiers support safe retries, and short-lived request counters limit traffic. Unrecognized answers remain recorded for content correction. Avoid entering personal or sensitive information into the answer box.

Optional accounts

If you choose to register, the account service stores your email, private name, verification state, a password hash and session records. Passwords are hashed rather than stored as typed. Verification and password-reset links are temporary credentials; do not share them. Sign-in uses an HttpOnly session cookie, SameSite=Lax and Secure over HTTPS, with a fourteen-day session lifetime. This application does not retain IP addresses or user-agent strings in account session rows.

Earlier guest games are attached only when you explicitly choose Attach saved games. The association preserves original owners, questions and scores. Signing in on another browser can then recover these games. After signing out or resetting your password, an attached guest cookie alone cannot open the account’s records. Password reset revokes existing account sessions.

In local testing, verification and reset messages are saved in a private operator mailbox directory, with no external email sent. The hosted application requires a configured sender before accepting new registrations; it does not use the local test mailbox for real users.

Local event and review records

The database also records loaded-game views, prompt activation, submissions and their outcomes, completion, and client-reported copying or scorecard generation. Event records contain a one-way hash of the game identity, game/version references, timestamps and outcome counts; they do not contain raw answers, the cookie value, IP addresses, referrers or user-agent strings. Original answers stay in separate game submission records. Unknown-answer review decisions are stored separately and never rewrite earlier scores.

These records are kept as playtest history until the operator explicitly archives or removes them; there is no automatic retention cleanup. They are not sent to an external analytics service. Database backups include private game and account records and must remain private. A restored copy does not recover a deleted guest cookie.

Public Daily standings

Public sharing starts off. Only a verified account that chooses a public nickname and opts in can appear in Daily standings. The public list shows that nickname, rank and eligible Daily score. It does not show emails, private names, answers, cookies or saved-game identifiers. All eligible Daily dates may appear while sharing is on; you can withdraw in Your games. Withdrawal removes public entries without deleting private scores. Public pages or screenshots previously saved by others are outside this application’s control.

Sharing and third parties

Text sharing contains the mode, date or practice round, score, status grid and game link. The PNG scorecard contains the score and status summary. Neither export includes the full submitted-answer list or a private attempt ID. You choose whether to copy or save these exports.

This build has no GA4, advertising scripts, social sign-in providers or external AI grading requests. Fonts are served from the project. Browser or hosting software can have its own network logging; Cloudflare processes requests to serve the site, and its platform logging is separate from the application event table.

Retention and control

Saved records remain in the database; no automatic deletion schedule is implemented. The operator controls storage and backups. There is no self-service account deletion dashboard. Keep a guest cookie or explicitly attach games to a verified account for recovery. For a privacy request, use Contact; the contact page identifies the current delivery state.