Privacy Policy

Last updated: September 30, 2026

This Privacy Policy explains how uAlarm handles information when you use the uAlarm mobile application, ualarm.app, and related services.

uAlarm is designed so that information that does not need to leave your device is processed on your device. Other information is stored or processed by our service providers when necessary to provide account backup, sign-in, purchases, subscriptions, regional payment options, and other online features.

This Privacy Policy applies to versions of uAlarm that link to it. Data handling may vary by platform, region, distribution channel and the features you use. If a future version materially changes what information uAlarm collects, uses or discloses, we will update this Privacy Policy before that processing begins.

1. Information processed on your device

Many uAlarm features operate entirely on your iPhone.

Your alarms, alarm schedules, mission configuration, local settings, downloaded sounds and themes, and other app state are stored on your device. Some of this information is also backed up to our servers as described in Section 2.

Camera-based missions, including push-ups, squats, jumping jacks and object-recognition missions, are analyzed on your device using Google ML Kit. uAlarm does not upload camera frames, photographs, video or detected body landmarks to its servers.

Walking and shake missions use motion, accelerometer or pedometer information on your device. Raw motion and sensor readings are not uploaded to uAlarm.

Math, memory and typing missions do not require camera or motion data.

When you register a QR code, barcode or NFC tag for a mission, uAlarm stores a one-way hash of the registered value rather than the original QR code, barcode content or NFC identifier.

Google ML Kit operates as an on-device SDK. According to Google's SDK privacy disclosures, ML Kit may process or report limited technical, diagnostic, performance or device-related information for operation and maintenance of the SDK. uAlarm does not use ML Kit to send your camera content to Google.

2. Account, backup and synchronization data

uAlarm automatically creates an anonymous account when the app is first used. You do not need to provide a name, email address or social sign-in to create this account.

The anonymous account gives uAlarm a random account identifier so that server-backed features can operate before you choose to sign in.

The information that may be stored in your uAlarm backup includes:

The backup begins while the account is anonymous.

If you never link the anonymous account to Apple or Google and later uninstall the app, the anonymous credentials stored on the device are lost. In that situation, the backup cannot be restored to you because there is no Apple, Google or email identity linked to that anonymous account.

If you want an anonymous account and its backup removed, use Settings → Account → Delete Account before uninstalling the app.

3. Apple and Google sign-in

Signing in with Apple or Google is optional for ordinary alarm use.

When you sign in from an anonymous uAlarm account, uAlarm normally links the Apple or Google identity to the account you are already using. The uAlarm account identifier, backup, subscription and other account data remain with the same account.

We do not intentionally create a second uAlarm account merely because you link Apple or Google.

If the Apple or Google identity you choose is already associated with another uAlarm account, uAlarm may ask you to use that existing account or contact support. We do not silently abandon a paid anonymous account in order to switch to another account.

Apple or Google may provide us with an account identifier and profile information made available through their sign-in service, such as an email address and, depending on the provider and your choices, a name or profile image. We use this information for authentication, account recovery and displaying account information inside uAlarm. We do not use it for advertising.

4. Signing out

Signing out is different from deleting your account.

When you sign out, uAlarm removes local alarms, statistics, settings and cached subscription information from that device and returns the app to onboarding.

Your server-side uAlarm account and backup are not deleted merely because you sign out. They can become available again when you sign in to the same account.

If you want the server-side account and associated data removed, use Delete Account instead.

5. Location and regional payment options

uAlarm uses your country or region to determine which storefront, currency and payment options should be shown.

Normally, uAlarm determines your country from network information. When the app contacts our regional storefront service, Cloudflare derives a country-level result from the IP address used for the connection.

uAlarm does not store that IP address in its application database for this purpose.

If network-based country detection fails, uAlarm may request permission to use your location while the app is in use. The app obtains a location fix and uses it as a fallback to determine your country or region.

uAlarm does not store your raw latitude or longitude in its database and does not send those raw coordinates to the uAlarm backend.

You may decline location permission. Location is not used for advertising, behavioral profiling or tracking your movements.

6. Payments and subscription information

Available payment methods depend on your region, platform and distribution channel. The sections below describe payment methods currently supported by uAlarm. If a future distribution channel introduces a different payment provider or materially different data processing, we will update this Privacy Policy before that processing begins.

App Store and Google Play purchases. Where in-app purchase is offered in the version of uAlarm you use, Apple or Google processes the payment.

uAlarm does not receive your payment card number or complete payment credentials.

