TriviaBusters privacy and account deletion

Delete your TriviaBusters account

Deleting an account removes its Firebase sign-in, online profile and friend code, friend relationships, requests, blocks, private and team match data and history, Bot Match, Puzzle Board, and Timed Solo Crossing verification sessions, ranked records, matchmaking records, cosmetic inventory and equipped choices, progression balances and reward ledger entries, solo consumable inventory and purchase receipts when that feature is enabled, submitted question reports, invites, Daily Board attempts and sharing choices, and Club membership and activity linked to you. When chat is available, deletion also removes messages sent by you, active chat restrictions, and safety reports involving your account. Puzzle Board verification records contain the server-issued scenario and questions, attempted cells, answer outcomes, and route result so we can check a first-clear XP reward. Timed Solo Crossing records contain the server-issued board and questions, attempted cells, correctness and timeout counts, and run outcome. Both are marked for deletion seven days after a run starts; Firestore applies TTL deletion asynchronously and this can take longer. In-app deletion also clears saved profile and settings, practice records, Puzzle Board progress and recent results, Timed Solo Crossing best and recent runs, saved reports, and match or team-party resume data on that device. Another player's own match summary can remain with your account identifiers removed. If you own a Club, ownership moves to its earliest-joined remaining member; an empty Club is deleted. We do not retain your report notes after deletion.

To request deletion from outside the app, email us from the address linked to your TriviaBusters account. We will verify the request and complete it within 30 days. You do not need to reinstall the app.

Email a deletion request

For help using the game or your account, contact support@triviabusters.com. For privacy questions and deletion requests, contact data@strathworks.com. Never send us your password. If you cannot access the linked email address, contact us and we will explain the identity check needed.

An external request deletes online account data. It cannot reach information stored only on your devices. In the app, choose Settings → Clear all data on this device, or uninstall TriviaBusters, to remove those local copies.

Privacy notice

Last updated: 3 November 2026

Who we are

TriviaBusters is developed by StrathWorks Ltd. For game or account support, contact support@triviabusters.com. For privacy questions or data requests, contact data@strathworks.com.

Information we use

