Privacy Policy

1. Service and Contact

Trivia Tussle is the name used for this online trivia service. 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 installation. 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.

4. Shared Quizzes and Unlisted Links

Shared quiz and game links are unlisted, not private. Anyone who has the link or identifier may be able to retrieve the shared quiz or game information exposed by that feature. Shared records can include owner and challenger user IDs or display-name snapshots, scores, answer or result summaries, category, timestamps, and outcome.

5. Analytics, Diagnostics, and Security Signals

Web Firebase Analytics collection is disabled. Native Firebase Analytics 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 analytics events are recorded. Cloud service logs used for operations, errors, abuse prevention, and security are separate from optional Firebase 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

Paid web advertising is not currently activated. If the applicable Google privacy message is configured and published, the Google tag initializes that message with advertising requests paused. Tag loading contacts Google and may read existing Google cookies before an ad request. Advertising additionally requires current applicable consent signals and separate account and serving configuration. Google may process cookies or local storage, IP address, device and browser information, consent signals, and ad interactions. Browser Privacy Choices / Do Not Sell or Share opens the available web message and shows when it is not configured. 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, other app interactions, crash logs, performance information and diagnostics to serve or measure ads, manage consent and improve SDK reliability. Personalized advertising through Google Mobile Ads is optional and subject to platform permission and applicable Google consent.

To recover a completed web game after a reload, we keep a short-lived, account-authorized reference to the existing saved result and a separate record of whether its advertising opportunity was attempted. An attempt is not an impression. Browser storage contains only minimal account-bound selectors, not authoritative scores. Expiration of the recovery handoff does not delete earned scores or inventory. If optional web rewarded offers are later approved, short-lived authenticated intents and one-time fulfillment records will distinguish browser-reported ad completion from independently verified provider evidence.

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 and manage Google ad personalization in Google Ads Settings.

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

The shared-link parent document is configured to expire after 14 days; related play, recap, and aggregate records may remain until separately deleted. Most account, gameplay, leaderboard, reward, and request records do not currently have a fixed automatic expiry.

Local data lasts until overwritten, acknowledged, the app or browser data is cleared, or it is otherwise removed. Google and Firebase provider logs and records follow provider and account settings, which may differ by record type.

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 describes controls for optional native Analytics, ad personalization, child-mode restrictions, do-not-sell/share signals, and data requests where those controls apply. Browser and device settings control permissions and stored data.

Depending on your location, applicable law may provide access, correction, deletion, restriction, objection, or advertising rights. Email contacttriviatussle@gmail.com to ask about a request; submitting a request does not by itself confirm that it has been fulfilled.

13. Children’s Privacy

Trivia Tussle is intended for players aged 13 and older, including teens and adults. This intended audience does not establish the age of an individual visitor or their consent to data processing.

The Service does not currently use an age gate or a verified parental-consent flow. Privacy Choices includes a child-mode setting that disables optional Analytics and personalized ads and enables restrictive advertising signals; that setting does not verify age or consent. If you believe a child provided personal information without appropriate authorization, email contacttriviatussle@gmail.com.

14. Location and International Processing

Trivia Tussle does not request precise GPS location for gameplay. Providers may infer approximate location from an IP address for security, consent, analytics, or advertising where those services are enabled. Firebase data and service-provider records may be processed in the United States and other countries where providers operate.

15. Security

No method of transmission or storage is completely secure, and absolute security cannot be guaranteed.

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.