Your play. Your choices.

Windows PC privacy notice

Effective November 13, 2026. Applies to Blocks Stack the Beat for Windows PC, version 1.0.2.0.

Justice James Peace, publishing as VIRAL⁴, provides this Windows version. The iOS advertising and Apple purchase disclosures elsewhere on this page do not describe the Windows version.

Local game information: The game stores progress, scores, saved game state and preferences on your device. It does not require a publisher account or upload these saved files to a publisher server. Music and sound effects are included and played locally. The reviewed Windows version contains no advertising SDK, advertising or developer-operated analytics service.

Microsoft Store purchases and licensing: The first 10 campaign levels are available as a trial without a time limit. A one-time Microsoft Store purchase unlocks the full game. Microsoft handles account sign-in, payment and Store licensing under its own privacy terms. The game uses Windows Store services to check license status and request purchase or restoration. Its licensing helper returns entitlement status, trial status, the displayed price and operation status to the game. It does not return Microsoft account identifiers or payment-card details to the game.

Microsoft may independently process account, transaction, device and service information. Microsoft’s privacy statement: https://privacy.microsoft.com/privacystatement

Support and website visits: Opening the privacy page creates a website request covered by https://viral4official.com/privacy. If you email viral4official@gmail.com, the publisher and email service receive what you send. Don’t send passwords, verification codes, payment-card details or unnecessary personal information.

Your choices: You can stop using or uninstall the game. Local progress and preferences may remain in the user-data folder or backups after uninstalling. Removing local save files can permanently erase progress. Removing the game or local files does not erase Microsoft’s purchase or account records. For Windows privacy questions, contact viral4official@gmail.com with the subject “Blocks Windows privacy request.” For Microsoft account, payment or purchase records, use Microsoft’s privacy and account controls.

Security and changes: Local game files rely on your Windows account and device protections. Keep Windows and the game updated. No storage or transmission method is completely secure. We will update this notice if the Windows game’s information practices change.

Who is responsible and what this policy covers

Justice James Peace, publishing as VIRAL⁴, is responsible for Blocks: Stack the Beat. For privacy questions or requests, email viral4official@gmail.com with the subject Blocks privacy request.

This notice describes build 104.3 of the iOS game: local puzzle gameplay, Google Mobile Ads (AdMob) 12.14.0, Google User Messaging Platform (UMP) 3.1.0, and Apple's StoreKit purchase and restore services. It replaces the build-102 policy for this release. The game's Settings contains a Privacy Policy link to this page. Other VIRAL⁴ products have separate policies. Website visits and website contact forms are covered by the website privacy policy. See Stack the Beat support for practical help.

The main privacy boundaries

• No publisher game account or sign-in is required. Saved boards, scores, progress and settings are stored on your device, without a publisher-operated cloud-save or leaderboard upload service.
• Advertising and privacy-consent services connect to Google. Purchases and restores connect to Apple. Local gameplay storage does not mean that the app or its SDKs collect no data.
• Build 104.3 applies Google's child-directed advertising treatment to every user, requests a maximum ad content rating of G, disables publisher ad personalization and publisher first-party ID, and does not request Apple's App Tracking Transparency permission.
• Google SDK data categories and their disclosure purposes remain relevant even with these restrictions. The app is configured not to use data for tracking as Apple defines it; this does not mean no identifiers, network information or diagnostic data can be processed.
• You can decline optional rewarded ads. The Remove Ads purchase disables automatic interstitial ads, but does not remove the Google SDKs or stop all Google service requests.

Information stored on your device

The game saves local files to resume play, keep preferences, apply purchase benefits and control ad opportunities. These can include:

• Board and tray pieces, random game state, moves, scores and best scores, combinations, cleared lines and musical rewards.
• Level completion, unlocked and selected levels, the last-used mode, and Endless progress.
• Music playback position, music and effects volume, mute, vibration and reduced-motion preferences.
• Attempt counters, ad timing and reward state, and the local state needed to apply the Remove Ads entitlement.
• Save-format versions, integrity checks, temporary files, recovery copies and local runtime logs.

These saved game files are not uploaded to a publisher server. Music and sound effects are included with the game and played locally, without sending a listening history to a music-streaming service. Google SDKs can separately process app or ad interactions and diagnostics as described below. Device backups may copy local app files under your operating-system settings; this is not game-operated cloud synchronization.

Google SDK data: categories, linkage and purposes

Google's advertising and consent SDKs receive information automatically through SDK operation, network requests and interactions with their ads or privacy forms. Network requests expose an IP address; approximate location can be inferred from it. Build 104.3 does not request GPS location permission for gameplay.

