Last updated: 12 August 2026
HammerPhone has no accounts and no servers of its own. The purposes you type and the apps you use never leave your phone— those are the things this app sees most of, and they stay on the device.
Two things are sent off the device: crash reports, always, so that breakage can be fixed; and anonymous usage counts, which are on by default and which you can switch off at any time in Settings. Neither one contains your purposes or the names of the apps you use.
HammerPhone is developed by Riser Apps. Questions about this policy or your privacy: [email protected]
HammerPhone uses Android's Accessibility Service to see which app is currently in the foreground— for example, that you are in a web browser rather than a notes app.
This is the core of how the app works. It is what allows HammerPhone to notice when you have moved away from the purpose you set, and it is what powers the "Lock device" button on an intervention.
HammerPhone does not read the contents of your screen, anything you type into other apps, your messages, your passwords, or any data inside other apps. It looks only at which app is in front.
This information is used on your device only. The name of the app you are in is never transmitted, to us or to anyone else.
If you grant Notification Access, HammerPhone watches for notifications being dismissed so it can tell when you opened an app by tapping a notification. This lets it send you to what you actually opened instead of bouncing you to the home screen.
HammerPhone does not read the content of your notifications, and does not store or transmit them. This permission is optional and the app works without it.
HammerPhone reads the list of apps you can launch, so it can show you app names and icons when you pick an app to bind a session to, or add an app to your exceptions list. This list is not transmitted.
When you set a purpose ("reply to emails", "look up a recipe"), that text is stored on your phone so the app can show it back to you and remind you of it later. It is never transmitted.
All of the following stays in HammerPhone's private storage on your phone:
-The purposes you type, and the purposes saved in your shortcuts -Your shortcuts, including any app a shortcut is bound to -Your settings, such as intervention frequency -Your exceptions list — the apps you have chosen not to be interrupted in -A local diagnostic log of app events, used for troubleshooting
There is no HammerPhone account and no HammerPhone server, so there is nowhere for this to be uploaded to.
When HammerPhone crashes or hits an internal error, a report is sent to Google Firebase Crashlytics so the problem can be found and fixed. This cannot be switched off in the app.
A crash report contains the technical details of the failure and the state of the device at the time:
-The error and the stack trace — which lines of HammerPhone's own code failed -Device model, manufacturer, operating system version -The version of HammerPhone you are running -Device state such as available memory and storage, and whether the device is rooted -A random identifier generated by Crashlytics for your app installation
A crash report does not include your purposes, your shortcuts, the names of apps you use, or HammerPhone's diagnostic log.
Crashlytics is operated by Google. Their handling of this data is covered by the Google Privacy Policy and the Firebase Data Processing Terms.