← Back to HistoryQuest

Privacy at HistoryQuest

Updated October 5, 2026. HistoryQuest is a free geography and history game currently available for testing.

Google and email sign-in

When you choose Google sign-in, Google shares your basic account identity, such as your name, email address and profile picture, with our authentication provider, Supabase. We use your account identity to sign you in and display your account. We do not request access to your Gmail, Drive, calendar or contacts. Google sign-in is optional; you can play as a guest.

Game records and browser storage

Supabase stores game rounds, selected map coordinates, guesses and results. A signed guest cookie lets this browser access its own rounds. Your guesses are game selections, not a request for your device location. Summary statistics, preferences and draft questions are stored in your browser. Account sign-in currently does not synchronize your game history between devices.

Authentication uses browser storage to maintain your session. Guest cookies can remain for up to one year. Clearing browser storage removes local preferences and can remove access to guest rounds; it does not delete records already stored on our servers. Signing out also does not delete your account or stored rounds.

Services used by the game

Vercel hosts the website and Supabase provides authentication and game storage. Google handles Google sign-in. Map imagery and labels are requested from the map providers identified in the map attribution. These services receive information needed to serve requests, such as your IP address and browser request information, and operate under their own privacy policies.

This version has no advertising integration. We do not sell your Google account information. Stored account and game records remain until removed by the site operator.

Questions or deletion requests

Contact the site operator at realtoshka@gmail.com for privacy questions or requests to remove your account and game records. To identify a guest round, include its round identifier if available. Do not send passwords or access tokens.

Google privacy policy · Supabase privacy policy · Vercel privacy policy