BlockZip Privacy Notice
Effective / updated: 2026-11-02
GAMES-S (Hong Kong) provides BlockZip: Color Escape. This notice covers the iOS game and explains information processing in local game storage, our own analytics service, Google advertising components, and optional game notifications. The privacy notice for the GAMES-S website does not replace this game-specific notice.
Privacy and support contact: games.aistudio@gmail.com. The game does not require account registration or sign-in, does not provide server-based cloud saves, and currently has no in-app purchases. You do not need to enter a name, phone number, or email address to play. If you contact support, your email address, message, and any attachments will be used to respond to and handle the request.
- 1. Game data on your device
- 2. Information received by our analytics service
- 3. Google advertising and privacy components
- 4. Purposes and recipients
- 5. Advertising and analytics choices
- 6. Retention and backups
- 7. Removing local data and making requests
- 8. Transmission and processing regions
- 9. General audience and updates
- 10. Optional game notifications
1. Game data on your device
The app stores level progress, results, the current level, language and sound settings, tool balances and usage counts, advertising frequency records, cached configuration, and records of rewards awaiting delivery on your device. These support progress, game functions, reward delivery, and the prevention of duplicate rewards.
Your device also stores a random analytics installation identifier, session state, and events not yet successfully reported. Queued events may be sent when a connection becomes available; acknowledged events are removed from the outgoing queue. These local records are not cloud saves. The effects of iOS backup, restore, and app removal also depend on the system and your settings.
2. Information received by our analytics service
The game sends the information below to the GAMES-S analytics service. Random identifiers do not directly contain a name entered by a player, but can link events from the same installation, session, or attempt. They are not equivalent to aggregate data that cannot be linked in this way.
The analytics event database has no event fields for a raw IP address or a full browser User-Agent. Network connections still use IP information. Rate limiting temporarily uses the connection IP, and fault logs may contain connection or IP information.
- Randomly generated identifiers for installations, sessions, events, attempts, and ad operations.
- Event time, the iOS platform, game version, and language information.
- Events for game loading; starting, pausing, resuming, completing, failing, retrying, or leaving levels; moves, remaining blocks, stars, elapsed gameplay time, hint results, and tool use.
- Ad requests, loading, presentation, impressions, clicks, dismissal, failures, and earned rewards; ad placements, configuration versions, errors, and SDK-reported estimated ad revenue values, currencies, and precision information.
3. Google advertising and privacy components
The game integrates Google Mobile Ads (AdMob) to display ads and Google User Messaging Platform (UMP) to handle applicable advertising privacy choices. These components communicate directly with Google services.
Google's disclosure for its iOS advertising SDK describes processing that may include IP addresses and approximate location estimated from them, device or app-scoped identifiers, ad presentation and interactions, and crash, performance, and other diagnostic information. Processing depends on the features, advertising settings, and applicable choices. See Google's advertising SDK data disclosure.
The game currently does not request precise location permission or initiate an Apple App Tracking Transparency (ATT) authorization request. This does not mean that the game or advertising components process no device identifiers, network information, or other data. Google's app- or developer-scoped identifier mechanisms may still apply. See Google's information about partner apps and the Google Privacy Policy.
4. Purposes and recipients
Local data supports game functions, progress, settings, rewards, and frequency management. Our analytics helps us understand level and feature usage, evaluate difficulty and performance, investigate errors, and reconcile ad presentation, rewards, and estimated revenue. Advertising service information supports ad delivery, measurement, diagnostics, and protection against anomalies or abuse.
Our analytics service and authorized administrators can process game analytics records. Authenticated administrators can view and export data, so administrative export copies may exist. Google processes information received by its advertising and privacy components under its service rules, applicable settings, and user choices, including processing involving its advertising services and partners.
5. Advertising and analytics choices
The release version integrates UMP to update status at launch, attempt to display forms when required, and use Google's returned status to determine whether ads may be requested. When Google requires a privacy options entry point, Settings displays “Ad privacy options” so you can revisit or adjust choices. Available messages and entry points depend on region, backend configuration, and Google's returned status. Declining personalized advertising does not necessarily stop all ads or measurement.
Regional messages are currently still being configured and tested for launch. This does not indicate that a complete consent flow is enabled in every region. See Google's UMP documentation for information about the component.
The current version has no separate switch to disable GAMES-S game analytics. Google advertising privacy options do not automatically disable that analytics. You may contact support to ask questions or make data requests. Stopping use and removing the app stops that installation from producing new game events in subsequent runs, but does not automatically delete previously reported records.
6. Retention and backups
Raw gameplay and advertising events in our online analytics database have a 365-day retention period measured from the event time, with a daily scheduled cleanup to remove expired records. This period applies to online raw analytics; it does not mean that every log, backup, or export copy is deleted at the same time.
Routine scheduled database backups rotate to retain the latest seven copies. This is not a promise that every copy is kept for no more than seven days. Manual snapshots and administrator exports may be retained separately. Before a backup is restored to resume service, analytics data past its retention period must first be removed so that expired records are not reintroduced.
Local game data generally remains with the app until its data is cleared or the app is removed. System backups may retain or restore some information. Operational fault logs, system logs, configuration administration audit records, support emails, manual snapshots, and administrative export copies currently have no single fixed automatic deletion period.
Information held by Google is subject to Google's own retention rules and relevant choices. Our 365-day online analytics period and backup rotation do not determine Google's retention periods. See the Google Privacy Policy.
7. Removing local data and making requests
Uninstalling the game does not send an automatic deletion request to our analytics service or to Google, and does not guarantee simultaneous deletion of server records, backups, or export copies.
To ask about or request action on relevant data, contact games.aistudio@gmail.com and describe the request, approximate usage time, game version, and other useful context. We first need to establish whether records can be reliably located and what action is possible. The service primarily links records by a random installation identifier. There is no player account or in-app one-tap server deletion feature. A name or email address alone may not locate historical analytics records that did not contain those details. If records cannot be reliably linked, the scope of the request needs further clarification.
Choices or requests concerning information held by Google also require Google's settings and request channels. We do not promise to delete all data held by Google on your behalf, or promise automatic deletion or a uniform completion deadline.
8. Transmission and processing regions
The app communicates with our analytics API over HTTPS, and access to the analytics administration interface requires authentication. The operator's location in Hong Kong does not mean all information is stored or processed in Hong Kong.
Google may process information outside your country or region; see its Privacy Policy. This notice does not promise that no cross-border processing occurs, or treat the company's location as the location of every server, backup, or administrative copy.
9. General audience and updates
The game is intended for a general audience and is not specifically directed to children. It currently has no player accounts or age-verification flow; this does not mean every player has been verified as an adult. A parent or guardian with questions about a child's use of the game or related information processing may contact support.
This notice needs to be revised when features, advertising services, or processing practices change. The published page will identify the effective version, date, and scope.
10. Optional game notifications
You can enable game update and event reminders under “Notifications” in the game settings. On the first launch, if you have not yet made a notification choice, the game requests system notification permission once. You can allow or decline. Declining or disabling notifications does not limit normal gameplay. You can select “Manage” in the game settings at any time to adjust or disable notifications in iOS settings. Notification choices are managed separately from advertising privacy choices.
When iOS allows notifications, we register the current game push token with Apple Push Notification service (APNs) and send it to our push server over HTTPS. Push registration data includes a separately generated random installation identifier, a random credential used to verify that installation, notification authorization status, APNs environment, the app bundle identifier, app version, preferred system language, registration and update times, and the request identifiers and revision numbers needed to process updates. The random push installation identifier is generated separately from player identifiers used for game and advertising analytics. Enabling notifications does not require a name, email address or account.
The game keeps the current APNs token only in device memory and does not write it to persistent device storage. The random installation credential is stored in the device Keychain; the server stores only its hash. Our server stores the current APNs token to send notifications and supplies the token and notification content to Apple when requesting delivery. Push tokens and installation credentials do not enter our game or advertising event analytics pipeline and are not displayed in the management interface or written to application logs.
To manage and evaluate notifications, we retain campaign content and identifiers, sending status, times and error codes, and installation-specific receipts. We record “received” when the foreground game actually receives the notification callback and “opened” when you tap the notification. Apple's acceptance of a send request does not establish delivery to the device or that you have read the notification. Background notifications do not always provide a received receipt to the game. The foreground game suppresses notification banners and sounds. Tapping a notification returns to the existing game and does not open an arbitrary webpage from a notification link. The device holds at most 20 pending receipts and removes records older than seven days when loading the queue; these receipts contain neither push tokens nor installation credentials.
After you disable notifications, iOS stops presenting notifications under that authorization. When the game next reads the disabled status and can connect to our server, it disables the registration and clears the server's token for that registration. A valid token-invalidation response from Apple also disables the corresponding old token. Disabling a registration does not immediately erase existing campaigns or historical receipts. Online push records are periodically cleaned under a 365-day retention rule: installation registrations are measured from their last update, operations from their creation, and completed campaigns and their sending and receipt records from the campaign's creation. Database backups rotate through the seven most recent copies, so online deletion and backup cleanup may occur at different times. Use the contact and rights-request methods already provided in this policy for deletion requests and other privacy rights.