Privacy policy
Awake runs entirely on your phone. It has no accounts, no servers and no analytics, so there is no copy of your data anywhere else. This page explains that in detail, permission by permission.
1. The short version
Awake does not collect your personal data. Everything the app knows about you stays in its own storage on your phone. There is no account to create, no server to sync with, no advertising SDK and no analytics SDK. Nothing is sold, rented or shared, because nothing is gathered in the first place.
This policy is published by Yasin Walum, the developer of Awake
(package com.yasinwalum.awake), who is the data controller
for the purposes of applicable data protection law.
2. What Awake collects
Nothing leaves your device. Specifically, Awake does not collect, transmit or receive:
- your name, email address, phone number or any account identifier,
- your location, at any precision,
- your contacts, calendar, messages or files,
- advertising identifiers or device fingerprints,
- photos or video from the camera,
- usage analytics, event logs or crash reports,
- anything at all, to any server operated by the developer or a third party.
Awake 1.0.0 makes no network requests as part of normal use. The app functions fully with the device offline.
3. What is stored on your device
Awake writes the following to its own private app storage, which other apps cannot read:
- Alarms. The times you set, which days they repeat, the sound, and which challenge has to be completed.
- Statistics and streaks. A record of completed wake challenges and practice runs, used to show your streak.
- Settings. Your theme seed color, clock format, haptics and sound preferences, challenge defaults, and whether you have finished onboarding.
- Optional profile details. A display name if you enter one, and a copy of a profile photo if you pick one. The photo is chosen through Android's system photo picker (no broad photo-library permission) and is never uploaded.
- Your QR payload. If you use the QR challenge, the text of the code you saved is stored so the app can check the scan against it.
This data is included in an Android system backup only if you have device backup switched on in your Android settings. That transfer is between you and your device backup provider. Awake never sends it anywhere itself.
4. Permissions and why each is needed
Awake requests the permissions below. Android asks you for the sensitive ones at the moment they are first needed, and you can revoke any of them later in Android settings.
| Permission | Why Awake asks for it |
|---|---|
| SCHEDULE_EXACT_ALARM USE_EXACT_ALARM |
Fires your alarm at the exact minute you set. Without these Android is free to delay it to save power, which defeats the point of an alarm. Awake declares the alarm-clock use case for these permissions. |
| USE_FULL_SCREEN_INTENT | Shows the ringing screen over the lock screen, so the challenge is in front of you rather than buried in a notification. |
| POST_NOTIFICATIONS | Shows the ongoing notification while an alarm is ringing. Android requires this permission before any notification can be posted. |
| WAKE_LOCK | Keeps the screen and CPU awake while the alarm rings and while you are completing the challenge. |
| VIBRATE | Vibrates the phone with the alarm, and gives haptic feedback in the app if you leave haptics on. |
| RECEIVE_BOOT_COMPLETED | Re-registers your alarms after the phone restarts. Without it, every reboot would silently cancel every alarm. |
| FOREGROUND_SERVICE FOREGROUND_SERVICE_MEDIA_PLAYBACK |
Keeps the alarm sound playing reliably while the alarm is active. Android kills background audio otherwise. |
| MODIFY_AUDIO_SETTINGS | Plays the alarm on the alarm audio stream at the volume you chose, rather than the media stream. |
| REQUEST_IGNORE_BATTERY_OPTIMIZATIONS | Lets Awake ask you to exempt it from battery optimization. Aggressive power management is the most common reason an Android alarm fails to ring. You can decline, and the app still works. |
| CAMERA | Used only by the challenges that need it: scanning your QR code, and counting push-up or jump reps. The preview is live only while that challenge is on screen. |
| RECORD_AUDIO | Declared because the camera libraries Awake bundles list it as part of their camera stack. Awake contains no audio-recording code, never enables audio capture on the camera, and records no sound. |
| ACTIVITY_RECOGNITION | Reads the phone's hardware step counter for the walk challenge, so the step count keeps working when the screen switches off. Requested when you set up a walk challenge, not while an alarm is ringing. |
5. Camera, pose detection and step counting
Three challenges use a sensor, and they are the part of the app people most reasonably want explained, so here is exactly what happens.
Push-ups and jumps
The front camera preview is opened only while the challenge is on screen. Each frame is passed, on the device, to a pose-detection model that is bundled inside the app itself. The model returns body keypoint positions, a rep counter turns those into a number, and that number is all that reaches the rest of the app.
No frame is written to disk. No frame, keypoint set or pose is transmitted. The model is not downloaded and does not contact anything: it ships in the app package. When the challenge ends, the camera closes and nothing about it is retained.
QR scan
The camera is used to read the code you saved in advance. The decoded text is compared against your stored payload on the device. No image is kept and no scan is reported anywhere.
Walk
The walk challenge uses no camera. It reads the accelerometer and the phone's hardware step counter, counts steps against a cadence-gated detector, and discards the sensor readings as it goes. Only the step total for the current challenge is held in memory, and it is not recorded once the alarm is dismissed.
6. Children's privacy
Awake is not directed at children and is not designed for them. It collects no personal information from anyone, including children under 13, because it collects no personal information at all. If you believe a child has somehow provided personal information through this app, please contact the developer, though there is no store of such data to search.
7. Deleting your data
Because the data never leaves your device, deleting it is entirely in your hands and takes effect immediately:
- In the app. Open the profile screen and use the clear-all-data action. It wipes your alarms, statistics, settings and the current challenge session in one step.
- Uninstall. Removing Awake deletes its app storage, and with it everything listed in section 3.
- Android settings. Clearing the app's storage from Android's app info screen has the same effect.
There is no request to send and no waiting period, because there is no server-side copy for anyone to delete. The data deletion page walks through each route step by step, sets out exactly what every method removes, and gives you an address to write to if you would rather have confirmation from the developer.
8. Changes to this policy
This policy will be updated if the app's behaviour changes, and the "last updated" date at the top of the page will change with it.
One change that is being considered
Crash reporting is not in Awake 1.0.0. It may be added in a future version, because diagnosing an alarm that failed to ring is very hard without it. If that happens, this policy and the Play data safety declaration will be updated before the release ships, and the section above will stop saying that nothing leaves the device. Today, it does not.
9. Contact
Questions about this policy, or about anything the app does, go to ywalum@gmail.com. It is a single developer reading that inbox, so please be patient and be specific.
See also the terms of use and the support page.