HardWake — Privacy Policy
Last updated 9 October 2026. Applies to the HardWake Android app
(com.obaylabs.hardwake).
HardWake does not upload your alarms or wake history to Obay Labs. Pro purchases use secure server verification. Android backup and device transfer may copy local data according to your system settings.
What HardWake collects
Pro verification processes purchase tokens and product IDs. There is no analytics SDK, no crash-reporting SDK, no advertising SDK and no tracking library of any kind in the app.
What HardWake stores, and where
| Data | Where | Sent to Obay Labs? |
|---|---|---|
| Alarms (times, repeats, challenges, sounds) | App-private database | No |
| A mirror of armed alarms | Device-protected app-private storage | No |
| Pending wake-up checks (alarm details, timing and progress) | Device-protected app-private storage | No |
| Latest alarm test setup and results (audio, vibration, lock-screen and challenge checks) | Device-protected app-private storage | No |
| Registered QR/barcode fingerprints and their names | App-private database | No |
| Wake history and statistics | App-private database | No |
| App settings | App-private storage | No |
| Tahajjud location (latitude/longitude) | App-private storage | No |
| Pro entitlement cache | App-private storage | No |
| Pro purchase token and product ID | Billing verifier and Google Play | Yes |
| Hashed receipt ID, Pro status, expiry and revocation record | Firestore | Yes |
HardWake does not write your alarm data to shared files or external storage. The local alarm database and settings can be included in Android backup; see Backup below.
Widgets and alarm checks
The Next Alarm and Wake Record widgets use data already stored on your phone. They pass the information needed to display the widget to your Android launcher, not to our server. Anyone who can see your home screen may be able to see that information. Remove the widget if you do not want it shown there. Widget picker previews use sample data, not your private records.
Wake-up checks store pending check details locally so they can continue if the app restarts. The alarm test stores its latest setup and diagnostic results locally, such as whether audio focus was granted and whether the alarm stream or full-screen access was available. These results are not uploaded. Running another test replaces the previous test results.
Accounts
You do not need a HardWake account, email address, phone number or social login. HardWake has no account-based cloud sync. Google Play uses your Google account to manage purchases. If you email us, we receive the information you choose to include so we can respond.
Permissions, and exactly why
| Permission | Why | When it is requested |
|---|---|---|
| Exact alarms | Ring at the time you set | Granted by Android or enabled in system settings, depending on Android version |
| Notifications | Show alarm and wake-up check notifications | First launch after onboarding on Android 13 and later, or from Settings |
| Run at startup | Restore your alarms after a reboot | Install time |
| Foreground service (media playback) | Keep the alarm ringing with the screen off | Install time |
| Wake lock, vibrate | Wake the device and vibrate | Install time |
| Modify audio settings | Temporarily adjust alarm volume while ringing, then restore it | Install time |
| Full-screen intent | Show the alarm over the lock screen | Granted by Android or enabled in system settings, depending on Android version |
| Ignore battery optimisation | Reduce background restrictions that may delay an alarm | Only from the reliability panel, only when needed |
| Physical activity | Count steps for the Walking challenge | Only when you enable that challenge |
| Camera | Scan the code you registered, to dismiss an alarm | Only when you set up a QR or barcode challenge |
| Approximate location | Compute Fajr for Tahajjud mode | Only when you turn on Tahajjud mode |
| Billing | Google Play purchases | Install time |
| Internet, network state | Google Play purchases and secure Pro verification | Install time |
No permission is requested during onboarding. Camera, location and physical activity are requested when you use the features that need them. Basic alarms work without these optional permissions; the features that rely on them may be unavailable.
About the camera
- Frames are decoded on the device, by a plain Java decoder with no network code in it.
- No frame is saved. Nothing is written to storage, to a cache, or to a log.
- The code's contents are never stored. A QR code can hold a home address, a Wi-Fi password or an account URL. HardWake only needs to answer "is this the same code as before?", so it keeps a salted SHA-256 fingerprint of the payload and separately stores the name you gave it ("Bathroom mirror"). The payload itself is discarded as soon as the fingerprint is computed.
- Each registration uses a random salt, so registering the same code again produces a different fingerprint. A fingerprint is not a copy of the original code.
- The camera runs only while code registration or a scanning challenge is on screen, and is released when that screen closes.
If you revoke the permission later, alarms that used a code fall back to a solvable challenge rather than becoming impossible to dismiss.
About location
- Only approximate location is requested, never precise.
- It reads the last known position rather than requesting continuous updates.
- HardWake stores the coordinates locally and does not send them to our server. They may be included in Android's backup of your settings.
- Tahajjud mode works entirely without the permission — you can type a latitude and longitude instead.
Google Play Billing
Google processes payments. HardWake sends purchase tokens and product IDs over HTTPS to its Google Cloud verification service. The service checks Google Play and stores hashed receipt IDs, Pro status, expiry and revocation records in Firestore. Application code does not store raw tokens. Infrastructure request logs may include IP addresses, request times, paths and response status. We use this service to verify purchases, restore Pro access and handle expiry, refunds and revocations, not for advertising or usage analytics. HardWake does not receive your card or bank details. No alarms, location, wake history, test results or challenge content is sent to this service. Google Cloud hosts the service and its verification records. Purchases and Google's handling of payment data are governed by Google's own privacy policy.
How long data is kept
- Local data: Saved alarms, wake history and settings remain until you remove them, clear the app's storage or uninstall it. Pending wake-up checks are updated or removed as checks finish or are cancelled. The latest alarm test results remain until replaced or app data is cleared. Backup copies are handled separately, as described below.
- Billing verification records: Hashed receipt IDs, Pro status, expiry, verification times and revocation records currently have no automatic expiry. They are retained, including after a subscription ends, to support purchase verification and restoration and prevent refunded or revoked purchases from being used again. You can request deletion as described below; some records may need to be retained for fraud prevention or legal obligations.
- Operational logs: Our Google Cloud request and application log bucket has a 30-day retention period. Separate Google Cloud administrative and system-event audit logs have a 400-day retention period. These audit logs are not a history of your alarm use.
Google Play keeps its own purchase records under Google's policies. Deleting HardWake data from our systems does not delete those records.
Backup
When Android backup or device transfer is enabled, Android may copy HardWake's alarm database and settings. This can include alarm labels, challenge settings, registered code fingerprints, wake history and saved Tahajjud coordinates. Backup storage, protection, retention and transfer depend on Android, your backup provider and your system settings; HardWake does not operate that backup service.
The local Pro entitlement cache, direct-boot alarm mirror, pending wake-up checks and alarm test results are excluded from HardWake's configured backup. Google Play is used to restore purchases. You can manage backup and available backup-deletion options in Android and your backup provider's settings.
Children
HardWake is not directed at children.
Deleting your data
You can clear wake history from Settings › Privacy, delete individual alarms in the app and remove saved Tahajjud location in Settings. Clearing Android's app storage or uninstalling HardWake removes its local app data. Removing a widget only removes its home-screen display; it does not delete your alarms or wake history. Android backups may remain or restore data until you manage them through your system or backup provider.
To request deletion of billing verification data, email hello@obaylabs.com with the subject HardWake data deletion. Explain what you want deleted. We may ask for a Google Play order reference or other limited purchase information to verify ownership and identify the relevant record. Do not send card details, passwords or purchase tokens. We use the information you provide to handle your request.
If a record must be retained for fraud prevention or a legal obligation, we will explain what is retained and why. Deleting a verification record may require another Google Play check to restore Pro; using purchase or restore again can create a new verification record. Logs expire under the retention periods above rather than through the app's Clear history button.
A data-deletion request does not cancel a subscription or request a refund. Manage those separately through Google Play.
Changes to this policy
If this policy changes, the updated version will be published at this address with a new date at the top. HardWake will never start collecting data without saying so here first.
Contact
Questions about this policy: hello@obaylabs.com
HardWake is made by Obay Labs. No ads. No account.