Legal

Privacy Policy

Last updated: November 9, 2026

In short

YetiX stores your game progress on your device. To improve the game, anonymous usage statistics are collected with Google Firebase and an anonymous ID is created for each installation. Optional Google/Apple linking and cloud backup are available only when the feature is enabled. Firebase Authentication may process the provider account identifier and permitted name/email fields. The app does not copy these profile fields to Firestore backups, analytics or a custom local profile. We do not request a phone number. Interstitial ads and optional rewarded ads are provided by Google AdMob. In-app purchases are made through the App Store / Google Play payment system and verified with RevenueCat; we never see your card or payment details.

What data is processed, and why?

Data that stays on your device

• Language, theme, sound preference, tutorial status, best score and game statistics are stored locally. Device preferences are not backed up; progress also stays only on this device when cloud backup is disabled.
• Profile: the player name you choose (otherwise a random tag such as "Player#1234"), your level and experience points, the badges you showcase and your total play time are stored on your device. The player name stays only on this device and in your backup (when cloud backup covers the profile); it is never sent to analytics, leaderboards or other players. When you change it, analytics only records that the name changed, not the name itself.
• Missions and achievements: daily and weekly mission progress, reward chests, the login streak and achievement counters are stored on your device; this is not a new type of personal data. Analytics only receives in-game details such as the mission or achievement ID, tier, reward amount and chest contents (see app interactions below).
• Your in-game currency (Crystal) balance and recent transactions are also stored on your device. When cloud backup is enabled, the balance, recent transactions and purchase delivery ledger are also stored in Firebase Firestore.
• The cosmetics you own and equip (ball sets, board, effect, avatar, frame) are stored on your device and, when enabled, backed up with your ownership and equipment selections (permanent paid rights remain verified by RevenueCat); viewing, trying, buying and equipping them in the collection are measured as part of the app interactions below, using only the cosmetic's catalog ID (no new type of data).
• The last known list of permanent products you bought (e.g. Ad-free, cosmetic packs) and the delivery record of Crystal packs (store transaction IDs, so that one purchase never gives Crystals twice) are stored on your device. Bought Crystals are part of the balance and, when cloud backup is disabled, stay only on your device; permanent products come back on another device with Restore purchases.

Firebase Analytics (Google) — usage statistics

• App interactions: app opens, game starts and ends (score, duration, longest chain, how the game ended, whether it was continued), use of the super power and continues, tutorial completion, screens viewed; a range of games played (e.g. "5-19"); Crystal earn and spend events (amount, source or kind of purchase, balance afterwards); shop views (tab, where it was opened from), purchase events (product ID, price and currency, Crystals given; cancel or error code), the restore result and whether you are a paying player and have an active Ad-free entitlement (yes/no), where an Ad-free offer was viewed, and free-use and automatic ×2 reward sources; missions being assigned, completed and collected, reward chests opened, the login streak and achievements unlocked (mission or achievement ID, tier, reward amount, chest contents), the device clock being noticed going back or forward, the rating question being shown (what triggered it: a new best, a chain or a cleared board), the answer given, the feedback screen being opened and the “Rate us” link being tapped (your text is not sent). No transaction ID or user ID is sent to analytics.
• App instance ID: a random identifier Firebase creates for each installation, used to group the sessions of the same installation.
• Device and session information: device model, operating system and app version, language, session length.
• Approximate location: country-level location derived from your IP address. Precise (GPS) location is not collected and no location permission is requested.
• Advertising ID: the advertising ID on Android; on iOS the IDFA only if you allowed tracking. AdMob ad events (e.g. ad requests) are added to these statistics as well.
• Purpose: understanding how the game is played, spotting errors and balancing difficulty, measuring new features. The data is not used to target ads at you and is never sold.
• No name, email address or the anonymous user ID below is sent to analytics.

Firebase Authentication — anonymous identity and optional linking

