Privacy Policy

Last updated: September 25, 2026

This Privacy Policy describes how AppLock Master (the "App", package jomostudio.app.lock.applock.locker.password) collects, uses, and protects information when you use it. By using the App you agree to the practices described in this policy.

1. The Short Version

• Your passcode, pattern, security question, locked-app list, intruder photos, notification history and private-browser data never leave your device. They are stored locally and are not uploaded to us or anyone else.
• We do not require an account and we do not collect your name, email address, or contacts.
• Like most free apps, the App shows ads (Google AdMob) and uses anonymized analytics (Amplitude, hosted in the European Union, and Google Firebase Analytics), crash reporting (Google Firebase Crashlytics) and purchase management (RevenueCat). These providers may process device identifiers as described below.

2. Information Stored Only on Your Device

The App's core features work entirely offline. The following data is created and stored only on your device and is never transmitted to our servers (we do not operate any servers for this data):

• Lock credentials — your PIN or pattern, and your security question and answer used for passcode recovery.
• Protected app list — which installed apps you chose to lock.
• Intruder selfies — if you enable the Intruder Selfie feature, the App uses the front camera to take a photo after repeated wrong passcode attempts. These photos are saved to the App's private storage on your device only. You can view and delete them at any time inside the App. Disabling the feature stops any capture.
• Notification history — off until you turn it on in the App and grant notification access in Android settings. It then records the notifications posted by the apps you choose (by default only the apps you locked; you can widen it to all apps), as they arrive and, when you turn it on, those already in your notification shade. For each one it keeps the app it came from, the title and text, and the time; for messaging apps also the conversation name, the sender's name and profile picture, and any photo the notification included. This is how a message its sender later deletes stays readable in the App. Notifications often contain messages written by other people; they are kept the same way, on your device only. The App sees only what a notification showed: it cannot read messages that never produced a notification, and it does not open other apps' own data. Records are kept for 30 days by default (you can choose 7 days, 30 days or no limit), and you can clear the whole history at any time. If you turn on hiding, the App also removes those notifications from the system shade once they are saved, so their content is readable only inside the App behind your passcode. An image you choose to save to your gallery is then outside the App's private storage.
• Private browser — cookies and cache are deleted every time a browsing session ends (when you swipe the App away from your recent apps). Browsing history is not saved unless you turn it on. Open tabs and their preview images are kept between sessions unless you turn that off. Bookmarks stay until you delete them. "Clear all browsing data" deletes history, tabs, cookies and cache, and keeps bookmarks.
• App usage information — with your permission (Usage Access), the App reads which app is in the foreground to show the lock screen, and aggregate usage times to sort your app list. This information is processed on-device and is not uploaded.
• Settings — themes, re-lock rules, and other preferences.

Uninstalling the App permanently deletes all of the above.

3. Permissions the App Requests and Why

• Display over other apps — to draw the lock screen over protected apps.
• Usage Access — to detect the foreground app so locked apps can be protected, and to order your app list by usage.
• Camera — only if you enable Intruder Selfie, to capture a photo after failed unlock attempts. The camera is never used otherwise.
• Notification access — only if you turn on the notification history, to record notifications and, if you ask, hide them from the shade, as described in Section 2. You can revoke it at any time in Android settings, and recording stops at once.
• See installed apps — to list the apps you can lock. The list is read on your device and is not uploaded.
• Post notifications — to show the ongoing protection-service notification.

Each permission is requested only when the related feature needs it, and the App keeps working (without that feature) if you decline.

4. Data Processed by Third-Party Services

We use a small number of industry-standard services. They may collect device identifiers (such as the Android Advertising ID), coarse technical data (device model, OS version, app version, language), and interaction events, under their own privacy policies:

• Google AdMob (advertising) — Google Privacy Policy, AdMob data usage. Where required, you will be asked for consent before personalized ads are shown; you can also reset or delete your Advertising ID in Android settings.
• Google Firebase Analytics & Crashlytics (anonymous usage statistics and crash reports that help us fix bugs) — Firebase Privacy.
• Amplitude (anonymous product analytics — which screens are opened, which settings are changed, whether a lock screen was unlocked — so we can see where the App is confusing and fix it). Amplitude receives an app-generated random device identifier, your device model, operating-system version, language, app version and the events themselves; it never receives your passcode, pattern, security answer, locked-app list, intruder photos, the content of any notification, or the addresses, titles or searches of pages you open in the private browser (only counts, such as how many trackers were blocked). Our Amplitude project is hosted in the European Union — Amplitude Privacy Policy.
• Google Play install referrer — on the very first launch the App asks the Google Play Store which campaign or link brought you to it, and reports that referrer string (never anything about you) so we can tell which marketing channels work — Google Privacy Policy.
• RevenueCat (managing premium subscriptions/purchases; receives purchase tokens and an anonymous app user ID, never your payment details) — RevenueCat Privacy.
• Google Play Billing (payment processing for premium; handled entirely by Google Play) — Google Privacy Policy.
• GitHub (the private browser's ad and tracker blocklist is refreshed about once a week from a public list hosted on GitHub; the download carries nothing about you or your browsing beyond what any download reveals, such as your IP address) — GitHub Privacy Statement.

Websites you open in the private browser, and the search engine you choose there, receive your requests directly, under their own privacy policies. The browser blocks known ad and tracker addresses before they are contacted.

We do not sell personal information, and we do not share the on-device data described in Section 2 with any of these providers.

5. Legal Bases (GDPR)

If you are in the European Economic Area, we process the limited data above on these bases: consent (personalized ads, optional features such as Intruder Selfie and the notification history), legitimate interest (crash reporting, aggregate analytics, fraud prevention), and contract (delivering premium purchases). You may withdraw consent at any time via the in-app ad-consent options or your device settings.

You have the rights to access, rectify, erase, restrict, or object to processing, and to data portability. Because the App's personal data lives on your device, you can exercise most rights directly (e.g. deleting intruder photos or clearing the notification history in-app, or uninstalling). For anything else, contact us using Section 10.

6. California Privacy Rights (CCPA/CPRA)

We do not sell or share personal information as defined by the CCPA/CPRA. California residents may request details about, or deletion of, personal information processed by our third-party providers by contacting us.

7. Children's Privacy

The App is not directed at children under 13, and we do not knowingly collect personal information from children. If you believe a child has provided personal information through the App, please contact us and we will take appropriate action.

8. Security

Lock credentials, intruder photos, the notification history and private-browser data are kept in the App's private, sandboxed storage that other apps cannot read on non-rooted devices. No method of electronic storage is 100% secure, but keeping this data off the network is the strongest protection we can offer: it cannot leak from servers we don't have.

9. Changes to This Policy

We may update this policy from time to time. Material changes will be reflected on this page with a new "Last updated" date. Continued use of the App after changes means you accept the updated policy.

10. Contact Us

If you have questions or requests about this Privacy Policy, contact us at:
📧 hello@jomostudio.tech

This page serves multiple apps we publish; the app it applies to is selected by the pkg parameter in the page address.