Mom Alarm Clock — Privacy Policy

Last updated: October 13, 2026

Mom Alarm Clock is a family alarm and morning routine app designed for guardians (a parent or legal guardian) and children (ages 3–17). This policy covers the Mom Alarm Clock mobile app (“the App”), our website, and email update or waitlist forms that link to this policy. It explains what data we collect, why, and how we protect it.

Who We Are

Mom Alarm Clock is developed and operated by VARR Stack Technologies LLC. For questions about this policy, contact us at momalarmclock@gmail.com.

Data We Collect

Guardian Account Data

• Email address — On iPhone and iPad, a guardian may create an account with an email address and password; on Android, a guardian may protect the family with an email address and password. In both cases the email address and password are used for sign-in and account recovery and stored in Firebase Authentication. Protecting the family is optional: until the guardian does it, the Android app signs in anonymously and collects no email address.
• Display name — In the original iPhone app, shown in the app to identify the guardian. Stored in Firestore.

Child Profile Data

• Child's name — Display name set by the guardian. Stored in Firestore.
• Child's age — Used to tailor wake-up check difficulty and wording to the child's age. We store the age in years, not a date of birth. Stored in Firestore.

Alarm and Session Data

• Alarm schedules — Wake-up times, active days, verification settings. Stored in Firestore and locally on-device.
• Morning sessions — Records of each alarm event: when it fired, verification method used, whether it was approved, points earned. Stored in Firestore.
• Wake-up check results — The kind of check (such as a math, picture or pattern quiz, a tap, or a QR code scan), its difficulty, whether it passed, timestamps, and the responses needed to run and evaluate it. No photos, location, step-count, or motion data are collected by the original iPhone app.
• Bedtime sounds — In the iPhone, iPad and Android apps, while a bedtime sound plays on the child’s device, the app records which sound is playing, when it started and when it stops, and the volume, so the guardian’s phone can show it. Stored in Firestore.

Audio Data

• Voice alarm recordings — Guardians may optionally record a personal wake-up message attached to an alarm. The audio is stored in our Firestore database (or Firebase Storage in the original iPhone app), scoped to the family, encrypted in transit (TLS) and at rest, and readable only by members of that family.
• Voice messages — On iPhone, iPad and Android, a guardian may record a short voice message (up to 30 seconds, typically 120–180 KB) for one of a child’s mornings. In the original iPhone app, guardians and children can send each other voice messages. They are stored in our Firestore database (or Firebase Storage in the original iPhone app), scoped to the family, encrypted in transit (TLS) and at rest, and readable only by members of that family. How long they are kept is under Data Retention.
• Calendar and Reminders — On iPhone and iPad, a guardian can choose to copy a reminder or event into that phone’s own Reminders or Calendar. The app asks for access only when the guardian turns this on, adds only the items the guardian chose, and keeps the link to them only on that phone. The Android app keeps reminders and events inside the app and does not copy them into the phone’s own calendar.

Website, Waitlist, and Email Data

• Email address — If an adult chooses to join an Android waitlist or product-update list, we use the submitted email to send the requested updates. An app account is not automatically enrolled in marketing email.
• Signup and source data — Our email provider may process the form, confirmation status, signup time, referring page, and campaign parameters so we can honor the request and understand which signup source was used.
• Email engagement and preferences — Our email provider may record delivery, confirmation, unsubscribe, and message-engagement data needed to operate the list. Every marketing email will include an unsubscribe method.

The public landing page does not currently run Meta, TikTok, or Google advertising pixels. We will update this policy and provide any required choices before adding advertising tracking.

Location Data

• None. None of the apps request or collect any location data.

Photo Data

• Camera — In the new iPhone and iPad app and the Android app, requested on the child’s device for two optional features: scanning a family QR code to join, and the QR wake check; in the new iPhone and iPad app, also the photograph wake check (the Android app does not offer a photograph wake check). The original iPhone app does not use the camera. A photograph taken for a wake check is classified on the device by Apple’s Vision framework and then discarded — never uploaded, never saved, never shown to the guardian; only whether the requested object was recognised is recorded. The app does not request photo-library access.

Device and Diagnostic Data

• Crash reports — The original iPhone app and the Android app use Firebase Crashlytics to collect crash reports so we can identify and fix bugs. Reports may include technical device, app-version, performance, and crash-context data.
• Device and account identifiers — Firebase Authentication and other Firebase services generate identifiers (on Android, the anonymous sign-in identifier is the only account identifier until a guardian protects the family with an email address) used for authentication, app functionality, diagnostics, and analytics. They are not used for cross-app advertising.
• Push notification tokens — Used to deliver alarm notifications and guardian alerts. Tokens are stored in Firestore and rotated by the operating system.
• Usage analytics — We record product-interaction events such as pairing success, alarm firing, wake-check method and difficulty, and whether a wake check passed. We do not send them to an advertising network. Some are associated with your family identifier, so we can tell for example whether a family finished pairing — our App Store and Google Play privacy disclosures therefore treat product-interaction data as linked to you. Others are recorded with no family or account identifier at all. The original iPhone app includes the Firebase Analytics SDK, so Google receives app and device identifiers from it. The Android app includes it too but turns it on only on a parent’s phone; a child’s Android phone sends Google Analytics nothing. The current iPhone and iPad app does not include it. The App does not show ads, does not use an advertising identifier, and does not use this data to track you across other companies’ apps or websites.
• Feedback and diagnostics — In the original iPhone app, feedback can include your app build, iOS version, device type and the start of your family ID, if you leave the “Include device + build info” option on. The Android app’s feedback email includes the phone model, Android version, role, alarm-permission settings, whether the phone has a notification token, and the last wake-check result; you can read and edit the email before you send it. The iPhone and iPad app can send diagnostic reports with the family, device and alarm identifiers, the phone’s role, times, app and iOS details, and alarm state; names and custom labels are left out. It also records alarm timing for each armed morning (see Data Retention).

Data the App Does NOT Collect

• Date of birth (we store only the age in years)
• Any location data — coarse, precise, or distance-only
• Photographs. A wake-check photo is classified on the device and discarded; no image is uploaded or stored
• Step counts or motion data. The new iPhone and iPad app and the Android app read the motion sensor only during the shake wake game, on the device; the readings are not stored or sent.
• Browsing history
• Contacts or call logs
• Financial information
• Advertising identifiers
• Data from other apps on the device

Children's Privacy (COPPA Compliance)

Mom Alarm Clock is designed for use by families where a guardian manages the experience for children ages 3–17.

• Parental consent: A guardian must create an account and explicitly add each child. Children cannot create accounts independently.
• Child pairing: Children join the family using a time-limited code generated by the guardian. By creating this code and giving it to the child, the guardian consents to the collection of the child's data as described in this policy.
• Minimal collection: About a child, we collect only what the guardian enters (name, age, avatar, alarms, routine steps, reminders, bedtime, rewards, and any written or voice notes) and what the child’s device records during mornings and at bedtime: wake-up check results, reward requests, tamper alerts (such as volume lowered or notifications turned off), which bedtime sound played and when, and alarm-delivery diagnostics. During a wake-up check, the child’s device collects only the responses and result needed for the selected check.
• No advertising: We do not serve ads to children or use children's data for advertising.
• No social features: Children cannot communicate with anyone other than their guardian through the app.
• Guardian control: Guardians can view and modify all child data, and can delete it in the app or ask us to delete it (see Your Rights). Deleting the guardian account in the app deletes every child’s profile; our account deletion page lists what else it deletes in the iPhone, iPad and Android apps, and the records only an email request removes.

How We Use Data

App account, family, child, alarm, audio, and session data are used for app functionality, security, analytics, and support:

• Delivering alarms and verification challenges
• Calculating streaks, points, and rewards
• Sending push notifications to guardians about verification status
• Tailoring wake-up check difficulty and wording to the child's age
• Detecting and reporting tampering (e.g., device volume changes, permission revocation)
• Providing diagnostic information for support

We do not use child or family App data for advertising or email marketing, and we do not sell personal data. If an adult separately submits an email form, we use that email and related list data to send the requested waitlist or product communications, measure delivery and engagement, and honor subscription preferences.

Data Storage and Security

• Firebase: Account data, family data, session data and voice recordings are stored in Google Firebase (Firestore and Authentication, and Firebase Storage for voice audio in the original iPhone app) with encryption in transit (TLS) and at rest.
• On-device: On iPhone and iPad, local data is kept in the app's private container and encrypted by iOS Data Protection. On Android, local app data is kept in the app's private storage, which other apps cannot read; it is encrypted when the device's storage encryption is on, which is standard on devices that shipped with Android 10 or later.
• App Check: In the original iPhone app, Firebase App Check with App Attest verifies that requests come from legitimate app installations.
• Access control: Firestore security rules enforce family isolation — a person can only reach data inside their own family. A child’s device can write only a limited set of records: its mornings and reports, reward requests, receipts for messages it plays, and some fields of the family’s child profiles. Only our servers can change the records that time and deliver a guardian’s alerts. Rules changes are checked against an automated test suite before they are deployed.
• Our practices: Access to production data is limited to the operator of the service and protected by two-factor authentication. Data from the iPhone, iPad and Android apps is backed up daily with a seven-day retention window, and that database supports point-in-time recovery over the same window. The original iPhone app’s database has no scheduled backups. We review the app’s data handling before each release. We do not sell data and we do not use it for advertising.
• Breach notification: If we become aware of a breach affecting personal data, we will notify affected guardians by email where we have an address, and otherwise through the app, and any regulator required by law, without undue delay.

