GAME-SPECIFIC PRIVACY
Fruity Crates: Sort Puzzle
Privacy Policy
Source-audited information about data, services and your choices.
Reviewed 2 September 2026. This policy records verified project behavior. Owner-only release settings remain explicitly marked below; the app is not represented as a verified public release.
1. Scope and current status
This privacy policy describes Fruity Crates: Sort Puzzle, 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.
The development artwork may use the name Fruit Crate Sort. This page applies to the same project identified here as Fruity Crates: Sort Puzzle. Privacy contact: braaqofficial@gmail.com.
2. Data on your device
The local profile includes a player-selected name, avatar index, coins, progression, completed levels, play time and sound/music/vibration preferences. Game saves and reward state use Unity PlayerPrefs. The audited profile code does not by itself create an online account.
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 and UMP are integrated for adaptive banners, rewarded ads and interstitials. The inspected AdSystem prefab contains Google test ad identifiers. A test ad is still a request to a third-party service; it is not proof that no data is processed.
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
The mobile ad provider performs the UMP flow and checks CanRequestAds. An AdPrivacyOptionsButton script is present. The audience treatment is Unspecified in the reviewed prefab; a G-rated ad-content limit is not a declaration that the game is child-directed. Production audience and consent-message settings require owner verification.
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
A custom AnalyticsManager is present in the enabled MAINMENU scene. Collection requires explicit consent, which defaults to not granted. If enabled with consent, its local queue can include event names, timestamps, random session/user IDs, level, completed-level count, coin balance, play time and avatar index. Player-name inclusion is disabled in the inspected scene. The upload endpoint is empty, so this custom analytics uploader does not upload in that configuration. Code supports later HTTPS uploads; enabling an endpoint requires a policy update. Consent-revocation code clears the local queue and identifier.
6. Other integrations and permissions
NativeGallery is installed, and a cached merged Android manifest contains legacy read/write storage permissions. No NativeGallery call was identified in the application scripts reviewed; do not infer photo collection from installation alone. Paid coin packs are gated behind a verified-purchase-provider interface; no concrete production provider was identified. In-game coin spending and rewarded-ad packs are separate from real-money purchases.
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.
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:
- Confirm which exact release build and AdMob configuration will be distributed.
- Confirm the intended audience, UMP messages and player-accessible privacy options.
- Confirm custom analytics remains disabled without consent and without an upload endpoint; verify accessible consent/revocation controls before enabling collection.
- Review or remove unused NativeGallery/storage permissions in the final app.
- Confirm whether paid purchases will ship, plus provider retention, deletion handling and Play Data Safety declarations.
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.