Privacy Policy
Last updated:
This Privacy Policy explains how Trivia Tussle collects, uses, and shares information when you use the mobile apps, web app, public website, shared quiz links, and related services (the “Service”).
1. Service and Contact
Matt Leikam, an individual based in Overland Park, Kansas, United States, operates Trivia Tussle and is responsible for deciding how the Service uses personal data (the data controller). Privacy questions, requests, and corrections can be sent to contacttriviatussle@gmail.com.
2. Accounts and Identifiers
Interactive play creates or uses an anonymous Firebase Authentication account. Optional Google sign-in and Sign in with Apple on iPhone and iPad may provide a provider user ID, email address, and display name. Apple users can choose Hide My Email; a real email address is not required. Guest progress is stored on our servers and linked to the current anonymous account. Shared browser play does not require an email or display name; Firebase browser storage keeps access to that account when storage is available. Trivia Tussle also stores account state such as a Firebase user ID, anonymous status, creation and last-active timestamps, a guest installation identifier, provider identifiers, profile fields, and topic or onboarding choices.
3. Gameplay, Progression, and Rewards
Trivia Tussle processes question and answer selections, question snapshots, category or topic, score, correctness, duration and timing, game or challenge identifiers, outcomes, XP, rankings, streaks, inventory, rewards, and related progression records used to run and explain the game. Some public leaderboard entries include a user ID, display-name snapshot, score, and update time. A shared-browser question report stores the quiz and question version, selected problem category, your description and a timestamp under your current account so it can be reviewed and duplicate or excessive reports can be limited. Please keep personal information out of report text.
4. Shared Quizzes and Unlisted Links
Existing user-shared quiz links are generally unlisted: anyone with the link can open the permitted quiz material, but the link is not added to a public directory. Restricted or expired quizzes remain unavailable for new play. The shared browser page omits account identifiers and other players’ private answers. Your answer selections, timing and completed review are saved under your authenticated or anonymous account. Public publisher challenges and permitted spoiler pages contain quiz material, not private attempts. Other game comparison features may show participant display names, scores and outcomes to their intended participants.
5. Analytics, Diagnostics, and Security Signals
Google Analytics for the website and optional shared-browser usage measurement are disabled. The browser does not send optional opens, starts, completions, review views, replay, share or failure counts, and the shared-quiz service rejects measurement from older clients. A saved native-app Analytics choice does not enable browser measurement. These restrictions do not stop the game from saving the answers, results and account records needed to provide play, history and recovery.
Native Firebase Analytics is separate: it is off by default and can be enabled through Privacy Choices. When enabled, native Analytics processes app-instance or device identifiers, approximate location and app usage events. Event filtering is designed to remove direct account, link and contact fields before custom events are recorded. Cloud service logs used for operations, errors, abuse prevention and security are separate from optional Analytics.
Firebase App Check and reCAPTCHA Enterprise may process browser, device, network, IP-address and security-signal information to protect the Service. Trivia Tussle does not request precise GPS location for gameplay.
6. Local Storage, Cookies, and Similar Technologies
The Service uses browser or device storage for authentication persistence, a guest installation identifier, privacy and notification choices, theme and motion preferences, selected topics, recent-question history, and bounded reliability or duplicate-suppression records.
The public website pages do not directly write first-party cookies. Firebase, reCAPTCHA, Google sign-in, consent, analytics, and advertising services may use cookies, local storage, IP addresses, or similar technologies under their own implementations when those services are active.
7. Advertising and Consent
All web advertising is disabled. The website does not load the AdSense publisher script or request ads. On Browser Privacy Choices / Do Not Sell or Share, explicitly opening the Google privacy message may load the separate consent service and contact Google. That service may process IP addresses, browser information, existing Google cookies and saved privacy choices. Opening or accepting a message does not enable web advertising or website Analytics. An unavailable, unrecognized or incompatible consent signal is not permission.
You can return to Browser Privacy Choices to reopen the available Google controls and change or withdraw a choice. The page reports when Google does not provide a dialog. Refusing or withdrawing optional consent does not prevent gameplay, account deletion or data requests. Native builds retain their separate Google Mobile Ads consent flow; native Analytics remains a separate choice.
On iPhone, iPad and Android, Google Mobile Ads and its consent SDK may process device or advertising identifiers, IP-derived approximate location, ad views and clicks, app interactions, crash logs, performance information and diagnostics to serve or measure ads, manage consent and improve SDK reliability. Personalized advertising is optional and subject to platform permission and applicable Google consent.
To recover a completed web game, we keep a short-lived, account-authorized reference to the saved result and a separate record of whether an advertising opportunity was attempted. An attempt is not an impression. Expiration of that reference does not delete earned scores or inventory. Web rewarded offers and interstitials are not enabled.
Trivia Tussle does not intentionally send email addresses, display names, precise GPS location or Firebase user IDs as ad-targeting parameters. Learn how Google uses information from sites or apps that use its services.
8. Optional Notifications
If you enable notifications, Trivia Tussle processes a Firebase Cloud Messaging token, Firebase Installation ID, notification choices, time zone and quiet hours, platform, bounded app version/build and locale, delivery state, and identifiers needed to open the selected in-app destination. Notification choices can be changed in Settings, and delivery also depends on device or browser permission.
9. How Information Is Used and Shared
Information is used to authenticate accounts, operate and secure gameplay, calculate results and progression, provide shared links, honor saved choices, troubleshoot, prevent abuse, deliver enabled notifications, serve or measure advertising where permitted, and respond to support or legal requests.
Information is shared with Firebase, Google, and other infrastructure providers that perform those functions; with other players through the public or unlisted features described above; and when disclosure is required for legal or safety reasons.
10. Data Retention
Ordinary user-created shared links are configured to expire after 14 days; publisher examples may remain available as ongoing public challenges. Related play, recap, question-report and aggregate records may remain until separately deleted. Most account, gameplay, leaderboard, reward and request records do not currently have a fixed automatic expiry. Previously collected shared-browser usage markers have a seven-day expiry timestamp, which does not itself guarantee removal. No new optional usage markers are written. Existing aggregate counts are not automatically removed when a preference changes.
Local data lasts until overwritten, acknowledged, the app or browser data is cleared, or it is otherwise removed. The project’s ordinary Cloud Logging bucket is configured for 30 days and its required audit-log bucket for 400 days. Account-deletion safeguards use separate short expiry periods; a sanitized completion receipt has a 90-day expiry. Automated expiry removal is asynchronous. Other Google and Firebase records follow the relevant provider settings.
11. Account Deletion and Data Requests
Open Profile → Settings → Account → Delete Account. This self-service action covers guest, Google, and Apple accounts without requiring support contact or advertising consent. Confirm and, when requested, reauthenticate the same account. Apple-linked accounts use fresh Apple authorization to revoke app access. The server removes profiles, progress, scores, rewards, owned shared quizzes, participation records, leaderboard references, and notification registrations, preserving other players’ independent data. The app shows pending until server cleanup completes, then Account deleted and the welcome screen. This does not delete your Apple or Google account. Temporary deletion safeguards expire after their operational purpose; independent provider logs and historical advertising/analytics records follow provider settings.
If the action does not complete, or if you want to ask about broader account-linked records, follow the Delete Account guide or email contacttriviatussle@gmail.com and include the Firebase user ID when available. A request may require enough information to locate the account and verify that the requester is authorized.
12. Your Choices and Rights
Privacy Choices explains disabled website measurement and advertising, optional native Analytics, available Google consent controls, and data requests. Turning off optional collection stops future collection; it does not automatically erase information already collected. You may separately request deletion. Browser and device settings control permissions and local storage.
Where the GDPR applies, you may request access and a copy, correction, erasure, restriction, objection to processing based on legitimate interests, and portability where applicable. You may withdraw consent as easily as you gave it, without affecting processing that was lawful before withdrawal. You may complain to the data-protection authority in your country of residence, workplace or the place of the alleged infringement. See the EDPB list of authorities.
Email contacttriviatussle@gmail.com to exercise a right. We will respond without undue delay and normally within one month. If a permitted extension is necessary, we will explain it within that first month. Requests are normally free. We may ask for proportionate information needed to locate your data and confirm account ownership. Never send a password or authentication code. You do not need advertising consent or a new account to contact us.
13. Children’s Privacy
Trivia Tussle is intended for players aged 13 and older. This intended audience does not establish the age of an individual visitor or their consent. Children under 13 must not use the game. A parent or guardian must authorize a minor’s use or consent-based processing where applicable law requires it. In Europe, the age for a child to give their own online consent varies from 13 to 16 by country; age 13 alone does not establish valid consent everywhere.
All optional website Analytics, usage measurement and advertising are disabled for every player. The Service does not currently use an age gate or a verified parental-consent flow. A child-mode switch is a privacy restriction, not proof of parental consent. If parental authorization is required, a parent or guardian should contact contacttriviatussle@gmail.com before the child plays; sending an email alone does not verify or approve consent. Contact the same address to report a child’s account or request deletion.
14. Location and International Processing
Trivia Tussle is operated from the United States. The game database is in Google’s us-central1 region; Firebase Authentication and other provider records may be processed in the United States or other countries where the provider operates. A US database location does not prevent international processing. We do not request precise GPS location. Providers may infer approximate location from an IP address for security or services you choose to use.
Google’s applicable processing terms describe safeguards for restricted international transfers, including the EU–US Data Privacy Framework for covered certified entities and Standard Contractual Clauses where applicable. See the Google Cloud Data Processing Addendum, Firebase processing terms and Google Analytics processing terms. Contact us for information about the safeguards relevant to your data or a copy of applicable terms.
15. Security
Account authentication, server-side authorization, Firebase security rules and App Check help limit access and abuse. Private attempts and saved results require the owning account. We use HTTPS for transmission and restrict access to operational systems. No method of transmission or storage is completely secure.
16. Changes to This Policy
This Privacy Policy may be updated from time to time. Material changes will be reflected in the “Last updated” date, with additional notice when appropriate.
17. Contact
Privacy requests and questions can be sent to contacttriviatussle@gmail.com. Do not send passwords, authentication codes, payment information, or government identification unless a legally required verification process specifically calls for it.
18. Legal Bases Where the GDPR Applies
Necessary account authentication, answer processing, scores, saved progress, requested shared games and account support are processed to provide the game service you request (performance of a contract or steps you request before a contract). Without the necessary account and gameplay information, we cannot save or recover your game. A guest account does not require an email address or real name.
Proportionate security, fraud and abuse prevention, service reliability and defense of legal claims rely on legitimate interests in protecting players and operating a reliable game, balanced against your rights. You may object. We do not use this basis to enable optional website tracking or advertising.
Optional native Analytics, consent-dependent advertising and optional permissions rely on consent where required. Website Analytics and advertising remain disabled. Processing necessary to meet applicable legal duties, including data-rights requests, relies on those legal obligations. The game calculates scores and rankings automatically; these are game outcomes, not decisions intended to have legal or similarly significant effects.