• Age, social access and advertising: Before account setup, the app asks you to enter your date of birth. It is checked on your device and is not saved or sent to our servers. On supported Google Play installs, the app may ask you or your parent to share an age range through Google Play Age Signals. The current source uses any shared range on-device to determine the local age group; otherwise it uses the entered date. An earlier internal version included a Firebase social-access check using a Play Integrity token and an Age-Signals-derived eligibility result. On 3 November 2026 we disabled public access to that server function and paused friend, invite, Club, and Daily Board comparison features while we clarify the permitted use of Age Signals. The function cannot grant or process a social-access decision. Current source does not send Age Signals-derived data to Firebase for this check. AAB 39, still present on the Internal testing track, contains the earlier request attempt but cannot obtain social access. We do not send or store your birth date, raw age range, age source, guardian email, or Play install ID for social authorization. Users younger than 13 cannot continue. Users aged 13–17 can use public online play, but the app does not initialize advertising or consent SDKs or request ads for them. Optional Firebase Analytics and crash reporting are also unavailable under 18. Advertising is available only for users whose age group places them at 18 or older and remains subject to consent. In-app local-data clearing and online account deletion leave the age group on this device so age-based rules continue to apply. Android app-storage clearing in system settings or uninstalling the app removes it and requires a new age check.
• Account: After the age check, the app creates an anonymous guest account automatically to support online features. Firebase Authentication stores your sign-in identity and linked sign-in providers. Link Google or email and password to keep access to that guest account. You can also sign in to a different Google account; the online histories stay separate and do not merge. An unlinked guest may not be recoverable after switching, so link it first to keep access or delete it in Settings before switching if you want its data removed. Local practice stays on this device. If the Google identity has not been used in TriviaBusters, a separate online account may be created. Google and Firebase Authentication use the relevant sign-in identity details; we do not receive or store your Google password. Email and password sign-in credentials are handled by Firebase Authentication. Settings lets you copy your Firebase account ID to your device clipboard as a support reference. TriviaBusters does not automatically send it to support; you choose whether to paste and send it.
• Game: account identifier, generated display name and shareable friend code, friend relationships and requests, blocks, private-match and team invites, casual and ranked matchmaking format and search status, board and turn state, results, per-format ranked rating and season placement, match history, and question history used to avoid recent repeats. Private rivalry records summarize match results, answer accuracy, and Quick/Classic mode records; only the account owner can read them. Daily Board attempts and replay state are linked to your account. Three independent Daily Board result-sharing choices (Friends, Club, Global) are stored with your account and default off. A current mutual friend can see only today’s completed score when you have enabled Friends sharing; active attempts and historical scores are not shared. Current Club members who opt in can see your completed score for today. If you opt into Global sharing, your generated display name and today’s completed score can appear in the global top-100 list. These social result views are temporarily unavailable while we review the permitted use of Play Age Signals. Shared challenge definitions do not contain your identity. Friend codes, match invites, and Club names can be seen by other players. Teens see an on-device safety reminder before opening Friends, Clubs, or a private friend-match invite; its acknowledgement is stored locally. There is no direct messaging. If you join a Club, its name, roster, role, invitations, challenge participation, and attributed member-organized match results are shared with Club members. Signed-in players can see Club names and total points on weekly and 13-week seasonal standings. Each member can contribute at most 10 points per Monday-to-Monday UTC week; eligible completed friend-invite matches earn one participation point and a win earns one bonus point. A season sums the weekly Club totals and carries no rewards. Public queues and Club challenges do not count. The leaderboard does not show member names or individual scores. Private contribution records are scheduled for deletion seven days after the active season ends, for up to 14 weeks; Firestore deletion is asynchronous. Account deletion and Club disband remove related contribution records. Ranked rating and placement data are server-managed; numeric ratings are hidden during placements and seasonal confirmation. If you earn or buy a cosmetic, its item ID, acquisition source, acquisition time, and equipped slot are stored with your account and removed on account deletion. The Shop currently previews three cosmetics; when enabled, they are visual only and do not affect match rules or results. If the separately gated solo-item feature is enabled, its Coin balance and single-use item count are stored in your account; a Coin purchase records its item, cost, resulting balance/count, and time. Account deletion removes those records. Remove-two-options can affect Bot Match, Puzzle Boards, and Timed Solo Crossing; extra time can affect Bot Match, verified Puzzle Boards, and Timed Solo Crossing. Verified Puzzle Board attempts store question deadlines and timeout outcomes for up to seven days to enforce the 15-second answer timer. These items never affect a human match.
• Reports: question identifiers and any note you choose to submit so we can investigate possible content errors. If you report another player, we store your account ID, the reported player's account ID and generated-name snapshot, your selected reason, and moderation status and notes so our Moderators team can investigate.
• Chat (not currently available): if chat is enabled, we store your account ID and generated display name with channel messages, the message text and time, moderation outcomes, and message/player reports. Message text is screened by Alecto Core, a StrathWorks Ltd moderation service. Alecto receives the text and a moderation profile, not your TriviaBusters account ID. We store Alecto's returned request ID with the matching message and any related report so Moderators can review the decision and identify it in a provider data request. We use this to prevent abuse and let the Moderators team review reports. There are no direct messages. Ordinary messages expire after 30 days. Report details, any appeal note, and message snapshots remain while a case is new or under review, then are marked for deletion 90 days after closure; reopening a case clears its expiry. Moderators may apply a 24-hour or 7-day restriction on sending chat messages. A restriction expires automatically and is recorded with its case. Account deletion removes chat records involving your account from TriviaBusters.
• On this device: display name and app settings, practice totals and results, up to 100 recently served question identifiers used to reduce repeats in local Quick/Classic practice and Timed Solo Crossing, Puzzle Board progress and recent clears or attempts, Timed Solo Crossing best and recent run results, pending report copies, and private-match or team-party resume references. Daily Board and authored Puzzle Board questions are excluded from local repeat suppression. Android backup rules ask the system not to back up or transfer this local data, but behavior can vary by device manufacturer. These records may be lost when you replace your device or reinstall the app. You can clear them in Settings. Clearing all device data also schedules the app's cached online data for cleanup after you reopen it; this does not delete your online account or history.
• Temporary Puzzle Board verification: when you choose an XP-verified attempt while online, we store the active scenario, questions, answers, and route state on our server to validate the clear. The answer key is not sent to the app. The session is marked for deletion seven days after it starts; the deletion may be delayed. Offline Puzzle Board play stays unscored and device-only. An XP amount is not available until we approve and enable reward settings.
• Timed Solo Crossing: personal bests and recent-run history are stored on this device. When you play online, the server temporarily stores a run's board, question attempts, and outcome to verify eligible XP. Records are marked for deletion seven days after a run starts; Firestore processes TTL deletion asynchronously, so removal can be delayed. Account deletion also removes these records.
• Optional diagnostics: adults can turn on Firebase Analytics and Crashlytics in Settings; both are off by default and unavailable under 18. When Analytics is enabled, Google assigns an app-instance ID and collects app lifecycle and session measurements, along with the app's documented tutorial and gameplay events. Google may derive approximate location from the device's masked IP address. We do not set your account ID or email as an Analytics user ID, enable Google Signals, or collect the Advertising ID in this build. Crash reports can include stack traces, relevant app state, device details, a Crashlytics installation ID, a Firebase Installation ID, and app/device session metadata. Turning collection off stops future Analytics and crash-report collection. Unsent crash reports are deleted when you turn reporting off and before a later opt-in, so a new opt-in sends only later crashes. Previously received Analytics data follows Google's retention period.
• Firebase operation and security checks: Firebase callable requests automatically include the function name, caller IP address, signed-in account ID, and an FCM token. Firebase also uses technical SDK user-agent data to operate and improve its services; Google says that data is not linked to a user or device ID. TriviaBusters does not use the FCM token to send notifications. Production builds use Firebase App Check with Google Play Integrity to help protect online features from abuse. Play Integrity checks send Google a request hash, app package/version/signing data, Play licensing status, and device integrity signals so Firebase can verify the app and request. An earlier internal build used an Integrity request hash to bind its Firebase account ID to a derived social-eligibility result. That access check is currently disabled; the current source does not send Age Signals-derived data to Firebase for social authorization. Google says Play Integrity does not transfer this information to third parties or use it to track individual users or devices.
• Advertising in current builds: the app includes Google Mobile Ads and Google's User Messaging Platform for consent. All current builds, including the production-flavor candidate, use Google's sample test ads; these do not grant game rewards and do not serve real paid ads. The Mobile Ads SDK may send your IP address, app/ad interactions, diagnostic information, and app-install or device identifiers to provide ads, analytics, and fraud prevention. Current Android builds exclude Advertising ID and Android Ad Services identifier, Topics, and Attribution permissions. If we enable optional Coin rewards for real ads, Google will receive a one-use random token, not your Firebase account ID, and send a signed completion callback to verify the reward. TriviaBusters associates that token with your account for up to 30 minutes; its replay-prevention record is marked for deletion after 30 days. Firestore TTL removal is asynchronous and can be delayed. Rewards remain off and no real ads are served in the current build.
• Purchases: real-money purchases are not enabled in the current version. The RevenueCat SDK is included in Android builds but is not initialized while cosmetic purchase and restore actions are disabled. The shop preview does not send your Firebase account identifier to RevenueCat or request an entitlement sync. If purchase and restore are enabled for Google Play testing, RevenueCat receives your Firebase account identifier to recognise your account and sync cosmetic entitlements. Purchases and restore require a linked Google or email sign-in so you can recover the same TriviaBusters account after reinstalling. If you buy a cosmetic, RevenueCat also processes the purchase history needed to verify and restore access to Neon Grid, Route Markers, and Victory Glow. Google Play handles billing; we do not send payment-card details to RevenueCat. Account deletion requests RevenueCat customer data deletion, which RevenueCat processes asynchronously. Separately gated solo items may use Coins earned through play: extra time for Bot Match, verified online Puzzle Boards, and Timed Solo Crossing; remove-two-options for those same solo modes; and skip-question for Bot Match, Timed Solo Crossing, and verified online Puzzle Board attempts. Extra time adds five seconds to the active clue. Verified Puzzle Board clues have a 15-second answer timer, and timeout consumes one attempt. A skip leaves the hex unclaimed; it consumes that mode's attempt in Timed Solo and Puzzle Boards, and passes the turn to the bot in Bot Match. Solo items are disabled and do not affect human matches. Offline Puzzle Board play stays available without account-backed item use.
• Service operation: Google services may process technical information such as network addresses, Firebase installation identifiers, callable-service tokens, and request metadata to provide, secure, and troubleshoot Firebase services.

