Privacy Policy

This Privacy Policy applies to the ApzLock Android application ("App"), developed and published by Dowble Technologies Pvt. Ltd. ("we", "us", or "our"), available on the Google Play Store.

ApzLock is an app-locking and biometric security application. It allows you to protect your sensitive apps with fingerprint, biometric authentication, or PIN-based access control. The App operates entirely on your device — it does not have a backend server, does not create user accounts, and does not communicate with external services to store or process your security data.

ApzLock processes the following information exclusively on your device to deliver app-locking functionality:

• Which apps you select for protection (app package names)
• Your master PIN, password, or pattern (salted, hashed, and encrypted on-device)
• Your biometric data (fingerprints, face scans) for local authentication only
• App lock preferences (re-lock timeout, lock method, intruder-selfie toggle)

All this data is stored locally on your device only and is never transmitted anywhere. We do not have access to it, cannot see it, and cannot retrieve it.

We do not collect, process, transmit, or store any of the following:

• Your name, email address, or personally identifiable information
• Which apps you actually open or how often you use them
• Your location, contacts, calendar, or call history
• Device identifiers (IMEI, Android ID, advertising ID)
• Usage analytics, crash logs, or behavioral data
• Screenshots or intruder selfie images (stored locally only, not transmitted)
• Any data that leaves your device for any purpose

There are no third-party analytics SDKs, advertising SDKs, or tracking libraries included in the App. Your phone stays yours.

ApzLock requests the following Android permissions solely to deliver app-locking and biometric security functionality. These permissions are used only on-device and are never used to collect or transmit data.

• 📊
  Package Usage Stats (PACKAGE_USAGE_STATS)

  Allows ApzLock to detect when you open a protected app so it can show the lock screen. This is processed locally on your device only and is never sent anywhere.
  Core feature
• 🖼️
  Display Over Other Apps (SYSTEM_ALERT_WINDOW)

  Allows ApzLock to show the lock screen overlay when you attempt to open a protected app.
  Core feature
• 🎯
  Fingerprint / Biometric (USE_BIOMETRIC, USE_FINGERPRINT)

  Allows ApzLock to authenticate you using your fingerprint or face recognition. Biometric data never leaves your device and is managed by Android's secure biometric framework.
  On-device only
• 📱
  Query All Packages (QUERY_ALL_PACKAGES)

  Allows ApzLock to detect installed apps so you can select which ones to protect. This data remains on your device only.
  On-device only
• 📷
  Camera (CAMERA) — Optional

  Used only if you enable the optional "intruder selfie" feature. Photos are stored locally on your device and never transmitted.
  Optional
• 📢
  Post Notifications (POST_NOTIFICATIONS)

  Used to display the ongoing notification that Android requires while the protection service is running. No promotional or tracking notifications are ever sent.
  On-device only
• ⚡
  Foreground Service (FOREGROUND_SERVICE, FOREGROUND_SERVICE_SPECIAL_USE)

  Allows ApzLock to run a special-use foreground service that continuously monitors app launches to enforce locks. This requires a visible notification while the service is active.
  Core feature
• 💫
  Boot Completed (RECEIVE_BOOT_COMPLETED)

  Allows ApzLock to restart its protection service when your device boots, ensuring your apps remain protected.
  Core feature
• 📳
  Vibrate (VIBRATE)

  Used to provide haptic feedback when you authenticate with biometric or PIN entry.
  Optional
• 🔋
  Ignore Battery Optimizations (REQUEST_IGNORE_BATTERY_OPTIMIZATIONS)

  Optional. If you allow it, Android won't suspend ApzLock in the background, so your protection keeps running and reliably restarts after the device reboots. You can decline this and the app still works.
  Optional
• ⚙️
  Accessibility Service

  Used as a fallback mechanism to detect app launches if standard methods are unavailable. Works on-device only for security monitoring.
  Fallback feature

You can revoke any permission at any time via your device's Settings → Apps → ApzLock → Permissions. If you deny critical permissions, the app's core features will not function.

When you grant the necessary permissions, ApzLock operates as follows:

• App Detection: The app monitors when you attempt to open an app you've selected for protection using Android's Package Usage Stats API.
• Lock Screen Display: When a protected app is launched, ApzLock displays a lock screen overlay asking for biometric or PIN authentication.
• Biometric Authentication: Your fingerprint or face is authenticated locally using Android's secure biometric framework. We never see or store this data.
• Access Control: If authentication succeeds, the app is allowed to open. If it fails, access is denied.

All of this processing happens locally on your device. The App has no internet connectivity requirement and makes no network requests. Lock data, protected app lists, and biometric information never leave your phone and are never shared with anyone.

ApzLock stores the following data locally on your device in its private app storage:

• Your PIN, password, or lock pattern — salted, hashed with PBKDF2, and stored in AES-256 encrypted storage
• The list of apps you have protected
• App lock preferences (re-lock timeout, lock method, feature toggles)
• Intruder selfie images (if the feature is enabled, stored locally only)

This data:

• Is stored only in your device's private app storage
• Is never transmitted off your device
• Is permanently deleted when you uninstall the App
• Contains no personally identifiable information (no names, emails, etc.)
• Is protected by your device's standard app data protection mechanisms

ApzLock does not integrate with or send data to any third-party service, including but not limited to:

• Analytics platforms (Google Analytics, Firebase, Mixpanel, etc.)
• Advertising networks or ad SDKs
• Crash reporting services
• Cloud storage or sync services
• Authentication services (except Android's built-in biometric framework)
• Social media platforms

The only external system involved is the Google Play Store, which distributes the App and may collect its own installation and update data under Google's Privacy Policy. We have no control over or access to that data.

For convenience, the in-app "Rate", "Share app" and "Feedback & report a bug" options open your Play Store, the Android share sheet, and your own email app respectively. These are launched only when you tap them, and ApzLock does not attach any personal data — the shared text is just the app's Play Store link, and anything you choose to write in an email is sent by you, through your email provider, directly to us.

ApzLock prioritizes your security:

• No Backend: Since we don't have a server, there's no central database to breach. Your data remains entirely under your control.
• Biometric Security: Your fingerprint and face data are managed exclusively by Android's secure biometric framework and never exposed to ApzLock code.
• Encrypted Storage: Sensitive data like PINs are encrypted before being stored locally.
• No Transmission: Because nothing leaves your device, there's no risk of data interception during transmission.

ApzLock is a general-purpose security utility app and is not directed at children under the age of 13. Since we collect no personal data whatsoever and all processing happens locally on the device, there is no risk of inadvertent collection of children's data through our App.

Since ApzLock stores all data locally on your device:

• All your lock preferences, protected app lists, and settings are deleted when you uninstall the App
• You can manually clear app data at any time via Settings → Apps → ApzLock → Storage → Clear Storage
• You have complete control over your data and can delete it whenever you want

We may update this Privacy Policy if the App's functionality changes in a way that affects how data is handled. Any updates will be posted at dowble.com/privacy/apzlock and, where significant, communicated via a Play Store update note. The "Last updated" date at the top of this page will always reflect the most recent revision.

If we ever change our data practices to include any form of data transmission or collection, we will seek explicit consent before doing so and update this policy accordingly.

If you have any questions or concerns about this Privacy Policy or about ApzLock, please contact us: