Privacy Policy

1. Who we are

PocketLoom Games ("we", "us" or "our") publishes Make Room, Kitties! This policy covers the Android and iOS game, including iPhone and iPad, and information you send when contacting us about it. The app identifier is com.pocketloom.makeroomkitties. For privacy questions, email main@pocketloom.games.

2. Information we handle

Data on your device

The game stores progress, unfinished puzzle layouts, your cat home, earned coins, Help charges and preferences locally so you can continue playing. Local app data also includes ad reward bookkeeping, privacy choices and the time of the last update check. We do not operate an account-based cloud-save service. Android or Apple’s operating system may back up or restore app data depending on your device, system settings and backup provider.

Analytics

The Android and iOS apps use Google Analytics for Firebase. On iOS, the analytics SDK is started and collection runs only while tracking permission is authorized in Apple’s system dialog and the Gameplay analytics switch is not turned off; the current Android version has analytics enabled. When collection is enabled, Firebase processes an app-instance identifier generated for an installation of the game. This is a pseudonymous identifier; analytics data is not necessarily anonymous.

• App and device information: device model, operating system, app version, language and basic app activity, such as first launch, sessions and engagement.
• Gameplay and home information: Play taps, levels started, completed or left, level and generator identifiers, puzzle size, resumed layouts, active play time and summary counts of placements, rotations, rejected moves and returns to the tray. Events also describe onboarding, visited game screens, adopted cats, owned or equipped decor, room and item identifiers, earned and spent coins, Help balances and use, settings changes, progress resets, save errors and ad or reward events. Random visit and snapshot identifiers group related events.
• Approximate location: Google may derive a general location from your IP address. The game does not request GPS or precise device location. Google states that Google Analytics does not log or store IP addresses.

Our custom gameplay events do not include names, email addresses, raw save files or cat placement coordinates. Firebase advertising identifier collection, advertising storage, advertising user data and advertising personalization are disabled in our app configuration. The iOS build uses the Analytics library without IDFA collection and disables Firebase’s collection of the vendor identifier (IDFV). These restrictions apply to Firebase Analytics; Google Mobile Ads is a separate SDK, described below.

Read Google’s explanations of Firebase Analytics data collection, Analytics collection controls and Analytics data handling.

Information you send us

If you email us, we receive your email address, message and any attachments you choose to send. Please avoid sending sensitive information or information unrelated to your request.

3. Why we use information

Local data lets the game remember your progress and account for earned rewards. Analytics helps us understand progression, identify difficult or confusing interactions and evaluate improvements. Ad-related processing supports delivery and measurement of test ads, SDK operation and fraud prevention. Update checks identify a newer store version. We use support messages to respond to questions and resolve issues, including privacy requests.

The legal basis for processing depends on the information, purpose and applicable law. On iOS, optional gameplay analytics is based on your permission, which you can withdraw in the game’s Settings or in iOS Settings → Privacy & Security → Tracking. Where other processing relies on consent, you may also withdraw it. Other applicable bases may include providing a service you request, responding to a request, complying with legal obligations or legitimate interests where permitted by law. Contact us for information about the basis relevant to your circumstances. The current analytics controls and their limitations are described in section 8.

4. Providers and sharing

Google processes information through Google Analytics for Firebase, Google Mobile Ads and the User Messaging Platform. Apple receives iOS version lookup requests and handles App Store interactions. Google Play handles Android store update checks. Our email provider processes messages you send us. Your device’s backup provider may process app data if you use system backup. These services may handle information under their own terms and privacy policies as well as applicable service agreements.

We may disclose information where required by law or necessary to respond to a lawful request or protect legal rights. Google Mobile Ads may share SDK data for advertising, measurement and related purposes described in its disclosures; using test ad units does not remove those SDK data flows.

See Google’s Privacy Policy, how Google uses information from apps that use its services and Apple’s Privacy Policy.

5. Advertising and ad privacy choices

The native game integrates Google AdMob test interstitials after selected first level victories and optional rewarded videos in Daily tasks. Rewarded videos grant Help charges only after a completed reward event. The browser version does not serve rewarded ads. Current native versions use Google’s dedicated test ad units; paid production advertising is not enabled.

Test advertisements still involve SDK network requests and data processing. Depending on the platform and available identifiers, Google Mobile Ads may process IP addresses and the general location inferred from them, app and device information, app- or developer-bounded identifiers, advertising identifiers where available, app launches, taps, video views, ads shown, crash and diagnostic information, and performance information such as launch time, hangs or energy use. Google describes these uses as supporting advertising, analytics, SDK improvement and fraud prevention.

On Android, the app declares the Advertising ID permission for Google Mobile Ads; collection remains subject to device settings and applicable ad privacy choices. On iPhone and iPad, the game asks for tracking permission only through Apple’s system App Tracking Transparency (ATT) dialog, shown on the Home screen shortly after launch when iOS allows a request and no decision has been made; we do not use our own dialog as a substitute. You can choose Allow or Ask App Not to Track without limiting gameplay or the availability of ads. With your permission, Google Mobile Ads can access Apple’s advertising identifier (IDFA) for delivering and measuring advertisements, which can include linking activity with data from other companies’ apps or websites. If permission is denied or restricted, Google Mobile Ads does not receive IDFA and ads continue in the mode allowed by your ad privacy choices. This does not mean that Google Mobile Ads collects no data: other app- or developer-bounded identifiers and usage or diagnostic information may still be processed. Firebase’s advertising restrictions do not disable Mobile Ads data collection.

Google’s User Messaging Platform checks the applicable ad consent status. Where required, it presents a privacy message before ad requests are permitted, and Settings offers Privacy choices to revisit them. UMP processes information needed to determine and record those choices. If ad requests cannot be permitted, gameplay remains available without ads. Ad privacy choices and gameplay analytics are separate controls. The iOS Gameplay analytics switch does not change your UMP ad choices or disable Google Mobile Ads data processing; UMP ad choices do not change your gameplay analytics choice.

See the Google Mobile Ads disclosures for iOS and Android, and Google’s Privacy Policy.

6. App update checks

On iOS, the game makes a non-blocking request to Apple’s public version lookup service at startup, limited to once in six hours between launches. The request includes the game’s bundle identifier and, when available, the App Store country or device region. Apple also receives ordinary network connection information, such as the IP address. We do not add your save, gameplay history, analytics installation identifier or contact information to this request. The returned version is compared locally. Choosing the update action opens the App Store; the game does not silently install an iOS update.

On Android, the game checks for updates through Google Play’s in-app update service. Downloads and installation use Google Play’s services and data practices. Store or network unavailability does not prevent normal play.

7. Storage and retention

Local progress remains in app storage until it is removed or replaced. Clearing app storage or uninstalling normally removes local data, but system backups may remain or restore it. Manage backups separately through your device or backup provider.

Information processed by Google Mobile Ads, UMP and Apple’s services is subject to their applicable retention practices and terms. Analytics data is retained according to the Google Analytics property’s retention settings and Google’s applicable processing terms. Aggregated reports can be retained differently from event-level data. See Google Analytics retention controls.

We keep support correspondence for as long as needed to handle the request and any related follow-up, resolve disputes or meet legal obligations. Retention depends on the purpose and applicable requirements rather than one fixed period for every type of information.

8. Your choices and privacy rights

Device data: use the game’s reset option to reset progress, or delete the app and its data through your operating system. Android also offers controls to clear app storage. These actions can erase progress. Offloading an iOS app may retain its data; backups can also remain or restore data. Deleting local progress does not automatically delete analytics already sent to Google or data held by ad services or backup providers.

iOS analytics: gameplay analytics is initialized and collected only while ATT permission is authorized and you have not turned analytics off in the game. If the permission is undecided, denied, restricted or cannot be confirmed, analytics stays off, the analytics SDK is not started and nothing is kept for later sending; you can continue playing. The game re-checks the permission every time it starts or returns to the foreground; withdrawing it in iOS Settings → Privacy & Security → Tracking stops collection. With permission granted, use the Gameplay analytics switch in Settings to turn analytics off or on at any time; this switch cannot override a refusal made in iOS, and resetting progress does not change your choice. A refusal saved by an earlier version is kept. A Privacy Policy link is always available in iOS Settings.

Turning iOS analytics off stops further collection, clears locally cached Firebase analytics data and resets the analytics app-instance identifier. Events that occur while analytics is off are not queued for later sending. Allowing analytics again starts collection for subsequent activity. Withdrawal does not automatically delete information already sent to Google or previously produced reports; privacy requests and applicable limitations are described below.

Android analytics: collection remains enabled in the current Android version. There is no in-game analytics switch, separate analytics permission prompt or analytics deletion button. Uninstalling stops future collection from that installation; clearing storage or resetting progress alone does not disable collection when you play again. Advertising ID controls, Apple’s tracking controls and the game’s ad Privacy choices are not a general analytics opt-out.

Ads: revisit Privacy choices in Settings when that entry is required and available. Your operating system also provides advertising or tracking controls. The availability and effect of these choices depend on the platform and applicable settings.

Privacy requests: depending on the law that applies to you, you may have rights to access, correct, delete or receive a copy of your personal data, restrict or object to processing, withdraw consent where processing relies on it, and complain to your local data-protection authority.

Email main@pocketloom.games with your request and the game name. We may ask for information reasonably needed to verify and handle it. Because there are no player accounts and analytics uses an installation identifier, an email address alone may not let us locate your analytics records. We will explain any identification or deletion limitations; some aggregate statistics may not be attributable to you. Do not send passwords or identity documents unless specifically needed and requested through an appropriate process.

9. Children’s privacy

The game does not ask players to provide their age. If you are a parent or guardian and believe a child has provided personal information that should not have been collected, contact us. We will review the request and take appropriate steps under applicable law, including deletion where required and where we can identify the information.

10. Security and international processing

We use reasonable safeguards appropriate to the information we handle. No method of storage or transmission is completely secure. Google and other service providers may process information in countries other than where you live, including countries with different data-protection laws. Applicable safeguards depend on the provider, service terms and legal requirements. Google describes its arrangements in its international data transfer information.

11. Updates to this policy

We may update this policy as the game, its services or legal requirements change. The effective date above identifies this version. Where required, we will provide additional notice or request consent before a material change takes effect.