Why we use it

We use this information to sign you in, operate Bot Match, casual and ranked matchmaking and matches, calculate ranked standing, run the Daily Board and let you review your 30 most recent completed results in Profile. Bot Match board state, selected questions, answer outcomes, and results are processed on the server. Daily Board result sharing is private by default. If you opt into Friends sharing, current mutual friends can compare only that day’s completed score; they cannot see older scores or an active attempt. Current Club members who opt in can see today’s completed score. If you opt into Global sharing, your generated display name and today’s completed score can appear in the global top-100 list. Social result views are temporarily paused while we review the permitted use of Play Age Signals. We also support Clubs and Club challenges, prevent question repeats and abuse, keep your history, process reports, recover interrupted games, protect service reliability, and support optional advertising consent in internal builds. When chat becomes available, we will use its messages and reports to provide channels, screen content, and investigate safety reports. We do not sell personal information.

Service providers and storage

Google Firebase provides Authentication, Firestore, Cloud Functions, Hosting, Analytics, and Crashlytics. Google also provides the Mobile Ads SDK and consent form in internal builds. Match and account data in Firestore is hosted in the europe-west2 region. If chat is enabled, Alecto Core, a content moderation service operated by StrathWorks Ltd, processes submitted message text to return a moderation decision. Its privacy notice and data processing terms describe its processing. Each provider processes information under its applicable service and privacy terms.

