WhiskerMatch itself does not collect any of the following:
The exceptions are the advertising data collected by Google on our behalf (§4), the anonymous product-analytics data collected via Firebase Analytics (§5), the crash/diagnostic data collected via Firebase Crashlytics (§6), and the ad-attribution data collected via the Meta SDK (§7).
WhiskerMatch saves your level stars, score, café warmth, purchased café decorations, and which cats you've rescued using Android's local app-preferences storage (SharedPreferences) — the same private, on-device mechanism used by the vast majority of Android apps. This data:
WhiskerMatch requests:
WhiskerMatch does not request camera, microphone, contacts, location, or storage permissions.
WhiskerMatch shows two kinds of ads, both served by Google AdMob:
To serve these ads, Google may collect and process data such as your advertising ID, device information, and general (non-precise) location, governed by Google's Privacy Policy. On your first launch, WhiskerMatch shows Google's User Messaging Platform (UMP) consent form, where (in regions that require it, such as the EEA/UK) you choose whether to allow personalized ads. You can change this choice later from Android Settings → Apps → WhiskerMatch → the app's own settings, or by clearing the app's data to see the form again.
WhiskerMatch does not itself receive or store any of the advertising data described above — it is processed by Google's ad-serving infrastructure, not by us.
WhiskerMatch uses Google Firebase Analytics to understand, in aggregate, how the game is played — for example, how many players start or clear a given level, how often a rewarded ad is watched to completion, or how often café decorations are purchased. This helps us find levels that are too hard, too easy, or otherwise not landing well, and is never used to identify you individually.
The events WhiskerMatch sends are things like: a level starting or ending (with its result and star count), a rewarded or interstitial ad being shown, and a café decoration being purchased — none of them contain your name, email, or any other personally-identifying information. Firebase Analytics also automatically collects standard app-usage signals (such as app opens and session length) and device/app information (device model, OS version, app version, and an advertising/analytics identifier), governed by Google's Privacy Policy.
In regions that require it (such as the EEA/UK), the same consent form described in §4 also covers analytics collection — declining ad personalization there reduces what Firebase Analytics is allowed to collect accordingly, via Google's Consent Mode.
WhiskerMatch uses Google Firebase Crashlytics to automatically detect when the app crashes or freezes, so problems can be found and fixed. When that happens, Crashlytics sends a crash report containing the technical error details (what code was running, and why it failed), your device model and OS version, and an installation identifier used only to group reports from the same installation — never your name, email, or any other personally-identifying information.
Unlike the advertising and analytics data described in §4 and §5, crash reporting is not tied to the ad-consent choice described in §4 — it's diagnostic data about the app's own stability, not advertising or user tracking, so it's collected regardless of that choice. It's governed by Google's Privacy Policy.
If you installed WhiskerMatch from an ad campaign we ran on Meta's platforms (Facebook, Instagram), the app uses the Meta (Facebook) SDK's App Events to tell Meta, in aggregate, how that campaign is performing — for example, that an install converted into a level being cleared, or a rewarded ad being watched. This helps us spend advertising budget on the campaigns that actually bring engaged players, and does not identify you individually to us.
The Meta SDK may collect your device's advertising identifier and general device/app information for this attribution purpose, governed by Meta's Privacy Policy. As with Firebase Analytics (§5), this collection is gated by the same UMP consent choice described in §4 — declining ad personalization there disables both the Meta SDK's advertising-ID collection and its automatic event logging.
WhiskerMatch integrates: Google AdMob (for ads) with its companion User Messaging Platform (for consent), Firebase Analytics (§5), Firebase Crashlytics (§6, for crash/stability diagnostics), and the Meta (Facebook) SDK (§7, for ad-campaign attribution only — WhiskerMatch does not use Facebook Login, Sharing, or any other Facebook feature). There is no other tracking or advertising service beyond these.
WhiskerMatch does not knowingly collect information from children under 13, and does not serve personalized ads to any user known to be under the age of consent in their region. The app contains no user accounts, social features, or chat.
If we update this Privacy Policy, we will revise the "Last updated" date above. Continued use of the app after changes constitutes acceptance of the updated policy.
If you have questions about this Privacy Policy, please contact us at:
matthew@bigriverads.com
© 2026 WhiskerMatch. All rights reserved.