Neural Breach — Cyberpunk Puzzle Game for Android
Effective Date: May 19, 2026 | Last Updated: July 31, 2026
Data Deletion Request).This page is the public data- and account-deletion endpoint for Neural Breach, as required by the Google Play User Data policy. Anyone can use the methods below without re-installing the app or signing in to it.
Neural Breach does not require account registration with us and we operate no backend server of our own. Because the app does not maintain a separate in-app account, deleting the data described below is equivalent to deleting your in-app account. The data linked to you is held in the following locations, all under third-party (Google) or device control:
For the full list of what we collect and why, see our Privacy Policy.
The table below summarises the main data categories and which deletion method removes each. It is a summary — the Privacy Policy is the authoritative inventory.
| Data category | Where it lives | Deleted by |
|---|---|---|
| Game progress (levels, stars, best scores) | Local Room database on your device | Method A, or uninstall + clear app data |
| In-game credits balance, inventory, upgrade progress | Local Room database on your device | Method A |
| Gameplay statistics (total moves, time played, win streaks) | Local Room database on your device | Method A |
| App preferences (volume, CRT effect, haptics, tutorial flags) | Local DataStore on your device | Method A |
| App language selection | Android per-app language setting | Android Settings → Apps → Neural Breach → Language |
| Cloud-save snapshot (mirror of progress, credits, inventory) | Google Play Games Services | Method A (best-effort) or Method B |
| Play Games player ID and display name, achievement unlock status, and player-profile binding for this game | Google Play Games Services | Method B |
| Advertising identifier (AdID) and ad personalization data | Google Mobile Ads (held by Google) | Method D |
| Ad-consent status (TCF v2 / UMP consent string) | Google User Messaging Platform | In-app Settings → > PRIVACY SETTINGS → OPEN (re-open the consent dialog) — see Method D |
| Purchase tokens and transaction records (Play Billing) | Your Google Play account, held by Google | Retained by Google for legal/tax reasons — see Section 7 |
| Diagnostic and ad-interaction telemetry (impressions, IP, app set ID, device model) | Google AdMob (held by Google) | Controlled by Google; managed via Method D and the in-app consent dialog |
| Android OS backups of app data (if Auto Backup is enabled) | Your personal Google Drive (held by Google) | Android Settings → Google → Backup |
This is the fastest way to delete the data we hold. A single confirmation wipes the local database and app preferences, and best-effort requests deletion of the Play Games cloud-save snapshot in the same action.
Cloud-save best-effort caveat. The cloud-save deletion in Method A succeeds only when (a) you are currently signed in to Play Games inside the app, (b) the device has network connectivity, and (c) there is no sync conflict on the snapshot. If any of those conditions fails, the local data is still wiped but the Play Games snapshot may persist. If you want to be certain that the cloud save is gone, run Method B afterwards.
Not cleared by Method A: the app language selection (this is the Android per-app language setting and lives outside the app); Play Games achievement progress and player profile (use Method B); advertising identifier (Method D); Play Billing purchase history retained by Google.
Use this method to ask Google to delete the Play Games data associated with Neural Breach (which may include the cloud-save snapshot, achievement progress, player ID/display name, and the player-profile binding for this game). It is required if you have already uninstalled the app or if you were not signed in to Play Games when you used Method A. The scope of what is actually removed is described in more detail at the end of this section.
Google's current help article is Delete your Play Games data or Play Games profile. Note that Google uses slightly different button labels in the two flows (Delete Play Games Account & Data on the web, Delete profile & game data on Android). Exact navigation steps may also drift between Play Games versions and Android releases; if you cannot find the option, follow the linked Google article for the latest path.
Scope of Method B. Deleting Play Games data for Neural Breach removes the data Google Play Games stores in connection with this specific game — which may include the cloud-save snapshot, in-game achievements, and the player binding for Neural Breach. It does not delete your overall Google Account, your Play Games profile across other games, your Web & App Activity, your Play Store purchase history, or any data Google holds independently of Play Games.
If the steps above are not practical for you — for example, you have lost access to the device or to the Google Account you played the game with — you may submit a deletion request by email:
Email:
support-komandakycto@proton.me
Subject line: Data Deletion Request
To help us identify what to delete, please include in your message:
Because Neural Breach does not operate a backend server, the developer cannot directly delete data that Google stores on your behalf — including the Play Games cloud-save snapshot, achievement progress, the AdID, or Play Store purchase records. For those, you remain the only party with the authority to act, through Method A, Method B, Method D, or your Google Account settings. By email we can:
Because Neural Breach operates no backend server and holds no developer-side copy of your in-game data, our ability to independently verify a request is limited. We will reply to your request, confirm in good faith that the email account contacting us is the originator, and use the information you provide to point you to the correct self-service method (Method A, B, or D) for the data Google actually holds on your behalf. We will not request government ID, your full legal name, or any other information beyond what is strictly necessary, and we will not ask for sensitive personal data.
We aim to respond to deletion requests within 30 days, in line with applicable data-protection law. If the request is complex, we may extend this period by an additional 60 days and will inform you of the extension within the initial 30-day period. These commitments are made with reference to, and are intended to be consistent with:
Where mandatory local law sets a stricter or different timeline, that local law prevails.
The app uses Google Mobile Ads (AdMob) to show interstitial and rewarded advertisements. AdMob may use the Android advertising identifier (AdID) tied to your device. To reset or delete this identifier:
You can also re-open the in-app ad-consent dialog at any time via Settings → Privacy Settings inside Neural Breach to withdraw consent or change your choice.
This same choice controls gameplay analytics. Neural Breach uses Google Analytics for Firebase to record which levels are started, completed or restarted, so we can see where players get stuck. Collection is switched off when the app is installed. In the EEA, the UK and Switzerland it begins only after you consent through the dialog; elsewhere, where prior consent is not legally required, it begins on first launch. Where the Settings → Privacy Settings entry is offered on your device, withdrawing consent there stops collection immediately; otherwise clearing the App's data or uninstalling it stops it.
These events are recorded against a randomly generated app-instance identifier rather than your name or Google Account, so we cannot identify you from them on our own. They are pseudonymous, not anonymous: if you send us that identifier we can ask Google to delete the events recorded against it. Withdrawing consent stops future collection but does not by itself erase events already recorded.
Some data is held by Google or other third parties under their own policies, not by us, and cannot be erased through any of the methods above:
For any question about this deletion procedure, or to submit a deletion request, contact: