Summary
Hard Wake is an alarm app designed to make wake-up dismissal more intentional using user-scheduled alarms, wake-up challenges, wake routine tasks, task check-ins, optional cloud backup, optional invite-based shared follow-up features, website waitlist signups, and support requests. This policy explains what data is stored on your device, what data may be sent to service providers, and how account deletion works.
Hard Wake does not sell personal information. Hard Wake does not request location, contacts, microphone, SMS, phone-call, camera, or photo-library permissions in the current app code. Hard Wake does not use waitlist or support email addresses for third-party advertising.
Data Hard Wake stores locally
Hard Wake stores core alarm data on your device using local app storage. This includes alarm times, labels, repeat days, mission choices, Awake Check settings, wake routine tasks, custom task names, task completion or follow-up dates, onboarding status, active alarm state, wake-up history, cached premium status, and app preferences.
Motion samples from Shake, Soldier Walk, and Jump missions are processed locally for mission progress. They are not stored as raw motion recordings in a Hard Wake cloud database.
Data collected or processed by service providers
Some data is transmitted off your device when you use account, purchase, analytics, crash reporting, subscription, website waitlist, or support features. The table below summarizes the main data types reflected by the current app and website code.
| Data type |
How it is used |
Provider or destination |
| Name, email address, profile photo URL if provided by Google Sign-In, provider identifier, authentication tokens |
Account creation, sign-in, password reset, account display, and account security. |
Firebase Authentication and Google Sign-In when selected. |
| User ID |
Firebase account identification and RevenueCat entitlement matching. |
Firebase Authentication and RevenueCat. |
| App integrity and security signals |
Abuse prevention, App Check, API/Firebase resource protection, and request validation for cloud-connected features. |
Firebase App Check, Google Play Integrity, Firebase, and Google services. |
| Purchase and subscription status |
Trial, subscription, restore, premium entitlement, cancellation state, and product identifiers. |
Google Play Billing, Apple App Store, and RevenueCat. |
| Waitlist email address |
Waitlist confirmation, launch updates, occasional product emails, promotions, referral offers, sale notices, unsubscribe management, and list abuse prevention. |
Hard Wake website functions and Sender.net. |
| Support request details |
Responding to support requests and troubleshooting. This may include the name, email address, topic, and message you choose to submit. |
Hard Wake support inbox, website functions, and email delivery providers such as Resend. |
| Website and function request metadata |
Hosting, security, abuse prevention, rate limiting, and error diagnosis. This may include IP address, technical request headers, timestamps, and hashed network fingerprints in logs. |
Firebase Hosting, Cloud Functions for Firebase, Google services, and Hard Wake security logs. |
| Website page-view analytics |
Basic website measurement such as page views, referrers, approximate location, device/browser type, and engagement signals so Hard Wake can understand site traffic and launch interest. |
Google Analytics / Firebase web analytics. |
| Cloud backup data when backup is used |
Signed-in account backup and restore for alarms, labels, repeat days, mission choices, wake routine tasks, settings, wake history, and protected wake-flow state. |
Hard Wake Firebase/Firestore services for the signed-in account. |
| Companion invite and shared follow-up data when Companion is enabled |
Invite status, accepted companion relationship, selected missed-confirmation or routine follow-up alert details, title visibility setting, allowed Rescue actions, and timing context for user-approved shared follow-up alerts. |
Hard Wake services and notification providers used for Companion delivery when the feature is enabled. |
| Rescue Mode settings and action records when Rescue Mode is enabled |
Pre-approved action settings, missed-confirmation state, rescue-window timing, and action attempt records. |
Hard Wake services and third-party services needed to perform the selected action when the feature is enabled. |
| App interactions and analytics events |
Optional analytics for onboarding, permission checks, alarm actions, mission completion, paywall views, purchases, restores, and reliability events. |
Firebase Analytics when analytics is enabled. |
| Crash logs, diagnostics, device/app state, and SDK identifiers |
Crash investigation, Reliability diagnostics, fraud prevention, security, and app quality improvements. |
Firebase Crashlytics, Firebase SDKs, RevenueCat, Google Play services, and app store services. |
| Advertising ID or Android advertising services identifiers |
Analytics and measurement when made available by Google/Firebase SDKs. Hard Wake does not use this data to show ads in the app. |
Firebase/Google SDKs. |
Waitlist and support emails
If you join the waitlist, Hard Wake sends your email address to Sender.net so Hard Wake can confirm your signup, manage unsubscribes, and send launch updates plus occasional product, promotion, referral, or sale emails. You can unsubscribe using the link in those emails.
If you submit a support request, Hard Wake uses the details you provide to respond. Do not send passwords, payment card numbers, government IDs, health records, emergency information, or other sensitive information that is not needed for support.
Analytics and crash reporting
Firebase Analytics is optional in Settings. When enabled, Hard Wake logs product events such as onboarding, permission checks, alarm actions, mission completion, paywall views, purchases, and restores.
The Hard Wake website uses Google Analytics / Firebase web analytics for basic page-view and traffic measurement. Website analytics helps Hard Wake understand which pages are visited and whether launch interest is growing.
Analytics events are designed to avoid raw personal content. Hard Wake does not intentionally send alarm labels, passwords, exact location, photos, or user-entered sensitive text in analytics events.
The Firebase Analytics switch controls Analytics events only. Firebase Crashlytics may separately receive crash logs, stack traces, app version, operating system information, device state, and non-fatal error reports to help diagnose reliability issues.
Permissions and device features
Hard Wake requests notification, exact alarm, full-screen alert, vibration, wake lock, foreground service (including media-playback type for alarm audio), audio settings, lock-screen display (DISABLE_KEYGUARD), reboot completion, and battery optimization access where supported so user-scheduled alarms can appear clearly and close to the time you set.
Hard Wake alarm notifications are local notifications created on the device. Companion, Rescue Mode, cloud backup, account, purchase, support-form, analytics, and crash-reporting features may transmit limited account or event data when those features are used.
Hard Wake does not collect location data. Hard Wake does not use camera/photo challenge functionality in the current app. If photo-based challenges are added later, this policy should be updated before release.
Children's privacy
Hard Wake is not designed for children and is not intended to target users under 13. If you believe a child has provided account information to Hard Wake, contact support so the issue can be reviewed.
Retention and deletion
Local alarm data stays on your device until you delete alarms, reset local app data, uninstall the app, clear app storage, or delete your account from the Account screen.
Deleting your Hard Wake account removes the Firebase account, deletes account-linked cloud backup where available, and clears local Hard Wake alarms, routine tasks, custom task names, settings, active alarm state, and cached premium status from that device. Visit Account & Data Deletion for step-by-step instructions.
Cloud backups, Companion invites, alerts, relationships, timelines, rescue requests, and push tokens may use expiry fields and provider cleanup processes. Some purchase, fraud-prevention, tax, security, abuse-prevention, analytics, crash, or compliance records may remain with Apple, Google, RevenueCat, Firebase, or other service providers according to their own policies and legal requirements. Aggregated or deidentified analytics and diagnostics may also remain after account deletion.
Security
Hard Wake relies on platform security, Firebase Authentication, Firebase App Check, Google Play Integrity, API key restrictions, app store billing systems, encrypted network transport used by its service providers, and local device storage. No app or network service can promise perfect security.
Use a secure device passcode, keep your operating system updated, and do not share passwords or payment information with support.
International users
Hard Wake and its service providers may process information in the United States and other countries where Firebase, Google, Apple, RevenueCat, or related service providers operate.
Policy updates
Hard Wake may update this Privacy Policy when app features, service providers, legal requirements, or store requirements change. The "Last updated" date shows when this page was last revised.
Contact
For privacy questions, data requests, or support, use the Hard Wake Support Form.
