Privacy
WakeSage Privacy Policy
Last updated: April 10, 2026
WakeSage is an Android alarm app built for reliable wake-up delivery. It does not run a user account system, does not sell user data, and does not include advertising or analytics SDKs.
The app is designed so core alarm behavior remains local on-device and local-first whenever possible. WakeSage primarily stores settings, alarm schedules, ring histories, and accountability audit records in local app storage.
We keep data only as long as needed for normal app function. You can remove your data by uninstalling the app or deleting your local session records in the in-app settings.
What WakeSage collects
WakeSage data types are narrowly scoped to alarm behavior:
- Alarm schedule settings and repeat patterns
- Readiness-test history and wake outcome summaries for the current device
- Optional accountability contact selections
- Optional proof interaction metadata that stays tied to wake outcomes
Proof methods are optional and only enabled by you (for example, camera/QR workflow and NFC proof station flow where supported).
What WakeSage does not collect
- No account profile or authentication identity
- No ad or analytics tracking SDK
- No geolocation service
- No remote contacts sync or cloud backup of your alarm data
Permissions and device access
WakeSage may request permissions needed for alarm reliability and optional accountability features:
- Exact alarm and notifications for scheduling and wake delivery
- Vibration and full-screen alarm handling where allowed by your device
- Optional camera access for QR-based proof workflows
- Optional NFC access for NFC proof stations
If you deny an optional permission, wake flow continues with available fallbacks.
Contact
For privacy questions, email support@wakesage.com.
For a plain-language explanation of the same model, read WakeSage privacy and local-first design.