Privacy Policy for Alarm Breaker

01. Who Operates Alarm Breaker

This Privacy Policy governs the mobile application Alarm Breaker for Android (Package Identifier: com.wakeforge.wakeforge), engineered, copyrighted, and published by CB DEV STUDIO ("we", "our", or "us"), an independent software development studio based in Sitapur, Uttar Pradesh, India.

Our engineering standard mandates data minimization: we process sensor and execution data on your device hardware whenever technically viable, enforce authenticated cryptographic controls across network relays, and maintain clear isolation between local alarm routines and optional cloud capabilities.

For any inquiries or developer verification, contact our desk at contact@cbdevstudio.in.

02. Information Stored Locally on Your Device

The core functionality of Alarm Breaker operates completely offline inside the sandboxed local storage of your Android operating system. We utilize an embedded SQLite database (managed via Drift ORM) to store:

• Alarm Configurations: Trigger timestamps, recurrence schedules, volume profiles, vibration cadences, snooze rules, and selected challenge routines.
• Challenge Data: Arithmetic configurations, memory sequences, typing benchmarks, and locally saved barcode/QR comparison hashes.
• Exercise & Workout History: Repetition tallies, hold durations, personal records, timestamps, and workout session journals.
• Gamification State: Wake streaks, achievement badges, and offline progress metrics.
• Victory Poster Cards: User-generated victory/streak cards saved directly to your device gallery (via Android MediaStore) strictly upon your manual tap.

All configuration and history data remains strictly on your device. It is never automatically synced, harvested, or uploaded to CB DEV STUDIO external databases.

03. Exact Alarms, Foreground Services & System Notifications

To guarantee that scheduled alarms trigger reliably regardless of Android Doze mode, deep battery standby, or aggressive OEM background task killing, Alarm Breaker utilizes specific system capabilities:

• Exact Alarms (USE_EXACT_ALARM & SCHEDULE_EXACT_ALARM): Used exclusively to schedule precise alarm clock events (setAlarmClock()) that fire at the exact minute configured by the user, bypassing battery optimization sleep states.
• Foreground Services (FOREGROUND_SERVICE_MEDIA_PLAYBACK & FOREGROUND_SERVICE_SPECIAL_USE): Used strictly while an alarm is actively ringing to ensure continuous, un-killable audio playback, vibration, and challenge processing until the wake-up task is verified.
• Full-Screen Notifications (USE_FULL_SCREEN_INTENT & POST_NOTIFICATIONS): Used solely to display the interactive challenge screen over the lock screen the moment an alarm fires, allowing immediate task completion without requiring prior device unlock.

These execution capabilities are used strictly for real-time alarm operations and never run background analytics or silent tracking.

04. Camera Access & Real-Time Computer Vision (ML Kit)

Alarm Breaker requests optional camera access (android.permission.CAMERA) strictly when camera-assisted challenges or barcode verifications are configured:

• On-Device Pose Estimation: During bodyweight workout challenges (Squats, Push-Ups, Planks, Lunges, High Knees), video frames are analyzed frame-by-frame entirely inside volatile device RAM using Google ML Kit's local computer vision model. Skeletal joint coordinates (landmarks) are computed to verify rep depth and posture.
• No Video Recording or Transmission: Raw camera frames, video feeds, and picture streams are immediately overwritten in memory and discarded. Zero video or camera data is ever written to disk, stored, or transmitted to any server.
• Barcode and QR Verification: When disarming an alarm via a bathroom or kitchen barcode, camera frames are evaluated locally to match barcode hash strings. The camera stream closes immediately once verified.

05. Motion Sensors, Accelerometer & Step Counter

Alarm Breaker utilizes device hardware motion sensors (android.permission.ACTIVITY_RECOGNITION and standard accelerometer APIs) for movement-based alarm disarming:

• Shake Challenge: Analyzes rapid acceleration and displacement patterns against anti-cheat curves to verify physical wakefulness.
• Pedometer (Step Counter): Reads step events from your phone's hardware step sensor to require walking a set distance out of bed before silencing the alarm.

All sensor processing occurs locally in real time. Sensor feeds are never logged, analyzed for behavioral profiling, or shared off-device.

06. Microphone Access & Tactical Voice Alarms

Alarm Breaker requests microphone access (android.permission.RECORD_AUDIO) solely when you explicitly create custom voice notes:

• Personal Wake Memos: Short voice notes (up to 7 seconds, Opus/AAC compressed) saved locally in private app storage to serve as custom morning alarm ringtones.
• Friend Audio Wake Dares: Voice dares recorded for mutual friends are compressed (maximum 24 KB) and dispatched via our relay.
• Automated 48-Hour Hard Deletion: Relay-stored voice notes are permanently deleted from server memory immediately upon recipient download acknowledgment (/relay/audio-ack), or automatically purged after 48 hours (AUDIO_TTL_MS = 48h).

Alarm Breaker never performs background listening, ambient audio monitoring, or acoustic profiling.

07. Anonymous Accounts & Cryptographic Friend Network

Alarm Breaker does not require an email address, telephone number, password, or third-party social media profile:

• Anonymous Firebase Authentication: When accessing peer features, the app authenticates anonymously, generating an ephemeral pseudonymous Firebase User ID (UID).
• Pairwise Cryptographic Keys: Friend connections are established by exchanging alphanumeric Friend IDs or scanning QR codes. Identity keypairs (X25519) and pairwise secrets are generated on-device using secure random entropy and saved in the hardware-backed Android KeyStore via encrypted storage.
• Pseudonymous Display Names: Users can assign optional custom nicknames (e.g., "Alpha" or "Titan") displayed only to mutually approved connections.