The following seven categories are the combined disclosure baseline from the privacy manifests packaged with Google Mobile Ads 12.14.0 and UMP 3.1.0 in build 104.3. A manifest describes an SDK's declared practices and capabilities, not a measurement proving that every field is sent on every request. The child-directed configuration in section 5 restricts how these services operate.

Linked means a category may be associated with an identity, device or other identifying information; it does not require a name or game account and is different from tracking. Where the SDKs differ, the list preserves the more inclusive disclosure. Not linked below describes the archived SDK declaration, not a promise that every network request is anonymous.

Coarse Location

Linked. Approximate location, such as an area inferred from an IP address. Declared purposes: Third-Party Advertising, Developer's Advertising or Marketing, Analytics, and App Functionality. Google Mobile Ads declares the first three purposes as linked; UMP declares App Functionality as not linked.

Device ID

Linked. Device-, app- or developer-scoped identifiers that the SDK can process. Declared purposes: Third-Party Advertising, Developer's Advertising or Marketing, and Analytics. The Google Mobile Ads manifest also marks this category as a general tracking capability. In this build, ATT requests and publisher first-party ID are disabled, and Google's child-directed treatment is applied to prevent IDFA transmission. See section 6 for the configuration-specific tracking assessment.

Advertising Data

Linked. Information about ads shown or interacted with, such as impressions, views and ad events. Declared purposes: Third-Party Advertising, Developer's Advertising or Marketing, and Analytics.

Product Interaction

Linked. App and advertising interactions, such as launch or interaction events and video views; UMP also processes interactions needed for its privacy functionality. Declared purposes: Third-Party Advertising, Developer's Advertising or Marketing, Analytics, and App Functionality. Google Mobile Ads declares the first three as linked; UMP declares App Functionality as not linked. This is separate from uploading detailed saved boards or game-progress files.

Crash Data

Not linked. Crash information used to identify and diagnose failures. Declared purpose: Analytics.

Performance Data

Not linked. Technical performance information relating to the SDK and service operation. Declared purposes: Third-Party Advertising, Developer's Advertising or Marketing, Analytics, and App Functionality. UMP supplies the App Functionality purpose; Google Mobile Ads supplies the other three.

Other Diagnostic Data

Not linked. Other technical diagnostic information. Declared purposes: Third-Party Advertising, Developer's Advertising or Marketing, and Analytics.

Advertising purposes cover serving and evaluating ads; Analytics covers measurement and service improvement; App Functionality covers operation of privacy tools and related service functions. The Developer's Advertising or Marketing purpose is retained from Google's SDK manifest. It does not mean that the game asks for an email address or sends a marketing mailing list to Google. The reviewed app does not supply a name, email address or publisher user ID to AdMob.

These disclosures are based on the versions included in this build. Google's online documentation can describe newer versions. See Google's SDK disclosure guidance and Apple's App Privacy definitions.

Child-directed treatment for every user

Children and younger players may use the game. Instead of collecting a date of birth or asking users to select an adult advertising mode, build 104.3 applies the same restrictive ad settings to everyone:

• Child-directed ad requests: Google Mobile Ads' tag for child-directed treatment (TFCD) is enabled globally before the advertising SDK initializes.
• Ad content rating: the maximum requested Google ad content rating is G (general audience). This is an ad-service filter, not the game's App Store age rating or a guarantee about every delivered creative.
• Personalization and identifiers: publisher ad personalization and publisher first-party ID are disabled. The app does not show an ATT permission prompt.
• Under-age privacy messages: UMP's under-age-of-consent flag is set to true at startup for all users. Google documents that UMP does not request consent when this flag is true. This is separate from Google's ad-request TFUA flag, which remains unspecified so it is not combined with TFCD.

Google documents child treatment as restricting interest-based and remarketing ads and preventing IDFA transmission, with additional restrictions on third-party ad-serving and measurement. These protections do not eliminate the SDK data categories in section 4. UMP's under-age setting is not a parental-consent verification system. The game does not collect a birth date to identify individual children.

These are technical settings in this release, not a certification of legal compliance or evidence that the app is enrolled in Apple's Kids Category. Parents or guardians can contact us about a child's information, request review or deletion of support information they or the child supplied, and raise concerns about ads. Please do not send a child's birth date, school, location or other unnecessary personal details. See Google's targeting documentation and Google's child-treatment explanation.

How tracking is treated in this build

Apple distinguishes data collection and linkage from tracking across other companies' apps, websites or offline properties for advertising or advertising measurement, or sharing with a data broker. For build 104.3, the app is configured not to use data for that tracking: TFCD applies to all ad requests, ATT requests and publisher first-party ID are disabled, publisher personalization is disabled, and the reviewed integration does not send publisher-supplied user identifiers.

The Google Mobile Ads privacy manifest still declares Device ID tracking as a general SDK capability. That declaration is preserved in our assessment rather than hidden or treated as proof of the configured behavior. Our build-specific no-tracking assessment rests on the implemented restrictions and Google's documented child-treatment policies. It is not a packet-capture result, a guarantee of zero data processing, or an unconditional guarantee about future SDKs or provider changes.

Turning off personalization alone is not the basis for this assessment. Child-directed restrictions are also applied. A later change to SDKs, advertising configuration, identifiers or data recipients requires a new assessment.

Consent checks and choices

After the startup presentation, the game asks UMP to update privacy information with under-age treatment enabled. It uses UMP's current permission-to-request-ads result, waits while a privacy form is pending, and checks purchase entitlements before proceeding with ad initialization. Request settings must be applied successfully before initialization. An error does not automatically grant permission: UMP's current result, which can reflect previously available information, still governs ad requests.

When UMP reports that privacy options are required, the game displays a Privacy choices control in its menu or pause options. Use that control to open the available form and change or withdraw choices it offers. Availability and form contents depend on Google's service, region and under-age treatment. Because this build sets UMP under-age treatment to true for every user, UMP does not request consent under that setting. The presence of UMP must not be read as evidence that adult consent or verified parental consent has been collected. There is no in-game option to switch to personalized adult advertising. See Google's UMP under-age guidance.

Changes are applied to subsequent ad checks; loaded ads are cleared when the privacy-options form closes. Changing a choice does not erase information already held by a provider. If the control is unavailable or you want to make a data request, use the contact in section 13 and the provider controls in section 12. You can decline optional rewarded ads and continue ordinary puzzle gameplay without choosing a reward. This build does not provide a single switch that deletes all third-party records or disables every SDK connection.

Apple purchases, restoration and Remove Ads

Remove Ads is an optional, one-time Apple in-app purchase, not a subscription. The App Store shows the price for your storefront before confirmation. It disables automatic interstitial ads; optional rewarded ads can still be offered. Apple's purchase and restore services verify the entitlement used to apply that benefit.

Apple handles the Apple Account, payment method and purchase records. The app receives the purchase status and verified entitlement information needed to apply or restore the benefit; it does not receive full payment-card details. The reviewed implementation does not upload receipts or transaction records to a publisher server or forward purchase history to AdMob. Local entitlement state and Apple's independently held records are different from a publisher purchase-history database.

Buying Remove Ads does not uninstall the Google SDKs or erase information previously processed. The installed implementation can still initialize the advertising service and request or preload optional rewarded ads when permitted, even before you choose to watch one. UMP privacy requests can also continue. Therefore, Remove Ads is not a promise that all advertising-related network processing stops.

Use the game's restore control for an existing purchase and player support for help. Apple handles payment and refund requests under its own policies. See App Store & Privacy and Apple's refund guidance.

Who receives information and how it is protected

• Google Mobile Ads and UMP: receive SDK information to provide advertising, privacy messaging, measurement, diagnostics and related service functions, subject to the restrictions described above. This is separate from local saved game files.
• Apple: provides downloads, StoreKit purchases and restoration, and may separately process platform, TestFlight or diagnostic information under its policies and device settings.
• Support email: Justice James Peace and the Google Gmail service used for the support mailbox receive messages and attachments you send. We do not automatically attach game saves to email.
• Website hosting: opening this policy or another website page creates web requests covered by the website privacy policy. Opening an ad destination can disclose request information to that separate site.

We require third parties with whom we share app user data to provide the same or equal protection described in this policy and required by Apple's App Review Guidelines. Provider terms, documented restrictions and the configured service controls are part of how that requirement is applied. This requirement does not represent a technical audit of every provider operation or an absolute security guarantee. Where a provider independently controls information, its policy and applicable rights process also apply; those notices do not waive our obligations.

Only Google Mobile Ads and UMP are included as advertising/consent SDKs in this reviewed build. AppLovin and Unity Ads SDKs or adapters are not included. Earlier notices mentioned possible future mediation partners; those plans are not a description of collection by the current build. Any future integration needs a separate audience, data, privacy and policy review before it is enabled.

We do not operate a game-account data brokerage or send saved boards, purchase receipts or support emails to advertising services through this implementation. We may disclose support correspondence when required by law or to protect legal rights. Third-party advertisements and external destinations do not become publisher-operated services when opened.