uAlarm uses RevenueCat to validate store purchases and to determine whether Pro or Premium is active. For this, RevenueCat receives your uAlarm account identifier (the same identifier that names your backup), the store's purchase receipt or token, the product purchased, and its subscription or entitlement status, including renewals, expirations, cancellations and refunds reported by the store. It does not receive your name, email address or payment details. Because the purchase is linked to your uAlarm account identifier, it can be restored on another device by signing in with the same account.

Payme payments. In Uzbekistan, uAlarm may offer payment through Payme.

The app displays your uAlarm payment ID (7 digits; an older 12-digit number, where one exists, also remains valid). You open Payme separately and make the payment through Payme. uAlarm does not receive or process your payment card number.

Payme communicates with uAlarm's Merchant API to create, confirm, check, cancel and reconcile payments.

For Payme transactions, we may store:

A refund or cancellation may change your entitlement and the time remaining on Pro.

Click payments. In Uzbekistan, uAlarm may also offer payment through Click, the payment app of CLICK LLC.

You open the Click app separately, find uAlarm, enter your uAlarm payment ID and the amount, and make the payment inside Click. uAlarm does not receive or process your payment card number.

Click communicates with uAlarm's API, which Click calls the SHOP API, using two requests for each payment: a request to check and prepare the payment, and a request to complete it.

For Click transactions, we may store:

Click does not notify uAlarm of refunds. A refund or reversal of a Click payment is initiated by uAlarm through Click and then recorded, after which your remaining entitlement is recalculated from valid payment records. A refund or cancellation may change your entitlement and the time remaining on Pro.

While the app is active, uAlarm may maintain a real-time connection to receive changes to your own entitlement record, including purchases, refunds, expirations or revocations.

7. Cloudflare and payment infrastructure

Cloudflare provides more than website delivery for uAlarm.

Cloudflare is used to:

Click requests are authenticated by checking a signature with a secret key.

Payment-provider requests passing through Cloudflare may contain information necessary to process the transaction, including payment identifiers, the uAlarm payment account number, amount and transaction status.

Our structured application logs for the Payme endpoint are intentionally limited to operational information such as the Payme method name, request duration, Cloudflare data-center location and country.

We do not intentionally place Payme authorization credentials, uAlarm payment account numbers, payment amounts or payment request parameters in those structured application logs.

Our structured application logs for the Click endpoint are likewise limited to operational information: whether the request was a check or a completion request, the response code, request duration, Cloudflare data-center location and country. We do not intentionally place Click secret keys, request signatures, uAlarm payment account numbers, payment amounts or request parameters in those logs.

Cloudflare necessarily processes network information, including IP addresses and request metadata, when providing its services.

8. Bedtime and app blocking

On supported Apple devices, uAlarm's optional Bedtime and app-blocking features use Apple's Family Controls and Screen Time technologies.

When you choose apps to restrict, Apple represents those selections to uAlarm using system-controlled identifiers. uAlarm does not receive the ordinary identity of the selected apps from those opaque selection tokens.

Those identifiers may be stored in the application's shared system container so that the selected restrictions can be applied.

If you choose a mission-based unlock, uAlarm may temporarily remove a restriction after you complete the required mission.

uAlarm also includes an optional setting that can prevent app deletion while an alarm is being dismissed. Apple's system control for this feature applies at device level, so while that protection is active it may prevent deletion of apps generally, not only deletion of uAlarm.

On Android, optional app blocking uses the AccessibilityService API. With your separate consent and Android Accessibility permission, uAlarm detects the package name of the foreground app and covers selected apps during the schedules you configure. It does not read screen text, inspect view contents, capture screens, or perform automated taps or gestures.

App names and package identifiers used by the picker and blocker remain on this device. Window events are processed transiently, not saved as a browsing history or transmitted. The selected app list and Accessibility consent are excluded from Android cloud backup and device transfer. You can disable the service at any time in Android Accessibility settings; uAlarm does not prevent access to Settings or uninstalling the app.

9. Notifications and system alarm services

uAlarm requests notification permission because notifications are used to provide alarm-related functionality.

On supported Apple devices, uAlarm may use Apple's system alarm services in addition to notifications.

Alarm times, labels and related alarm information may be displayed by iOS on the Lock Screen or in system alarm interfaces according to your device settings.

uAlarm does not use alarm notifications for third-party advertising.

10. Service providers

Depending on the platform, region, distribution channel and features you use, some or all of the following service providers may process information in connection with uAlarm.

Supabase provides authentication, database services, account backup and synchronization, storage for downloadable alarm tones and themes, and real-time subscription-entitlement updates.

Cloudflare provides website delivery and security, regional country detection, backend execution through Cloudflare Workers, Payme Merchant API and Click SHOP API infrastructure and database connectivity.

