Effective date: 9 October 2026 · Last updated: 9 October 2026
The short version
WakeVault is an alarm clock with wake-up missions, an App Lock, private notes and a wake-up history. It is built to work entirely offline. Everything you create in the app stays on your phone.
No collectionWe do not collect, receive or store any of your data on our servers. We have no servers.
No internetThe released app does not request Android's Internet permission, so it cannot send anything over the network.
No sharing or sellingNothing is shared with, or sold to, anyone. There are no ads, analytics, trackers or crash reporters.
No accountNo sign-up, no email, no phone number. Your data is deleted when you delete it or uninstall the app.
1. Who we are
WakeVault ("the app", "we", "us") is published on Google Play by the developer named on the app's Play Store listing. This policy explains how the app handles information. Because the app works fully on your device and has no network access, the developer never receives your information.
2. Scope
This policy covers the WakeVault Android app (package com.wakemission) and all of its features: alarms and wake missions, App Lock (including Strict mode), Notes and History. It does not cover other apps you choose to protect with App Lock. Those apps have their own privacy policies.
3. Information the app handles on your device
The app creates and uses the following information only locally, in its private storage on your phone. Android does not let other apps read this storage. None of it is transmitted off the device.
3.1 Alarms and wake missions
The alarms you create: time, repeat days, label, sound, vibration, snooze settings, strict mode and the chosen wake mission (Math, Memory, Typing or Tap) with its difficulty.
Mission puzzles are generated on the device. Your answers are only checked on the spot and are never stored.
3.2 Wake-up history
For each alarm that rings: when it was scheduled and rang, whether you woke up, snoozed, missed it or stopped it, and how long you took. These records power the History tab and its statistics (streak, success rate, average time to wake).
3.3 Notes
The title, text, colour, pinned state and lock state of notes you write, with the time each was created and last edited.
Locked notes are hidden until you confirm it's you with your App Lock PIN, pattern or biometric, and are kept out of screenshots and the Recents screen. Their text is kept in the app's private storage. It is not separately encrypted beyond the encryption Android applies to your device storage.
3.4 App Lock
Your list of protected apps (their package names and display names).
Your PIN or pattern is never stored as typed. The app keeps only a salted verifier. It is computed with a key held in the Android Keystore that never leaves your device's secure hardware, and it can only be used to check a future entry.
Recovery code: shown to you once. Only a verifier of it is stored, never the code itself.
Biometrics (fingerprint / face): handled entirely by Android. The app never receives, sees or stores any biometric data. It only learns whether authentication succeeded.
Settings such as the re-lock policy, biometric on/off and Strict mode.
App Lock history (can be turned off and cleared in the app): events such as "lock shown", "unlocked with PIN", "incorrect attempt" or "permission turned off", with the time and the name of the protected app concerned. It never contains what you typed. Viewing it requires your PIN, pattern or biometric.
Foreground-app detection: with your permission ("Usage access"), the app checks which app is currently on screen, so it can show the lock when a protected app opens. With Strict mode on, this also covers the system Settings app and the app installer. This information is read in real time on the device and immediately discarded. The only things recorded are the App Lock history events above, which concern your protected apps.
Installed apps list: to let you choose which apps to protect, the app lists the apps that appear in your launcher, with their icons (icons are cached in the app's private cache). It does not use the broad "query all packages" permission.
3.5 Technical state
Small technical records the app needs to work reliably, for example the next scheduled alarm time, internal event logs used to keep the alarm engine and the screen in sync, and whether App Lock protection is expected to be running. These stay on the device.
We do not collect your name, email address, phone number, contacts, location, photos, files, messages, advertising ID, device identifiers or browsing activity.
4. What we do not do
We do not transmit any data. The released app has no Internet permission.
We do not use advertising, analytics, attribution, crash-reporting or tracking software development kits (SDKs).
We do not sell, rent, trade or share data, and we do not use it for advertising or profiling.
We do not back up your data to the cloud. Android cloud backup and device-to-device transfer are turned off for this app, so your alarms, notes, history and App Lock data are not copied to Google Drive or another phone.
We do not use Android's Accessibility service, and we do not read the content of other apps' screens.
5. Android permissions and why we ask for them
Permissions marked "you grant" are only requested when you turn on the feature that needs them, after an explanation in the app. You can revoke any of them at any time in Android Settings. The related feature then stops working, and the app tells you so.
Plays the alarm sound reliably, and keeps App Lock protection running while it is turned on.
Keep awake (WAKE_LOCK) and vibration (VIBRATE)
Keeps the phone awake while the alarm rings and vibrates for the alarm.
Usage access (PACKAGE_USAGE_STATS) · you grant
App Lock only: detects which app is on screen, so the lock appears when a protected app opens. Read on the device only; never stored or sent (see 3.4).
Display over other apps (SYSTEM_ALERT_WINDOW) · you grant
App Lock only: shows WakeVault's own, clearly labelled lock screen on top of a protected app the moment it opens.
Biometrics (USE_BIOMETRIC, USE_FINGERPRINT)
Optional fingerprint or face unlock through Android's system prompt. No biometric data reaches the app.
Ignore battery optimisation (REQUEST_IGNORE_BATTERY_OPTIMIZATIONS) · you grant
Asks you, through Android's own dialog, to let WakeVault run in the background, so battery savers do not silently stop alarms or App Lock.
The list may also show com.wakemission.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION. Android adds this internal permission automatically so the app's own components can talk to each other privately. It grants no access to anything.
6. Storage, retention and deletion
All information stays in WakeVault's private storage on your phone for as long as you keep it. You are always in control:
Alarms and notes: delete them individually in the app.
App Lock history: turn history off, or clear it, in App Lock → Settings / History.
All App Lock data (PIN/pattern verifier, recovery verifier, protected apps, history, settings): App Lock → Settings → Reset App Lock.
Everything: uninstall WakeVault, or use Android Settings → Apps → WakeVault → Storage → Clear storage. This permanently deletes all of the app's data from your phone. Because nothing is stored anywhere else, it cannot be recovered afterwards.
We cannot access, export, restore or delete your data for you, because we never have it.
7. Security
Data lives in the app's private storage, isolated from other apps by Android and protected by your device's storage encryption.
App Lock credentials are stored only as salted verifiers bound to a key in the Android Keystore. Repeated wrong attempts trigger growing delays.
App Lock data is kept in storage that becomes readable only after you first unlock your phone following a restart.
Sensitive screens (App Lock settings, protected-app list, App Lock history, locked notes) are kept out of screenshots and the Recents screen.
App Lock adds privacy within your phone. It is not a substitute for your device's own screen lock, and it cannot hide notifications or widgets from other apps.
No method of storage is 100% secure. If your phone is lost, or someone knows your PIN, data on it may be exposed. Please keep your device screen lock enabled.
8. Sharing and disclosure
We do not share information with anyone, including service providers, advertisers or partners. Because we do not hold any of your information, we have nothing to disclose in response to requests from third parties or authorities.
9. Children
WakeVault is a general-audience utility and is not directed at children under 13. It does not knowingly collect personal information from anyone, including children, since it collects no information at all.
10. Your rights
Depending on where you live (for example under the GDPR in the EU/UK or the CCPA/CPRA in California), you may have rights to access, correct, delete or port your personal data, and to object to or restrict its processing. Since all data is held only on your device, you can exercise these rights directly in the app (view, edit or delete) or by uninstalling it. We do not sell or share personal information as defined by the CCPA. If you have a question about your rights, contact us using the details below.
11. Changes to this policy
If a future version of the app changes how it handles information (for example by adding an optional feature that uses the internet), we will update this policy and its effective date before that version is released. Where the law requires it, we will also tell you in the app or ask for your consent.