Retention and deletion

• Global Daily Board score index entries are marked for deletion after 48 hours; Firestore TTL deletion is asynchronous. Turning Global sharing off or deleting your account removes the entry sooner. Account data remains while the account is active. In-app deletion removes the Firebase account and associated cloud records as part of the same request. For external requests, we verify the requester and complete deletion within 30 days.
• While an in-app or externally verified account deletion is running, we temporarily store your Firebase account reference and the request start time in Firestore to block new account activity. A successful deletion removes this temporary record. In the currently deployed service, this lock expires after two hours. If cleanup is interrupted, retry deletion or contact us at data@strathworks.com so we can verify completion; do not assume an interrupted request completed.
• Bot Match board/session records expire seven days after a match starts and are typically deleted within a further 24 hours. Bot Match rate-limit records expire after two hours and are typically deleted within a further 24 hours. Account deletion removes these records immediately.
• Member-organized match contribution events used for weekly and 13-week Club standings are scheduled for deletion seven days after the active season ends, for up to 14 weeks. Firestore deletion is asynchronous. Account deletion and Club disband remove related records.
• Another player's own match summary may remain after your identifiers are removed. Editorial corrections to questions may remain without your account identity or report note.
• Player safety reports remain while they are new or under review. After a report is closed, its report and review details are marked for deletion after 90 days. Firestore deletes expired records asynchronously, so removal may be delayed. Reopening a case clears the expiry until it is closed again. Account deletion removes reports involving that account.
• If chat becomes available, ordinary messages and their Alecto request IDs are marked for deletion 30 days after posting. A request ID is also copied into a related report, where it follows that case's retention. Reported message snapshots follow the linked report case and are marked for deletion 90 days after closure. Active chat restrictions expire automatically after 24 hours or 7 days. Firestore TTL deletion is asynchronous, so removal can be delayed. Alecto Core's API request metadata may be retained for up to 90 days in active storage and 12 months in archive storage. Hosted review is currently off for the TriviaBusters Alecto project. If it is enabled before chat launches, flagged message text may be retained in that queue for up to 30 days. Account deletion cannot directly remove Alecto-held records. We retain only an opaque operational account reference and provider request IDs in a restricted queue until we request deletion from Alecto and record its outcome; resolved queue entries are marked for deletion after 90 days. We will use these IDs to request provider-side deletion by writing to data@alectocore.com.
• Google Analytics user-level and event-level data is retained for two months. New activity does not reset the user-data retention period. This setting does not affect most standard aggregated reports, which may remain. Firebase Crashlytics removes crash reports and associated identifiers starting 90 days after collection. You can leave both optional collections off in Settings.
• Google Cloud application and service logs use the project's 30-day default log retention. Required administrative audit logs are retained for 400 days by Google Cloud. These service logs are separate from your game account and are not presented as game history.
• Firestore keeps prior database versions for one hour while point-in-time recovery is disabled. Deleted records are no longer available to the app, and this recovery window expires automatically.
• Google Firebase Hosting may retain IP address information for a few months to detect abuse and provide service usage information.
• For deletion requests sent by email, we verify the requester and complete the request within 30 days. In-app deletion starts immediately; if the service is temporarily unavailable, sign in again and retry.

Security and your choices

Firebase Authentication, server authorization, App Check, and encrypted HTTPS connections protect online operations. Use a unique sign-in password and keep your account credentials private. You can clear local practice data from Settings without deleting an online account. You can turn off optional Analytics and crash reporting there at any time. Where required, ad privacy choices are available from Settings.

You can ask to access, correct, or delete information associated with your account by contacting us at data@strathworks.com. We will verify the request before making account changes.

Children

TriviaBusters is not designed for children under 13. Do not create an account if you are under 13.

Changes

We will update this notice when the app's data practices change and revise the date above.