Apple provides Sign in with Apple, App Store billing, system alarm functionality and Family Controls/Screen Time functionality.

Google provides Google sign-in, Google Play billing and Google ML Kit.

RevenueCat validates App Store and Google Play purchases and keeps the subscription and entitlement status linked to your uAlarm account identifier.

Payme (Paycom) processes supported payments in Uzbekistan and sends transaction information to uAlarm's Merchant API.

Click (CLICK LLC) processes supported payments in Uzbekistan and sends transaction information to uAlarm's SHOP API.

These providers process information according to their own privacy and security practices as well as the services they provide to uAlarm.

11. How we use and disclose information

We use information only as reasonably necessary to:

We do not sell personal information.

We do not use camera content or raw mission sensor data for advertising or profiling.

We do not use personal information for cross-app behavioral advertising.

We may disclose information when reasonably necessary to our service providers described above, to comply with applicable law or valid legal process, to protect the security or integrity of uAlarm, or in connection with a merger, acquisition, financing, restructuring or sale of all or part of the service.

12. Retention and account deletion

You may delete your uAlarm account from Settings → Account → Delete Account.

When deletion succeeds, uAlarm deletes the account data associated with normal use of the service, including alarms, dismissal history, mission registrations, user statistics, settings, entitlement information and the payment account number mapping used for Payme and Click payments.

The authentication account is deactivated and its uAlarm identifier is retired so that the deleted account cannot later be restored or reused.

Linked Apple or Google identities are released from that deleted uAlarm account so that the same person may create a new, separate uAlarm account later. uAlarm does not maintain a separate identifier intended to recognize that person as the owner of the deleted account.

Payme and Click transaction records are treated differently. We retain transaction records needed for payment reconciliation, refunds, disputes and recordkeeping. When the related uAlarm account is deleted, the account link is removed from those retained payment records and the separate mapping between the payment account number and the deleted uAlarm account, which is shared by Payme and Click payments, is deleted.

Those retained transaction records are no longer linked in our application database to an active uAlarm account or Apple/Google sign-in identity.

A Pro or Premium entitlement bought through the App Store or Google Play stays linked to the identifier of the deleted account, so a new account cannot restore it in the app. It is not lost: write to support@ualarm.app with your store receipt or order number and, once the purchase is verified, we move it to your new account. A Payme or Click entitlement belongs to the account it was paid for and ends with it.

If an account is deleted while a Click payment is in progress and the card has already been charged, uAlarm cannot deliver the entitlement and reverses (refunds) that payment.

Deleting your uAlarm account does not itself cancel an Apple or Google subscription or cause the store to issue a refund. Subscriptions must be managed through the store.

Anonymous accounts require particular care. If an anonymous account is never linked to Apple or Google and the app is uninstalled before the account is deleted, we no longer have a sign-in identity that can be used to identify that anonymous backup for you. Such a backup may therefore remain stored after uninstalling. Use Delete Account before uninstalling if you want the anonymous account removed.

13. Security

We use technical and organizational safeguards intended to protect information handled by uAlarm.

These include encrypted network connections, account-based access controls, database permissions, and controls designed to limit payment-processing systems to the data and operations they need.

No internet-connected service can guarantee absolute security.

14. Children's privacy

uAlarm is not directed to children under 13.

We do not knowingly seek personal information from children under 13. Where applicable law requires parental or guardian authorization for a younger user, the required authorization must be obtained before that user uses account-based or paid features.

If you believe a child has provided personal information to uAlarm in circumstances where it should not have been collected, contact us at support@ualarm.app.

15. Your choices and privacy rights

Depending on where you live, applicable law may give you rights concerning your personal information, including rights to request access, correction, deletion, restriction, objection or a portable copy.

You can delete your uAlarm account directly inside the app.

For account or privacy questions, you may also contact support@ualarm.app. We may need to verify that you control the account involved before providing account-specific information or acting on a request.

You can control camera, motion, location, notification and other system permissions through your iPhone settings.

16. International processing

uAlarm's service providers operate infrastructure in multiple countries.

As a result, information processed through Supabase, Cloudflare, Apple, Google, RevenueCat, Payme or Click may be processed outside the country where you live, subject to the safeguards and legal requirements applicable to those providers and services.

17. Changes to this Privacy Policy

We may update this Privacy Policy when uAlarm, its data practices or applicable requirements change.

When we update it, we will publish the revised version and update the Last updated date.

If a change materially affects how uAlarm handles personal information, we may also provide additional notice through the app or another appropriate method.

18. Contact

For privacy questions or requests, contact support@ualarm.app.