Privacy Policy
Privacy Policy
App name: AppLock
Effective date: September 30, 2026
Developer / publisher: Apps Haven
Permission disclosure and choice: Before you enable Usage Access, Display over other apps, Camera, notifications, or optional Device Administrator access, AppLock explains the relevant purpose in its settings flow. You can decline or revoke access at any time; the related feature may then be unavailable.
1. Scope and commitment
This Privacy Policy explains how Apps Haven (“we”, “us”, or “our”) handles information processed by AppLock (the “Application”). AppLock is a device-security utility. We aim to minimize data access, request permissions only for relevant features, and keep the Application’s core security data local.
2. Information processed on your device
The following information may be processed locally to provide features you choose to use:
- Credentials: PINs, passwords, patterns, knock codes, and related authentication records are stored as protected local credential records. The app does not upload them to Apps Haven.
- Biometrics: Fingerprint and face unlock use Android’s native biometric prompt. AppLock does not receive or store raw fingerprint or face data.
- Installed-app information: AppLock reads the launchable apps visible to Android so you can choose which apps to lock. Selected package names, lock methods, and schedules are stored locally.
- Foreground-app state: Usage Access is used to determine which protected app is currently open so the lock overlay can be shown. The current app is not uploaded to Apps Haven.
- Intruder selfies and logs: If you enable Intruder Selfie and grant camera access, a front-camera image may be captured after a failed verification. Local logs can include the target app name, failed method, date, time, and local file path.
- Vault files: Photos, videos, and documents selected by you for the Secret Vault are encrypted and stored in the app’s private local storage. Current vault encryption uses AES-256-GCM with a key held by Android Keystore.
- Settings and customization: Theme choices, wallpapers, emoji themes, PIN button style, dark mode, schedules, relock preferences, disguise preferences, local backups, and security settings are stored locally to remember your choices.
- Device protection state: The app may read whether required Android settings, notification access, overlay access, Usage Access, battery-optimization exemptions, widgets, and optional Device Administrator protection are active.
3. Permissions and why they are used
| Permission or access | Purpose in AppLock |
|---|---|
PACKAGE_USAGE_STATS | Detect the foreground app for app-lock enforcement. This access is not used to upload a browsing history. |
SYSTEM_ALERT_WINDOW | Display the lock screen over a protected app. |
CAMERA (optional) | Capture an Intruder Selfie only after you enable that feature and grant camera access. |
USE_BIOMETRIC (optional) | Call Android’s fingerprint or face authentication prompt. |
| Foreground service | Keep foreground-app monitoring and protection reliable while the service is active. |
POST_NOTIFICATIONS | Show the ongoing protection status and, when configured, a re-entry shortcut. |
RECEIVE_BOOT_COMPLETED | Resume protection after the device restarts. |
| Device Administrator (optional) | Add an authentication step before AppLock can be disabled or uninstalled. |
VIBRATE | Provide haptic feedback for selected lock-screen actions. |
| Android Photo Picker / system file access | Import media or documents only when you explicitly select them for the Vault. The app uses Android’s user-controlled picker flow rather than requesting broad all-files access. |
4. Collection, transmission, and sharing
The current AppLock project does not include a developer-operated backend, user account system, advertising SDK, analytics SDK, or in-app billing SDK. We do not knowingly receive or sell your PINs, passwords, biometric data, vault content, app-lock list, schedules, or intruder photos.
AppLock can open external Google Play links when you use Explore. Google Play may collect and process information under Google’s policies. Android, device manufacturers, app stores, or crash-reporting services included by the device may also process system information independently of Apps Haven. Review those providers’ policies for details.
5. Retention and deletion
- Local settings, logs, credentials, and vault files remain on the device until you delete them, clear app data, or uninstall the app, subject to Android storage behavior.
- Deleting an intruder record removes the record and the associated local image when the operation succeeds.
- Removing a vault item deletes the encrypted local copy. Exporting a file creates a separate copy in the destination chosen by Android.
- Before uninstalling, clearing data, switching devices, or factory-resetting, export vault content and create any backup you need. The Android Keystore key is installation-specific and is not recoverable by Apps Haven.
6. Security
We use Android security facilities and local encryption for the features described above. No software can guarantee absolute security. Keep Android updated, protect your device, use strong credentials, review permissions, and do not share your backup or re-entry codes.
7. Children’s privacy
AppLock is a general device-security utility and is not directed at children. We do not knowingly collect personal information from children through a developer-operated service. If you believe a child has provided information to Apps Haven, contact us so we can review the request.
8. International use and changes
AppLock may be used in different countries. You are responsible for complying with local law when recording images, locking apps on a shared device, or using Device Administrator features. We may update this Policy when the Application or legal requirements change. The new effective date will appear on this page.
9. Contact us
For privacy questions, requests, or concerns, contact:
Apps Haven
mafizulislam018678@gmail.com
Google Play publisher search: pub:Apps Haven
Comments
Post a Comment