• Each installation receives an anonymous Firebase user ID. Linking is not required to play. You may link Google on Android or Apple on iOS and sign in with the same provider to recover that account. Google and Apple are not automatically treated as one account.
• Firebase Authentication may process the provider account identifier and permitted profile fields. The app does not copy your name, email, photo or identity tokens to the Firestore progress document, analytics or a custom local profile record.
• The Firebase UID is used for account access and RevenueCat purchase matching, never as a Firebase Analytics user ID.

Firebase Firestore — cloud backup when enabled

• Stored under your UID: Crystal balance/recent transactions, the purchase delivery ledger (transaction identifiers and cutoff time), in-game cosmetic ownership/equipment, classic and timed game statistics, and synchronization version/change metadata. Clients can access only their own account.
• Purpose: backing up and recovering progress with a linked account and preventing duplicate purchase rewards. Firebase backups do not grant permanent paid rights; RevenueCat verifies those rights.
• With backup disabled this feature does not send progress to the server. Even linked accounts can lose progress not yet successfully backed up. Unlinked anonymous accounts cannot be recovered after deletion or a phone change.
• Switching accounts requires explicit confirmation. Current local progress is not merged into the target account. A source snapshot and recovery/journal record stay on the device; they are not sent to analytics or the target account.

Firebase Remote Config (Google) — remote settings

• The app downloads setting values from Firebase so that game settings (e.g. the continue countdown) can change without an app update. The Firebase installation ID and app information are sent with the request; no new personal data is collected.

Invites (Firebase Cloud Functions and App Check)

• While the invite feature is on, every player gets a short invite code (e.g. YETI-7K3P), linked in Firebase to your user ID (UID). You share it yourself through your device’s share menu; the app does not access your contacts.
• If you enter a friend’s code (on Android automatically through the Google Play link, otherwise by hand), the invite relationship is stored on the server: whose code, who entered it, when, how and the reward status. When the invited player has played a few games, both sides get in-game Crystals. Names are not shared; the profile name stays on the device.
• To stop the invite reward being collected many times on one device, the app’s device identifier (Android ID on Android, the vendor identifier on iOS) is stored only as a salted one-way digest; the raw identifier is not stored, the digest is not linked to your account and is used only for fraud prevention. It is deleted after 12 months.
• Server calls are protected by Firebase App Check: Google Play Integrity on Android and Apple App Attest on iOS check that the app is genuine and unmodified; device and app integrity information is sent to Google/Apple for this.
• The invite reward never depends on rating the app or installing another app. No invite code, user ID or device digest is sent to analytics.

Rating and feedback email

• The app occasionally asks whether you enjoy the game. To decide when to ask, the number of games played, the number of days the app was opened, the date of the last question and your answer are kept on your device only; they are not backed up to the cloud.
• If you answer “Yes”, Apple’s or Google’s own review sheet is requested; your rating and review go straight to the store and the app never sees them. Nothing is given in return for a rating.
• If you answer “Not really”, write feedback and tap Send, your device’s email app opens with a prefilled draft containing your text, the app version, device model, operating system and language. The email reaches us (the developers) only if you send it from your own email app; the app itself sends nothing to a server. We use such emails only to review and, if needed, answer your feedback.
• Analytics only receive events such as the question being shown, which answer was given and the feedback screen being opened; your text, the email addresses and the device details are not sent to analytics.

Google AdMob — interstitial and rewarded ads

• Interstitial ads may appear at intervals after you choose to leave a game-over screen. Rewarded ads for super powers, continues and doubling the end-of-game reward are optional. Ads require an internet connection and applicable consent and eligibility conditions.
• For advertising, fraud prevention and measurement, AdMob may process and share IP addresses (which may yield approximate location), advertising, app or device identifiers, ad and app interactions, crash and performance diagnostics. On iOS, IDFA requires ATT permission. Processing may occur during ad preparation and SDK operation, as well as when an ad is visible.
• An active Ad-free entitlement removes interstitial ads and allows free uses without watching ads. The app does not initialize the AdMob ads SDK on the next launch. If it was already initialized when you purchased, no new ads are loaded, and initialization is skipped from the next launch. Firebase, purchase verification and required consent management are separate services; buying Ad-free does not grant analytics consent.

