Cookie Notice
What cookies are
Cookies are small pieces of data stored in your browser. JonGem uses essential cookies for sign-in, security, and language settings. Advertising cookies are not used.
Cookies we use
These cookies are host-only on the hub domain. They are not given a broadened Domain attribute. On HTTPS they also receive the Secure flag.
- jongem_session: keeps you signed in. Holds only a random session id. HttpOnly, SameSite=Lax, up to 30 days (ends after 3 days without use, up to 12 hours for reviewers). Revoked on the server as soon as you sign out. Essential
- jongem_oauth_state, jongem_oauth_verifier, jongem_oauth_next: a short-lived state value and PKCE verifier used to validate the Google sign-in flow through Supabase Auth, and the hub page to return to after sign-in. HttpOnly, about 10 minutes, deleted when sign-in finishes. Essential when that sign-in is used
- jongem_mfa: used only during the two-step verification step. Holds the sign-in token from Supabase Auth and the id of the account or session being checked, encrypted so that only the server can read it. HttpOnly, sent only to the two-step verification pages (/auth/mfa), about 10 minutes, deleted once the check is done. Essential when you sign in with two-step verification or change its settings
- jongem_play_claim: lets you take the last game score you submitted without signing in to your account after you sign in. Holds that play's token, encrypted so only the server can read it. HttpOnly, SameSite=Lax, up to 3 hours, deleted once you take the score. Necessary (when you play a game with scoreboards without signing in)
- jongem_locale: remembers the language you last read in (a page under /en or /ja, or one you picked with ?lang=), so sign-in, upload and account pages show it too. About 1 year. A functional cookie treated as necessary for that feature
- jongem:recent: not a cookie but a value in the browser storage (localStorage) of the hub domain. To fill "Recently played" on the home page it keeps only the address names (slugs) of the last games you opened and when, at most 8. The home page sends just those names to the hub to get the game cards, and the hub does not store the list. Clearing site data in your browser removes it. Functional
Third-party cookies
If you sign in with a Google account, Google or Supabase may set cookies or other storage on their own domains for authentication. Their policies apply to that processing. Optional server-side features such as Google Web Risk or the translation API do not, by themselves, place advertising cookies on the hub.
The sign-in, game upload and first community post pages, and the game play page when you submit a score that would enter a top 10, load the Cloudflare Turnstile script from a Cloudflare domain to check for bots. Cloudflare may use cookies or browser storage for that check, and Cloudflare's policies apply to it. Security alert mail to the Operator (Resend) is sent from the server only and sets no cookie in your browser.
Separation from the play origin
Games run in a sandboxed iframe on an origin that is different from the hub. Hub session cookies are designed not to be sent to the play origin. Game code should not be able to read account cookies.
How to control cookies
You can delete or block cookies in your browser settings. If you block the session cookie, you will not be able to sign in. Signing out deletes the session cookie. You can reset the language cookie by choosing a language again or by deleting it in the browser.
Privacy policy
The purposes, retention periods, and your rights are described in the privacy policy (/legal/privacy). Questions can be sent to [email protected] or [email protected].