AMaze Alarm Privacy Policy

Last updated: June 27, 2026

A privacy-first app

AMaze Alarm does not collect personal data in the app and does not operate user accounts, advertising identifiers, tracking SDKs, analytics profiles or developer servers that receive your personal app data.
Your alarms, challenge settings, sleep routine, audio choices, app language, widgets, Health data, Apple Watch context, location context and sleep insights are not sent to the developer.
As the developer, I do not have access to your app data and cannot see how you use the app.

The app may use alarm settings, challenge settings, sleep routine preferences, selected audio, app tone, language, widget state and other preferences to run the features you configure.
Optional Apple Health and Apple Watch sleep data are used only when you grant permission through iOS.
Approximate location or system-provided context may be used when you enable weather or local morning context.
Motion, camera or other device sensor access is requested only when needed by selected challenges or optional features.

App data is intended to remain on your device, in iOS-provided storage, or inside Apple/system services required for features such as notifications, widgets, Health, WeatherKit, Apple Watch and App Store purchases.
Subscription billing, refunds, cancellation and purchase records are handled by Apple. The app may check whether premium access is active, but the developer does not receive your full payment details.

News, podcasts, books, weather or external content may come from Apple or third-party providers and can be subject to their own availability and policies.
Opening external links or content can take you outside AMaze Alarm and may be handled by the destination service.

If you contact support by email, the developer receives only the information you choose to include, such as screenshots, device model, iOS version, app version or a description of the issue.

Sleep Insights, Energy Forecast, sleep debt and restlessness-related signals are for personal context only. Medical and safety disclaimers are described in the Terms of Use.