Legal
Privacy Policy
Last updated: September 19, 2026
1. Introduction
SnoozeWar is operated by Himanshu Lal, an individual (sole proprietor) based in India ("SnoozeWar," "we," "us," or "our"). We operate the SnoozeWar mobile app, currently available on Android through Google Play (an iOS version is in development), and the websites snoozewar.com and snoozewar.app (together, the "Service").
This Privacy Policy explains what information we collect, what stays on your phone, what leaves it, why, who helps us process it, and the choices you have. We have tried to describe what the app actually does, in plain language.
By downloading, installing, or using the Service, you acknowledge that you have read this Privacy Policy. If you do not agree with it, please do not use the Service.
2. Data Controller
Himanshu Lal, trading as SnoozeWar, is the data controller responsible for your personal data. For any privacy question or request:
- Email: privacy@snoozewar.com
- Website: snoozewar.com
3. The Short Version
- Stays on your phone: your alarms and their settings, your detailed sleep sessions and any Health Connect sleep records, your screen-time and app-usage details, the apps you choose to block, your mission photos, your diagnostic log, and the rhythm estimate shown on your profile.
- Stored with your account: your sign-in details, name, avatar choice, onboarding answers, basic device details, and a daily history of your consistency scores, so your progress survives a new phone or a reinstall.
- Sent to service providers: usage analytics (which you can turn off), crash reports, subscription status, and approximate location for the weather card.
- Never: we do not sell your data, we do not show ads, and we do not use an advertising ID.
4. Information We Collect
4.1 Account Information
- Sign-in details: When you create an account, we collect the sign-in method you choose: your phone number (verified by a one-time SMS code through Google Firebase Authentication) or your Google account's name, email address, and profile photo link. Apple sign-in will be offered on iOS.
- Before verification: When you request an SMS code, the phone number you entered and the country you selected are sent to our analytics provider (PostHog), before the code is verified, so we can diagnose sign-in problems such as codes that never arrive. This record is kept for up to 12 months or until you delete your account, whichever is sooner.
- Analytics profile: Once you are signed in, your account identifier and the details you signed in with (display name, email address, phone number, sign-in method, and sign-up date) are attached to your profile at PostHog, so we can recognise your account when you contact support and understand how real accounts use the app. These details are removed from that profile when you delete your account; the remaining usage events stay linked only to a pseudonymous identifier.
4.2 Information You Give Us
- Profile: your display name, your avatar choice, and your analytics choice (allowed or not).
- Onboarding answers: what you want to fix (waking up, sleeping on time, or both), the obstacles you select, your birth year, your usual sleep need, and the features you tell us you want, including any wish you type in. These are stored with your account and help us personalise the app and decide what to build.
- Feedback: when you send feedback or a bug report in the app, we store your message, the area and type you picked, your account identifier, your name, phone number, and email address (whichever your account has), and your phone's platform and OS version.
- Support messages: anything you send us by email or WhatsApp.
- Website feedback form: if you use the form on snoozewar.com, your message and any email address or phone number you add are delivered to our inbox by our form provider, Web3Forms.
4.3 Information Collected Automatically
- Consistency history: for each day, whether an alarm and a bedtime were set, your bedtime, and the day's score on seven checks: woke on time, slept enough, kept your bedtime, kept your phone down in your sleep window, the alarm rang, a bedtime was set, and you opened the app. Some of these checks are worked out on your phone from your sleep and phone-use data; only the resulting scores are stored with your account, for up to 400 days, so your history can be restored on a new phone.
- Streak and plan: your current streak and whether you have Premium.
- Device details: device model, brand and manufacturer, operating system and version, app version, time zone offset, and when the app was last opened. We use these to support your phone, fix device-specific problems, and keep alarms reliable.
- Usage analytics: screens you view, features you use, and actions you take (for example setting an alarm, finishing a mission, or changing a bedtime), plus summary settings such as how many alarms you have, your main mission, and which reliability options are on. Some events include an approximate sleep duration (for example when a night is detected or logged), your birth year, and the onboarding answers above. See Section 6 for how to turn analytics off.
- Session replays: if analytics is allowed, we may record how you move through the app's screens to find confusing moments. Text you type and images are masked. Other text shown on screen, such as your name or sleep times, may be visible in a replay.
- Crash and performance data: crash reports, error messages, app start times, and performance measurements, linked to your account identifier.
- Device identifiers: Firebase generates an installation identifier and a device-integrity token (Firebase App Check with Google Play Integrity) used only to run the app and protect it from abuse. We also use pseudonymous analytics identifiers. None of these are advertising identifiers; the advertising ID permission is removed from the app.
- Approximate location: only if you allow location for the weather card. We use coarse location, round the coordinates to about 1 km, and send them to our weather providers (Section 7). We never request precise GPS location and do not store your location.
4.4 Information That Stays on Your Phone
The following is processed on your device and is not uploaded to us or our service providers, except for the specific summaries named in Section 4.3:
- Alarms and reminders: your alarms, missions, sounds, wallpapers, reminders, and bedtime settings.
- Sleep: your sleep sessions, whether detected by the app, read from Health Connect, or logged by hand. Health Connect access is read-only; we never write to it.
- Rhythm estimate: the rhythm shown on your profile is calculated on your phone from your sleep history.
- Screen time and app usage: which apps you use and for how long, your installed apps, and the apps you choose to block.
- Watchdog signals: if you turn on Watchdog, it uses your phone's sleep detection, step counter, motion sensors, and screen activity to check that you got up. These signals stay on your phone.
- Mission photos: the reference photo for the Photo mission and the photo you take in the morning are compared on your phone by an on-device model. They are not uploaded.
- Diagnostic log: a technical log of alarm, bedtime, and sleep events kept on your phone. It can include alarm labels, the names of apps opened during bedtime blocking, and text you typed during a mission. It is only shared if you choose "Send diagnostic log" and pick where to send it.
5. Sleep and Wellness Information
Information about your sleep and your sleep habits can be health information under laws such as the EU General Data Protection Regulation (GDPR) Article 9. We handle it with extra care:
- Detailed sleep records stay on your phone (Section 4.4).
- What leaves your phone is limited to: your onboarding answers and birth year, the daily consistency scores in Section 4.3, and approximate sleep durations in analytics events if analytics is allowed.
- We never sell this information, never share it with advertising networks, and never use it for advertising or marketing.
- Our analytics providers process it only on our behalf, under data processing terms, with advertising features turned off.
- You can turn off analytics at any time (Section 6) and delete your account and its data at any time (Section 10).
6. Your Analytics Choice
- In the EEA and UK, analytics and session replays stay off until you agree on the consent screen.
- Elsewhere, analytics is on by default and you can turn it off.
- Changing your mind: in the app, go to Settings, then Data and privacy. When analytics is off, we stop sending usage events, session replays, and analytics error reports.
- Always on: crash reports and performance monitoring stay on, because we need them to keep alarms working. They do not include your sleep data.
7. Who We Share Data With
We do not sell your personal data. We do not show advertisements and do not share data with advertising networks. If we ever introduce ads, we will update this Policy first, and ads will never be targeted using sleep or wellness information.
We use these service providers, who process data on our behalf:
- Google Firebase (Google LLC): sign-in (Authentication), account and feedback storage (Firestore), usage analytics (Analytics), crash reports (Crashlytics), performance monitoring (Performance), and abuse protection (App Check).
- PostHog: usage analytics, session replays, and error tracking, hosted in the United States.
- Sentry (Functional Software, Inc.): crash and error reports.
- RevenueCat: checks and manages your subscription status. It receives your account identifier and your Google Play purchase details.
- Google Play: app distribution, payments, in-app review prompts, and in-app updates. We never receive your card details.
- Open-Meteo and OpenWeatherMap: weather for your approximate location, only if you use the weather card. Open-Meteo is used first; OpenWeatherMap is a fallback. No account information is sent.
- Speech recognition on your phone: the Speak or Type mission uses your phone's speech recognition. Where your phone supports on-device recognition, audio stays on the phone. Otherwise your phone's speech service (on most Android phones, Google's) may process the audio over the network. We do not record, store, or upload your voice, and the recognised words are discarded after the check.
- jsDelivr: serves the avatar images in the app, so it sees your IP address when they load.
- Web3Forms: delivers messages sent from the feedback form on our website.
- Vercel: hosts our website and keeps standard server logs, such as IP addresses.
We may also disclose information:
- To legal authorities, when required by law, court order, or a valid government request.
- In a business transfer, such as a merger, acquisition, or sale of assets. We will tell you before your data becomes subject to a different privacy policy.
8. Legal Basis for Processing (EEA and UK)
- Contract (Article 6(1)(b)): to provide the Service, including your account, sync, alarms, feedback, and subscriptions.
- Consent (Article 6(1)(a)): for analytics and session replays in the EEA and UK, for approximate location, and for optional permissions such as Health Connect, the microphone, and the camera. Where sleep or wellness information is involved, we rely on your explicit consent (Article 9(2)(a)). You can withdraw consent at any time.
- Legitimate interests (Article 6(1)(f)): crash reporting, performance monitoring, security, and fraud prevention, which keep the Service working and safe.
- Legal obligation (Article 6(1)(c)): where the law requires us to keep or disclose information.
9. Data Storage, Security, and Retention
- Security: data is encrypted in transit (TLS) and encrypted at rest by our cloud providers. Access to our systems is limited to what is needed to run the Service.
- Active accounts: we keep account data for as long as your account exists.
- Inactive accounts: if an account is unused for 24 months, we may delete or anonymise its data after notifying you.
- Analytics and crash data: kept under our providers' retention settings, linked to a pseudonymous identifier.
- Feedback and support messages: kept as long as needed to help you and improve the Service, and deleted with your account.
- Anonymised data: statistics that no longer identify you may be kept for longer.
10. Deleting Your Account
You can delete your account at any time in the app: open your Profile and tap Delete account. You can also email privacy@snoozewar.com or follow the steps at snoozewar.com/delete-account.
When you delete your account, we delete your sign-in account, your account record (including your consistency history and onboarding answers), and your feedback, remove your name, email address, and phone number from your analytics profile, and clear the app's data from your phone.
Some records stay after deletion:
- Usage events and crash reports: stay with our providers under a pseudonymous identifier until their retention period ends.
- Purchase records: Google Play and RevenueCat keep purchase records as required for billing and tax.
- Email requests: if you ask by email, we complete the deletion within 30 days of verifying the request.
11. Your Rights
Depending on where you live, you may have the right to:
- Access a copy of the personal data we hold about you.
- Correct inaccurate or incomplete data.
- Delete your personal data.
- Restrict or object to certain processing.
- Receive your data in a portable, machine-readable format.
- Withdraw consent at any time, without affecting processing that happened before.
- Complain to your local data protection authority.
To use any of these rights, email privacy@snoozewar.com. We will respond within 30 days, or sooner where the law requires.
12. California Privacy Rights (CCPA/CPRA)
If you live in California, you have the right to know what personal information we collect, use, and disclose; to request deletion; to correct it; and not to be discriminated against for using these rights. We do not sell or share personal information for cross-context behavioural advertising, so there is nothing to opt out of.
13. International Data Transfers
We are based in India, and our service providers process data in other countries, mainly the United States. When personal data from the EEA or UK is transferred, we rely on appropriate safeguards such as the European Commission's Standard Contractual Clauses.
14. Children's Privacy
The Service is not intended for children under 13, or under 16 in the European Economic Area. We do not knowingly collect personal information from children under these ages. If you believe a child has given us personal information, contact privacy@snoozewar.com and we will delete it.
15. Notifications
The app uses notifications on your phone for alarms, reminders, bedtime and wind-down reminders, and occasional tips such as a weekly summary. These are scheduled on your phone; we do not currently send push notifications from a server. You can manage notifications in your phone's settings, but turning them off can stop alarms and reminders from working.
16. Permissions We Request
We ask for each permission when you use the feature that needs it, and explain why.
- Notifications, alarms and reminders, full-screen alerts: so alarms and reminders ring on time, including when the app is closed or the phone is locked.
- Display over other apps: to show a ringing alarm on top of whatever is open, and, if you choose Full enforcement, to show the bedtime block screen. It cannot see what is inside other apps.
- Accessibility service (optional): used only for the bedtime block and Resist escape. It detects which app is in the foreground so it can cover it at bedtime or bring you back to a ringing alarm, including when the power menu, phone settings, or the uninstall screen is opened while a Resist escape alarm is ringing. It is configured so it cannot read screen content, and it only sees app names. It runs on your phone and you can turn it off at any time in Android settings.
- Device admin app (optional): used only for Prevent uninstall. While it is on, Android will not uninstall SnoozeWar. We ask for no device admin powers: it cannot lock your phone, erase it, change your password, or read anything, and it collects and sends no data. You turn it on yourself: the app first explains what it does, then Android shows its own confirmation screen. The app turns it off by itself when no active alarm or bedtime uses it, when your Premium ends, and when you sign out. You can also turn it off at any time in the app or in Android settings under Security, Device admin apps, and then uninstall as normal.
- Usage access (optional): for the screen-time report, the apps-in-your-sleep-window report, bedtime blocking, and Watchdog. Usage details stay on your phone (Section 4.4).
- Health Connect sleep access (optional): read-only access to sleep sessions to show your sleep. The records stay on your phone.
- Physical activity (optional): for sleep detection, the Walk mission, and Watchdog's step check. Step counts stay on your phone.
- Motion sensors: for the Shake mission, pick-up detection, and Watchdog. Readings stay on your phone.
- Camera (optional): for the Photo mission. Photos stay on your phone.
- Microphone (optional): for the Speak or Type mission. See Section 7 for how speech recognition works.
- Photos (optional): only if you choose your own alarm wallpaper. The image stays on your phone.
- Approximate location (optional): for the weather card.
17. Our Website
Our websites do not use advertising cookies, tracking pixels, or third-party analytics. Our hosting provider keeps standard server logs, and the feedback form sends your message through Web3Forms (Section 7).
18. Third-Party Links
The Service links to other services, such as Google Play, WhatsApp, social media profiles, and research papers. Their privacy practices are governed by their own policies.
19. Changes to This Privacy Policy
We may update this Privacy Policy as the Service changes. When we make material changes, we will update the "Last updated" date above and tell you in the app. Where the law requires, we will ask for your consent again.
20. Contact Us
For any question, concern, or request about this Privacy Policy or your personal data:
- Email: privacy@snoozewar.com
- Website: snoozewar.com
If you are in the EEA or UK and are not satisfied with our response, you can complain to your local data protection authority.