Privacy Policy

Effective date: September 10, 2026

This Privacy Policy explains how Game Guessor ("we", "our", "us") collects, uses, shares, retains, and protects information when you use the Game Guessor mobile app, website, and related services. Some information is collected only when you use the corresponding feature, such as signing in, enabling notifications, or sharing a profile.

Information We Collect

• Guest, account, and authentication data: the app automatically creates an anonymous Firebase guest account with a Firebase user ID. If you register or sign in, we may receive your email address, authentication provider (Google, Apple, or email/password), provider account identifier, and Firebase user ID. Your password is handled by Firebase Authentication and is not stored by Game Guessor. Native Sign in with Apple requests your email address only. If you choose Hide My Email, we receive Apple's private relay email address. The account-deletion website uses Firebase's Apple sign-in flow, which may also request your name. Provider profile information does not replace your Game Guessor nickname or become part of your public game profile.
• Date of birth: the exact date you provide is stored with your account and used only to determine whether you may play and to select age-appropriate game content. It is not displayed on your public profile or used to select advertising.
• Profile and referral data: nickname, the initial avatar assigned by the app and any avatar you select from the app's built-in artwork, referral nickname or code, inviter and invitee identifiers, referral status, referral rewards, and public game statistics. Public statistics may include best score, maximum round, number of completed runs, and maximum play time.
• Blocking and reports: when you block a player, we store that player's user ID and the time of the block in your account's private blocked-user list. If you send a report by email, we receive your email address, the message, and any information or attachments you choose to include.
• Gameplay and reward data: game progress, level and round state, selected and submitted answers, answer times, play time, scores, game statistics, virtual coin balances, earned and spent rewards, and related app state needed to provide and restore game functionality.
• Analytics and installation data: app launches, sessions, screen views and other app interactions, app version, install source or referral data, device and app installation identifiers, language, operating system, device model, network information, and approximate location derived from an IP address. On Android, this may include the Google Advertising ID and Android device identifiers.
• Notification and messaging data: Firebase Cloud Messaging may automatically create or refresh an app-installation registration identifier and communicate with Firebase when the app starts, even before notification display permission is granted. After notification permission status is checked, the app may subscribe the installation to language, time-zone, and notification-audience topics. If notification permission is or has been granted, we may also associate a push token with your account and process permission and enabled status, notification-category preferences, delivery and interaction information, and notification event history.
• Diagnostics and service data: crash and non-fatal error reports, Firebase user ID attached to diagnostic reports, timestamps, app state, app version, device model, operating system, memory and storage information, network request diagnostics, IP address, and other technical information used to operate, secure, and troubleshoot the service.
• Content-delivery, support, and website data: when the app downloads game data, screenshots, or default-avatar artwork, or when you use our website, our hosting and content-delivery providers may process an IP address, requested URL or asset, browser or app request information, language, timestamps, and network or security diagnostics. The website also requests fonts from Google Fonts, which receives your IP address and browser request information to serve them. We also process information you include when contacting support.
• Information stored on your device: settings, authentication and account caches, date of birth, gameplay state, game data, referral state, notification preferences and history, a cached blocked-user list, and the version of the Public Profile Terms accepted for each account on that device. We also store other data required for continuity and offline or startup behavior. The operating system may include this data in a device backup, subject to your platform and backup settings.

How We Use Information

• To create and maintain guest or registered accounts and authenticate sign-in.
• To enforce the age gate and provide age-appropriate game content.
• To provide gameplay, public profiles, referrals, rewards, and progress tracking.
• To deliver app data and media through content-delivery services.
• To deliver optional notifications according to your preferences.
• To understand app usage and improve features, performance, and reliability.
• To detect, prevent, and resolve fraud, abuse, and technical issues.
• To apply your blocking choices, review reports, and moderate public nicknames.
• To comply with legal obligations and enforce our terms and policies.

Public Profiles and Referrals

Game Guessor profiles are designed to be shared. An authenticated Game Guessor user who has a valid profile link or user identifier can view the profile nickname, built-in avatar, and public game statistics, including best score, maximum round, completed runs, and maximum play time. The initial avatar is assigned automatically, and you may select another avatar from Game Guessor's built-in artwork. It is not a photo uploaded by you. Your email address, date of birth, balances, answers, and notification information are not part of the public profile.

When you share or use a referral, the inviter or invitee may receive your nickname and information about the referral or related reward. A shared link may contain a profile or referral identifier and nickname. Information that another user has already received may remain in that user's referral, reward, or notification history.

Nickname Terms, Reports, and Blocking

Before you create or edit a custom nickname, we ask you to accept the Public Profile Terms and Community Rules. The accepted version is stored locally for your account on that device, not sent to our backend as an acceptance record. We do not record an acceptance timestamp. You can decline and continue using the app with your current nickname. Accepting these terms is separate from analytics consent.

