Privacy policy
Last updated 12 October 2026. Orbit Breaker is a game for Wear OS watches and Apple Watch, made by Dmitrii Samoilenko, the developer of the Google Play listing for package com.dmitry.orbitbreaker and of the App Store app with bundle id com.dmitry.orbitbreaker. The sections below describe the Wear OS app; the Apple Watch app is described in its own section.
What the app accesses
Orbit Breaker has no account, advertising, analytics or crash reporting service. It uses Google Play Billing for one optional full-game purchase and, with your permission, the watch's heart-rate sensor for the HEART game mode.
Google Play tells the app whether the full game is owned. Google holds its own purchase records. This is declared as purchase history in Google Play's Data safety form. Orbit Breaker never receives your card number, billing address or name.
Heart rate and the HEART mode
HEART uses the current heart rate to change game speed, beat timing and level mechanics relative to a baseline measured for the run. It is a game, not a medical device, and does not diagnose, treat, cure or prevent any medical condition.
When you first choose HEART, the game explains how it uses heart rate before offering the system permission request. Permission is optional: choose the simulated pulse or decline permission to play without sensor access. HEART also uses a simulated pulse if the sensor or a reading is unavailable. Other game modes do not need heart-rate access. You can revoke the permission in the watch's system app settings.
With permission, the sensor runs while HEART screens are visible and the app is in the foreground. It stops when you leave HEART or the app goes into the background. Orbit Breaker does not request background sensor access and does not read or write Health Connect records.
Heart-rate readings are used in memory on the watch. The app does not send them to the developer, Google Play Billing, advertisers or an analytics service, and does not keep a heart-rate history. Starting with version 1.10.1, saved runs do not retain your measured heart rate or baseline. The game establishes its pulse input again when a run resumes.
What the app stores on the watch
Settings, progress, best scores, the run in progress, full-game entitlements and the Google Play order number, when provided, are written to the app's private storage. The order number identifies the purchase and is not shown in the game or sent to the developer. The game works when Google Play does not provide an order number. A complimentary access-code entitlement is stored separately from the purchase; the entered code is not saved.
Earlier versions could include the current pulse and baseline in a saved HEART run. Version 1.10.1 ignores those old values and removes them when the save is rewritten. Settings > Reset progress clears progress and the saved run while keeping settings and full-game entitlements. Uninstalling removes the app's local file.
Android backup can copy the private game file to the watch owner's account or another device during a system restore or transfer. New saves from version 1.10.1 contain game progress and settings, not measured pulse or baseline values. Existing backups made by earlier versions may still contain those older values. Android manages and protects backups under the owner's account and Google's terms; Orbit Breaker does not operate a backup server. Backup can be controlled in system settings. Removing local progress does not itself erase an existing system backup; manage that backup through the system or Google account controls.
Network use and purchases
The game's own code opens no network connection and has no server. Google Play Billing talks to the Google Play app to show the price, complete the payment and restore the purchase. Google operates that exchange over its encrypted connections, under Google's privacy policy.
All game modes, settings and progress work offline. The price, purchase and restore need Google Play. Once bought, the full-game unlock is kept on the watch; a failed connection does not remove it. A refund removes the purchase from the Google Play account but does not remove an unlock already saved on that watch.
Permissions
- Heart rate: android.permission.health.READ_HEART_RATE on Android 16 / Wear OS 6 and later, or android.permission.BODY_SENSORS on earlier supported versions. This optional runtime permission is used only for HEART's foreground gameplay. No background health permission is requested.
- VIBRATE: haptics during play. Haptics can be switched off in Settings.
- com.android.vending.BILLING, INTERNET and ACCESS_NETWORK_STATE: supplied by the billing libraries to reach Google Play.
- com.dmitry.orbitbreaker.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION: an app-specific signature permission used by Android support libraries for their own receivers.
The app does not request access to location, contacts, microphone, camera or shared files.
Security, retention and deletion
Android restricts the save file to the app's private storage. Orbit Breaker does not transmit it to a developer server. Android manages the protection and retention of system backups; Google Play manages purchase records and payment security.
Local game data is retained while the app is installed, until replaced or cleared. Reset progress removes game records and the saved run. Uninstalling removes the local file. Revoking sensor permission prevents new readings; current saves contain no measured pulse or baseline. Manage older Android backups and Google Play purchase records through their respective system or account controls.
There is no Orbit Breaker account or server-side profile to delete. We do not sell health data, use it for advertising or share it with other apps.
Apple Watch
The Apple Watch app is bought on the App Store. Apple handles the payment under Apple's privacy policy; the app has no in-app purchase and receives no payment or account information.
With your permission, the Apple Watch app reads your heart rate through HealthKit for the HEART game mode, which uses it as described above. When you first choose HEART, the game explains how it uses heart rate before watchOS asks for permission. Permission is optional: choose the simulated pulse or decline to play without it, and HEART plays to a simulated pulse whenever no reading is available.
An Apple Watch measures the heart rate every few seconds only during a workout, so the app runs a workout session while a HEART screen is open and the app is on screen. It ends the session when you leave HEART or the app leaves the screen, and discards the workout, so nothing is written to Health. watchOS lets an app start a workout session only with permission to save workouts, so the app asks for that as well as for reading heart rate; it saves no workout or other health data.
Heart-rate readings are used in memory on the watch. The app does not send them to the developer, advertisers or an analytics service, does not keep a heart-rate history, and reads no other HealthKit data. HealthKit data is not used for advertising, sold or shared. You can change the permission in the Health settings on the watch or the iPhone.
The Apple Watch app does not request access to location, contacts, the microphone or the camera, and it has no account, advertising, analytics or crash reporting service.
The game's code opens no network connection. Settings, progress, best scores and the run in progress are written to the app's own storage on the watch and are not sent to the developer. Settings > Reset progress clears progress and the saved run. Deleting the app from the watch removes its local data. watchOS may include app data in the backup that the paired iPhone keeps of the watch; Apple manages that backup.
People under 13
The app is not aimed at people under 13.
Changes
If this policy changes, the date at the top changes with it.
Contact
Dmitrii Samoilenko, trdmitriisamoilenko@gmail.com