Deepwake Privacy Policy
Deepwake is built to get heavy sleepers out of bed. Your alarms, missions and settings stay on your phone. The app sends us one kind of data automatically: technical failure reports, so we can find and fix problems with alarms on different Android phones. This page says exactly what that means. The same text is available inside the app under Settings › Privacy policy.
Why we collect it
To find crashes, late or missing alarms, failed sound or notifications, permission problems and unexpected Android behavior, and to fix them in the code.
What may be sent
- App version and build, phone manufacturer and model, Android version.
- The time a failure happened, and the planned and observed time of an alarm, but only when an alarm failed or was late.
- Technical error codes, the names of the code that failed and the error messages Android or the app produced, crash details, and relevant permission or background state.
- Pseudonymous identifiers for this installation and for the failure. The installation identifier is a random value created by Deepwake. It is not your advertising ID, Android ID or any hardware identifier.
Error messages come from the software that failed. In rare cases they can contain text you typed, and we do not filter them.
Sent later
Events are recorded on your phone when they happen and kept until they are delivered or replaced by newer events. Any upload happens later, outside an active alarm or mission, so reporting cannot delay waking you. Reports are sent over an encrypted connection to our own server. There is no switch to turn reporting off.
Never sent
Your alarm schedule and alarm labels, names you give tags or items, mission answers, camera images, sound recordings, contacts, your name or email address, or an advertising ID. Object recognition runs entirely on your phone.
Optional usage statistics
If you choose Help improve Deepwake, we may send which mission types are used and whether they complete, which features are opened, and aggregated use of Deepwake sounds. This helps us understand how the app is used and make better product decisions. Sharing is voluntary, and you can change your choice at any time in Settings.
How long we keep it
Failure reports are kept on our server for six months from the time they arrive, and are then deleted automatically. Deletion runs on a schedule, so a report can remain for up to one hour beyond the six months.
Who can see it
Only Deepwake's developer, for the purpose of fixing the app. We do not share reports with anyone else, and we do not use third-party crash reporting or analytics services. Reports are stored on a server we operate.
Deleting your reports
Request deletion of reports at data deletion form using your diagnostics ID from Settings › Privacy policy. The app can open the form with the ID filled in. An ID is created when the first report is sent. The request is processed manually.
Deepwake sounds
When you create an alarm sound with Deepwake, the description you type is sent to our server to produce the sound, and is kept together with the sound you saved. If you publish a sound to the Deepwake catalog, its name, the sound itself and how many people use it become visible to other users. Your description is not shown publicly. Sounds you download are stored on your phone so alarms never depend on the network.
Purchases
Deepwake PRO is sold through Google Play. Google handles payment and shares no payment details with us. To verify your purchase, our server receives the purchase token that Google issues for your order.
Privacy requests
The deletion form collects only your diagnostics ID. Closed requests are removed from the active database after 30 days when the request service is next used. Backup copies may remain until the backup is retired.