Mom Alarm Clock — Privacy Policy

Last updated: November 1, 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, iPad and Android, a guardian may protect the family with an email address and password. From version 2.3.0 of the iPhone and iPad app this is optional and can be done later: a guardian can create the family without one and add one later in the app’s Settings. Earlier versions of the iPhone and iPad app ask for an email address and password when the guardian signs up (a guardian whose account was set up before an email address was required can add one later). The email address and password are used for sign-in and account recovery and stored in Firebase Authentication. Until the guardian adds one, the app signs in anonymously and collects no email address. A child’s phone always signs in anonymously and is never asked for an 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.
• Look and routine — The emoji and colour chosen for the child, and any daily note and routine steps the guardian adds. Stored in Firestore.

Alarm and Session Data

• Alarm schedules — Wake-up times, the time zone the alarm is set in, 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.
• Tamper alerts — While a wake-up check is open (on Android, while an alarm is due), the child’s phone records events such as the volume being lowered or muted, notifications being turned off, the connection dropping, the phone’s clock or time zone being changed, the phone being locked, or the wake-up check being left, so the guardian can see them. On Android, a time-zone change records the new time-zone name (for example “Europe/London”). Stored in Firestore.
• 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 (up to 30 seconds) 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 and iPad, a guardian may record a short voice message (up to 30 seconds, typically 120–180 KB) for one of a child’s mornings. The Android app does not record messages for a single morning; on Android, a guardian’s recording is always a wake-up message attached to an alarm (above). In the original iPhone app, guardians and children can send each other voice messages; in the current iPhone, iPad and Android apps, children cannot record voice. 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.
• Notes — On iPhone and iPad, a guardian can attach a short written note (up to 500 characters) or voice note (up to 30 seconds) to an alarm or reminder for the child. Stored in Firestore, scoped to the family.
• Calendar and Reminders — Only on a guardian’s phone, and only if the guardian turns it on, the app can put copies of the family’s events or reminders into that phone’s own Calendar or Reminders; it asks for access only then. A copy shows the item’s title, times and notes, and can include the child’s name. The link to each copy is kept only on that phone. On iPhone and iPad, the guardian picks each reminder to copy. From version 2.3.1 of the iPhone, iPad and Android apps, a guardian can also have all the family’s events copied, including ones another guardian adds, and can leave any event out; the app updates or removes its copies when an item changes or is deleted in the app. Earlier Android versions copy nothing, and the Android app never copies reminders. From 2.3.1, the iPhone and iPad app asks for full Calendar access, which iOS requires before an app can update or remove an event it added; it looks up only the copies it added, by their identifiers, and never reads your other events or reminders. From 2.3.1, the Android app asks to read and change the calendar; it reads only the list of calendars on the phone (their names and accounts), so the guardian can choose one, and never reads calendar events. The app sends nothing from your calendar or reminders off the phone, but the account the copies are in (for example iCloud or Google) may sync them to its servers and your other devices.

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

• No location permission. None of the apps request location permission or collect GPS or other precise location.
• Approximate location estimated from the network — Google Analytics for Firebase, used in the original iPhone app and on a parent’s Android phone (it is switched off on a child’s Android phone), may estimate an approximate location, such as the country or city, from the device’s IP address for aggregated reports. We do not store IP addresses or that estimate with your family’s data.
• Time zone — The apps store the time zone an alarm or reminder is set in, so it rings at the right local time, and Android tamper alerts can record a time-zone name (see Tamper alerts). A time zone shows a region, not where someone is.

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, but if an alarm that asks for one reaches an Android child’s phone, the phone can complete it). 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 on iPhone and iPad, and by Google ML Kit image labeling on Android) 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 (on a parent’s phone only; it is switched off on a child’s phone, and stays off until a phone is set up as a parent’s) 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. The current iPhone and iPad app does not include Crashlytics.
• 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. The apps also create a random identifier for each installation, so the family’s records show which phone rings each alarm. They are not used for cross-app advertising.
• On-device recognition diagnostics — On Android, Google ML Kit, which a child’s phone uses for the QR wake check and, if one is ever required, the photo wake check, sends Google information about the device and app, a per-installation identifier, and performance, configuration and error events, for diagnostics and usage analytics. Camera images are not sent.
• Push notification tokens — Used to deliver alarm notifications and guardian alerts to every phone in the family. 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. In the iPhone and iPad app, 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 Android app records only daily counts, with no family or account identifier. 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.
• Ideas and feedback you send in the app — In the iPhone, iPad and Android apps, a guardian can send us an idea or feedback in writing (up to 500 characters), with an optional topic; we receive it with the app version, build and platform, linked to your family. A child can write an idea too (up to 300 characters), but it goes to the child’s guardian first and reaches us only if the guardian chooses to share it; we then learn that it came from a child, but not which child. Only we can read these; they are stored in Firestore.
• 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, on a parent’s or a child’s phone, opens an email to us in your own email app. It includes the app and Android versions, the phone model, the phone’s role, the result and time of the phone’s last check that its alarms are set, whether exact alarms, notifications, full-screen alarms and unrestricted battery use are allowed, when the alarm sound last started and stopped, whether the phone has a notification token, and a technical log of recent syncing with shortened alarm identifiers; names and account, family and child identifiers are removed. 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)
• Precise or GPS location, or distance data (see Location Data for the approximate location Google Analytics may estimate, and for time zones)
• 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. Our Terms of Service require guardians to be at least 18.
• 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, daily note, 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, ideas the child writes for the guardian, and alarm-delivery diagnostics. During a wake-up check, the child’s device collects only the responses and result needed for the selected check. Separately, on Android, Google ML Kit on the child’s phone sends Google the diagnostic data described under Device and Diagnostic Data.
• No advertising: We do not serve ads to children or use children's data for advertising or profiling for advertising.
• No social features: Children cannot communicate with anyone other than their guardian through the app. A child’s idea for the app reaches us only if the guardian chooses to share it.
• No disclosure: We do not disclose children’s personal information to third parties other than the service providers listed under Data Sharing, which process it for us.
• 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). A guardian can stop us collecting more information about a child at any time by removing the child or deleting the account in the app. 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
• Reading the ideas and feedback you send us, and measuring how the App is used so we can improve it

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.
• Where it is stored: For the iPhone, iPad and Android apps, the family database (Cloud Firestore) is stored in Google’s United States multi-region (nam5), and our server functions run in Google’s us-central1 region in the United States. If you use these apps outside the United States, that data is sent to and stored in the United States.
• 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. The Android app turns off Google Drive backup of its data.
• App Check: The original iPhone app uses Firebase App Check with App Attest to help verify 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 to its own family’s records, such as its mornings and alarm records, tamper alerts, bedtime sound status, reward requests, receipts for messages it plays, ideas for its guardian, diagnostic reports and usage counts, and some fields of the family’s child profiles (such as the child’s name and look). Only our servers write the records of the notifications we send. 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. In the iPhone and iPad apps, a message recorded for one particular morning is deleted automatically after midnight at the end of that day, and a note attached to an alarm or reminder is kept until the guardian removes it or the alarm or reminder is deleted. 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).
• Reminders: The iPhone and iPad app removes reminder history older than 90 days.
• Notification records: Our log of the notifications we send is deleted automatically after 30 days.
• 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.
• Crash reports: Google keeps Crashlytics crash reports for 90 days.
• 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.
• Ideas and feedback: Ideas and feedback you send in the app, and feedback emails, are kept until you ask us to delete them.
• 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: Authentication, Cloud Firestore, Cloud Functions and Cloud Messaging, plus Crashlytics and Google Analytics for Firebase where described above (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. A notification to a guardian can include the child’s name and the alarm’s name, and in the original iPhone app a notification can include the text of a family message, so that text passes through Google’s and Apple’s notification services
• Google ML Kit — On Android, reads QR codes on the phone during a wake-up check, and labels a wake-check photograph on the phone if one is ever required; images are not sent to Google; Google receives metrics about how these on-device features perform
• Kit — Email form, confirmation, list-management, and product-update delivery provider for adults who choose to subscribe
• Google (Gmail) — Emails you send us, including feedback emails and deletion requests, arrive in and are kept in our Gmail mailbox

Your Rights

Wherever you live, you can:

• 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.
• Stop collection about a child: Remove the child or delete the account in the app, or email us.
• Object or restrict: Ask us to stop, or limit, a use of your data, such as analytics.
• Withdraw consent: Unsubscribe from email lists at any time, and turn off the App’s access to the camera, microphone, Calendar or Reminders in your phone’s settings. Withdrawing consent does not affect what was done before.
• Email choices: Unsubscribe using the link in an email or contact us to request access, correction, or deletion of waitlist and product-update data.
• Complain: Tell us first if you like, at the address below. You can also complain to your local data-protection authority.

How to ask: email momalarmclock@gmail.com. A guardian makes requests for their children. To protect your family, we confirm the request comes from the family’s guardian, as described on our account deletion page. There is no charge. We will reply as soon as we can, and we complete a deletion request within 30 days of confirming it, as our account deletion page explains.

Changes to This Policy

We may update this policy as the app evolves, and we change the “Last updated” date at the top when we do. Material changes will be communicated through the app or via email. If the law requires your consent for a change, for example a new use of a child’s information, we ask for it first.

Contact

For privacy questions, data requests, or concerns:

• Email: momalarmclock@gmail.com