# Privacy Policy for Alarm Clock: Timer & Bedtime
**Effective Date:** October 31, 2026
**Last Updated:** October 31, 2026
---
## 1. Introduction
Welcome to **Alarm Clock: Timer & Bedtime** (the "Application", "App", "we", "us", or "our"), packaged under the Application ID `com.alarm.deskclock.alarmclock`. This Privacy Policy explains transparently and comprehensively how our application collects, uses, stores, processes, and protects your information when you download, install, and use Alarm on your Android device.
We take your digital privacy seriously. Our core design philosophy is **local-first privacy**: your alarm schedules, clock configurations, timer data, bedtime preferences, and personalized app settings are stored locally on your device and are never sold, rented, or transferred to remote servers. Where external connections and third-party software development kits (SDKs) are utilized—such as for serving advertisements, measuring application stability, and loading news content—we maintain strict compliance with Google Play Developer Program Policies, the General Data Protection Regulation (GDPR), the California Consumer Privacy Act as amended by the California Privacy Rights Act (CCPA/CPRA), and other applicable global privacy regulations.
Please review this Privacy Policy thoroughly. By installing, opening, or continuing to use the Application, you acknowledge and agree to the data handling practices outlined herein. If you have questions or concerns, please contact us at **shivanshspices3@gmail.com
---
## 2. Information We Collect
We categorize the data processed by our Application into two primary categories: **(A) Information processed and stored strictly on your device**, and **(B) Information processed or collected by integrated third-party service providers**.
### 2.1 Information Processed Locally on Your Device
The Application operates primarily offline for its utility functions. The following information remains entirely on your physical device:
1. **Alarm and Clock Records:**
- Specific alarm wake-up times, snooze durations, recurring day schedules, custom alarm labels, selected ringtone audio URIs, and challenge settings (e.g., math problems or device shake dismiss).
- Configured countdown timers, stopwatch lap records, bedtime schedules, sleep target durations, and local sleep logs.
- Selected world clock cities and custom timezone offsets.
- *Storage:* Stored in encrypted or sandbox-protected SQLite databases via Android Room (`alarm_clock.db`) and device-protected direct boot storage.
2. **Call Duration and Telephony State (After-Call Feature):**
- When the optional After-Call feature is enabled, the App detects call termination events (`EXTRA_STATE_IDLE`), calculates elapsed call duration, and reads the incoming/outgoing telephone number if available to display a local post-call summary card and allow one-tap follow-up alarm creation.
- *Processing:* Processed purely in transient device memory (`CallReceiver` and `AfterCallEndActivity`) and stored locally if you choose to create a reminder in the local `ReminderDatabase`. **Phone call audio, call audio recordings, SMS text messages, and full call history logs are never collected, recorded, or transmitted to any server.**
3. **Screen Time and App Usage Statistics:**
- If you grant the system Usage Access permission, the App queries Android's `UsageStatsManager` locally to display daily and weekly screen time summaries and frequently used apps on the launcher screen.
- *Processing:* Computed entirely on-device (`ScreenTimeRepositoryImpl`). Usage metrics are neither uploaded to our servers nor shared with advertising partners.
4. **Wi-Fi and Network State Details:**
- The App monitors local network connectivity states via `ConnectivityManager` and `WifiManager` to display network connection speed (Mbps), frequency band (2.4 GHz, 5 GHz, 6 GHz), and signal quality indicators (`WifiConnectionMonitor`).
- *Processing:* A normalized composite network signature (local router gateway, subnet, and network ID) is held in local memory to prevent duplicate popups when reconnecting to the same router. Network signatures are never transmitted off the device.
5. **Battery and Charging Status:**
- The App monitors battery level, charging source (AC, USB, wireless), and charging speed to provide battery full/unplug notifications and charging animations (`ChargingReceiver`).
- *Processing:* Handled exclusively on-device.
6. **Home Launcher and Installed Application Metadata:**
- When used as your home launcher (`android.intent.category.HOME`), the App reads installed package names, application labels, and launcher activity icons via Android's `PackageManager` and `LauncherApps` APIs to render your desktop, dock, and app drawer.
- *Processing:* Monitored via local receivers (`PackageMonitorReceiver`). Your app catalog is never uploaded or shared with advertisers.
7. **Search History and Preferences:**
- Recent search terms entered into the home search bar are retained in local application preferences (`SearchPreferences`) for quick auto-complete.
- *User Control:* You can clear your search query history at any time with a single tap inside the search interface.
### 2.2 Information Collected Automatically by Third-Party SDKs
When connected to the internet, certified third-party SDKs integrated into our App collect certain diagnostic, analytics, and advertising data:
1. **Device and Technical Identifiers:**
- Device manufacturer, model, screen resolution, operating system version (e.g., Android 14, 15, 17), system language, mobile carrier, battery level, network connection type (Wi-Fi, 4G, 5G), and IP address.
- Google Advertising ID (GAID / AD_ID) and Android Privacy Sandbox Topics / Attribution credentials, subject to your device privacy settings.
2. **Usage, Analytics, and Attribution Data:**
- Session duration, screen views (e.g., `main_screen`, `alarm_tab`, `timer_tab`), feature button interactions, in-app ad impressions, and click events.
- Google Play Install Referrer parameters (e.g., `utm_source`, `utm_medium`, `utm_campaign`, `gclid`) retrieved via the Play Store service to measure user acquisition campaigns.
3. **Crash and Diagnostic Reports:**
- Stack traces, crash timestamps, out-of-memory logs, and application performance metrics (e.g., cold start time, network latency).
---
## 3. How We Use Information
We use the collected and locally processed information solely for legitimate operational, analytical, and commercial purposes:
1. **Delivering Core Application Functionality:**
- Triggering high-priority audible alarms, full-screen wake alarms, snooze countdowns, and bedtime reminders accurately at the user's intended local time.
- Maintaining alarms reliably across device restarts, time zone shifts, Daylight Saving Time updates, and Android Doze battery optimizations.
- Rendering customizable launcher home screens, widgets, application drawers, and search tools.
- Delivering After-Call follow-up alarm creation and charging alert feedback.
2. **Serving Advertisements:**
- Displaying contextual, non-personalized, or personalized banner, interstitial, native, rewarded, and app open advertisements via Google AdMob to support free access to our features.
3. **Performance Monitoring and Diagnostics:**
- Detecting runtime errors, application crashes, memory leaks, and unresponsive UI threads via Firebase Crashlytics and Firebase Performance Monitoring to improve app reliability.
4. **Installation Attribution and Analytics:**
- Analyzing aggregate demographic trends, active user counts, feature adoption, and campaign effectiveness via Google Analytics for Firebase.
5. **Displaying Curated News Content:**
- Querying the Infinity Infotech News API (`https://news.infinityinfotech.co.in/`) using cryptographic HMAC request signatures to fetch news headlines, category articles, and story content.
---
## 4. App Permissions
To deliver its utility and alarm clock functions, the Application requests several Android system permissions. Below is an itemized breakdown of why each permission is required and how it is handled:
| Android Permission | Type | Why It Is Needed & Feature Used | Data Transmitted? |
|---|---|---|---|
| `android.permission.USE_EXACT_ALARM` | Normal (Restricted) | Mandatory for scheduling alarms that must ring at the exact millisecond set by the user, bypassing Android Doze mode. Core Alarm & Timer feature. | **No.** Local system registration only. |
| `android.permission.SCHEDULE_EXACT_ALARM` | Normal (API <= 32) | Legacy compatibility declaration for scheduling exact alarms on Android 12 and 12L devices. | **No.** Stays on device. |
| `android.permission.POST_NOTIFICATIONS` | Runtime (Dangerous, Android 13+) | Required to display alarm notifications, active timer countdown banners, charging status alerts, and bedtime reminders in the notification tray. | **No.** Stays on device. |
| `android.permission.USE_FULL_SCREEN_INTENT` | Normal (Special) | Enables the incoming full-screen ringing screen (`RingingActivity`) to wake the display and overlay the lock screen when an alarm rings. | **No.** Stays on device. |
| `android.permission.RECEIVE_BOOT_COMPLETED` | Normal | Allows the app to reschedule all active alarms, timers, and bedtime reminders automatically after the device reboots or updates. | **No.** Stays on device. |
| `android.permission.WAKE_LOCK` | Normal | Prevents the device CPU from sleeping while an alarm or timer is playing its audio/vibration sequence. | **No.** Stays on device. |
| `android.permission.VIBRATE` | Normal | Allows haptic vibration patterns during alarm ringing, timer alerts, and user UI interactions. | **No.** Stays on device. |
| `android.permission.FOREGROUND_SERVICE` & `FOREGROUND_SERVICE_MEDIA_PLAYBACK` | Normal | Required on Android 9+ and Android 14+ to run background services (`RingingService`, `TimerRingingService`, `SleepSoundsService`) for continuous audio playback without system termination. | **No.** Stays on device. |
| `android.permission.ACCESS_NOTIFICATION_POLICY` | Special Access | Allows the Bedtime feature to activate and deactivate Do Not Disturb (DND) mode automatically according to your sleep schedule. | **No.** Stays on device. |
| `android.permission.READ_PHONE_STATE` | Runtime (Dangerous) | Used exclusively by the optional After-Call feature (`CallReceiver`) to detect call start and termination, calculate call duration, and offer instant follow-up alarm creation. | **No.** Processed locally only. |
| `android.permission.SYSTEM_ALERT_WINDOW` | Special App Access | Required for displaying transparent overlay dialogs and after-call notification cards over other applications. | **No.** Stays on device. |
| `android.permission.PACKAGE_USAGE_STATS` | Special App Access | Enables the Screen Time feature (`ScreenTimeRepositoryImpl`) to query device foreground app usage locally and show daily/weekly digital wellbeing summaries. | **No.** Processed locally only. |
| `android.permission.ACCESS_NETWORK_STATE` & `ACCESS_WIFI_STATE` | Normal | Monitors network connectivity for loading news/ads and powers the Wi-Fi alert tool to inform users of Wi-Fi connection quality and frequency bands. | **No.** Processed locally only. |
| `android.permission.INTERNET` | Normal | Mandatory for downloading news articles via News API, fetching Remote Config values, loading ad content, and transmitting crash/analytics reports. | **Yes.** Diagnostic/ad data only. |
| `com.google.android.gms.permission.AD_ID` | Normal (Merged SDK) | Allows Google Mobile Ads to access the Google Advertising ID for ad frequency capping and relevant ad attribution. | **Yes.** Transmitted to Google. |
> **User Control & Revocation:** You can grant, deny, or revoke any runtime permission (`POST_NOTIFICATIONS`, `READ_PHONE_STATE`) or Special App Access permission (`Display over other apps`, `Usage access`, `Do Not Disturb access`) at any time via your device's **Settings > Apps > Alarm > Permissions**. Revoking optional permissions will only disable the associated feature (e.g., After-Call or Screen Time) while core alarm functions remain functional.
---
## 5. Advertising and Third-Party Services
We integrate vetted third-party SDKs that process technical data under their own independent privacy policies:
### 5.1 Google Mobile Ads (AdMob)
- **Provider:** Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA.
- **Purpose:** Monetization via Banner, Interstitial, Native, Rewarded, and App Open ads.
- **Data Processed:** Advertising ID (GAID), IP address, device telemetry, interaction timestamps, diagnostics.
- **Privacy Policy:** [https://policies.google.com/technologies/ads](https://policies.google.com/technologies/ads)
5.2 Google Firebase (Analytics, Crashlytics, Remote Config, Performance)
- **Provider:** Google LLC.
- **Purpose:** Operational stability, crash logs, dynamic feature configuration, and installation attribution.
- **Data Processed:** Firebase installation IDs, device hardware model, OS version, stack traces, app session events, install referrer parameters.
- **Privacy Policy:** [https://firebase.google.com/support/privacy](https://firebase.google.com/support/privacy)
5.3 Google Play Install Referrer
- **Provider:** Google LLC.
- **Purpose:** Verifying whether installations originated from paid promotional campaigns or organic Play Store searches.
- **Data Processed:** Play Store referrer URL string, click timestamp, install begin timestamp.
5.4 Infinity Infotech News API & Image Loading
- **Provider:** Infinity Infotech (`https://news.infinityinfotech.co.in/`).
- **Purpose:** Fetching global news feeds, categories, and article details.
- **Data Processed:** API requests containing HMAC-signed security headers, application package code, and version code. No personal user data is sent. Article thumbnail images are loaded via the Coil open-source image loading library.
5.5 Microsoft Clarity (Inactive Integration)
- **Provider:** Microsoft Corporation.
- **Status Notice:** The Microsoft Clarity SDK is present as a compiled dependency library (`com.microsoft.clarity:clarity`), but session recording and analytics capturing have **not** been enabled or initialized within our production code. No user session recordings or heatmap data are transmitted to Microsoft.
---
6. Data Storage and Security Practices
We implement industry-standard security safeguards to protect all user data:
1. **Encryption in Transit:** All external communication between the App and third-party servers (Google Firebase, Google AdMob, News API) is strictly encrypted using modern Transport Layer Security (TLS/HTTPS). Plaintext HTTP connections are disabled.
2. **Encrypted Local Storage:** Sensitive API authorization tokens are encrypted on-device using AndroidX Security Crypto (`EncryptedSharedPreferences`) backed by AES-256-GCM encryption and the hardware-backed Android KeyStore.
3. **Sandbox Isolation:** All local SQLite databases (`alarm_clock.db`, `ReminderDatabase`, `news_database`) are stored within the application's private internal storage sandbox (`/data/data/com.alarm.deskclock.alarmclock/`), protected by Android kernel-level Linux user ID separation. Other applications cannot access these files.
4. **Direct Boot Protection:** Alarm scheduling definitions necessary for ringing before device unlock are stored in Android Device Protected Storage (`DirectBootAlarmStorage`), ensuring alarm reliability while isolating personal data until the user unlocks the device.
---
## 7. Data Sharing and Disclosure
We **do not sell, trade, or rent** your personal information to third parties. Data sharing is limited strictly to the following circumstances:
1. **Third-Party Service Providers:** Technical diagnostic, ad-serving, and analytics data is transmitted directly to our contracted partners (Google LLC) as described in Section 5.
2. **Legal and Safety Compliance:** We may disclose information if required to do so by applicable law, valid judicial subpoena, court order, or governmental regulation, or in good faith to protect the property, safety, or legal rights of our users, the public, or the developer.
3. **Business Transfers:** If the Application undergoes a merger, acquisition, asset sale, or reorganization, user data handling will remain subject to the commitments made in this Privacy Policy until a new policy is established.
---
## 8. Data Retention and Deletion
1. **Local Device Data:** All local alarm entries, reminders, world clocks, timers, preferences, and cached news remain on your device until you modify them, delete them within the App, clear application data via system settings, or uninstall the Application. Uninstalling the App permanently purges all local SQLite databases and preferences.
2. **Analytics and Advertising Data:** Google Analytics for Firebase retains user-level and event-level data in accordance with Google's default retention periods (typically 2 to 14 months), after which data is aggregated or automatically purged.
3. **Data Deletion Inquiries:** Because we do not operate remote user accounts or maintain a proprietary cloud database of user profiles, we do not hold personal identity records on remote servers. To erase all data associated with your use of Alarm, simply clear the App storage in **Android Settings > Apps > Alarm > Storage > Clear Data** and uninstall the application. To reset your advertising profile, navigate to **Settings > Google > Ads > Reset advertising ID** (or *Delete advertising ID*).
---
## 9. User Choices, Rights, and Privacy Controls
Depending on your geographic jurisdiction (including the European Economic Area, United Kingdom, Brazil, and California/US States), you possess specific privacy rights:
1. **Permission Management:** You maintain full authority to grant or revoke any optional permission via Android System Settings.
2. **Ad Personalization Opt-Out:** You can opt out of interest-based personalized advertising by navigating to **Android Settings > Google > Ads** and selecting "Delete advertising ID" or adjusting your ad privacy topics.
3. **GDPR / UK Data Protection Rights (EEA & UK Users):**
- *Right of Access & Portability:* You can review all data stored in the app directly on your screen.
- *Right to Erasure ("Right to be Forgotten"):* You can instantly delete all local records by clearing application storage or uninstalling.
- *Right to Object / Restrict Processing:* You may disable internet access or revoke runtime permissions at your discretion.
4. **California Privacy Rights (CCPA / CPRA):**
- We do not sell personal information or share personal information for cross-context behavioral advertising without providing appropriate statutory opt-out rights.
- We do not collect or process sensitive personal information to infer characteristics about consumers.
---
## 10. Children's Privacy
The Application is designed as a general-audience utility for individuals aged 13 and older (or 16 and older in the EEA). We do not knowingly target, solicit, or collect personal data from children under the age of 13.
If you are a parent or legal guardian and believe that your child has provided us with personal information, or if you suspect third-party SDKs have inadvertently captured data from an underage user, please contact us at **[INSERT_CONTACT_EMAIL]**. We will promptly take steps to delete any such data from our analytics and systems.
---
## 11. International Data Transfers
When external network connections are made, technical data collected by our third-party service providers (such as Google LLC) may be transferred to, stored, and processed in the United States and other countries where Google maintains data centers. These third parties utilize standard contractual clauses (SCCs) and adherence to recognized data transfer frameworks to ensure an adequate level of data protection in compliance with GDPR and international data protection standards.
---
## 12. Changes to This Privacy Policy
We may periodically revise and update this Privacy Policy to reflect changes in our operational features, legal obligations, platform security standards, or Google Play policies. When changes occur, we will update the **Last Updated** date at the top of this document.
For material modifications that affect data handling or user rights, we will provide prominent notice within the Application (such as via an in-app banner or update notice) or direct you to review the revised terms before they take effect. Continued use of the Application after an updated Privacy Policy is posted constitutes your acceptance of the revisions.
---
## 13. Contact Us
If you have questions, feedback, privacy requests, or complaints regarding this Privacy Policy or our data handling practices, please contact us:
- Developer / Organization:- Shivansh Spices
- Contact Email : - shivanshspices3@gmail.com
- Official Policy URL:** https://sites.google.com/view/alarm-clock-home/home