Local-first alarm data
HardWake stores alarm times, labels, repeat days, mission choices, Awake Check settings, onboarding status, and app preferences on your device.
HardWake does not sync alarm schedules, alarm labels, motion samples, photos, contacts, messages, microphone data, or precise location to a HardWake server.
Account and sign-in data
If you create or sign in to an account, Firebase Authentication processes the information needed for sign-in, such as your email address, display name, provider identifier, and authentication tokens.
Google Sign-In may provide your name, email address, and profile photo URL when you choose that option. HardWake uses that information for sign-in and account display only.
Purchases and subscriptions
HardWake uses RevenueCat together with Apple App Store or Google Play Billing to manage trial, subscription, restore, and premium-entitlement status.
HardWake receives entitlement status and product identifiers. Payment details are handled by Apple or Google and are not stored by HardWake.
Analytics and crash reporting
Firebase Analytics is optional in Settings. When enabled, HardWake logs product events such as onboarding, permission checks, alarm actions, mission completion, paywall views, purchases, and restores.
Analytics events are designed to avoid raw personal content. HardWake does not send alarm labels, photos, precise location, passwords, or user-entered sensitive text in analytics events.
Firebase Crashlytics may receive crash diagnostics, device/app state, and non-fatal error reports to help improve reliability.
Permissions
HardWake requests notification, exact alarm, full-screen alert, vibration, wake lock, foreground service, reboot, and battery optimization access where supported so alarms can appear clearly and close to the time you set.
HardWake uses motion sensors on device for Shake, Step, and Jump missions. Motion samples are processed locally for mission progress.
HardWake does not request location, contacts, microphone, SMS, or phone-call permissions.
Retention and deletion
Local alarm data stays on your device until you delete alarms, reset local app data, uninstall the app, or delete your account from the Account screen.
Deleting your HardWake account removes the Firebase account and clears local HardWake alarms, settings, active alarm state, and cached premium status from this device.
Some purchase, fraud-prevention, tax, security, or compliance records may remain with Apple, Google, RevenueCat, Firebase, or other service providers according to their own policies and legal requirements.
Contact
For privacy questions, data requests, or support, contact support@hardwake.app.