ToughAlarm is an alarm clock that requires wake-up missions before an alarm can be dismissed. This policy explains how the app handles data.
Your alarms, missions, photos, history, settings and local diagnostic log stay on your device. ToughAlarm has no developer-operated server, account system, advertising or cross-app tracking. Google ML Kit processes photos and recognition results on-device, but collects limited technical metrics for operation, diagnostics and usage analytics. Those metrics are not linked to your identity, are not used for tracking, are not shared with third parties and are encrypted in transit.
1. Scope
This policy applies to ToughAlarm on Google Play, the Apple App Store and other legitimate channels. Independent platform services such as app stores, system backups and operating-system permission dialogs are governed by their own policies.
2. Limited technical data collected by Google ML Kit
ToughAlarm uses Google ML Kit for on-device image labeling. When photo features are used, ML Kit may contact Google for bug fixes, model updates and hardware accelerator compatibility information, and may send limited performance and utilization metrics.
| Store data type | Examples | Purpose | Handling |
|---|---|---|---|
| Device ID / device or other identifiers | A per-installation identifier not intended to identify a user or physical device | App functionality, diagnostics and usage analytics | Not identity-linked; no tracking; no third-party sharing; HTTPS |
| Product interaction / app interactions | Feature initialization, model download, detection, resource release, feature version and API configuration events | App functionality, diagnostics and usage analytics | Not identity-linked; no tracking; no third-party sharing; HTTPS |
| Performance and diagnostic data | Device and app information, ML accelerators, latency, input/output size, image format or resolution and error codes | Diagnostics, maintenance, performance measurement and usage analytics | Not identity-linked; no tracking; no third-party sharing; HTTPS |
Google states that ML Kit does not transfer these metrics to third parties. They are not used for advertising, marketing, personalization or tracking across apps or websites. See Google's ML Kit Terms and Privacy, Android disclosure, iOS disclosure and Privacy Policy.
3. Data ToughAlarm does not collect
Except for the limited ML Kit metrics above and information you voluntarily send for support, ToughAlarm does not collect personal data on a developer server. It does not collect names, contact details, location, photos, image features, recognition inputs or outputs, audio, health data, payment data, advertising identifiers, alarm contents, mission answers or local logs.
4. Data stored locally
Alarm configuration, mission configuration, reference photos, active alarm state, alarm history, settings and the small rotating diagnostic log are stored in the app's private device storage. They are not uploaded as content. You can remove them in the app, by clearing app data or by uninstalling. The Developer has no server-side copy and cannot restore them.
5. Camera and photo missions
Camera access occurs only when you actively use a photo mission. Image recognition and matching run on-device. Google ML Kit does not send input images or recognition results to Google servers. Reference photos stay in the app's private documents directory; dismissal photos are used only for on-device comparison and are not added to the system photo library.
6. Permissions
ToughAlarm may request notifications, exact alarms, full-screen alarms, foreground media playback, vibration, run-after-reboot, camera access, and iOS AlarmKit or time-sensitive notification capabilities. On Android it may also open the system power-management page so you can review device-specific background settings, but it does not request a direct battery-optimization exemption. These are used for alarm and mission functions, not advertising or tracking.
7. Retention, deletion and security
Local content remains until you delete it or the operating system removes it. ML Kit metrics are handled by Google according to Google's policies. Because ToughAlarm has no account and those metrics are not identity-linked, the Developer cannot identify or delete a particular user's ML Kit metrics. Local content uses private app storage, and transmitted ML Kit metrics are encrypted using HTTPS.
8. Contact and children
ToughAlarm is a general-purpose alarm clock and is not directed at children under 13 or the applicable local minimum age. It does not knowingly collect identity-linked personal information from children.
If you contact us, we may receive your email address and whatever information you choose to send. We use it only to respond, troubleshoot and meet legal obligations. Contact: kf1@yummbj.com.
9. Store privacy summary
- Collected: Device or other IDs, app/product interactions, and performance/diagnostic data.
- Linked to identity: no. Tracking: no. Shared under Google Play's definition: no.
- Encrypted in transit: yes.
- Photos and image-recognition inputs or outputs collected: no.
10. Updates
We may update this policy when features, platform rules or legal requirements change. Updated terms will be published through app updates, store listings or other appropriate channels.