Data Retention

• Active accounts: Data is retained while the account is active.
• Session history: In the original iPhone app, limited to the most recent 500 sessions per child (older sessions are automatically deleted by a Cloud Function).
• Tamper events: In the original iPhone app, limited to the most recent 2,000 events per child.
• Account deletion: Deleting the account in the app, on iPhone, iPad, and the Android versions that offer it, permanently deletes the family data listed on our account deletion page, which also lists the records only an email request removes. In the original iPhone app, Delete Account deletes your children’s profiles but not all of the family’s data; email us and we delete the rest (see Your Rights). Deletion cannot be undone.
• Email lists: Waitlist and product-update data are retained until you unsubscribe, the list is retired, or you request deletion, subject to limited records needed to document consent, suppression, security, or legal obligations.
• Voice recordings: In the iPhone, iPad and Android apps, a wake-up message attached to an alarm is kept until the guardian replaces or removes it, or the alarm is deleted, and a message recorded for one particular morning is deleted automatically after that morning. In the original iPhone app, a child’s voice message is deleted after 72 hours; other recordings are kept until a new recording replaces them or you ask us to delete them (see Your Rights).
• Analytics events: Analytics events linked to your family: deleting the account in the app does not remove them; we delete them when you ask us by email (see Your Rights). Google Analytics data collected by the original iPhone app and by a parent’s Android phone is not linked to your account and cannot be deleted per family; Google keeps event-level data for the retention period set in our Analytics property.
• Diagnostics: Diagnostic reports — the ones you send, and the ones the iPhone and iPad app files automatically (on by default in TestFlight builds, off by default in the App Store build, and switchable in Settings) — are kept until you ask us to delete them; we do not yet delete them automatically. The alarm-timing records the iPhone and iPad app keeps for each armed morning are deleted when the child is removed or the account is deleted, in either app.
• Backups: Retained for seven days. Data deleted from the live database is removed from backups as those backups age out, within that window.
• Children’s data: We keep a child’s data no longer than is reasonably necessary for the purpose it was collected for, and delete it when that purpose is fulfilled. Deleting the account in the app deletes the child’s profile at once; our account deletion page lists what else it deletes, and we delete the rest when you ask by email (see Your Rights).

Data Sharing

We do not sell, rent, or share personal data with third parties. Data is processed by:

• Google Firebase — Cloud infrastructure provider (data processing agreement in place)
• Apple Push Notification service (APNs) — For delivering push notifications on iPhone and iPad
• Firebase Cloud Messaging — For delivering push notifications on Android, and for routing notifications to Apple’s push service on iPhone and iPad
• Google ML Kit — On Android, reads QR codes on the phone during a wake-up check; Google receives metrics about how the scanning feature performs
• Kit — Email form, confirmation, list-management, and product-update delivery provider for adults who choose to subscribe

Your Rights

• Access: See your children, alarms and recent mornings in the app; the original iPhone app also has History and Diagnostics screens. Email us for a copy of anything else.
• Correction: Edit child profiles and alarm settings at any time.
• Deletion: A guardian can delete the family’s data in the app, or ask us to delete it by email. In the Android app, deletion is in Account on the parent’s phone (version 8 and later); on an older Android version, email us. Our account deletion page shows where the controls are in each app, what each one deletes, and how to ask us. In the original iPhone app, Settings > Delete Account deletes your children’s profiles but not all of the family’s data; email us and we delete the rest.
• Data portability: Contact us to request an export of your data.
• Email choices: Unsubscribe using the link in an email or contact us to request access, correction, or deletion of waitlist and product-update data.

Changes to This Policy

We may update this policy as the app evolves. Material changes will be communicated through the app or via email. Continued use of the app after changes constitutes acceptance.

Contact

For privacy questions, data requests, or concerns:

• Email: momalarmclock@gmail.com