Privacy Policy
Last updated: July 2026
Alarmor does not sell your data. Does not run advertising. We collect anonymous usage analytics and crash reports solely to improve the app — never to profile or target you.
1. Overview
Alarmor is built on a simple principle: we only collect what is strictly necessary to provide and improve the service, and nothing more. We do not sell your data. We do not run advertising. We collect anonymous usage analytics and crash reports solely to understand how the app is used and fix bugs — never to profile or target you.
2. Information You Provide Directly
When you create an account using Google Sign-In or Apple Sign-In, we collect:
• Your account email address (used solely to identify your account) • Your display name, if provided by Google or Apple (used only to personalise the in-app experience)
We do not collect your phone number, physical address, or any other information beyond what you explicitly provide through the sign-in flow.
3. Information Generated on Your Device
If you use Alarmor without creating an account, no personal data leaves your device — all alarm data, mission results, streaks, and preferences are stored locally.
If you sign in, the following is additionally synced to the cloud so it can be restored on a new device:
• Alarm configurations (time, days, sound, mission type, difficulty, snooze settings) • Wake-up history (date/time, mission type, completion status), used to power your streak and stats • Your Alarmor Pro purchase status, verified via your app store receipt
App preferences such as dark mode and onboarding status are stored locally on your device only and are never synced.
We do not collect your name, physical address, contacts, calendar, or browsing history.
4. Automatically Collected Technical Information
When you use cloud sync, our backend (Supabase) records standard server-side connection metadata — such as IP address and request timestamps — as part of normal infrastructure logging. This is not queried or used to identify you individually; it exists simply as part of how any web-connected backend operates.
We use Firebase Analytics to collect anonymous, aggregated usage data (such as which screens and features are used) and Firebase Crashlytics to collect anonymous crash reports, both solely to understand app behaviour and fix bugs. Neither tool is used for advertising or cross-app tracking, and neither is linked to your account identity.
We do not collect your device's precise GPS location, advertising identifier (IDFA/GAID), contacts, calendar, or browsing history.
On the alarmor.app website only, we store a single first-party cookie named "alarmor_country" holding a two-letter country code (for example "IN" or "DE"). It is derived from the country your IP address resolves to, and its only purpose is to show Alarmor Pro pricing in your local currency. It contains no identifier, is not shared with anyone, is not used for advertising or tracking, and you can clear it at any time in your browser settings. We do not store your IP address for this purpose.
5. Sensor and Hardware Data
Certain missions use your device's camera, microphone, or motion sensors. In every case, this data is processed entirely on-device and is never transmitted to our servers or stored beyond the mission session:
• Camera — used only for the Barcode Scan, QR Code, and Word Hunt missions, to decode a barcode/QR value or recognise printed text. No images or frames are ever transmitted or stored. • Microphone — used only for the Blow to Dismiss mission, to measure audio volume in real time. Audio is never recorded or transmitted. • Accelerometer / Gyroscope — used for the Shake to Wake, Flip and Hold, and Squat Counter missions to detect motion. Motion data is processed in real time and is not stored or transmitted. • Pedometer (step count) — used only for the Step Walk mission, read directly from your device's step sensor. Not stored or transmitted beyond the local mission result.
6. How We Use Your Data
We use the information described above exclusively to:
• Operate the app — schedule alarms, run missions, and track completion • Restore your alarms, preferences, and Pro status when you sign in on a new device • Respond to support requests when you contact us • Understand aggregate usage patterns to improve the app (via Firebase Analytics) • Diagnose and fix crashes (via Firebase Crashlytics)
We do not use your data for advertising, profiling, automated decision-making, or any purpose beyond delivering and improving the core service, and we never sell or rent it to third parties.
7. Legal Bases for Processing (EEA/UK Users)
If you are located in the European Economic Area or the United Kingdom, we process your personal data on the following legal bases:
• Operating the app and providing core features — performance of a contract (Article 6(1)(b) GDPR) • Cloud backup and sync — performance of a contract • Account creation and authentication — performance of a contract / legitimate interest • Responding to support requests — legitimate interest • Anonymous analytics and crash reporting — legitimate interest, limited to aggregated, non-identifying data
8. Data Storage and Security
Account data is stored on Supabase, a PostgreSQL-based cloud platform with industry-standard encryption at rest and in transit. Access to the database is restricted to authenticated users who can only read and write their own data (row-level security). We do not store passwords — authentication is delegated entirely to Google and Apple. No storage method is 100% secure; in the event of a breach, we will notify affected users as required by applicable law.
9. Data Retention
Your data is retained for as long as your account is active. When you delete your account — via Settings → Delete Account in the app, or at alarmor.app/delete-account — all associated data (alarms, streaks, wake history, preferences, and account records) is permanently deleted from our systems immediately once the deletion is confirmed. Your App Store or Play Store purchase receipt is retained by Apple or Google independently of this; we have no control over that.
10. Third-Party Services
The App uses the following third-party services:
• Supabase (account sync) — stores your alarm data and wake history when signed in; see supabase.com/privacy • Google Sign-In / Apple Sign-In (authentication) — we receive only the email address and display name you authorise • Firebase Analytics (Google) — anonymous, aggregated usage analytics to understand app behavior • Firebase Crashlytics (Google) — anonymous crash reports to identify and fix bugs • Google Play Billing / Apple App Store — process your Alarmor Pro purchase and share a purchase receipt with us to verify Pro status; they do not share payment card details with us
This website (alarmor.app) separately uses Google Analytics to understand visitor traffic. No personally identifiable information is collected by it, and you can opt out via your browser's privacy settings or a Google Analytics opt-out extension.
We do not use advertising SDKs, the Facebook SDK, Mixpanel, Amplitude, or any data broker services.
11. Permissions Explained
The following permissions may be requested by the app, and are used only for what is stated here.
Android: • INTERNET — required for cloud backup, sync, and sign-in; never used if you don't have an account • RECEIVE_BOOT_COMPLETED — re-schedules your alarms after the device restarts • SCHEDULE_EXACT_ALARM / USE_EXACT_ALARM — fires your alarm at the precise time you set • WAKE_LOCK — wakes the processor briefly to launch your mission screen when the alarm fires • USE_FULL_SCREEN_INTENT — displays the mission screen over the lock screen • POST_NOTIFICATIONS — shows the alarm notification (Android 13+) • FOREGROUND_SERVICE / FOREGROUND_SERVICE_SPECIAL_USE — keeps the alarm-guard service running so alarms can't be silently killed by battery management • REQUEST_IGNORE_BATTERY_OPTIMIZATIONS — requests that Android not kill the alarm process • SYSTEM_ALERT_WINDOW (Display over other apps) — ensures the mission screen appears immediately when the alarm fires, even on Samsung, Xiaomi, Oppo, and other OEMs that otherwise block background launches • CAMERA, RECORD_AUDIO, ACTIVITY_RECOGNITION — used only for the specific missions described in "Sensor and Hardware Data" above
iOS: • Camera — Barcode Scan, QR Code, and Word Hunt missions only • Microphone — Blow to Dismiss mission only • Motion & Fitness — Step Walk mission only • Local Notifications — displays the alarm notification when the app is in the background
12. Children's Privacy
Alarmor is not directed at children under 13 (or 16 in the EEA). We do not knowingly collect personal data from children under these ages. If you believe a child has provided us with personal data, contact us at support@alarmor.app and we will delete it promptly.
13. Your Rights
Depending on your jurisdiction, you may have rights to access, correct, delete, restrict, or export your personal data, and to object to processing based on legitimate interest. To exercise any of these rights, email support@alarmor.app — we respond within 30 days. You can delete your account and all associated data at any time without contacting us, via Settings → Delete Account or alarmor.app/delete-account.
California residents (CCPA/CPRA): you have the right to know what personal information we collect, the right to delete it, the right to opt out of its sale (we do not sell personal information), and the right not to be discriminated against for exercising these rights.
EEA/UK users additionally have the right to lodge a complaint with your local data protection authority.
14. Changes to This Policy
We may update this Privacy Policy. Material changes will be communicated via the App or at alarmor.app/privacy. Continued use after the effective date constitutes acceptance.
15. Contact
For privacy-related questions, contact us at support@alarmor.app or via alarmor.app/contact.