Privacy policy

Data stored on your device

RiseReady stores alarm times and labels, selected days, snooze and wake-check settings, wake-up task settings, selected sounds, and app defaults. RiseReady does not keep an alarm-delivery history.

App diagnostics and usage analytics

Usage analytics and crash/performance diagnostics are independent choices in Settings. Both are off by default. If usage analytics is enabled, Firebase Analytics may receive pseudonymous app-instance or device identifiers, app and operating-system versions, device and technical metadata, coarse region inferred from network information, and a small allowlisted set of app-interaction events. If diagnostics is enabled, Firebase Crashlytics and Performance Monitoring may receive identifiers, crash and exception details, stack traces, app/device metadata, and performance measurements.

RiseReady does not set a Firebase user ID or send alarm labels, alarm times, record IDs, sound paths, answers, images, face data, or raw sensor readings. Android advertising-ID collection and ad-personalization signals are disabled. Routine development and test builds keep Firebase collection disabled; only deliberately configured verification or production builds can initialize it. Turning usage analytics off disables its collection and resets the local Analytics identifier. Turning diagnostics off disables Crashlytics and Performance collection and deletes unsent crash reports. Data already transmitted is retained and deleted under the RiseReady Firebase project settings and Google's terms.

Camera, motion, and light

On Android, camera access is used only for blink, wink, smile, or head-turn checks. Frames and face-detection results are processed temporarily on the device and are not saved or sent to Google. Face tasks detect a requested gesture; they do not identify a person or create a face identity template.

These tasks use the bundled Google ML Kit face-detection SDK. Google may receive SDK diagnostics such as app/device information, installation identifiers, API configuration, usage events, performance measurements, and errors. RiseReady shows this information before requesting camera permission. Raw motion and light samples are used only while their selected task is active and are not retained.

Imported alarm sounds

When you choose your own alarm sound, RiseReady copies it into private app storage so it remains available when the alarm rings. It is not uploaded or shared by RiseReady.

Deleting your data

Delete individual alarms in the app. Uninstalling RiseReady removes its private alarms, settings, and imported sounds from the device. RiseReady has no server-side account or cloud alarm copy to delete. Android app backup is disabled. On iPhone, alarms and settings stored in system preferences may remain in a user-controlled encrypted iCloud or computer backup until that backup is deleted; imported sounds are excluded from backup.

Permissions

Alarm, notification, lock-screen, wake-lock, vibration, foreground service, reboot recovery, camera, and local-file access are requested only for the alarm features described above. Availability varies by platform and operating-system version. Network access may be used by ML Kit diagnostics when a face task is used and by Firebase only after the corresponding optional setting is enabled. Alarms and wake-up tasks continue to work offline.

Controller and processors

RiseReady's app publisher is responsible for the processing described here. Google acts as a service provider for ML Kit and, when enabled, Firebase. Website hosting and security providers process ordinary web request data to deliver and protect this site.

This website

This public website does not use advertising, analytics cookies, tracking pixels, accounts, or a contact form. Its hosting and security providers may process standard request information, such as IP address, browser details, requested URL, and security signals, to deliver and protect the site.

Contact

Start with the RiseReady support page or email support@proappcenter.com. RiseReady has no account and does not set a Firebase user ID, so diagnostics generally cannot be located from an email address alone.