Menu

Sudoku — Android 1.2.0

Sudoku — Android 1.2.0 privacy notice Effective date: 3 November 2026 (UTC) This notice covers Sudoku (com.gameshush.sudoku) 1.2.0, including internal testing. It does not announce availability on Google Play. Older-version coverage remains in the historical notice below. The website and other apps retain their own notices. Sudoku privacy notice Shree Krishna Enterprise provides Sudoku. Contact: shreekrishnaenterprise0721@gmail.com. Your puzzles and progress Sudoku stores puzzles, entries, notes, undo history, elapsed time, hint counts, results, archives, settings and a local profile identifier on your device. Normal play does not require advertisements or Google sign-in. Clearing app storage or uninstalling removes local saves and unspent local hint credits. Android automatic app backup is disabled. Age and advertising choices The game is intended for ages 13 and above. The neutral choices are Under 13, 13–15, 16–17 and 18 or older. Your selected age range is stored locally, rather than your date of birth. Update saves a changed selection; Cancel preserves your previous choice. You can correct your selection through Age and ad privacy. Under 13 and unknown age do not receive ad requests. Rewarded hints are unavailable for Under 13; normal play and one free hint per saved puzzle remain available. When ads are available, Sudoku uses Google's Mobile Ads SDK and User Messaging Platform for a labelled banner and optional rewarded hints. One SDK-confirmed earned reward provides one additional hint. Ad availability varies. Declining or closing a video does not prevent normal play. Applicable Google privacy options are accessible through Age and ad privacy. Refusing personalized advertising does not necessarily stop all ad processing. Google documents collection and sharing of IP addresses (which may indicate approximate location), product interactions, diagnostic information and device/account identifiers for advertising, analytics and fraud prevention, subject to configured restrictions. Age-related request protections and applicable consent choices are applied before ad requests. Sudoku does not attach saved puzzles, its local profile identifier or a Play Games identifier to ad requests. Transfers use encryption in transit. The app does not request Android location permission or supply device GPS coordinates. IP-derived approximate location is separate from GPS. Where ads are available, ad partners listed in Google's privacy message may process information under the applicable choices and restrictions; the list does not mean every partner receives information from every request. No third-party mediation SDK is bundled. Earned hints Earned hint credits are saved locally for the originating puzzle and profile. Receipt markers prevent reuse. Credits are withheld from redemption while Under 13 is selected; correcting age does not restore the free-hint allowance. Uninstalling or clearing app storage removes unspent credits. Google-held information and deletion Play Games is optional. Connect allows Google sign-in, achievements and cloud backup/restore. The SDK initializes after explicit Connect and a known age choice. Google may process gamer identity and diagnostics/analytics. Age changes revoke app operations but cannot undo previously transmitted data or uninitialize Google SDKs. Backups transfer puzzle progress, solutions, notes, moves, timings, archives, local/backup-player identifiers, revisions and applied reward markers to Google Saved Games. Preferences stay local. Achievements may be submitted after a successful backup. Eligible unassisted completion times may also be submitted after a successful backup, following Play Games profile and leaderboard visibility settings. Previously stored Play Games data is not erased by removing local app data. Use Google's Play Games game-data deletion and Google account controls for applicable Google-held records. Google controls retention and deletion of its service records. Sudoku has no in-app command deleting every Google-held record. Support correspondence is handled through Gmail to address requests and retained as needed, subject to legal obligations. Google privacy policy: https://policies.google.com/privacy Sudoku data deletion guidance: https://gameshush.com/privacy#sudoku-data-deletion

Android apps: Sudoku and Merge Numbers

