Privacy Policy for WakeLock — Alarm Clock

Last updated: 11 May 2026

Developer: Zeenova

Contact: muhammadzeeshu0786@gmail.com

App package: com.zeenova.wakelockalarmclock

This Privacy Policy explains what information the WakeLock — Alarm Clock app ("the app", "we", "our") collects, how it is used, and the choices you have. By installing or using the app, you agree to this policy.

1. Information the app handles

1.1 Data stored only on your device

The following data is created and stored locally on your device. It is not transmitted to us or any third-party server:

1.2 Data collected by advertising partners

The app shows banner, interstitial and rewarded ads supplied by Google AdMob (Google Mobile Ads SDK). To deliver and measure ads, AdMob may collect:

This collection is performed by Google, not by us, and is governed by Google's own privacy policy:

You can limit ad personalisation at any time via: Settings → Privacy → Ads → Reset advertising ID / Delete advertising ID on your Android device.

1.3 Data we collect ourselves

None. The app does not have user accounts, does not contact any server we control, and does not include analytics or crash-reporting SDKs.

2. Permissions the app requests, and why

Permission Purpose
POST_NOTIFICATIONS Show the silent "Alarm set" notification and the full-screen alarm.
SCHEDULE_EXACT_ALARM, USE_EXACT_ALARM Fire alarms at the exact minute you chose.
USE_FULL_SCREEN_INTENT Bring the alarm screen to the foreground when the alarm rings.
WAKE_LOCK, TURN_SCREEN_ON, SHOW_WHEN_LOCKED, DISABLE_KEYGUARD Wake the screen so you actually hear and see the alarm.
VIBRATE Vibrate while the alarm rings, if you enabled it.
RECEIVE_BOOT_COMPLETED Re-arm scheduled alarms after the device reboots.
FOREGROUND_SERVICE, FOREGROUND_SERVICE_SPECIAL_USE Keep the alarm reliably playing when it fires.
REQUEST_IGNORE_BATTERY_OPTIMIZATIONS Ask you to whitelist the app so the OS doesn't kill alarms.
CAMERA Capture frames locally for the QR / Barcode and Object Scan challenges.
ACTIVITY_RECOGNITION Read live step counts for the Steps challenge.
ACCESS_NOTIFICATION_POLICY Ensure the alarm can ring even in Do Not Disturb mode.
INTERNET, ACCESS_NETWORK_STATE Required by Google AdMob to load ads and to show a "no internet" message before the rewarded-ad unlock flow.

We never sell or share these signals with third parties for their own marketing.

3. Children

The app is not directed to children under 13 (or the equivalent age in your jurisdiction). We do not knowingly collect data from children. The AdMob integration is configured for a general-audience app; if you are a parent or guardian and believe your child has used the app, please contact us so we can advise.

4. Data retention and deletion

Because all of the data created by your use of the app is stored on your device, you can delete it at any time by:

For data Google AdMob collects, follow Google's deletion / opt-out controls linked in section 1.2.

5. Security

Your local data is stored in the app's private storage area, which is sandboxed by Android from other apps. The anti-snooze PIN is never stored in plain text — only a salted hash is kept. Network traffic to AdMob is sent over HTTPS by the Google Mobile Ads SDK.

6. Your rights

Depending on where you live (e.g. EEA, UK, California), you may have rights to access, correct, delete, or port your personal data, or to object to certain processing. Because we do not collect personal data ourselves, most requests should be directed to Google for the AdMob data described in section 1.2. For anything held on your device, see section 4.

7. Changes to this policy

We may update this policy from time to time. The "Last updated" date above will change, and material updates will be highlighted in the app's release notes on Google Play.