Privacy at a glance
BlockWake does not require an account. Core alarm information, preferences, notes, and wake-up history remain on your device and are not sent to the developer by the current version. BlockWake contains no advertising or developer-operated behavioral analytics.
1. Introduction
This Privacy Policy explains how BlockWake handles information when you use the BlockWake Android application.
BlockWake is a local-first alarm application. It does not require you to create an account. Its core alarm, preference, and wake-up history information is designed to remain on your device rather than being sent to the developer.
2. Information stored on your device
BlockWake stores information needed to provide its features, including:
- Alarm Sequence names, enabled states, repeat days, dates, and schedules
- Individual alarm times and optional notes entered by you
- Selected ringtones, vibration patterns, and wake-up controls
- Theme and application preferences
- Dates on which you use Skip today
- Alarm events such as snoozes, dismissals, and response times used for local wake-up Insights
- Scheduling and reliability information needed to restore alarms after a restart, app update, clock change, or timezone change
This information is stored locally in BlockWake’s application storage and, where needed for restart recovery before first unlock, Android device-protected storage.
3. Information accessed on your device
To operate reliably, BlockWake may access limited device and system information:
- Your Android version, device manufacturer, and model, so the app can show relevant reliability guidance
- The state of notification, exact-alarm, full-screen alarm, and battery-related access
- The dedicated Android Alarm volume level, so the app can warn when it is muted or low
- Ringtone names or references made available by Android
- Current time, date, timezone, and selected repeat days
- Alarm lifecycle events, including ringing, snoozing, and dismissal, for local Insights
BlockWake uses this information on the device for application functionality and reliability guidance. The current version is not designed to transmit this information to the developer.
4. Information BlockWake does not collect
The current version of BlockWake:
- Does not require or provide a BlockWake account
- Does not collect your name, phone number, physical address, contacts, precise location, photos, messages, or advertising identifier
- Does not contain advertising
- Does not use alarm notes for advertising or profiling
- Does not include developer-operated behavioral analytics
- Does not sell or rent personal information
If BlockWake later adds accounts, cloud backup, analytics, crash reporting, advertising, or another network service, this policy and the Google Play Data Safety disclosure will be updated before that feature is released.
5. How local information is used
Information stored or accessed by BlockWake is used to:
- Schedule, ring, snooze, dismiss, and restore the alarms you create
- Show your next scheduled alarm
- Apply your selected theme, ringtone, vibration, and wake-up controls
- Calculate wake-up summaries from local alarm history
- Warn about system settings that may prevent an alarm from working as expected
6. Android permissions and special access
BlockWake may request or use the following Android capabilities:
- Notifications: to show alarm notifications and Android-supported fallbacks
- Exact alarms / Alarms & reminders: to trigger a user-created alarm at the selected time
- Full-screen alarm access: to present a ringing alarm over the lock screen when permitted
- Foreground service and media playback: to continue playing active alarm audio
- Vibration: to run the selected alarm vibration pattern
- Wake lock: to wake the device while an alarm is ringing
- Receive boot completed: to restore eligible alarms after a restart
- Battery optimization exemption: to let you request unrestricted alarm operation where Android allows it
- Internet access: used by the application framework and Google Play Billing. BlockWake does not use it to send alarm schedules, notes, preferences, or wake-up history to the developer.
Some manufacturers provide additional lock-screen, popup, auto-start, or battery controls. BlockWake may open a relevant Android settings screen, but you remain in control of those settings.
7. Google Play purchases
BlockWake may offer BlockWake Pro as a one-time purchase through Google Play. Google processes the transaction under its own terms and privacy policy. BlockWake receives product availability, localized pricing, purchase state, and entitlement information needed to unlock or restore Pro. The developer does not directly receive your full payment-card details.
9. Android system backup
The current BlockWake Android configuration disables application backup. Data from an earlier version or an external device-management tool may be subject to that provider’s behavior. The BlockWake developer cannot view or delete backups controlled by Android, Google, your manufacturer, or your organization.
10. Retention and deletion
BlockWake retains local information for as long as it remains in the app. You can delete alarms or Alarm Sequences individually, reset wake-up history without changing alarms, clear BlockWake storage through Android Settings, or uninstall the app to remove locally installed application data.
Because BlockWake does not operate user accounts or a developer-controlled alarm database, there is no BlockWake cloud account to delete.
11. Security
BlockWake limits its current data handling to information required for local alarm functionality. Android application sandboxing protects its application storage from ordinary access by other apps.
No storage method is completely risk-free. Maintain appropriate device security and avoid placing highly sensitive information in alarm notes.
12. Children’s privacy
BlockWake is a general alarm utility and is not designed to collect personal information from children. The current version does not require an account and does not knowingly transmit children’s personal information to the developer.
13. Changes to this policy
This policy may be updated when BlockWake’s functionality, data practices, legal requirements, or third-party components change. The effective date will be updated when revisions are published.
14. Contact
For questions, requests, or concerns about this policy or BlockWake’s data practices, contact: