Privacy Policy — Uh Oh Puzzle
Effective Date: 12 October 2026
Last Updated: 12 October 2026
Developer: Silly Games
Contact: hello@playsillygames.com
1. Introduction
Uh Oh Puzzle ("the App") is a mobile puzzle game. Uh Oh Puzzle is published by an individual developer based in the United Arab Emirates, operating under the brand name "Silly Games" ("we", "us", "our"). This Privacy Policy explains what information we collect, how we use it, and your rights regarding that information.
By downloading or using the App, you agree to the practices described in this policy.
2. Information We Collect
2.1 Information You Provide
We do not require you to create an account or provide any personal information to use the App.
2.2 Information Collected Automatically
Device & Usage Data (via Firebase Analytics & Crashlytics)
This data is collected only if you turn on "Share usage & crash data" in the App's Settings screen. This setting is OFF by default for every player, everywhere — it is not turned on automatically based on your region, and is never required to play the App. If you turn it on, we may collect:
- Device type, operating system version
- App version
- In-app events (e.g., level started, level completed, difficulty selected)
- Session duration and frequency
- Crash reports (via Firebase Crashlytics)
This data is not linked to your name, email address, or any other directly-identifying information you give us (we don't collect any). If you use the cloud save / leaderboard features described below, crash reports may include the same Firebase Anonymous Auth UID used for those features, which could let us correlate a crash report with your save data or leaderboard entry — see Sections 2.2 (Cloud Save) and 2.2 (Leaderboard) below. It is used solely to improve the App.
You can turn this setting on or off at any time from the App's Settings screen. Turning it off: usage-analytics collection stops immediately; crash reporting stops from the next time you open the App (this one-launch delay is a documented behaviour of the underlying crash-reporting SDK, not a design choice we can bypass). Turning it on may likewise only take full effect from the next time you open the App. Crash reports already captured on your device before you turn this setting off may remain stored on the device and are not uploaded once it's off, but we cannot guarantee any report queued for upload at the moment you turn it off will be cancelled. This setting is independent of the advertising consent choice described in Section 2.4 below — however, turning it off also withholds the ad-related analytics consent signals (ad storage, ad user data, ad personalization) sent to Google's analytics platform.
Advertising Identifiers (via Google AdMob)
Unless you have purchased an available ad-removal upgrade, the App displays advertisements provided by Google AdMob. AdMob may collect:
- Advertising identifier (IDFA on iOS, GAID on Android)
- Approximate location (derived from IP address)
- Ad interaction data (impressions, clicks)
On iOS, the App will separately request your permission via Apple's App Tracking Transparency (ATT) framework before using your advertising identifier for cross-app tracking. ATT relates only to this advertising identifier — it has no connection to, and does not control, the analytics/crash-data setting described above. Because of how ad networks initialize, an ad may appear before the ATT prompt is shown or answered; until you allow tracking, your advertising identifier is not used for ad personalization. You may decline the ATT prompt at any time; declining does not stop ads from being shown, it only limits ad personalization.
App Check (via Google Firebase App Check / Play Integrity / Apple App Attest)
Every time you open the App, it asks Google Play Integrity (Android) or Apple App Attest (iOS) to confirm the App is a genuine, untampered copy running on a genuine device, and uses the result to get a short-lived App Check token from Firebase. This runs before any consent choice and regardless of your settings. It is designed to help prevent abuse of our backend (for example, forged leaderboard scores or save data). Enforcement of this check is not yet turned on; today it only issues and monitors tokens. This process can involve your device sending its IP address to Google. We do not use App Check to identify you or track you across apps.
Separately, also before any consent choice, the App reads a small configuration record (adminConfig) from our own database. This record is read-only to the App and controls feature switches (for example, turning a feature on or off remotely); it contains no information about you.
Cloud Save Data (via Firebase Firestore)
The App signs you in automatically and invisibly using Firebase Anonymous Authentication — this does not ask you for a name, email, or password, and happens before any consent choice because it's necessary to operate the save feature. This gives your device a Firebase Anonymous Auth UID (not a name, email, or other directly-identifying value). If you use the cloud save / restore feature, we store, keyed to a 10-character restore code (shown to you as XXXXX-XXXXX) and not to the UID directly — the stored record also notes which device (by anonymous UID) most recently saved to it, since the same code can be used on more than one device:
- Your puzzle progress, stars earned, best times, hint balance, streaks, and badges
- Your colorblind-mode preference, display name, and country (if you set them)
- Unlock records (which levels, weekly collections, or rewards you've unlocked)
Sound, music, and haptics preferences are stored locally on your device only and are never sent to our cloud save.
Separately, a small technical record keyed to your Firebase Anonymous Auth UID (users/{uid}) stores which restore code your device is currently using, a save schema version number, your platform (iOS/Android), app version, and the last time your device was active. This record exists to operate the save system and is not shown to other players.
This data is associated only with the anonymous UID and the restore code — not with your name, email, or any other identifier we collect. Your restore code itself is never sent to our analytics, crash-reporting, or advertising providers. See "Leaderboard data" below for information that is shown publicly if you play with the leaderboard feature. See our Terms of Service §7 for what someone who obtains your restore code can do with it, and why you should treat it like a password.
Leaderboard Data (via Firebase Firestore) — publicly readable
If you complete a puzzle level, the App automatically submits an entry to the all-time leaderboard and the current weekly leaderboard. Each entry contains:
- A display name — a name you choose yourself in Settings (optional; if you don't set one, or if the one you chose can't be displayed (for example, it's blocked by our word filter), a generic name like "Puzzler" is used instead)
- A country code — taken from your device's locale setting by default, but you can change it yourself in Settings
- Your star score and the date/time of the submission
Unlike the cloud save data above, leaderboard entries are stored so that anyone can read them — the leaderboard is a public feature, visible to every player in the App, not just you. We apply a basic word filter to display names, but we cannot guarantee it blocks every inappropriate name, and we strongly advise you not to use your real name, or any other name that could identify you, as your leaderboard display name. Leaderboard entries are linked to your Firebase Anonymous Auth UID rather than to your real-world identity, so we describe this data as pseudonymous rather than fully anonymous — if you choose a display name that identifies you, that choice can make you identifiable to other players from the leaderboard itself. You can delete your leaderboard entries at any time by contacting us (Section 7).
2.3 In-App Purchases
If the App offers in-app purchases (for example, an ad-removal upgrade or hint packs), purchases are processed by Apple (App Store) or Google (Google Play). We do not collect or store your payment information. We only receive confirmation that a purchase was completed. If a given version of the App does not offer in-app purchases, this section does not apply to that version.
2.4 Advertising Consent (EEA, UK, Switzerland)
If you are in the European Economic Area, the United Kingdom, or Switzerland, the App is designed to show a consent message (built on Google's User Messaging Platform / the IAB Transparency & Consent Framework) before any ads are requested. This message is intended to let you:
- Consent to the advertising partners listed in the message using your data for personalized advertising, or
- "Do not consent" — in which case you may be shown limited, non-personalized ads, or no ads at all, depending on which ad partners are able to serve without personalization data.
You can change your choice at any time via Settings → Privacy Options in the App.
The advertising partners shown in this message are Google and the other ad networks, exchanges, and vendors that Google's AdMob platform automatically keeps up to date as "commonly used ad partners" for apps using AdMob (we have not restricted this to Google alone). We do not rely on "legitimate interest" as a legal basis for any advertising purpose covered by this message — every purpose requires your affirmative consent, and no partner may process your data under a legitimate-interest basis for these purposes through this App.
Outside the EEA, UK, and Switzerland, this consent message is not currently shown by Google's platform; the separate "Share usage & crash data" setting described in Section 2.2 above still applies to every player everywhere, regardless of region.
3. How We Use Your Information
| Data | Purpose |
|---|---|
| Analytics & crash data | Identify bugs, improve gameplay, prioritise features |
| Advertising identifier | Serve advertisements (where no ad-removal upgrade is active) |
| App Check / device attestation | Help prevent abuse of our backend (forged scores/saves) and keep the service available (enforcement not yet enabled) |
| Cloud save data (keyed to restore code) | Allow you to restore progress across devices using a 10-character restore code |
| Leaderboard data (display name, country, score) | Show you and other players a public all-time and weekly leaderboard |
| Purchase confirmation | Unlock purchased features (Calm Mode, Hint Packs, Streak Shields), where offered |
We do not sell, rent, or share your personal data with third parties for their own marketing purposes.
4. Third-Party Services
| Service | Provider | Purpose | Privacy Policy |
|---|---|---|---|
| Firebase Analytics | Google LLC | Usage analytics (opt-in) | firebase.google.com/support/privacy |
| Firebase Crashlytics | Google LLC | Crash reporting (opt-in) | firebase.google.com/support/privacy |
| Firebase Firestore | Google LLC | Cloud save / restore / leaderboard | firebase.google.com/support/privacy |
| Firebase Authentication (Anonymous) | Google LLC | Assigns the anonymous UID that identifies your device to our backend | firebase.google.com/support/privacy |
| Firebase App Check (Play Integrity / App Attest) | Google LLC | Confirms the App is genuine/untampered before trusting backend requests; runs pre-consent (enforcement not yet enabled) | firebase.google.com/support/privacy |
| Google AdMob | Google LLC | Advertisements | policies.google.com/privacy |
Each provider's privacy policy governs their own data handling. We encourage you to review them.
5. Children's Privacy
Uh Oh Puzzle is intended for a general audience aged 13 and up. It is not directed at, marketed to, or designed for children under 13.
We do not knowingly collect personal information from children under 13. The Firebase Anonymous Auth UID described in Section 2.2 does not by itself constitute personal information, and the "Share usage & crash data" setting is OFF by default for everyone, including any player who may be under 13. If you are between 13 and 17, be aware that the leaderboard feature (Section 2.2, "Leaderboard Data") is public and shows whatever display name you choose — we advise every player, and especially players under 18, not to use their real name there.
If you are a parent or guardian and believe a child under 13 has used the App and provided us with information, please contact us at the email below and we will address it promptly.
6. Data Retention
| Data type | Retention period |
|---|---|
| Analytics events | Retained by Google Analytics for the retention period configured for our project, then deleted automatically |
| Crash reports | Retained by Firebase Crashlytics for its standard retention period, then deleted automatically |
| Cloud save & leaderboard data | Until you request deletion (see Section 7) |
| Local device data (PlayerPrefs) | Until you uninstall the App |
7. Your Rights
Depending on your location, you may have the right to:
- Access the personal data we hold about you
- Delete your data — contact us at the email below and we delete your technical record (
users/{uid}), your leaderboard entries, and your anonymous account. Because a restore code can be shared across more than one device, we retire the cloud save itself once you confirm no other device is still using that code; a retired save is replaced with a marker holding no player data, so it can't be restored. Weekly leaderboard entries are removed for the weeks you tell us you played. If you had turned on "Share usage & crash data," analytics and crash reports are a separate case: individual records aren't retrievable or deletable by us on request once submitted — Google holds them only for the retention periods described in Section 6, then deletes them automatically. Contact us and we'll explain what applies to your account. - Change your advertising consent at any time via Settings → Privacy Options in the App (see Section 2.4)
- Turn analytics/crash-data sharing on or off at any time via the "Share usage & crash data" setting in the App (see Section 2.2) — available to every player, in every region, not only the EEA/UK/Switzerland
To exercise any of these rights, contact us at: hello@playsillygames.com
8. Data Security
We take reasonable technical measures to protect your data:
- All data transmitted to Firebase is encrypted in transit (TLS)
- Firebase Firestore access is restricted by security rules — our rules make your cloud save reachable only to someone who holds its restore code, and deliberately make leaderboard entries public by design (see Section 2.2, "Leaderboard Data")
- We do not store payment information
No method of transmission over the internet is 100% secure. We cannot guarantee absolute security.
9. International Transfers
Your cloud save and leaderboard data (Firebase Firestore) are stored on Google servers located in europe-west1 (Belgium). Analytics, crash reporting, advertising, and App Check processing are handled by Google LLC, which processes data in the United States and other countries where Google or its sub-processors operate. This can include processing your IP address (for example, in connection with App Check or ad serving). Where Google transfers personal data from the EEA/UK/Switzerland to the United States or elsewhere, Google relies on Standard Contractual Clauses (SCCs) or another legally recognized transfer mechanism as described in Google's own privacy documentation (linked in Section 4) — we do not operate our own international-transfer mechanism separately from Google's.
10. Changes to This Policy
We may update this Privacy Policy from time to time. We will notify you of significant changes by updating the "Last Updated" date at the top of this page. Continued use of the App after changes constitutes your acceptance of the updated policy.
11. Contact Us
If you have any questions or requests regarding this Privacy Policy, please contact:
Silly Games
Email: hello@playsillygames.com
Website: playsillygames.com
This Privacy Policy was written for Uh Oh Puzzle by Silly Games.