08. End-to-End Encrypted Friend Alarms & Relays

When mutual friends send wake-up challenges ("Friend Wakes"):

• Authenticated Encryption (EtM): Challenge parameters (challenge type, target reps, custom messages, action links) are encrypted on-device using Encrypt-then-MAC with HMAC-SHA256 derived from the pairwise secret.
• Zero Relay Payload Visibility: Cloud relays (hosted on Koyeb/Render) cannot inspect or tamper with challenge payloads. Any tampering causes an immediate authentication failure (CRYPTO_AUTH_FAILED).
• Ephemeral Transit: Undelivered challenge packets are held for a maximum of 7 days (PACKET_TTL_MS = 7d). Once delivered, the recipient phone acknowledges receipt (/relay/ack), instantly purging the packet from relay memory.
• Push Routing (FCM): Alerts are routed via Google Firebase Cloud Messaging using encrypted references.

09. Third-Party Services & SDK Disclosures

To deliver push alerts, cloud relay, and optional monetization, Alarm Breaker integrates selected industry-standard SDKs:

• Google Firebase (Google LLC): Anonymous Authentication, Firebase Cloud Messaging (FCM), and Firebase Crashlytics crash telemetry.
  Google Firebase Privacy Policy →
• Google ML Kit (Google LLC): On-device computer vision models for movement detection. Operates 100% locally on device hardware without sending media to Google.
  Google ML Kit Terms →
• Google Mobile Ads / AdMob (Google LLC): Displays optional rewarded advertisements (e.g., earning optional in-app cosmetic sweat coins). AdMob may process device identifiers and advertising IDs subject to user consent.
  Google Ad Technologies & Privacy →
• Koyeb / Render: Container hosting for our ephemeral relay service, compliant with ISO 27001 / SOC 2 standards.
  Koyeb Privacy Policy →

10. Data Safety & Retention Matrix

The table below provides a full, transparent inventory of all data categories handled across the Alarm Breaker ecosystem in compliance with the Google Play Data Safety standard:

11. User Privacy Rights & Permanent Data Deletion

You maintain complete sovereignty over your data:

• Instant Local Data Wipe: Clear all local alarms, challenge logs, coin balances, and workout records at any time via: Android Settings → Apps → Alarm Breaker → Storage → Clear Data.
• In-App Account & Cloud Erasure: You can permanently delete your friend network identity, local cryptographic keys, and all pending relay data directly inside the application: Settings → Advanced → Delete Account & Cloud Data (requires typing DELETE to confirm). This calls DELETE /me on our relay, wiping all FCM tokens, audio files, and active packets, and inserting a permanent tombstone record.
• Web-Based Deletion Portal: Users who have uninstalled the application can review step-by-step instructions or request manual erasure via our official web guide: Alarm Breaker Account & Data Deletion Portal →
• Permission Revocation: You may revoke Camera, Microphone, Notification, or Activity Recognition permissions at any time via Android system settings.
• No Sale of Personal Data: CB DEV STUDIO has never sold, rented, monetized, or brokered personal data, and will never do so.

12. Advertising Identifiers & Consent Management (UMP)

Alarm Breaker integrates Google AdMob for optional rewarded ads:

• European Economic Area (EEA) & UK (GDPR): We implement Google's User Messaging Platform (UMP) SDK. Users in covered jurisdictions receive an explicit consent form allowing them to consent to or decline personalized advertising and tracking cookies.
• Non-EEA Jurisdictions: Where affirmative cookie consent is not required by local statute, ads are served in accordance with standard Google AdMob policies.
• Resetting Advertising Identifiers: You can reset or delete your Google Advertising ID (GAID) at any time via: Android Settings → Google → Ads → Delete Advertising ID.

13. Diagnostic Logs & Crash Telemetry

To monitor system stability across diverse Android versions and hardware manufacturers, Alarm Breaker includes Google Firebase Crashlytics. When a software exception occurs, non-identifying telemetry is collected:

• Device manufacturer, model, and CPU architecture (e.g., ARM64).
• Operating system build version and free RAM/storage metrics.
• Stack trace of the runtime error and exact timestamp.

Diagnostic logs contain zero photos, video frames, audio recordings, or personal message contents.

14. Security Safeguards & Architecture Controls

• All network communication occurs exclusively over encrypted HTTPS/TLS 1.3 connections.
• Cryptographic keys and pairwise pairing secrets are stored in the Android KeyStore.
• Relay endpoints enforce strict rate limiting (e.g., hourly and daily request caps) to prevent denial-of-service abuse.

Security Notice: While we implement defense-in-depth security, no digital storage architecture can guarantee absolute immunity against device-level operating system compromises, root exploits, or malware installed on rooted devices.

15. Children's Privacy (COPPA & Google Play Families)

Alarm Breaker is an intensive wake-up utility and physical fitness application engineered for general audiences and adult heavy sleepers. It is not directed toward children under 13 years of age (or under 16 in applicable European jurisdictions). We do not knowingly solicit or collect personal information from children. If you become aware that a child has provided data through our app without parental consent, notify our team at contact@cbdevstudio.in and we will immediately purge the data.

16. Policy Modifications & Revisions

We may update this Privacy Policy to reflect application improvements, updated challenge features, or regulatory amendments. Any revisions will be published to this page with an updated "Last Updated" timestamp. Continued use of Alarm Breaker following any update constitutes acceptance of the revised policy.

17. Official Contact Information & Grievance Officer

In compliance with the Information Technology Act (2000), the Information Technology Rules (2021), and the Digital Personal Data Protection Act (DPDP Act, 2023), the designated Grievance Officer and developer contact for Alarm Breaker is: