Critter Escape
Privacy Policy

1. Scope and current status

This privacy policy describes Critter Escape, developed by Braaq Game Studio, based on the Unity project reviewed on 2 September 2026. The game is listed on this website as in development. It covers the audited development configuration, not a verified future Google Play release.

Privacy contact: braaqofficial@gmail.com.

2. Data on your device

Current and unlocked levels, completed-level counts, best stars, tutorial and rating-prompt state, and music/sound/haptics preferences are saved locally in Unity PlayerPrefs, with a backup save.

This local data supports progression, preferences and the game experience. Local storage is not the same as sending the data to Braaq. Clearing app storage can erase these records; operating-system backup and restore behavior depends on the device and final build.

3. Advertising and providers

Google Mobile Ads code provides banner, interstitial and rewarded ads. The reviewed AdMob configuration uses test ad identifiers; production identifiers are not enabled.

Google documents that its Mobile Ads SDK processes IP addresses (which can indicate approximate location), app/ad interactions, diagnostics and device/account identifiers, including advertising and app-set IDs. Its stated purposes include advertising, measurement and fraud prevention. The exact processing depends on SDK configuration, device settings and available consent choices. See the Google Mobile Ads data disclosure and Google Privacy Policy.

4. Consent and privacy controls

Google UMP and privacy-options code are installed. However, the current GameConfig consent flag is false, so the test configuration can initialize ads without that UMP flow. A consent prompt is not promised for the current build. Production consent and privacy messaging require owner verification before release.

Where a game exposes a working privacy-options control, use it to revisit available ad choices. Android’s advertising controls may also allow you to reset or delete the advertising ID. These controls do not necessarily remove all SDK processing or historical provider records.

5. Analytics and diagnostics

No separate application analytics, Firebase or crash-reporting integration was identified in the reviewed scripts and package manifest. Unity Analytics, crash reporting and performance reporting are disabled in the reviewed service settings. Google Mobile Ads has its own diagnostic processing.

6. Other integrations and permissions

The reviewed save system is device-local. A player login, cloud-save service or verified billing integration was not identified in the audited application code.

The inspected Android build manifests include internet/network-state and vibration permissions, plus ad-related permissions added through Google dependencies. Cached build manifests are supporting evidence, not proof of the exact permissions in the next release. Internet access supports ads and enabled online services; vibration supports haptic feedback.

7. Sharing and security

When enabled, Google advertising services process information under their own terms and privacy policies. Braaq receives information you choose to send by email. We do not infer a separate cloud profile or database merely from a profile screen. Any future third-party service must be disclosed before it is enabled.

Google’s SDK disclosure states that its transmitted user data uses TLS. This does not guarantee the security of every local file, message or future integration. Avoid including sensitive information in support attachments.

8. Retention, requests and deletion

Local game information generally remains on the device until reset or removed. Clearing application storage can permanently remove progression and does not automatically erase information already processed by Google or another provider. We cannot remotely erase device-only saves through this website.

For access, correction or deletion requests, use Data Requests & Choices or braaqofficial@gmail.com. Identify the game and the type of data involved. We may need limited information to locate a request, but not your password or payment credentials. Provider retention, support-email retention and applicable requirements still need owner confirmation; no unsupported deletion deadline is promised.

9. Children and international processing

The intended audience, age settings and any child-directed treatment are Owner Verification Required before release. Colorful artwork is not evidence of a particular legal age category. If you are a parent or guardian with a concern, contact braaqofficial@gmail.com without including unnecessary information about a child.

Third-party services may process information in countries other than yours, as described in their policies. Exact regional settings and required safeguards must be checked for the release.

10. Owner Verification Required

These items are open release checks, not claims about unverified practices:

• Verify and enable the appropriate production consent configuration and AdMob messages before real-ad release.
• Verify the final ad formats, identifiers and privacy-options UI on an Android device.
• Confirm intended age groups, children’s treatment, retention periods and provider settings.
• Align the final build, permissions, app policy link and Play Data Safety answers.

The website policy, in-app links and Google Play Data Safety answers must be reviewed together against the final distributed build. This source audit is not a guarantee of Google Play approval.

11. Updates and contact

Last updated: 2 September 2026. This page will be revised as release behavior is verified or changes. Contact Braaq Game Studio at braaqofficial@gmail.com.

Game support · Privacy Center · About the game