Effective Date: August 26, 2026
App Name: ToughAlarm
Package Name: com.yummbj.evil.alarm
Developer: Beijing Yummbj Technology Co., Ltd.
ToughAlarm (hereinafter referred to as "this Application") is an alarm clock application that requires you to complete wake-up missions (such as math questions, shaking the device, typing text, or taking a photo) before an alarm can be dismissed. We value your privacy and explain through this Privacy Policy how this Application handles data.
Your alarms, missions, photos, history, settings, and local diagnostic logs remain on your device unless otherwise expressly described in this Privacy Policy.
This Application does not operate its own user account system, advertising platform, or cross-app tracking system. The Application does not sell your personal information.
The Application integrates the following third-party SDKs:
Firebase Analytics and Firebase Crashlytics may collect technical information such as application identifiers, device and operating system information, application version, usage events, session information, performance information, crash information, and other technical diagnostics. The specific information collected depends on the SDK configuration and the features used by the Application.
The Application does not intentionally send your alarm contents, typed answers, photos, facial data, or image recognition results to Firebase Analytics or Firebase Crashlytics.
The Application does not use Firebase Analytics or Firebase Crashlytics for cross-app behavioral advertising or to sell personal information.
Please read this Privacy Policy carefully before using this Application.
This policy applies to this Application and its mobile versions released on Google Play, or other legitimate channels.
This policy does not apply to independently provided third-party websites, services, or platform features ( system backups, or operating system permission dialogs). Those services are governed by their respective privacy policies.
This Application uses third-party SDKs provided by Google to provide photo recognition, application analytics, and crash diagnostics.
This Application integrates Google ML Kit for on-device image recognition.
When you use photo-recognition functionality, ML Kit may periodically contact Google to obtain bug fixes, updated models, and hardware accelerator compatibility information. ML Kit may also send limited technical performance and utilization metrics to Google.
The relevant technical information may include:
| Data Type | Examples | Purpose | Linked to Identity | Used for Tracking |
|---|---|---|---|---|
| Device / installation identifiers | Per-installation identifiers | SDK operation, diagnostics, analytics | No | No |
| Application interaction data | Feature initialization, model download, detection, resource release, feature version and API configuration events | SDK operation, diagnostics and usage analytics | No | No |
| Performance / diagnostic data | Device and application information, available ML accelerators, latency, input/output size, image format or resolution, error codes | Diagnostics, maintenance and performance measurement | No | No |
Google states that ML Kit's technical metrics are not transferred by Google to third parties for advertising or cross-app tracking.
The Application does not transmit photo inputs or recognition results to the Developer's servers.
For more information, please refer to Google's applicable privacy documentation.
This Application uses Google Analytics for Firebase (Firebase Analytics) to understand how users interact with the Application and to improve application functionality, usability, and stability.
Firebase Analytics may automatically collect certain application usage and technical information. Depending on the Application's implementation, this may include:
Firebase Analytics automatically generates an application-instance identifier for each installation of the Application and uses it to distinguish application installations and calculate usage metrics.
The Application may also configure custom analytics events to measure feature usage. Such events may include information such as which application feature was opened, whether a feature was completed, or whether an error occurred.
The Developer will not intentionally send the following information to Firebase Analytics unless this Privacy Policy is updated and the relevant disclosure and consent requirements are satisfied:
Firebase Analytics is used for application measurement, usage analysis, feature optimization, and service improvement. It is not used by the Developer to sell your personal information.
Firebase Analytics may provide reporting and audience functionality within the Firebase/Google Analytics service. The Developer will configure these functions in accordance with applicable laws and platform requirements.
This Application uses Firebase Crashlytics to detect, diagnose, and analyze application crashes, non-fatal errors, and application stability problems.
When a crash or relevant error occurs, Crashlytics may automatically collect information such as:
| Data Type | Examples | Purpose |
|---|---|---|
| Crash information | Crash stack traces, exception information and relevant application state | Diagnose crashes |
| Device information | Device model, CPU architecture, memory and storage information | Diagnose device-specific problems |
| Operating system information | OS name and version | Compatibility and crash analysis |
| Application information | Application identifier, application version and SDK information | Identify affected application versions |
| Installation / technical identifiers | Crashlytics Installation UUID, Firebase installation/session identifiers | Distinguish crash reports and measure affected installations |
| Crash timing information | Time and session information associated with the crash | Diagnose and reproduce problems |
| Developer-defined logs | Logs or custom keys added by the Developer | Diagnose technical issues |
Google's current Firebase documentation states that Crashlytics automatically collects crash stack traces, relevant application state, device/OS information and a Crashlytics installation identifier.
If the Developer configures additional Crashlytics custom keys, logs, user identifiers, or non-fatal events, those additional data may also be included in crash reports.
The Developer will configure Crashlytics so that crash reports do not intentionally contain unnecessary personal information, passwords, photos, typed answers, or other sensitive content.
Crashlytics is used solely for application stability, error diagnosis, maintenance, and improvement.
If Firebase Analytics and Crashlytics are used together, Crashlytics may use analytics "breadcrumb" information to help identify application actions that occurred shortly before a crash.
Such information may include application interaction events and crash-related session information.
The Developer will configure analytics events and Crashlytics logs to minimize the collection of unnecessary personal or sensitive information.
Except for technical information described in Sections 2.1–2.4 and information voluntarily provided when contacting us, this Application does not intentionally send the following content to Firebase Analytics or Firebase Crashlytics:
Your alarm configurations, missions, photos, history, settings, and local diagnostic logs remain stored locally on your device unless otherwise expressly described in this Privacy Policy.
To provide its alarm functions, this Application stores the following data only in local device storage:
| Data Category | Examples | Purpose | Uploaded to Developer Server |
|---|---|---|---|
| Alarm configuration | Alarm times, repeat rules, ringtone, volume, vibration, difficulty, missions | Schedule and ring alarms | No |
| Mission configuration | Math level, text length, shake count, photo mission settings | Run configured missions | No |
| Reference photos | Photos taken when setting up a photo mission | Compare against the photo taken when the alarm rings | No |
| Alarm session state | Currently ringing alarm queue and mission progress | Resume an in-progress mission | No |
| Alarm history | Dismissed, snoozed, missed, or escaped alarms | Display alarm history | No |
| Settings and consents | Preferences and consent records | Remember configuration choices | No |
| Local diagnostic log | Local error records | Diagnose problems on the device | No |
Deleting an alarm removes its alarm and mission records. Reference photos that are no longer used by any alarm are removed during subsequent local cleanup.
The Developer does not maintain a server-side copy of this local content.
If you configure a photo mission, this Application uses the device camera to let you capture a reference photo during setup and a matching photo when the alarm rings.
You may decline camera permission. In that case, photo missions cannot be used, but other Application functions remain available.
ToughAlarm does not intentionally collect, process, store, or transmit face data.
The Application does not use face detection, face landmark detection, face mesh, face tracking, face recognition, or face-based authentication technology.
The photo mission is designed for generic object or image recognition and does not identify or verify a person.
No facial templates, faceprints, facial geometry, or other biometric identifiers are intentionally created or stored.
This Application requests permissions necessary to provide its alarm and photo-mission functions:
Firebase Analytics and Firebase Crashlytics primarily collect data through their SDK operation and do not require a separate user-facing system permission equivalent to camera or notification permission.
However, Firebase Analytics may use application/device identifiers. On Android, Firebase Analytics may collect the Android Advertising ID depending on SDK configuration and available permissions. On iOS, IDFA is subject to Apple's applicable requirements and user authorization; if IDFA is unavailable, Firebase Analytics may use other technical identifiers such as the vendor identifier.
The Developer does not use Firebase Analytics or Crashlytics to perform cross-app tracking.
This Application does not operate an advertising service and does not use Firebase Analytics or Firebase Crashlytics to provide personalized advertising within the Application.
The Application does not request App Tracking Transparency permission solely for Firebase Analytics or Crashlytics.
The Developer does not intentionally combine Firebase Analytics data with directly identifying personal information for the purpose of identifying individual users.
If future features require advertising, personalized advertising, cross-app tracking, or other uses of advertising identifiers, the Developer will update this Privacy Policy and implement any consent or permission mechanisms required by applicable laws and platform policies before such processing begins.
The Application uses the following third-party services:
Used for on-device image recognition and related technical diagnostics.
Used for application usage analytics, feature measurement, user engagement analysis, and service improvement.
Used for crash reporting, non-fatal error reporting, application stability monitoring, and technical diagnostics.
Google processes Firebase data in accordance with its applicable terms and privacy policies.
For more information about how Google processes information when you use apps or services that use Google technologies, please refer to Google's applicable privacy documentation.
If you voluntarily contact the Developer by email or another channel, we may receive your email address, message content, and any device information, screenshots, or descriptions you choose to include.
We use this information only to respond to your request, troubleshoot problems, comply with legal requirements, and protect our rights.
Please avoid sending unnecessary sensitive personal information.
Local Application data remains on your device until it is removed through an applicable in-app action, system data-clearing function, application uninstall, or operating-system cleanup.
Firebase Analytics and Crashlytics data are processed and retained by Google according to the applicable Firebase/Google service configuration and retention policies.
Because Firebase Analytics and Crashlytics use technical identifiers rather than the Developer's account system, the Developer may not be able to identify or delete a specific individual's data in all circumstances.
You may also be able to control certain analytics or advertising-related data collection through available Application settings, device settings, platform controls, or Firebase/Google mechanisms where applicable.
Device-local content is stored in the Application's private storage area, which other applications cannot normally access.
Data transmitted by Firebase SDKs to Google is protected using appropriate transport security mechanisms.
The Developer configures Firebase Analytics and Crashlytics to minimize unnecessary personal information and sensitive data.
No method of storage or transmission is completely secure. We nevertheless take reasonable technical and organizational measures to protect information against unauthorized access, use, alteration, or disclosure.
This Application is a general-purpose alarm clock and is not directed at children under 13 years old, or the applicable minimum age defined by local law.
The Application does not knowingly collect identity-linked personal information from children.
If you are a minor, please use this Application with the consent and guidance of your guardian, particularly for physical missions such as shake missions.
Because the Application uses Firebase Analytics and Firebase Crashlytics, the Developer's store privacy declarations must accurately reflect the actual Firebase SDK configuration and the data that is actually collected.
Depending on the final SDK configuration, analytics events, identifiers, and Crashlytics settings, the relevant disclosures may include:
The Developer will not claim that Firebase Analytics or Crashlytics collect no data when these SDKs are enabled.
We may update this Privacy Policy due to feature additions, third-party SDK changes, platform policy revisions, or legal and regulatory changes.
Updated policies will be published through application updates, store listings, or other appropriate channels.
Material changes will be highlighted with reasonable prominence where required by applicable law.
If you have any questions regarding this Privacy Policy, data handling, or privacy rights, please contact us: