Sour Roll Privacy Policy

Effective date: 20 October 2026

Last updated: 20 October 2026

HOL4B provides Sour Roll, a puzzle game intended for people aged 13 and older. It is not directed to children under 13. You can play the core puzzles offline without an account.

This policy describes version 0.7.2 and later. Older versions may still ask for an age range and use age-based service restrictions. In the latest version, we do not ask you to choose an age range or provide a date of birth. Store audience settings and advertising content ratings do not replace applicable privacy choices.

Your choices

Open the game menu and select Privacy to manage optional analytics and crash reports. Both start off. Analytics turns on only when Google’s User Messaging Platform (UMP) provides a confirmed, explicit grant for analytics storage. Permission to request ads alone does not enable Analytics. If the analytics consent signal is unavailable, not configured, not applicable, denied or still being checked, Analytics remains off. You can pause Analytics in Privacy even after granting consent.

Crash reports stay off unless you turn on Share crash reports in Privacy. Advertising or analytics consent does not turn on crash reporting. Turning either optional service off does not block the core puzzles.

Advertising is enabled as an app feature. Before requesting ads, the app checks Google’s UMP privacy status and displays a Google consent form when the SDK requires one. Where available or required, you can reopen Ad & analytics privacy choices in Privacy. Purchases are available separately; optional Analytics or crash-report permission is not required to buy or restore Remove ads.

Information stored on your device

The game stores your progress, puzzle state, settings, play history and privacy choices on your device. An older saved age-range preference may remain on the device. It does not require an account or ask for your name, email address, contacts, camera, microphone or precise location.

Resetting saved progress removes local game progress. It does not automatically remove records already held by a service provider. Removing the app may remove local data; Android backup and device settings can affect whether data is restored.

Optional analytics

When analytics consent is granted and Analytics is not paused, Google Analytics for Firebase helps us understand and improve puzzle play and service reliability. It can process an app-instance identifier, device and operating-system information, app version, gameplay events and service outcomes. Examples include tutorial completion, level starts, completions and restarts, errors, and advertising or purchase outcomes. Google may derive approximate location from network information.

Our custom analytics events do not include your selected age band, full game save, account email or purchase receipt. The game does not set an account user ID for Analytics. Analytics advertising-ID collection is disabled. The app’s own Analytics consent calls deny advertising storage, advertising user data and advertising personalization; Google SDKs also interpret applicable UMP consent signals. Disabling Analytics does not disable the separate advertising or purchase services, and does not mean that all identifiers or other service data are absent.

Pausing Analytics or withdrawing its consent stops future app analytics collection and clears the app's pending analytics queue and local analytics data. It cannot recall a transmission already initiated or automatically delete information already received by Google. The app's pending event queue is limited to 64 events and expires after 24 hours; events from before your opt-in are not uploaded later.

Our current Analytics retention settings are 2 months for event data and 14 months for user data. The user-data retention period resets when there is new activity. These controls apply to the data covered by Google's retention settings; standard aggregated reports can remain available on a different basis. See Google's retention explanation.

Optional crash reports

If you enable crash reports in Privacy, Firebase Crashlytics helps us diagnose errors. Technical reports can contain error traces and codes, app version, device and operating-system information, Crashlytics installation UUIDs and Firebase installation IDs. Reports can be stored on your device.

The app may initialize Firebase while optional Analytics collection and automatic crash-report uploads are disabled. Optional services being off does not mean that SDK initialization or the separate advertising, consent and purchase services make no network connections.

Automatic report uploads are disabled. The app requests an upload only for reports that pass its consent checks, including the relevant previous session and the current choice. Withdrawing crash-report permission causes unsent reports to be deleted; reports from ineligible sessions are also deleted. A transmission already initiated cannot be recalled.

Google states that Crashlytics retains crash traces and associated identifiers for 90 days before beginning removal from its live and backup systems. This is not a promise that every copy is deleted at exactly 90 days. See Firebase's privacy information.

Advertising privacy

The app uses Google AdMob and limits ad content to Google’s G (general audience) rating. It does not ask for an age range and does not mark an age-unconfirmed player as a verified adult. With no older age preference available, the app uses unspecified age treatment and the applicable regional privacy choices; it does not block ad personalization for every user. Older saved teen preferences receive restricted, non-personalized requests, and a saved Under 13 preference blocks these services.

UMP checks and, when required, presents the applicable Google privacy message. The app requests ads only when UMP permits requests. Refusing personalized advertising does not automatically mean that all ads disappear: non-personalized or limited ads may be available depending on the choices, region and SDK result. If ad requests are not permitted, the app does not request them. You can keep playing puzzles when consent is refused or a consent request fails. Buying Remove ads stops automatic ads between levels.

Google AdMob and its advertising partners may process IP and network information, device or app identifiers, ad interactions and diagnostics to deliver and measure ads, prevent fraud and maintain security. The app removes advertising-ID permissions, but that does not eliminate other identifiers or data processing. The consent interface identifies applicable advertising choices and providers. More information is available in Google's advertising information and Mobile Ads data disclosures.

Purchases and ownership checks

Google Play handles checkout and payment details. RevenueCat helps process and validate purchases, restore purchases and maintain the purchase that removes automatic ads between levels.

For eligible players, RevenueCat can process an SDK-generated app-user identifier, product and ownership information, purchase tokens or receipts, and relevant app, device and network information. Purchase-service availability and ownership checks can connect to the service even when you do not complete a purchase. The game does not provide RevenueCat with your email address, exact age or a custom account identifier, and does not send the RevenueCat app-user identifier to optional gameplay Analytics. Additional SDK device-identifier collection and SDK diagnostics are disabled; this does not eliminate the information needed to operate the purchase service.

Purchase and transaction records may be retained for ownership checks, restoration, fraud prevention, accounting and legal obligations under the providers' applicable rules. See RevenueCat's Privacy Policy and Google's Privacy Policy.

Providers and international processing

Google and RevenueCat may process information outside your country. Their policies describe their processing and safeguards. This policy page does not load advertising or game Analytics SDKs. Our content-delivery provider may add a Cloudflare browser measurement script for website usage and performance. The servers and content-delivery services that deliver this page may process basic connection information, such as IP addresses and request details, to provide the page, maintain security and prevent abuse. See Cloudflare's Privacy Policy.

Questions and privacy requests

Contact HOL4B at support@hol4b.com with questions or a request to access or delete information. If you email us, we use your email address and message to respond. We may need enough information to locate the relevant service record, especially because the game has no account. Do not send passwords or full payment-card details.

Requests are handled subject to applicable law and necessary retention. Local reset, switching off sharing and a provider-data deletion request have different effects; switching off sharing does not itself erase previously received provider records.

Changes to this policy

We may update this policy when the service or its data practices change. We will update the date shown above and provide any additional notice required by applicable law.