1. Contact and purposes
Globus Game processes information to operate accounts and games, display results, deliver requested Daily Challenge emails, answer support requests and protect the service. Privacy questions and requests: globusgame.support@gmail.com. Updated 1 November 2026.
2. Accounts and local storage
Registration uses an email address, password and player name. Supabase handles authentication, account identifiers, password verification, confirmation and password-reset messages. The game does not keep a separate copy of your plaintext password.
The website keeps sign-in sessions in browser cookies and stores preferences locally. The iOS project uses the device’s protected Keychain storage for sign-in tokens; ordinary settings may use local app storage. Signing out removes the active session from that client.
3. Game results and public information
For supported online features, we store the account identifier, player name, game, difficulty, start and finish locations, route, route lengths, score and time. Daily Challenge records also identify the challenge and date. Some game modes do not save online results.
Leaderboards and shared result pages display the player name and relevant game results. Your email address is not used as the public fallback name: the neutral fallback is Player. Other players can view public results. You can play without registering; account features require sign-in.
4. Daily Challenge emails
The signup subscription control is off initially. Daily Challenge emails require an affirmative subscription, and each delivery includes an unsubscribe link. We store subscription status, language, unsubscribe identifier and delivery records, including the recipient address and delivery status. Unsubscribing stops future challenge mail; necessary account messages, such as password resets, are separate.
5. Support requests
A feedback request may include an email address, message, chosen country, device, browser, operating system, language, game, web/iOS client and an optional image. The form also includes the submission time and User-Agent. The supplied email is used as a reply address. Messages and attachments are delivered through Resend and stored in an operator-managed Gmail mailbox.
The dedicated support tool stores minimal case and delivery identifiers, dates, linked-message identifiers, selected system labels and synchronization status in a separate Supabase database. It does not store message bodies, participant addresses or attachments in that database. Encrypted recovery checkpoints in private Vercel Blob contain case identifiers, keyed message fingerprints, states and dates.
6. Google mailbox access
The hosted support reader uses gmail.readonly and reads metadata to link known requests and replies, including Sent and Trash and replies in separate conversations. It does not download message bodies or attachments through the Gmail API. Ambiguous links require review.
The mailbox operator separately authorized the broader https://mail.google.com/ permission. It can read, compose, send, change and permanently delete mail. Its separate credential is stored in protected server secrets of the dedicated Production support service and in a restricted local operator configuration. The hourly reader does not use it. The automatic retention worker acts only on an exact eligible inventory under the fixed 90-day policy. The manual service requires a short-lived signed operator approval. No mail-sending operation is exposed by this service. Google mailbox data is not used for advertising, sold, or used to train AI models.
7. Providers and analytics
Supabase processes account and game data and the separate support registry. Google processes Gmail correspondence and OAuth authorization. Resend processes outgoing email and any submitted attachments. Vercel hosts the website and server functions and provides private Blob storage and Web Analytics. These providers may process data internationally under their terms.
The website uses Vercel Web Analytics for aggregated traffic information, such as page paths, referrers, approximate region and device/browser information. Vercel documents that this analytics service uses no third-party tracking cookies and discards its visitor hash after 24 hours. Before sending page views, the site removes query strings and fragments, omits private account/recovery routes and replaces shared-result tokens with a generic path. Hosting and authentication have their own network/security logs. The standalone information pages have no analytics script of their own; language preference is stored locally. No separate native advertising or analytics SDK was found in the reviewed iOS project.
8. Retention and backups
Account, score, Daily Challenge, subscription and email-delivery records remain until account deletion or another applicable removal procedure.
Production tracking and hourly metadata checks are active. Known, unambiguously linked form conversations become eligible for permanent mailbox removal after 90 days without a verified new message. A separate hourly worker removes messages and their attachments in bounded steps, then clears working case metadata. New replies, incomplete checks, ambiguity or operator/legal holds stop removal. Earlier and direct emails require manual handling. Verified earlier-removal requests are handled within 30 days, subject to applicable law.
The target for application-managed technical and authentication logs is up to 30 days. The dedicated support scheduler checks completed job logs daily and removes records older than 30 days; a record may remain until the next daily check. This is not a guarantee that every provider log or backup is erased within that period.
Resend documents 30-day email/log retention for Free, Pro and Scale plans and seven days for backups. The verified Vercel Hobby plan documents one hour of runtime logs; build logs can remain with deployments. Supabase Free does not provide the customer-accessible daily backup history offered on paid plans. These statements do not establish the lifetime of every provider-internal copy.
Minimal completion evidence — case identifiers, keyed message fingerprints, states and dates, without bodies, participant addresses or attachments — expires 365 days after case completion, except a documented hold. A successful retention pass replaces the current encrypted journal before removing obsolete encrypted objects and expired database evidence. Copies may remain until that pass succeeds. Detection of older restored data is limited after evidence expires. This does not guarantee erasure from provider backups.
9. Deleting your account and requesting removal
The signed-in account menu offers Delete Account with confirmation. Successful deletion removes the authentication account and linked leaderboard scores, Daily Challenge results, email subscription and linked delivery records across Globus Game, then signs you out. Separate support correspondence and provider logs are not automatically erased by that action.
To request access, correction or removal of support data, contact the support address, preferably from the original address. We may request proportionate evidence of ownership. Do not send passwords. Deleted active data may remain in provider backups.
For account deletions confirmed after activation of this safeguard, a separate encrypted record keeps only account and operation identifiers, states and dates. Confirmed evidence is removed after 365 full days through successful periodic processing; unresolved requests require review. Before online data access and new sign-in tokens, we check the independent record. An hourly reconciliation can remove the same previously deleted account and related restored game data again. An ambiguous request is held for review and is not automatically deleted. Verification failures or capacity limits can temporarily suspend online services. This does not identify older deletions without evidence, changed identifiers, or every provider restore; operators must isolate and check restored systems before reuse. Protection against restores older than the evidence period is limited.
10. Protection and changes
We use HTTPS, restricted server credentials, database access controls and encrypted private recovery storage. Only the operator and services needed for the stated purposes are intended to access private data. No method provides an absolute security guarantee.
This policy will be updated when processing changes. Required permissions must be obtained before new Google data access is used. The mailbox operator can revoke the application in Google Account connections. Revocation stops future access but does not itself erase existing correspondence or stored records.
Provider documentation
Vercel Web Analytics · Vercel logs · Supabase backups · Resend · Google Account