Privacy Policy
1. Overview and Scope
This Privacy Policy explains how FaceLock Vault ("the App", "we", "us", or "our"), developed by Orbit Tech Lab, handles user data when you download, install, and use the mobile application available on the Google Play Store.
The application is designed specifically as a secure container for private media (photos and videos), confidential documents, and encrypted text notes protected by front-camera biometric facial recognition and hardware-backed PIN encryption.
2. Data We Do NOT Collect
Unlike standard cloud-connected applications, FaceLock Vault collects no personal data off-device. Specifically:
- No Identifiers: We do not collect names, email addresses, phone numbers, IP addresses, advertising IDs (GAID), or hardware serial numbers.
- No Location Data: We do not access, track, or request coarse or fine geographic location.
- No Network Telemetry: We do not bundle analytics SDKs (e.g., Google Analytics, Firebase, Mixpanel), crash reporting loggers (e.g., Crashlytics, Sentry), or advertising networks.
- No Cloud Accounts: The application operates without login portals or remote user databases.
3. Data Processed Strictly On-Device
To deliver the core security features of FaceLock Vault, the following data types are created, processed, and stored strictly in the private storage sandbox of your physical device:
| Data Category | Storage Location & Cryptography | Purpose & Handling |
|---|---|---|
| Biometric Face Embeddings | Processed in volatile RAM; stored encrypted in Android Keystore / Hardware TEE | Used strictly on-device to match your face during unlock. Raw camera photos are never stored; only an irreversible numerical feature vector is retained. |
| Vault Files (Photos, Videos, Documents) | App-private sandbox, encrypted with AES-256-GCM (unique 96-bit IV) | Imported files are encrypted immediately upon entry. Stored unindexed and inaccessible to other apps or gallery indexers. |
| Confidential Notes | App-private sandbox, encrypted with AES-256-GCM | Personal text notes created inside the app vault, stored exclusively on your device. |
| Master PIN Hash | Salted and stretched using PBKDF2-HMAC-SHA256 (100,000 iterations) | Provides fallback authentication when facial recognition is unavailable or unsuited. |
| Intruder Snapshots (Optional) | App-private sandbox, encrypted with AES-256-GCM | If enabled in settings, captures a silent front-camera selfie after 3 consecutive failed unlock attempts. Stored locally in encrypted logs. |
4. Android System Permissions
FaceLock Vault requests only the minimum runtime permissions required to deliver its security functionality:
-
Camera (
android.permission.CAMERA): Required for on-device face recognition during enrollment and unlock, and for optional intruder snapshots. The app provides a transparent in-app disclosure before requesting this permission. Camera frames are processed in-memory and never sent over the network. -
Haptic Feedback (
android.permission.VIBRATE): Normal install-time permission used solely to provide tactile confirmation when interacting with the PIN keypad. -
Photo & Media Access: Utilizes modern Android system Photo Pickers and Storage Access Framework. FaceLock Vault does not request broad storage permissions (such as
MANAGE_EXTERNAL_STORAGEorREAD_EXTERNAL_STORAGE) and never scans external folders. -
Network Permissions Blocked: In production builds,
android.permission.INTERNETandandroid.permission.ACCESS_NETWORK_STATEare stripped from the manifest. The app is physically incapable of making outgoing HTTP or socket connections.
5. Data Sharing and Third-Party Disclosure
We do not share, sell, lease, or disclose any user data to any third party. Because the app has no internet capability, data transmission to advertising partners, analytics platforms, data brokers, or cloud providers is technically impossible.
6. Cloud Backup Exclusion
To safeguard against unauthorized cloud extraction, FaceLock Vault explicitly disables Android system cloud backups (android:allowBackup="false" and android:fullBackupContent="false"). Your encrypted files and biometric keys will never be mirrored to Google Drive or manufacturer backup services.
7. Data Deletion and Retention Policy
In full compliance with Google Play Store policies and global privacy regulations (including GDPR and CCPA), users have absolute autonomy to delete their stored data at any time.
In-App Instant Data Purge
You can permanently purge all stored data directly from within the app:
- Open FaceLock Vault and unlock using your Face or Master PIN.
- Navigate to the Settings tab.
- Scroll to the Data & Reset section and select Delete All Data.
- Confirm the action by typing DELETE into the security prompt and tap Yes, erase everything.
This immediately and permanently:
- Erases all encrypted photos, videos, documents, and notes from disk.
- Wipes all biometric facial templates and encryption keys from the Android Keystore.
- Purges all intruder photos and access activity audit logs.
- Resets the application back to its fresh initial installation state.
Device Uninstall Deletion
Because all app data is maintained exclusively in app-private storage (Android internal sandbox) and cloud backup is strictly disabled, uninstalling the FaceLock Vault application from your Android device immediately and irreversibly destroys all local database files, encrypted payloads, and biometric keys.
Data Retention Duration
Data is retained only as long as you keep the items inside the vault and keep the application installed on your device. We do not retain any server-side copies or retention logs.
Deletion Questions & Support
If you have questions regarding data retention, keystore sanitization, or privacy compliance, you can contact our developer support team at:
Email: support@orbittechlab.com
8. Child Safety & Target Audience
FaceLock Vault is designed for individuals aged 13 and older (target audience: 18+). The app does not knowingly collect, request, or solicit personal data from children under the age of 13.
9. Changes to this Privacy Policy
If we ever modify our security architecture or release features requiring policy updates, we will update the "Effective Date" at the top of this page. Any changes will be published publicly at this URL (https://vault.orbittechlab.com/privacy.html) and linked within the application's Settings menu.
10. Contact Information
For privacy inquiries, technical audits, or support requests regarding FaceLock Vault, please contact:
Application: FaceLock Vault (com.orbittechlab.facelockvault)
Support Email: support@orbittechlab.com
Official Website: https://vault.orbittechlab.com