📑 Table of Contents
- Introduction & Core Principles
- Data We Collect & Process
- Data We Strictly Do NOT Collect
- Android Permissions & Technical Usage
- Private Vault & Intruder Security Architecture
- Freemium Model, Rewarded Ads & In-App Purchases
- Third-Party Services & SDK Partners
- Google Play Data Safety Disclosures
- Data Retention & Permanent Deletion
- International Privacy Rights (GDPR, CCPA, DPDP)
- Children's Privacy (COPPA Compliance)
- Terms of Use & Service Agreement
- Disclaimers & Limitations of Liability
- Updates to This Privacy Policy
- Contact & Grievance Redressal
🛡️ 1. Introduction & Core Principles
Welcome to AppLock (also referred to as Aegis Lock) — Secure App Lock & Privacy Guard (package name: com.rn.namoksha.secure.applock), developed and published by Namoksha Digital ("we", "our", or "us").
We believe your personal privacy is a fundamental human right. AppLock was engineered from the ground up on a zero-knowledge, on-device architecture. Our core mission is to empower you to lock applications, secure private media files, prevent unauthorized physical intrusions, and manage notification privacy without having to sacrifice your privacy to cloud servers.
This document constitutes both our comprehensive Privacy Policy and our Terms of Use. Please read it carefully to understand how your device data is handled.
📊 2. Data We Collect & Process
To deliver core security functionality, crash analytics, and optional cloud feature updates, AppLock handles data in the following distinct categories:
2.1 Data Stored Exclusively on Your Device (App-Private Storage)
- Lock Credentials: Your PIN, Pattern, or Password is salted, hashed with cryptographic algorithms, and stored in protected, sandboxed Android app storage. Raw passwords are never retained or transmitted.
- Biometric Authentication: Biometric verification (fingerprint or face unlock) is delegated to Android's native
BiometricPromptAPI and handled directly inside the device's hardware-backed Trusted Execution Environment (TEE) / Secure Element. AppLock never reads, captures, or exports biometric templates. - Private Vault Content: Photos, videos, documents, and audio files placed in your Vault are encrypted using hardware-backed Android Keystore + AES-256-GCM authenticated encryption. Plaintext copies are unlinked from public media galleries upon import.
- Intruder Snapshots: When enabled, photos taken by the front camera upon repeated failed unlock attempts are saved locally with timestamps and failed attempt counts. They are never uploaded to any remote server.
- App Lock Configurations & Schedules: The list of packages you choose to lock, auto-lock timeouts, Focus Mode profiles, and notification privacy preferences are saved locally via Android Jetpack DataStore.
- Pro Style Preferences & Camouflage: Chosen lock screen background aesthetics, OLED black theme, acrylic blur settings, and decoy app icon configurations are stored locally.
2.2 Data Processed Automatically via Third-Party SDKs
- Diagnostics & Crash Reporting (Firebase Crashlytics): Device hardware model, operating system version, memory status, battery level at time of crash, and anonymized stack traces to rapidly fix bugs. This data contains no personally identifiable information (PII).
- Aggregated App Metrics (Google Analytics for Firebase): Pseudonymous, aggregated interaction metrics (such as screen visits, session frequency, onboarding completion, and feature adoption) to improve app responsiveness and usability.
- Advertising Identifiers (Google AdMob): For non-premium users, Google AdMob may process the Google Advertising ID (AAID), coarse IP-derived geographic location (country/city level), and ad interaction telemetry for frequency capping, ad mediation, and personalized/contextual advertising (subject to user consent).
- In-App Purchase & Subscription Tokens (Google Play Billing): Purchase tokens and subscription status indicators returned by the Google Play Store to verify premium entitlements. We do not process or store financial card numbers or bank information.
🚫 3. Data We Strictly Do NOT Collect
- No Account Information: We do not require you to create an account, register, or provide your name, phone number, or email address to use AppLock.
- No Upload of Private Vault Files: Your photos, videos, and documents never leave your physical smartphone. We have no cloud servers capable of receiving them.
- No Content Snooping: We do NOT monitor, inspect, or intercept the internal text, messages, chats, or media inside the applications you lock.
- No Tracking of Browsing or App Activity: We do NOT log which websites you visit or record user behavior inside other apps.
- No Location Tracking: We do NOT request GPS permissions or track real-time physical locations.
- No Access to Notification Messages: While the optional Notification Privacy feature blocks sensitive lock-screen preview cards, our service never reads, parses, stores, or transmits notification message text.
- No Sale of Data: We do NOT sell, broker, rent, or trade your personal data or advertising identifiers to data brokers or third parties.
⚙️ 4. Android Permissions & Technical Usage
Android requires explicit permissions for security apps to perform real-time monitoring and overlay display. Below is an honest, transparent accounting of every permission used by AppLock:
| Permission | Type | Technical Purpose & User Benefit |
|---|---|---|
| PACKAGE_USAGE_STATS | System Access | Granted in Android System Settings. Required to detect when a protected application is launched so AppLock can instantly present the security challenge. No usage logs are transmitted off-device. |
| SYSTEM_ALERT_WINDOW (Display Over Other Apps) |
System Access | Required on Android 10+ (API 29+) to display the security PIN/pattern/biometric overlay on top of protected apps before they can be opened. |
| FOREGROUND_SERVICE & SPECIAL_USE |
Service | Keeps the app protection monitor alive in the background so the Android operating system does not kill the security loop during low memory conditions. |
| POST_NOTIFICATIONS | Optional (API 33+) | Shows the mandatory system notification indicating that app protection is active, and sends immediate security alerts when an intruder attempts unauthorized access. |
| RECEIVE_BOOT_COMPLETED | System Event | Restores lock screen protection automatically whenever your device is rebooted, ensuring your apps remain secure even after a restart. |
| USE_BIOMETRIC | Hardware | Allows biometric unlocking (fingerprint / face recognition) via Android's hardware-isolated BiometricPrompt API. |
| CAMERA | Optional | Strictly optional. Used exclusively to capture a front-camera snapshot of an unauthorized person who repeatedly inputs incorrect credentials. Snapshots are stored strictly in private local storage. |
| BIND_NOTIFICATION_LISTENER_SERVICE | Special Access | Optional Notification Privacy feature. Used solely to dismiss notification preview cards from locked apps until they are legitimately unlocked. Notification text is never read, recorded, or transmitted. |
| VIBRATE | Hardware | Provides pleasant haptic feedback when entering digits on the keypad or unlocking apps. |
| INTERNET & ACCESS_NETWORK_STATE | Network | Required to load advertisements (for free-tier users), process in-app billing tokens, fetch remote config flags, and transmit anonymized crash reports. |
| com.google.android.gms.permission.AD_ID | Advertising | Google Mobile Ads Advertising ID used for frequency capping, fraud prevention, and personalized/non-personalized ad delivery based on your consent. |
| com.android.vending.BILLING | Commerce | Enables secure subscription purchases and lifetime unlocks via the Google Play Billing library. |
🔐 5. Private Vault & Intruder Security Architecture
5.1 Military-Grade Vault Envelope Encryption
Our Private Vault does not simply rename or hide file extensions. Instead, files imported into the Vault are secured using an advanced envelope-and-chunked AEAD (Authenticated Encryption with Associated Data) architecture:
- Hardware-Backed Master Key: A cryptographic master key is generated inside the Android Keystore system. This key never leaves the hardware TEE (Trusted Execution Environment) or StrongBox keymaster.
- Per-File Random Data Key: Each encrypted file is assigned a unique, cryptographically random 256-bit AES-GCM data key. The file content is encrypted with this key and broken into authenticated stream chunks with sequential nonces.
- Key Wrapping: The file's data key is wrapped using the Keystore hardware key. Even if an attacker physically extracts the device's flash storage, ciphertext without the hardware Keystore key remains mathematically unrecoverable.
- Gallery Cleansing: Plaintext media is securely unlinked from Android's public MediaStore once successfully encrypted into the sandbox.
5.2 Intruder Detection & Photo Snapshot Handling
When Intruder Detection is enabled by the user:
- The app monitors sequential failed credential attempts. Once the configured threshold (e.g., 3 failed attempts) is exceeded, the front camera captures a silent snapshot.
- The captured image is written exclusively to the app's sandboxed private storage directory (
context.filesDir), invisible to public gallery apps and other applications. - Intruder logs and images are automatically purged according to your selected retention duration (default: 30 days) or immediately upon manual deletion with secure file overwrite.
5.3 Camouflage & Decoy Protection
AppLock provides an optional Fake Crash decoy dialog that simulates a system crash message when an unauthorized user attempts to open a protected app. Only the legitimate owner knows the secret dismissal gesture to bring up the real unlock interface.
💎 6. Freemium Model, Rewarded Ads & In-App Purchases
AppLock is funded through a fair, ethical hybrid monetization model: a generous free tier, opt-in rewarded ads for extra utility, and a premium subscription / lifetime license for power users.
| Feature Scope | Free Tier | Rewarded Ad Unlocks | Premium Pro (IAP) |
|---|---|---|---|
| App Protection Limit | Up to 5 Apps | +1 Permanent App per Ad | Unlimited Apps |
| Private Vault Storage | Up to 5 Files | +3 Files per Ad | Unlimited Files |
| Smart Focus Schedules | 1 Schedule | +1 Schedule per Ad | Unlimited Schedules |
| Pro Themes & Lock Styles | Standard Themes | 24h Access per Pro Style | All Themes Unlocked |
| Advertisements | Banner, Interstitial, Open | User-Initiated Video | 100% Ad-Free |
6.1 Google Play In-App Purchases & Subscriptions
- Billing Process: All transactions are conducted directly through Google Play Billing. Namoksha Digital never collects, stores, or handles credit card numbers, PayPal details, or billing addresses.
- Automatic Renewal: Recurring subscriptions automatically renew unless cancelled at least 24 hours prior to the end of the active billing cycle.
- Management & Cancellations: You can manage or cancel your active subscriptions at any time via the Google Play Store app > Payments & Subscriptions.
- Refunds: Refund requests are governed strictly by Google Play's standard refund policies.
6.2 Rewarded Advertising Policy
Watching rewarded ads is always 100% optional. When you choose to watch a rewarded video ad, Google AdMob serves a video from third-party advertisers. Upon verified completion, the app grants your bonus quota (bonus locked app slot, vault files, or schedule slot) which is persisted permanently in your local preferences.
🔗 7. Third-Party Services & SDK Partners
AppLock integrates selected, industry-standard Google SDKs to provide analytics, crash monitoring, dynamic configuration, and monetization. Each partner operates under its own strict privacy policy:
| Partner & SDK | Provider | Primary Functionality | Privacy Documentation |
|---|---|---|---|
| Google Play Services | Google LLC | Operating system bridge, biometric prompt, base services | Google Privacy Policy |
| Google Play In-App Billing | Google LLC | In-app purchases, subscription management, digital receipts | Google Play Terms |
| Google AdMob | Google LLC | Banner, Interstitial, Rewarded, and App Open advertising | AdMob Data Policy |
| Google User Messaging Platform (UMP) | Google LLC | Consent management platform complying with GDPR & IAB TCF v2.2 | Google Advertising Privacy |
| Firebase Crashlytics | Google LLC | Anonymized stack traces, crash diagnosis, OS telemetry | Firebase Privacy Policy |
| Google Analytics for Firebase | Google LLC | Aggregated usage trends, feature interaction statistics | Analytics Data Security |
| Firebase Remote Config | Google LLC | Dynamic feature configuration, seasonal themes, ad tuning | Firebase Data Security |
📋 8. Google Play Data Safety Disclosures
For complete compliance with Google Play's Data Safety declaration requirements, below is a structured summary of data types and handling practices:
| Data Category | Data Type | Collected? | Shared? | Purpose | Encrypted in Transit? |
|---|---|---|---|---|---|
| Device or Other IDs | Advertising ID (AAID) | Yes (Non-Premium) | Yes (AdMob) | Advertising, Analytics, Fraud Prevention | Yes (HTTPS/TLS) |
| App Info & Performance | Crash Logs & Diagnostics | Yes | Yes (Firebase) | App functionality, Stability, Crash troubleshooting | Yes (HTTPS/TLS) |
| App Activity | App interactions & Screen views | Yes (Aggregated) | Yes (Firebase) | Anonymous Analytics & Product Improvement | Yes (HTTPS/TLS) |
| Photos, Videos, Audio, Files | User Vault Media | NO (Local Only) | NO | Stored encrypted on device; never transmitted | N/A (Never sent) |
| Personal Info | Name, Email, Phone, Address | NO | NO | Not collected (No account required) | N/A |
| Financial Info | Credit Card / Payment Info | NO | NO | Processed exclusively by Google Play Billing | N/A |
| Location | Precise GPS Location | NO | NO | Not requested or collected | N/A |
| Messages / Notifications | SMS, Chat, Notification text | NO | NO | Not read or collected | N/A |
🗑️ 9. Data Retention & Permanent Deletion
9.1 User Control & In-App Deletion
You have continuous, real-time control over all data stored by AppLock:
- Vault Files: Decrypt and restore files back to your public gallery at any time, or delete them permanently from within the Vault.
- Intruder Photos: Review intruder records and delete individual snapshots or wipe the entire intruder log with one tap.
- Lock Settings & Protected Apps: Toggle off app protection or uncheck specific apps whenever you desire.
9.2 Uninstalling the App
context.filesDir), uninstalling AppLock or clearing app data in Android System Settings permanently and irrevocably deletes all your encrypted vault files and intruder logs. Please restore any important media from the Vault to your public storage prior to uninstalling the app.
9.3 Excluded from Cloud Backups
AppLock explicitly configures android:allowBackup="false" and enforces custom extraction rules. This ensures that your encrypted vault, PIN hashes, and intruder photos are never inadvertently leaked to unencrypted third-party cloud backup servers.
🌍 10. International Privacy Rights
We respect international data protection legislation and provide robust user controls regardless of where you reside.
10.1 European Economic Area (GDPR) & United Kingdom (UK GDPR)
Under the General Data Protection Regulation, our legal bases for processing data are: (i) User Consent for personalized ads via the Google UMP consent banner, (ii) Legitimate Interests for crash analytics and security maintenance, and (iii) Contractual Performance for in-app billing transactions.
10.2 California Privacy Rights (CCPA / CPRA)
California residents have specific rights under the California Consumer Privacy Act (CCPA) and California Privacy Rights Act (CPRA):
- Notice at Collection: We inform you of the categories of personal information collected at or before collection.
- No "Sale" of Personal Information: We do NOT sell your personal data for monetary consideration.
- Opt-Out of "Sharing" for Cross-Context Behavioral Advertising: You can opt out of targeted advertising by resetting your Android Advertising ID (Settings > Google > Ads > Reset/Delete Advertising ID) or opting out through our in-app consent preferences.
10.3 India's Digital Personal Data Protection Act, 2023 (DPDP)
Under India's Digital Personal Data Protection Act, 2023, you have the right to access an overview of processed personal data, the right to correction and erasure, the right of grievance redressal, and the right to nominate an individual to exercise rights in the event of incapacity.
🧸 11. Children's Privacy (COPPA Compliance)
AppLock is a utility designed for general audiences and is not directed to children under the age of 13 (or under 16 in the EEA/UK). We do not knowingly collect, solicit, or maintain personally identifiable information from children under these ages. If we become aware that a child has provided us with personal information, we will take immediate steps to delete such data from our records.
📜 12. Terms of Use & Service Agreement
12.1 Acceptance of Terms
By downloading, installing, accessing, or using AppLock, you agree to be bound by these Terms of Use. If you do not agree to these terms, please do not install or use the application.
12.2 License Grant
Namoksha Digital grants you a personal, worldwide, non-exclusive, non-transferable, revocable license to use AppLock on Android devices you own or control for personal, non-commercial security purposes in accordance with this agreement.
12.3 Prohibited Activities
You agree that you will NOT:
- Decompile, disassemble, reverse engineer, or attempt to derive the source code of AppLock.
- Use AppLock for unlawful surveillance, stalking, espionage, or unauthorized monitoring of third parties without their express, informed consent.
- Bypass, tamper with, or circumvent any licensing, feature gating, or security enforcement mechanisms built into the application.
- Distribute modified, cracked, or unauthorized APK packages bearing our name or trademark.
12.4 User Responsibilities & Credentials
You are solely responsible for maintaining the confidentiality of your PIN, pattern, or password. Because AppLock uses a zero-knowledge local security architecture, we cannot recover or reset your PIN if you forget it and have not configured biometric unlock or recovery safeguards.
⚠️ 13. Disclaimers & Limitations of Liability
13.1 "As-Is" Warranty Disclaimer
AppLock is provided on an "AS IS" and "AS AVAILABLE" basis without warranties of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
13.2 Operating System Limitations & Rooting
While AppLock utilizes resilient background monitoring mechanisms, Android OS battery optimization frameworks, manufacturer-specific task killers (e.g., Xiaomi MIUI/HyperOS, Samsung OneUI, Huawei EMUI aggressive battery managers), or rooting the device may interfere with or terminate background services. We strongly recommend adding AppLock to your device's battery optimization whitelist for uninterrupted protection.
13.3 Limitation of Liability
To the maximum extent permitted by applicable law, in no event shall Namoksha Digital, its developers, or affiliates be liable for any indirect, incidental, special, consequential, or punitive damages, including loss of data, unauthorized access to your device by third parties, hardware failure, or device corruption arising out of or related to your use of AppLock.
13.4 Governing Law & Jurisdiction
These Terms shall be governed by and construed in accordance with the laws of India, without regard to conflict of law principles. Any dispute arising under these terms shall be subject to the exclusive jurisdiction of the competent courts located in Delhi, India.
🔄 14. Updates to This Privacy Policy
We may update our Privacy Policy and Terms of Use from time to time to reflect new app features, updated security protocols, or modifications in statutory legal requirements. When updates are published, the "Last Updated" date at the top of this document will be amended.
We encourage you to review this document periodically. Continued use of AppLock following the posting of changes constitutes your binding acceptance of the updated terms.
📧 15. Contact & Grievance Redressal
If you have any questions, suggestions, feedback, or data protection inquiries regarding this Privacy Policy or our privacy practices, please contact our dedicated Privacy & Grievance Officer:
- Developer & Organization: Namoksha Digital
- Lead Privacy Officer: Grievance Officer, Namoksha Digital Team
- Email Support: namokshadigital@gmail.com
- Developer Page: Namoksha Digital on Google Play
- Country of Operation: India
- Response Window: We endeavor to address and resolve all legitimate inquiries within thirty (30) business days.