Effective date: June 19, 2026
Bedly is designed as a local-first alarm and morning routine app. The app does not sell personal data, track users across apps or websites, or upload bedroom photos.
Bedly does not include account creation, login, third-party tracking, analytics SDKs, advertising SDKs, or photo uploads.
Bedly purchases are processed by Apple and managed with RevenueCat. RevenueCat receives purchase history and an anonymous app user ID so the app can unlock Pro features, restore purchases, and show Pro access. Bedly does not receive payment card details or create an account.
The app keeps a local entitlement snapshot so the interface can continue showing whether Pro features are active between RevenueCat refreshes.
Smart Wake can optionally read Apple Health Sleep Analysis from HealthKit after you grant permission. Bedly uses this data only on device to decide whether a Smart Wake alarm can move inside your selected wake window. Deep sleep is avoided when choosing an earlier wake moment, and HealthKit sleep-stage data is preferred over lower-confidence sleep-cycle estimates.
Auto Smart Wake can keep a latest-time fallback alarm armed, detect a recent HealthKit sleep session, request a best-effort background refresh near the wake window, use a conservative sleep-cycle estimate when useful, and update the managed alarm when local sleep data suggests a better wake moment. Raw HealthKit sleep samples are not uploaded, sold, synced, used for tracking, or stored as a sleep log. Smart Wake alarm records store only planning metadata such as latest wake time, wake window, selected wake time, selected timing source, optional selected sleep-stage label, compact confidence/reason text, managed alarm ID, recent planning timestamps, and the last local sleep-data check status such as checked time, sample counts, useful-sample count, optional source label, compact observed-stage summary, and local error text.
Verification photos are processed on device and discarded after scoring. They are not saved to the app's history, written to Photos, sent to a server, or used for tracking. While an alarm is still waiting for verification, the app may keep a bounded set of compact duplicate-attempt signatures to reject repeated or near-duplicate attempts; those signatures are not photos and are cleared when the session is verified, snoozed, bypassed, or logged as an unverified stop.
Users set, retake, or reset a made-bed reference photo in Settings. A usable local reference is required before enabling new alarms so Bedly can compare verification photos against the user's own bed. Bed references are stored only on this device under app storage with file protection and are not uploaded. Verification photos are still discarded after scoring.
Alarm settings, app settings, and completion history are stored locally on the device. History contains metadata such as timestamp, status, confidence, and attempt count. It does not contain bedroom photos or duplicate-attempt image signatures after a verification session ends.
Bedly requests alarm permission to schedule wake-up alarms, camera permission to capture fresh made-bed verification photos, and optional HealthKit read permission for Apple Health Sleep Analysis used by Smart Wake. The app does not request Photo Library access.
The app does not require network access for alarm creation, alarm delivery, bed verification, emergency bypass, or local history. It does not track users across apps or websites.
Network access is used by Apple's StoreKit system and RevenueCat when a user loads plans, buys, restores, refreshes, or manages Pro access. See RevenueCat's privacy policy at revenuecat.com/privacy.
For help, use the Bedly support page.