Privacy Policy — Sudoku and Merge Numbers Updated: 23 October 2026 Shree Krishna Enterprise provides Sudoku (com.gameshush.sudoku) and Merge Numbers (com.gameshush.mergenumbers). For privacy questions, contact shreekrishnaenterprise0721@gmail.com. Which version this covers The Play Games features below apply to Sudoku 1.1.0 with Play Games enabled, including its internal test release. Sudoku 1.0.0 and builds without Play Games keep gameplay on the device. Merge Numbers 1.0.1 remains local-only; the separate Merge Numbers 1.1.0 notice below covers its Play Games-enabled upgrade, including internal testing. Browser/PWA games and the separately packaged Sudoku demo (com.gameshush.sudoku.demo) do not currently use Play Games; their storage is separate and does not automatically transfer to the Play app. Sudoku data on your device Sudoku keeps puzzles and solutions, entered digits, pencil notes, undo history, elapsed time, hints, difficulty, results, archived sessions and completion records in app storage. A locally generated profile identifier identifies your progress independently of Google. Sound, haptics and reduced-motion preferences stay on your device; cloud payloads contain neutral defaults rather than your preference choices. The app keeps multiple session archives and recovery/conflict copies. Starting a new puzzle does not erase the entire archive. Storage limits, device settings or storage failures may affect retention and recovery. Google Play Games at startup The Play Games SDK initializes when the enabled Android app starts and can authenticate with your selected Play Games profile. Google processes gamer identity and automatically collects SDK analytics and diagnostics for service stability and improvement. Declining cloud backup does not disable SDK initialization or this processing. Local puzzles remain playable without a successful Play Games connection. The app has no separate developer analytics SDK, advertising SDK, in-app purchases or player messaging. Optional backup, restore, achievements and rankings Back up or restore asks you to associate your local profile with the selected Google Play Games profile before its first backup association. It uses Google's app-specific Saved Games storage, not general access to your Drive files. A backup sends puzzle state (including clues, solution and entered digits), notes, undo history, timing, hints, difficulty, results, archived sessions, completion records, local profile and backup-player identifiers, and save revision metadata to Google. Restoring reads this game data back. Conflicting active puzzles or profiles require a choice, with recoverable copies retained locally where storage succeeds. Backup and restore depend on connectivity, account access and successful operations; they are not a guarantee of recovery or cross-device synchronization. After a successful backup commit, the app submits earned achievements and eligible completion times by difficulty to Play Games. Eligible rankings exclude hinted or undo-assisted completions. Google associates achievements and scores with the selected profile; their visibility to others depends on Play Games profile and leaderboard settings. The app does not call the friends API or upload screenshots to Saved Games. It does not send gameplay to a separate developer-operated server. Google processing and controls Google's handling is described at https://policies.google.com/privacy and https://developer.android.com/games/pgs/data-collection. Google documents HTTPS protection for Play Games transfers; this is not a claim of end-to-end encryption. Manage profile visibility and game sign-in through Play Games settings. Merge Numbers 1.0.1 on your device Merge Numbers stores its board, score, move count, next tile, milestone state and best score locally. It has no accounts, cloud saves, cross-device synchronization, advertising or analytics. Its bundled game code does not transmit saved gameplay to us or third parties. Restarting preserves its best score. Shared installation code may read local installation preferences; installation invitations are suppressed in the Android apps. Retention and deletion Clearing Android app storage or uninstalling removes app-local saves, archives, recovery copies and preferences. Both apps disable Android application backup; this is separate from optional Play Games Saved Games in the enabled versions described here. Local deletion does not delete data already held by Google. Use the Play Games profile's game-data deletion controls or Google My Account to manage Google-held game data: https://support.google.com/googleplay/answer/9130646 and https://myaccount.google.com/. Google manages retention and deletion of its service data. Deleting Google-held data does not remove local copies. If you later back up remaining local progress, game data, earned achievements and eligible times may be uploaded again. Avoid another backup and remove local copies too if you want to prevent that reupload. There is no in-app command that deletes all Google-held data. Support and privacy emails If you email shreekrishnaenterprise0721@gmail.com, your email is used only to respond to and resolve your request. Emails are processed through Gmail and kept only as long as needed for that purpose, subject to legal obligations. Email correspondence is separate from the games' local saves. You can use the same address for privacy inquiries or requests about your correspondence. Intended audience Both games are intended for people aged 13 and above. The website If you separately visit gameshush.com, the website privacy notice at https://gameshush.com/privacy describes its hosting and website-specific processing. This app policy does not replace that website policy. Changes We will update this policy if the apps' data practices change, before distributing a release that introduces those changes. Contact Shree Krishna Enterprise shreekrishnaenterprise0721@gmail.com

Merge Numbers — Android

Merge Numbers — Android privacy notice Updated: 13 November 2026 Who provides the game Shree Krishna Enterprise provides Merge Numbers (Android package com.gameshush.mergenumbers). Contact us at shreekrishnaenterprise0721@gmail.com for privacy questions. This notice describes Android 1.1.11, including internal testing. It includes optional gameplay analytics and crash reporting. Older versions and separate browser or preview editions have their own notices. This notice does not announce availability on Google Play. Your game on your device Classic and Cascade Lab work without a successful Google connection. We save your board, next tile, score, moves, best score, milestones, challenge progress, settings and recovery records locally. Classic and Lab progress are separate. Eligible-run evidence and pending achievement/score submissions may also be stored locally. Storage limits or failures can affect recovery. Imported personal bests do not become ranked scores or historical achievements. Diamond balances, block-goal unlocks and claims, daily-reward streaks, calendar/time-zone information, video-reward counts and cooldowns, and pending/confirmed reward and spending records are also stored on this device. They support daily rewards, optional earned-video rewards, tool spending and duplicate-reward prevention. Diamonds are not purchased with money, cannot be cashed out, and are not included in Play Games backups or synchronized to other devices. Clearing app storage or uninstalling removes these local records and unspent diamonds. Optional reminders Daily-reward and return-to-play reminders are optional and off by default. If you enable them, Android may request notification permission. Reminder preferences, your last visit, the last reminder day, and a copy of your local reward calendar are stored on this device to schedule and limit reminders. These reminder records are not sent to our servers or included in Play Games backups. Android controls delivery and may delay or suppress reminders. You can turn each reminder off in game settings or block notifications in Android settings. Opening a reminder does not automatically claim a reward or spend diamonds. Google Play Games and optional cloud features The Android game initializes Google Play Games at startup. It can authenticate the Play Games profile selected in your Google settings. Google processes gamer identity and SDK analytics and diagnostics for service stability and improvement, even if you decline cloud backup. The game displays your gamer name and game-specific player identifier. It does not request your Google email address, friends list or general Drive files. You may associate local progress with that player. After a successful backup or sync you request, eligible queued achievement identifiers and completed Classic scores are sent to Google; unsuccessful submissions remain queued. Your Google profile and leaderboard settings govern visibility. Reading your Google score does not submit a new score. Back up or restore reads the game's Saved Games slot and may create or upload a backup, including an empty slot. This is not continuous automatic backup. Backups contain Classic and Lab progress, board/next tile/score/moves/milestones/best, challenge paths, player association, version metadata, and the previous move and next-draw state required for undo, plus reward-use metadata. They exclude audio preferences, screenshots, raw damaged saves, in-flight ad tokens, the full competitive move ledger, and the device-local diamond wallet, block-goal claims and daily/video-reward ledger. Backups use Google's game-specific storage, not general Drive access; a backup is limited to 256KiB. Account changes pause the previous association. Different boards require your explicit restore choice. A submitted backup is not a guarantee of restoration. Advertising and age choices The game uses Google Mobile Ads and Google's User Messaging Platform (UMP) for a banner and optional rewarded Undo, full-board rescue, and diamond rewards. Each video requires a separate user choice; earning diamonds does not automatically spend them. Videos are not forced after moves; restarting is free, and there are no interstitial ads. Google must report a reward earned before it is applied. Local receipts prevent duplicate rewards and support interruption recovery. We do not add your board, score or Play Games identifier to rewarded requests; no server-side reward verification is used. The neutral age choices are under 13, 13–15, 16–17 and 18 or older. We store the band locally, not a date of birth, and exclude it from backups. Under-13 and unknown-age states make no ad requests. Ages 13–15 receive Google's restricted under-consent-age treatment, ages 16–17 its teen treatment, and adults standard consent-based treatment. Google receives the corresponding treatment signals, not a birth date. Ads are requested only when UMP permits them. Ad privacy choices lets you change your age band and access Google's applicable consent or opt-out choices. Declining personalized advertising does not stop every kind of ad processing. Google documents Mobile Ads collection/sharing of IP addresses (which can indicate approximate location), app interactions, performance diagnostics and device/account identifiers such as advertising ID and app set ID for advertising, analytics and fraud prevention. UMP processes consent choices. The game does not supply its saves, backups, personal best or Play Games identifier to this integration. Advertising choices are separate from cloud backup and the optional controls below. Optional gameplay analytics and crash reports Settings offers two independent choices to players who selected 18 or older: “Help improve gameplay” and “Share crash reports.” Both start off. Younger and unknown-age players cannot enable them in this initial rollout. Declining either does not affect gameplay or rewards. The age band is not sent as an analytics event or crash field. With gameplay analytics enabled, Google Analytics for Firebase receives a limited set of screen, tutorial, game-start/end, milestone and rewarded-outcome categories to help us understand use and improve the game. Google's SDK also measures automatic app/session interactions and associated technical information; this can include first opening, engagement and automatic AdMob impression/revenue information where available. These are not limited to our custom events. Google uses app-instance identifiers and device/app information, and can derive approximate geographic information from the connection. The integration does not collect the advertising ID for Analytics and denies Analytics advertising storage, advertising user-data and personalization consent. This does not disable the separate advertising SDK's processing. With crash reports enabled, Google Firebase Crashlytics receives crashes and limited error reports, installation/crash identifiers, app and operating-system versions, device characteristics, timing and diagnostic stack information to help us fix failures. Our JavaScript error bridge sends only a bounded error category; it discards raw JavaScript messages, stacks, URLs and arbitrary payloads. Native crash diagnostics are produced by the SDK and may include native exception messages and stack traces. We do not set a custom player identifier or attach your name, email, saved board, full score history or exported files to either service. SDK-generated identifiers mean these reports are not completely anonymous. You can turn either option off in Settings. Analytics forwarding stops and its local analytics state is reset. Crash forwarding stops and pending unsent reports are scheduled for deletion; a full app restart may be required before crash reporting can be enabled again. Reports may be retained on-device while offline. Disabling a choice does not recall data already uploaded or a request already in flight, and some SDK diagnostic files may remain until cleanup or restart. Changing to a younger or unknown age band turns both options off; returning to adult does not restore the old grants. Advertising and Play Games processing have their own controls and are not disabled by these switches. Recipients, protection and retention Google processes data for Analytics, Firebase Crashlytics, Mobile Ads, UMP and Play Games, under the applicable service terms and account configuration. Data may be processed on Google's infrastructure internationally. The services use encrypted HTTPS/TLS transfers; this is not end-to-end encryption. We do not operate a separate gameplay server, player messaging or in-app purchase feature. The Analytics property currently retains event-level data for 2 months and user-level data for 14 months, without resetting user retention on new activity. These settings do not determine retention of all aggregated reports. Google states that Crashlytics keeps crash traces and associated identifiers for 90 days before beginning removal from live and backup systems; this is not a promise of complete deletion on day 90. Other Google service records follow the relevant service retention policies. Google Signals, granular location/device collection and regional advertising personalization are disabled for this Analytics property. Optional account sharing for Google products and services, modeling contributions, business recommendations and technical-support access is disabled. The Google Ads link remains for measurement with personalization disabled; AdMob and Play Games have separate processing and controls. These settings do not erase previously collected data or disable every linked-product data flow. Local saves remain until replaced, removed through available controls, or cleared using Android app storage/uninstall. Restart does not erase every best, progression, queue or recovery copy. Android automatic app backup is disabled; Saved Games is separate. Exports may contain private progress and player association, and are not password-protected or encrypted by this app. Keep them private and manage those files separately. Deletion and contacting us There is no in-app command to delete all Google-held records or unlink every service. Clearing storage, uninstalling or deleting a local export does not delete data already held by Google. Google's Play Games game-data/profile deletion and Google account controls can manage relevant Google-held data. Deleting a cloud record does not clear local copies; a later backup can upload remaining local progress again. We cannot promise instant or complete deletion of all Google records, or identification of every Analytics/Crashlytics record from your email alone. Contact us for privacy requests and we will explain the available process and its limits. The game is intended for ages 13 and above. If you email us, Gmail processes that correspondence; we use it to respond and resolve your request, keeping it only as long as needed, subject to legal obligations. The website and other games have separate notices at gameshush.com/privacy. Google information and controls https://policies.google.com/privacy https://policies.google.com/technologies/partner-sites https://firebase.google.com/support/privacy https://support.google.com/analytics/answer/7667196 https://developers.google.com/admob/android/privacy/play-data-disclosure https://developer.android.com/games/pgs/data-collection https://support.google.com/googleplay/answer/9130646 https://myaccount.google.com/

Sudoku data deletion — Shree Krishna Enterprise

For Sudoku (com.gameshush.sudoku), you can remove game data from the Google Play Games profile used for Sudoku without deleting your entire Google account.

  1. Open your Play Games profile using the Google account associated with Sudoku.
  2. Choose Your Data, then Delete Play Games Account & Data.
  3. Under Delete individual game data, find Sudoku and choose Delete. Review Google's confirmation before proceeding.

This requests deletion of Sudoku game data held in that Play Games profile; achievements and progress may also be removed. It does not clear Sudoku's local puzzles, notes, archives, recovery copies or preferences on your devices. To remove those, use Android Settings → Apps → Sudoku → Storage → Clear storage on each relevant device. This removes local progress and cannot be undone through the app.

Do not back up remaining local progress after deletion if you want to avoid uploading it again. Local deletion alone does not remove Google-held data. Google's separate Play History and SDK/service data follow Google's controls and retention policies; this page does not promise a fixed deletion period or that deleting game data removes all Google service records. See Google's current game-data deletion instructions.

For privacy questions or requests about support correspondence held by Shree Krishna Enterprise, contact shreekrishnaenterprise0721@gmail.com. There is no separate developer-operated gameplay server or in-app command that deletes all Google-held data.


Arrowloom — Android privacy notice

Updated: 31 October 2026

Shree Krishna Enterprise provides Arrowloom: Arrow Puzzle (com.gameshush.arrowloom). This notice covers the Android edition with the optional GamesHush guest leaderboard, including testing. Contact: shreekrishnaenterprise0721@gmail.com.

Local play

Puzzles remain playable without joining the leaderboard. Puzzle progress, hints, quests, local animal profile and preferences are stored on your device. The guest-enabled edition does not use Google Play Games, Google sign-in, advertising or in-app purchases. The separately distributed website APK remains offline and does not use this leaderboard. Website visits have the separate website privacy notice below.

Optional guest leaderboard

If you choose Join guest leaderboard, the app creates a random credential on your device and a guest identity with a generated alias on our Cloudflare-hosted service. No email address or Google profile is required. The service processes the guest identifier and credential, completed level numbers, puzzle-generation version, completion move sequences, ranked points and request times. It stores hashes of the sign-in credential and, when configured, a separate deletion recovery code, plus guest ID, generated alias, ranked total, next eligible level and registration time. Completed move sequences are checked to calculate valid scores; the current application database does not keep those sequences. Other leaderboard participants can receive generated aliases and scores for leading players. Your local animal name is not uploaded.

Ranking starts with the level after joining; previous local points are not imported. Up to 256 pending completion proofs are stored locally for retry. Rankings depend on connectivity and free-service capacity. This is not a cloud backup or a way to restore your local game on another device.

Network processing and retention

Requests use HTTPS. Cloudflare processes network addresses and request information to deliver and protect the service. Our code uses keyed network-address digests and request counters for abuse prevention rather than storing raw addresses in the application database. Guest ranking records remain until authenticated deletion. Bounded maintenance removes old abuse-counter records after they become eligible for cleanup; this is not an exact deletion deadline. Cloudflare request logs include operational request/response and performance information. On the current Free plan, Cloudflare documents Workers Logs retention of 3 days and D1 recovery history of up to 7 days. These service records and backups may remain after active ranking records are deleted; other provider security records follow Cloudflare’s policies. The application does not deliberately log recovery codes or sign-in credentials. Query-string redaction is enabled for Worker observability. We do not claim that guest data is fully anonymous or end-to-end encrypted.

Deletion and controls

While you still have the installation, open Guest leaderboard and choose Delete guest ranking data while online. A successful request removes the active guest identity, credential hash and ranked score and associated guest records. Local puzzle progress remains. A failed request remains pending; retry while online until deletion is confirmed. You can keep playing without rejoining.

To delete your ranking without the app, save a deletion recovery code from the Guest leaderboard menu while you still have access. This code is separate from the app's sign-in credential. It has no automatic expiry and remains valid until replaced or the guest is deleted. Keep it private: anyone who has it can delete that guest ranking, but it cannot be used to play as you or submit scores. Replacing the code in the app invalidates the previous code.

Open the “Arrowloom — Delete guest ranking data” web page at https://arrowloom-guest-test.shreekrishnaenterprise0721.workers.dev/delete, enter your saved code and confirm deletion. The code is sent only to our Cloudflare-hosted deletion service over HTTPS. Do not email the code or put it in a web address. The page does not reveal whether an unknown code belongs to a player. If a request fails because the service is unavailable, try again later.

Clearing app storage or uninstalling removes local data and loses the installation's credential; it does not delete server records. Use the in-app delete control first or keep your deletion recovery code for the web route. If you lose both the installation and recovery code, email shreekrishnaenterprise0721@gmail.com with the subject “Arrowloom privacy request” for assistance. We cannot verify ownership from a public guest alias alone, and may be unable to delete a specific identity without proof. Never send passwords, sign-in credentials or deletion codes by email. Neither deletion route deletes local game progress on your device; local data can be removed separately through Android's app-storage controls.

Support

Support emails are processed through Gmail, used to respond to and resolve your request, and kept only as long as needed for that purpose, subject to legal obligations. Correspondence is separate from game saves. Arrowloom is intended for people aged 13 and above.

Website and demo-app privacy

PRIVACY

Your game data, explained.

Block Flow keeps your game records in this browser. This notice explains local storage, offline files, and requests made when you visit GamesHush.

Previous Block Flow edition: stored data

The previous Block Flow edition uses browser local storage for a randomly generated anonymous player identifier, your best score, music and sound preferences, dismissed control hints, and installation prompt preferences. It also keeps completed-run records: scores, piece sequences, seed, duration, levels, clear statistics, and completion times associated with that local identifier.

These previous-edition records are not uploaded by that edition’s game code. There is no account or cross-device sync. An unfinished board is held in memory, not saved for later recovery. A session-storage key may also record whether a control hint has been seen.

Block Flow Wood edition: local game data

Block Flow Wood edition stores its current run (including the board, current and next pieces, random seed, score and progress counters), best score, sound preference and whether a previous best was imported in the local-storage entry gameshush.blockflow.wood.v1. It restores a valid saved run when storage is available. It does not create the previous edition’s anonymous player identifier or completed-run history.

Importing a previous browser best score is optional. The import reads the previous edition’s best-score entries and writes only to the Wood edition’s storage entry; it leaves the original records intact. Other games’ saves are separate. There is no game account, game-data upload, advertising or analytics in the Wood edition’s game code. The website hosting and measurement disclosures below still apply to website visits.

Clearing site data removes browser saves. Storage restrictions or private browsing can prevent persistence. The Wood edition’s Android app bundles its game files, requests no Android permissions and stores game data locally in its separate app storage. Browser/PWA and previous-app saves do not transfer automatically. Clearing app storage or uninstalling removes the app’s local saves.