Information you choose to send us

If you email support, we receive your email address, subject, message, attachments and normal email delivery information. We use that information to respond, troubleshoot, manage privacy requests, prevent misuse and meet applicable legal obligations. Support messages are not used by us for targeted advertising.

Send only what is needed, such as the app build, device model, operating-system version and a description of the issue. Redact screenshots. Do not send passwords, verification codes, payment-card details, advertising identifiers, full purchase receipts or unnecessary information about a child. If an attachment is needed later, we can explain why.

How long information stays

• Local game files: remain until the app overwrites them or you remove its data. Normal play does not erase all progress, settings, old recovery copies or logs. There is no automatic expiry schedule or dedicated delete-all-data button in this build.
• Support correspondence: we retain it while needed to handle the request and related follow-up, resolve disputes, protect against misuse or meet legal recordkeeping obligations. There is no fixed automatic mailbox-deletion period. You can request deletion; information still needed for a legal obligation or dispute may be retained for that purpose.
• Google SDK and consent information: retention depends on Google's applicable service policies, the information involved, privacy controls and legal requirements. We do not set or promise a single retention period for independently held provider records.
• Apple purchase and platform records: are retained under Apple's policies and applicable legal obligations. Deleting the game does not cancel a completed purchase or erase Apple's records.
• Backups: device and email providers may retain separate backup copies under their own settings and retention processes. Removing an active copy does not necessarily erase every backup immediately.

We cannot remotely retrieve or erase local saves or independently controlled provider records. Provider information is available through the links below; no fixed deletion deadline or irreversible anonymization is promised where it has not been established.

Remove local data and contact the right provider

1. Local iOS data: use iOS Settings, General, iPhone Storage (or iPad Storage), select the game, then Delete App. Deleting the app removes its local app container and can permanently lose progress and preferences. Offload App can preserve data and is not the same as deletion.
2. Backups: review iCloud or computer backup settings separately. A retained backup or later restoration can bring back previously saved app files. The game does not operate an iCloud synchronization account.
3. Support messages: email the privacy contact in section 13 to request access, correction or deletion of information you sent us. Deleting the app does not delete email copies.
4. Google-held information: review the Google Privacy Policy, information from partner apps and the controls and contact routes those notices provide. Google Account controls may not cover every record from use without a signed-in account.
5. Apple-held information: review Apple's privacy controls and Apple's Privacy Policy. Payment, refund and purchase-record requests are handled by Apple.

To stop future requests from the installed app, stop using it or delete it. This does not undo completed processing or delete provider records. The app does not ask for camera, microphone, Photos or Contacts access for puzzle gameplay. Network-derived coarse location and SDK information are addressed in section 4, even though these device permissions are not requested.

Your privacy rights and how to reach us

Email viral4official@gmail.com, addressed to Justice James Peace, with the subject Blocks privacy request. Explain whether you want access, correction, deletion, a restriction or an answer about processing. Include only enough information to identify the relevant correspondence or issue. If verification is needed, we will seek information proportionate to the request, not passwords or full payment details.

Depending on where you live and the processing involved, you may have rights to access or receive a copy, correct or delete information, restrict or object to processing, withdraw consent where consent applies, or complain to a privacy regulator. These rights can have legal exceptions. We will explain applicable limits and whether another provider controls the requested records. A parent or guardian may contact us about information they or their child supplied. Withdrawing consent does not retroactively erase earlier processing.

There is no publisher-created game account to delete in this build. Local data removal, Apple Account information, Google records and email deletion are separate processes.

Security and processing locations

Local files rely on iOS application isolation and your device's lock, encryption and backup settings. The game does not add separate file-level encryption to its save files. Keep your device and operating system updated and avoid sending unnecessary personal information through support.

Google, Apple and email or hosting services may process information on infrastructure in more than one country. Their notices explain their international processing and applicable safeguards. We do not claim that every provider record stays in your country or that any method of storage or transmission is completely secure.

Updates and related information

This version replaces outdated build-102 references with build 104.3, describes the seven SDK categories and their purposes and linkage, explains all-user child-directed and UMP under-age settings, distinguishes local saves and Apple purchases from SDK collection, and expands retention, deletion and provider details.

If practices change, we will update this policy and its effective date and provide any disclosures or choices required for the change. This notice explains the reviewed release; it is not a promise of App Store approval or a legal-compliance certification. Current store disclosures and the actual app behavior must remain consistent with it.

For help, visit Stack the Beat support or email viral4official@gmail.com.