Kitten Haven – Privacy Policy
Last updated: 18 November 2026
Kitten Haven is published by MadManBroz, a studio operated by Storitveni servis Sergej Pust s.p., Slovenia ("we", "us"). That legal entity is the controller of the information we process for our own services. This policy covers the Google Play edition and, where specifically stated, our web and direct-download editions.
1. Google Play Games, sign-in and game saves
The Google Play edition uses Google Play Games for sign-in and cloud saves. These services use your Google Play Games profile; we do not create a separate studio account or receive your Google password. The game receives your Play Games player identifier and display name to associate your game profile with Google's services and show your name in the game. These identifiers are not included in our own analytics database.
Progress, including levels, stars, coins, crystals, rescued cats, decorations and settings, is stored locally on your device and can be synchronised to Google Play Games. Cloud saves let devices using the same Play Games profile continue saved progress. Our own servers do not receive or host your cloud-save files. Google handles the cloud service under its Privacy Policy.
Web and direct-download editions may store progress only on the device when Google Play Games is unavailable. Clearing app storage removes local data. Uninstalling the game or resetting local progress does not, by itself, delete Google Play Games cloud data or Google's purchase records. Cloud data can be managed through Google's Play Games data controls. Android or Google backup services may also restore device data according to your backup settings.
2. Purchases
Google Play edition: purchases are processed by Google Play Billing. We do not receive or store your card number, bank details or Google payment credentials. The app uses the product identifier, purchase status and a purchase token supplied by Google to deliver purchases and avoid duplicate grants. Purchase tokens are kept with the game save on the device and, if synchronised, in Google Play Games. Our own analytics may record the product code, purchase outcome and catalog value; this is not a copy of your payment credentials or Google's billing record.
Web and direct-download editions: if purchases are offered through Stripe, Stripe processes the payment. Our payment service processes the product code, a random player reference, Checkout Session/PaymentIntent identifiers and payment status to deliver the purchase. It does not store full card or bank details. Stripe maintains its payment records under its Privacy Policy. These Stripe routes are separate from Google Play Billing.
3. Usage statistics and technical error reports
The Settings option "Anonymous mode" is OFF by default, which allows first-party statistics and error reporting. Turning Anonymous mode ON stops new first-party statistics and error reports, clears queued telemetry, and requests deletion of previous records linked to this installation. When Anonymous mode is OFF, the game can send the following information to our service:
- Usage events such as sessions, level starts and results, moves and boosters used, shop and purchase outcomes, ad interactions, cat-care actions, repairs, decorations and expeditions.
- Technical error reports, including error messages, stack traces, source file and line, build version, operating-system/browser information and device model where available.
- A randomly generated installation identifier, session identifier, event timestamps and the game edition/store.
The installation identifier lets us associate technical records from one installation. This information is pseudonymous, rather than a promise that every record is completely anonymous. We do not intentionally include your nickname, cat names, email address, Google Play player identifier, advertising identifier or precise location in these analytics payloads. Our analytics tables do not contain an IP-address field. Hosting and network providers necessarily process connection information, such as IP addresses, to deliver and protect their services.
We use these records to diagnose errors, improve performance, understand game difficulty and maintain game features. We do not sell this data or use our own analytics database to personalise advertisements. For players in the EEA/UK, our basis for this first-party analytics is our legitimate interest in maintaining and improving the game, subject to your right to object by switching Anonymous mode on.
4. Advertising and consent
The Android game uses Google AdMob for optional rewarded ads and occasional ads between levels. The advertising SDK may collect IP addresses and approximate location derived from them, advertising or other device identifiers, ad/app interactions and diagnostic information for advertising, measurement and fraud prevention. Google processes this information under its Privacy Policy; see also Google's advertising SDK data disclosures.
Where required, including applicable EEA, UK and Swiss consent requirements, Google's consent mechanism presents privacy choices before ads are requested as permitted by your choices and applicable rules. Where available, use Settings → "Ad privacy choices" to review or change those choices. You can also manage your advertising identifier in Android settings. Turning Anonymous mode on stops our first-party telemetry; it does not itself change Google’s advertising consent settings or stop essential Google sign-in, cloud-save and purchase processing.
Buying "Remove ads" stops the between-level ads covered by that purchase. Optional rewarded ads may still be available when you choose them. Web editions may use Google's web advertising services where enabled; the Android AdMob description does not imply that every edition shows the same ads.
5. Service providers, location and security
Our own analytics/database and web/direct payment-service infrastructure is hosted in the European Union. Necessary hosting and database service providers process information on our behalf. Google provides Play Games, Google Play Billing and advertising services; Stripe provides payments in editions that use Stripe. Their processing is governed by their respective policies and may involve locations outside the EEA. Our use of EU infrastructure does not mean all processing by Google or Stripe takes place only in the EU.
Our app-to-service requests use HTTPS. Database and payment-service credentials are kept server-side, and access to our database requires service credentials. We limit access to information needed to operate the game and handle support or legal obligations. No internet service can guarantee absolute security. We may disclose information when necessary to comply with law or protect against fraud and abuse.
6. Retention
Our first-party usage events and technical error reports use a rolling three-day (72-hour) retention window. Derived activity and installation records are rebuilt solely from retained events and errors, so historical activity, first-seen dates and build information do not remain after their source records expire. Regular cleanup and deletion requests remove records from the active analytics database. Our hosting provider is configured to automatically expire its logs after three days. This retention period applies to our application telemetry and hosting logs; Google and Stripe independently control their own records.
Google controls retention of its account, cloud-save, advertising and payment records. Stripe controls its payment records, including records it needs to keep for legal or financial obligations. Contact messages are kept only as needed to handle the request and any applicable legal obligations. Support messages are handled through our contact email, separately from the game's analytics database.
7. Your choices, deletion and privacy rights
Settings → "Anonymous mode" is OFF by default. Turn it ON to stop our usage statistics and technical error reports. Queued telemetry and the current analytics identifier are removed from the device. The game asks our service to delete records linked to its previous installation identifier. A deletion request sends only the previous random identifier for that purpose and retries when online. Deletion cannot finish without an internet connection; the three-day retention limit continues to apply.
Settings → "Delete account and data" lets you delete Kitten Haven progress from this device and the game’s Google Play Games cloud saves, and requests deletion of our analytics data. You must explicitly confirm deletion; Google cloud deletion requires a signed-in Play Games profile and working connectivity. Local progress is retained if cloud deletion fails. The game uses your Google Play profile rather than creating a separate studio account. This action does not delete your Google account or Google’s independently held purchase, advertising or account records. Manage those records through Google Play Games data controls. You may also request deletion through the contact email below without deleting your entire Google account.
Depending on applicable law, you may request access, correction, deletion, restriction or portability of personal data, object to processing, withdraw consent where processing relies on consent, and complain to your data-protection authority. Contact us using the address below. We may need information sufficient to locate the relevant installation or record; do not send passwords or full payment-card details. We normally respond within one month where the GDPR applies, subject to its permitted extensions and exceptions.
8. Children
Kitten Haven is intended for teenagers aged 13 and over and adults. It is not intended for children under 13. We do not knowingly request personal information from children under 13. If you believe a child under 13 has provided us information inappropriately, contact us so we can investigate and take appropriate action.
9. Contact and policy updates
MadManBroz / Storitveni servis Sergej Pust s.p.
Gornje Ložine 18, 1332 Stara Cerkev, Slovenia
Registration no. 9216103000 · Tax no. 11817402
Email: info@storitveniservis.si
We may update this policy when the game or our processing changes. The date above identifies the current version; material changes will be communicated where required.
Optional notifications
If you enable notifications, Firebase Cloud Messaging handles delivery. We store a separate random installation identifier, notification token, app version, last registration time and a hashed deletion secret solely to route messages and manage your preference. Gentle care and eight-hour-away reminders are scheduled locally on your phone from existing care state; that care state is not sent to Firebase or our server. You can turn these reminders off separately in Settings. We do not attach your name, Google player ID, game save or wallet. Turning notifications off, turning Anonymous mode on, or deleting your game account asks our service to remove the push registration; server removal requires a working connection. Push-routing records remain while enabled and are separate from analytics and error logs, whose existing three-day retention is unchanged. Google processes Firebase installation and delivery information under its own policies.
Usage reports
When Anonymous mode is off, existing event records include timestamps, random installation and session identifiers, level elapsed time and selected in-game action counts. The service also derives coarse operating-system, browser and, when provided, device-model information from the request User-Agent. It does not store the full User-Agent or IP address. These analytics records and derived reports use the same three-day retention period and are removed by the existing analytics deletion control. Session and level duration are elapsed-time estimates, not exact active-play measurement. We do not identify you by Google account name.