Sudoku saved progress

Sudoku stores the current puzzle and solution, entered digits, pencil notes, recent undo history, elapsed play time, hint count, difficulty and input preferences in this browser. It uses a separate local-storage key and does not upload these records. Reopening restores the saved puzzle. The updated web/PWA game keeps a local profile identifier, puzzle archives, recovery copies, completion records and sound/motion preferences. Starting a new puzzle retains previous puzzles in Saved puzzles when storage succeeds. Legacy progress is migrated locally. There is no Play Games SDK or cross-device sync in this browser edition.

Merge Numbers browser saves

Merge Numbers stores its board, score, move count, next tile, milestone state and best score in this browser’s local storage. Reopening restores a valid saved board when storage is available. Starting a new game replaces the current board while preserving the best score. Clearing site data removes these saves. They are not uploaded by the current game code and do not sync to another device or the Android app.

Android demo apps

The optional Android demos bundle their game files and keep data in separate app storage. They do not include website analytics or advertising, upload game records, or automatically download updates. Browser and TEST app saves do not migrate. Uninstalling or clearing app storage removes that demo’s data. See Android demo terms and privacy for details. Download requests use the website hosting described below.

Offline files

A service worker caches site pages, game code, styles, and icons so supported browsers can play offline. A later visit can download an updated version. This cache is separate from your saved scores and preferences.

Hosting and requests

GamesHush is hosted on Cloudflare Pages. Opening the site sends network information to Cloudflare to deliver and protect the site. Cloudflare provides traffic summaries and infrastructure request logs to the site operator. These logs can include your IP address, request time, hostname and path, HTTP method, response and cache status, and country inferred from your connection. See Cloudflare’s privacy policy. The live hosting response also enables Cloudflare Network Error Logging: supported browsers may send reports of failed network requests to Cloudflare.

Performance analytics

The domain’s Cloudflare Real User Measurements setting is enabled for visitors outside the EU. On pages where Cloudflare can add its measurement script, it sends page-load and performance measurements to Cloudflare. Some pages prevent this script from being added through their response headers, so the script does not run on every page. The separate Pages-project Web Analytics integration is disabled. See Cloudflare’s explanation of measurement data.

Ads and cookies

The game code does not load an advertising provider, upload gameplay records, or set application cookies. A Monetag ownership-verification meta tag is present; that tag alone does not load ads. The previous Block Flow edition’s rewarded-continue interface has no connected ad provider and cannot grant a reward from a click.

Google ads and a consent-management platform are not implemented. If advertising or additional analytics is added, this notice and any required consent choices must be updated to describe the actual providers, information collected or shared, and cookie or identifier use before those services run.

Your choices

The previous Block Flow edition offers music and sound controls; Wood edition offers a sound control. Clearing this site’s data in your browser removes locally stored scores, identifiers, preferences, and run records; clearing offline data removes downloaded files. This cannot be undone and may affect installed play. Private browsing or blocked storage may make these features temporary or unavailable.

Questions and requests

For privacy questions, email shreekrishnaenterprise0721@gmail.com. Do not send sensitive information through the game; it has no message-submission feature.

Number Slide: local game data

Number Slide stores one current puzzle, its original arrangement, moves, elapsed active time, sound preference and separate records for each board size in browser local storage. Best moves and fastest time can come from different solves. The game uses its own storage entry and does not combine progress with other GamesHush games.

There is no Number Slide account, server synchronization, analytics, advertising or game-data upload. Hosting still receives ordinary page and asset requests. Browser storage can be unavailable or cleared; clearing this site’s data removes local progress and records. Private browsing and storage restrictions can limit persistence. The game reports storage failures without blocking play.

A browser-installed PWA uses the web game’s browser storage context. It does not synchronize between devices, browsers or profiles. Cached files support offline use after a successful initial online cache.

The Number Slide Android app bundles its game files, requests no Android permissions and has no network permission. Its local app data is separate from browser/PWA storage. Clearing app data or uninstalling can remove the app’s puzzle and records.