AppLocker Privacy Policy
Effective Date: 2026年10月10日
Overview
AppLocker ("the App") is developed by DevCodeApps. This Privacy Policy explains how we collect, use, and protect your information when you use AppLocker. The same policy is published at https://null-byt3s.github.io/applocker-privacy-policy/ (last updated October 2026).
Data We Collect
● Installed app list: We query the list of installed applications on your device solely to display them in the app list so you can choose which apps to lock. This data never leaves your device. ● Camera (Intruder Selfie): If you enable the Intruder Selfie feature (paid: AppLocker Pro or Lifetime Premium) and allow camera access, the front camera captures a photo when someone enters the wrong PIN. Photos are stored locally on your device and never leave it. ● Usage Stats: We use Android's UsageStatsManager to detect when a locked app is launched. This data is processed locally in real time and is never stored or transmitted. ● Biometric data: Fingerprint/biometric authentication is handled entirely by the Android OS (BiometricPrompt). We do not access or store any biometric data. ● Notifications: The app shows local notifications, for example break-in alerts and the prompt to lock a newly installed app. They are not sent to external servers. ● Notification access (optional, AppLocker Pro): If you turn on Hide notification content, AppLocker uses Android's notification access to remove notifications from the apps you have locked and shows a neutral placeholder instead. It does not read, store, or send the content of any notification.
Usage Analytics and Crash Diagnostics
● Usage analytics: Via Google Analytics for Firebase we collect anonymous product events (for example which onboarding step you reached, which features you open, and whether a purchase screen was shown) together with app version, device model, OS version, coarse region, and a randomly generated app-instance identifier. In the European Economic Area, the UK and Switzerland, collection stays off unless you agree in the privacy message the app shows when you first open it, and you can change your choice at any time under Settings → Privacy settings in the app. Elsewhere, usage analytics is on by default. ● Crash diagnostics: Via Firebase Crashlytics, if the app crashes we collect the crash report (stack trace), device model, OS version, and app version so we can fix the fault.
Data We Do NOT Collect
● We do not collect your name, email address, phone number, or location. ● Your PIN and pattern never leave your device. ● Intruder photos stay on your device. ● We never collect the contents of your locked apps, your messages, or your files. ● Analytics and crash data never include your PIN, your photos, or the list of apps you have locked. ● We do not sell your data.
Third-Party Services
● Google AdMob: The free version displays ads served by Google AdMob. AdMob may collect an advertising ID (GAID) for ad personalization. In the European Economic Area, the UK and Switzerland, ads are personalized only if you agree in the privacy message. ● Google Play Billing: Purchases and the AppLocker Pro subscription are processed by Google Play. We do not handle or store payment information directly. ● Google Play in-app updates and reviews: Update prompts and the optional rating prompt are shown by Google Play. ● Google Analytics for Firebase: Anonymous usage analytics (in the European Economic Area, the UK and Switzerland only with your consent). ● Firebase Crashlytics: Crash and stability reporting. ● Firebase Remote Config: Lets us change app settings, such as the free-plan app limit, without an app update. See Google's Privacy Policy for each of these services.
Permissions Explained
● QUERY_ALL_PACKAGES: Required to list all installed apps for the app-locking interface. ● FOREGROUND_SERVICE / FOREGROUND_SERVICE_SPECIAL_USE: Keeps the app monitor running to intercept locked app launches. ● SYSTEM_ALERT_WINDOW: Required to display the lock screen over other apps. ● PACKAGE_USAGE_STATS: Detects which app is currently in the foreground. ● CAMERA: Used only for the Intruder Selfie feature (AppLocker Pro or Lifetime Premium), and only after you allow it. ● USE_BIOMETRIC: Allows fingerprint unlock (AppLocker Pro or Lifetime Premium). ● RECEIVE_BOOT_COMPLETED: Restarts the lock service automatically on device reboot. ● POST_NOTIFICATIONS: Shows the local notifications described above (Android 13 and later ask first). ● REQUEST_IGNORE_BATTERY_OPTIMIZATIONS: Asks to run without battery restrictions, because some phones stop background apps and that would switch your locks off. ● Notification access (BIND_NOTIFICATION_LISTENER_SERVICE): Only if you turn on Hide notification content (AppLocker Pro), as described above. ● Device administrator (BIND_DEVICE_ADMIN): Only if you turn on Uninstall Protection, to stop others from uninstalling AppLocker. It uses no device-administrator policies. ● INTERNET / ACCESS_NETWORK_STATE / AD_ID: Used by the ad, purchase, analytics, crash-reporting and configuration services listed above.
Data Security
Your PIN is stored locally on your device in a hashed format (SHA-256) and never leaves it. Apart from the usage analytics, the crash diagnostics, and the ad, purchase and configuration services described above, no data is sent off your device.
Data Retention and Deletion
Everything AppLocker stores on your device (the hashed PIN or pattern, your settings, the list of locked apps, intruder photos and the break-in history) stays there. You can delete intruder photos and the break-in history in the app at any time, and uninstalling the app or clearing its data deletes all of it. Analytics and crash data are kept by Google under its retention settings. To ask about them or to request deletion, contact us at the address below.
Children's Privacy and Changes to This Policy
AppLocker is not directed at children under 13. We do not knowingly collect data from children. We may update this Privacy Policy. Updates will be reflected with a new "Last updated" date. Continued use of the App after changes constitutes acceptance of the revised policy.
Contact Us
If you have questions about this Privacy Policy, contact us at: under.cntrl.dev@gmail.com