The Report action opens a draft in your email app; it does not send a report automatically. A profile-report draft may include the reported nickname and referral code. A screenshot-report draft may identify the game and screenshot. You can review and edit the draft before sending it. We receive it only if you send the email and use the information to review the concern, respond, and take appropriate action. Please do not include passwords, sign-in codes, or unnecessary personal information.

Blocking hides that player's profile from you. Your blocked-user list is not public, and blocking does not automatically report the player, remove their account, or prevent them from viewing your public profile. You can unblock a player from their profile.

Analytics

We use Firebase Analytics to measure app usage, engagement, installation attribution, and feature performance. Analytics may collect certain events and identifiers automatically. On Android, analytics collection includes advertising and device identifiers where available. We may use aggregated analytics to improve the app.

We associate analytics with your Firebase user ID, including a guest account's ID, so analytics is not anonymous. Custom events describe features used and their outcomes, such as sign-in method and success or failure, age-gate completion and eligibility, gameplay results and timing, tips and rewards, referrals and sharing, and notification permissions and interactions.

Our custom analytics event parameters do not include your email address, nickname, date of birth, password, authentication tokens, raw submitted answers, full shared links, or notification message text. They use categories, counts, durations, and outcome values instead. These limits apply to our custom events; Firebase also processes the account, installation, device, and usage identifiers described above.

How We Share Information

We may disclose information in the following circumstances:

• Service providers: Google and Firebase services used for Authentication, Analytics, Realtime Database, Cloud Functions, Crashlytics, Cloud Messaging, Remote Config, Hosting, and installation attribution; Google Fonts for website typography; Cloudflare for object storage and content delivery of game data, screenshots, and default avatars; and Apple services used for sign-in, app distribution, and platform functionality.
• Other users: public-profile and referral information as described above.
• Legal and safety reasons: when reasonably necessary to comply with law, respond to lawful requests, protect users or the public, investigate abuse, or enforce our rights.
• Business changes: as part of a merger, acquisition, financing, reorganization, or transfer of the service, subject to appropriate safeguards.

We do not sell personal information for money. Our analytics and service providers may process identifiers and activity information for measurement, attribution, content delivery, and fraud prevention.

Data Retention

Account, date-of-birth, profile, gameplay, balance, and referral information is generally retained while the account exists. Blocked-user entries remain until you unblock the player or delete your account. Reports and related correspondence are retained as needed to review and resolve the concern, handle follow-up, and meet applicable safety or legal requirements. Notification history is limited to a recent set of events, while push tokens and preferences are retained while needed to provide the notification service. Firebase Crashlytics generally retains crash reports and associated identifiers for approximately 90 days. Analytics, hosting, content-delivery, security, and other provider records are retained under the providers' configured or documented retention periods.

When a guest or registered account is deleted, we delete its Firebase Authentication account and primary backend user record, including its stored date of birth and blocked-user list. For Apple-linked accounts, both in-app and website deletion revoke Apple's sign-in authorization before deleting the Firebase Authentication account. Limited information that was already delivered to another user, such as a referral or reward record, references in another user's blocked-user list, and provider logs, backups, fraud-prevention records, or records required by law may remain for their applicable retention periods. Cached information on a device may remain until it is overwritten, the app's data is cleared, or the app is uninstalled.

Your Choices and Rights

• You can review your account inside the app. Creating or editing a custom nickname requires accepting the Public Profile Terms.
• You can report a profile or block and unblock a player from their profile.
• You can request password reset from the sign-in flow for email accounts.
• A registered account can be deleted inside the app or through our account-deletion page using email, Google, or Apple authentication.
• An anonymous guest account can be deleted inside the Android or iOS app from Account > Delete Account. After in-app deletion, the app automatically creates a new guest account. Referral-abuse prevention records remain in place.
• If you can no longer access your guest account on its original device or cannot access your registered account, contact us at support@gameguessor.com with the subject "Delete Account Request" for assistance.
• You can change notification permission in your device settings and notification-category preferences in the app.
• You can use device privacy settings to reset or limit advertising identifiers.
• Depending on where you live, you may have rights to request access, correction, deletion, restriction, portability, or objection concerning your personal information. Contact us to exercise an applicable right.

Age Requirements and Children's Privacy

Game Guessor gameplay is intended for users aged 16 or older. We ask for a date of birth before play and prevent gameplay when the submitted age is under 16. We use the date of birth only for age eligibility and age-appropriate game content; it is not public and is not used to select advertising. The submitted date remains associated with the account until the account is deleted.

The service is not directed to children under 13, or a higher minimum age where required by local law. If you believe we collected information from a child beyond what is needed to perform the age screen, secure the service, or process a deletion request, contact us so we can investigate and take appropriate action.

International Processing

Your information may be processed in countries other than your own, including where our service providers operate infrastructure.

Security

We use administrative, technical, and organizational measures intended to protect data. No method of transmission or storage is completely secure.

Changes to This Policy

We may update this page when our features, providers, or data practices change. The "Effective date" above shows the most recent update date. If a change materially affects your privacy choices, we may also provide notice in the app or through another appropriate channel.

Contact

For privacy questions, contact: support@gameguessor.com