RevenueCat — in-app purchases

• Payment is taken by Apple (App Store) or Google (Google Play); your card and payment details are never passed to us or to RevenueCat. The app uses RevenueCat, Inc. to verify and restore purchases.
• Data processed: purchase history (product, date, price and currency, store transaction ID and receipt / purchase token); the app user ID — the anonymous or linked Firebase ID above (or, until it exists, a random anonymous ID created by RevenueCat); device and store information (platform, operating system and app version, store country and currency, language, IP address).
• Purpose: verifying that a purchase is genuine, delivering the product (Crystals, Ad-free, cosmetics) exactly once, bringing products back to a new installation with Restore purchases, and handling refunds and cancellations.
• Retention: purchase records are kept at RevenueCat while the service runs; on your deletion request the records under your ID are deleted. Apple and Google keep their own purchase records under their own policies.
• Transfer: RevenueCat, Inc. (USA); the data is processed on servers in the United States. Details: https://www.revenuecat.com/privacy
• Revenue events to Firebase (only with analytics consent): if you allowed analytics, the Firebase app instance ID is passed to RevenueCat, and RevenueCat sends purchase, renewal and refund events (product, price, currency) to Firebase Analytics under that ID. Without consent the ID is not passed; if you withdraw consent, the ID is deleted at RevenueCat.

Consent and withdrawing it

• Where required (e.g. the EU/EEA and the UK), consent is requested at first launch through Google's User Messaging Platform. If you do not consent to storing information on the device and to measuring content performance, no analytics is collected.
• In these regions you can change or withdraw your consent at any time under Settings → Privacy options; analytics stops as soon as you withdraw it.
• On iOS, permission to track for ads is asked separately; declining does not affect the game.
• In other regions analytics is on for the purposes described in this policy. To object to analytics or request deletion of your data, write to the contact address below.

Retention

• Firebase Analytics event data is kept for 14 months and then deleted automatically.
• The anonymous/linked identity, Firestore backup and RevenueCat purchase records are kept until you ask for them to be deleted.
• Your invite code and invite relationships are kept until you delete your account; the one-way device digest kept for fraud prevention is kept for 12 months.
• Data on your device stays there until you delete the app.

Third parties and international transfers

• Data is processed by Google (Firebase and AdMob) as a service provider and may be stored on servers outside your country. Details: https://policies.google.com/privacy and https://firebase.google.com/support/privacy
• Purchase data is processed by RevenueCat, Inc. (USA) as a service provider: https://www.revenuecat.com/privacy. Payment is taken by Apple or Google.
• Data is not shared with or sold to any other third party.

Account and data deletion

• In the app: Delete my account in the Account section of the Profile screen (or the Settings menu when the profile is off). Your Firebase account (the anonymous ID and any linked Google/Apple sign-in), your Firestore cloud backup and all game data on the device are deleted; with Sign in with Apple the app's access at Apple is revoked, and the analytics ID on the device is reset. The game restarts like a new install. An internet connection is needed.
• Without the app: follow the steps on the account deletion page and email the address below with the subject "YetiX account deletion request". Requests are completed within 30 days.
• Uninstalling does not delete cloud backups; one of the two routes above is needed. Deleting the app removes the data on your device.
• Deleting your account also deletes your invite code, pending invite rewards and the invite you entered; your ID is removed from the records of players you invited. The one-way device digest, which is not linked to you, is deleted after 12 months.
• Analytics events are tied to a random installation ID, not to your account, and are kept for at most 14 months. Purchase records at RevenueCat are kept as long as needed for refunds and legal obligations; on request by email, the records under your ID are deleted. Apple and Google keep their own records under their own policies.

Children

YetiX is intended for a general audience and is not specifically directed to children. Advertising content is restricted to a general-audience rating.

Changes

We will update this page if this policy changes.

Contact

alperayar@hotmail.com