Beyond Alarm has no app account or sign-up. Alarm settings and camera processing are local. The app also uses Google AdMob, Google Analytics for Firebase, Firebase Remote Config and RevenueCat: those services process technical identifiers, usage or purchase information as described below. Removing the app does not automatically delete records held by these services.
Beyond Alarm is the app and service described here. For privacy questions or a data request, contact nionnavi@gmail.com. If you email us, we receive the address and information you send so we can reply. Do not send payment-card details or passwords.
Your saved alarms, labels, block schedules and selections, preferences, optional display name and avatar, streak records and mission reference data are stored on the device. We do not operate an account-based backup of that content. Selected sound files or photos are accessed when you choose to use them; the app does not upload your personal files.
Feature events are separate from those saved records: the app reports alarm dismissal and mission completion, including mission type, through Analytics as described in section 8. Therefore, we do not claim that all information about using the app stays on the phone.
Uninstalling or clearing app storage removes the local copy. Android backup or device-transfer services may retain or restore eligible app data under your own device and Google settings.
Camera missions process images on the device to count exercise movements, recognise selected household objects, scan barcodes or compare a photo with a saved reference. Camera frames are not sent to our servers or to an image-recognition cloud service. The camera is used during camera missions and reference-photo setup.
The photo mission keeps the reference pictures you choose in private app storage. Replacing or deleting a reference removes it from the app; uninstalling removes the local app copy. These pictures may be included in eligible Android backups. Prefer a place or object to a photograph of a person.
Step and motion sensors support walking and shaking missions on the device. We do not upload raw step-counter readings, motion streams or camera frames. A completed mission may generate the mission-type event described below.
The optional guard uses foreground-app and window information to enforce the blocking rules you select. For website blocking, it examines accessible browser address-bar text and may inspect accessible window nodes to locate a URL. It also inspects relevant system-window information for guard and power-menu behavior. It is therefore inaccurate to say the service never accesses screen text.
This information is used locally for enforcement, not to build or upload a browsing-history or message-content record. Browser coverage depends on what the browser exposes; an inaccessible address bar or an in-app browser may not be covered. You can manage accessibility access in Android Settings. Beyond Alarm is not an accessibility tool for people with disabilities.
Overlay access supports the blocking screen. Optional device-administrator access makes uninstalling require deactivation first. It is not permission to wipe the device or reset your password. Android remains in control of these permissions, and power-off prevention is not guaranteed.
Alarm, notification and full-screen permissions support scheduled alarms and showing the ring screen. An optional bedtime reminder is scheduled using the time you choose. Background and battery settings affect reliability.
Optional purchases are processed by Google Play. We do not receive payment-card details. RevenueCat processes an app-user identifier and transaction or subscription information so the app can recognise purchases and restore access. The app does not require a personal account, but that does not mean billing records contain no identifiers.
Google handles its own account and payment records under Google's Privacy Policy. Prices, renewal terms and any available trial are shown in Google Play before you confirm a purchase.
The current offering makes alarm missions and blocking features available free with advertising. An optional purchase removes ads. This is not a promise that all future versions or offers will be identical. The app no longer runs the old five-day device-based trial. Any store trial must be explicitly offered by Google Play and follows the terms on its purchase screen.
The former app-managed trial and its device-hash ledger were removed on 1 August 2026. This does not mean today's advertising, analytics and configuration SDKs use no identifiers.
Ad-supported use can include ads on alarm, mission and blocking screens, full-screen ads after some flows, and rewarded ads offered for specific actions. Placements and frequency can change. An active ad-free entitlement disables ads; it does not automatically disable analytics or purchase processing.
Google AdMob processes information such as IP address, advertising or app identifiers, ad interactions and diagnostics for advertising, measurement and fraud prevention. IP addresses can indicate approximate location; we do not request precise GPS location for the alarm. See Google's Mobile Ads data disclosure.
Google's User Messaging Platform presents privacy choices where required by its configuration and your region. Use the app's privacy-options entry when available to revisit those choices. Android's advertising-ID controls are separate. These ad choices should not be interpreted as an app-wide analytics opt-out.
Google Analytics for Firebase measures app use and advertising performance. In addition to SDK-collected technical and interaction information, the app sends events for alarm dismissal, completed mission type, viewing the purchase screen and purchase completion with the selected plan. These events do not include your alarm label, chosen display name, reference photos or blocked-app list.
Analytics can process app-instance identifiers, device/app information and usage events. Firebase Remote Config uses installation identifiers to deliver settings such as whether ads are enabled and their refresh interval. Neither service is needed to process camera missions. Ads, purchases and fetching configuration require a connection; core alarm and mission functions run locally.
These providers may process information outside your country. Retention depends on the service and its configuration; uninstalling stops future collection by that installation but does not automatically erase historical provider records. See Google's privacy information and Firebase's data-handling documentation.
Our marketing and legal pages use Firebase Hosting. Hosting processes technical request information, including IP addresses, to deliver and protect the websites. Links to Google Play or other sites take you to services with their own policies. Download links may include a page or campaign referrer, not a personal identifier, to distinguish referral sources.
Delete individual content in the app where supported, or clear app storage/uninstall to remove local data. Manage any backup separately in Android or Google settings. Cancelling a subscription must be done through Google Play; uninstalling does not cancel it.
For a request concerning information we or our service providers process, email nionnavi@gmail.com with the subject Privacy request. Explain what you want accessed, corrected or deleted. Because there is no app account, we may need enough information to locate the relevant pseudonymous or purchase record; please do not send sensitive documents unless needed and requested. We will explain what we can identify and act on, subject to applicable retention obligations.
Deleting a RevenueCat record can affect recognising a purchase until it is restored. It does not erase Google's transaction records, cancel a subscription or issue a refund.
Beyond Alarm is not directed at children under 13. Contact us if you believe a child has provided personal information. We update this page when our data practices change and show the revision date above.