01 Introduction

Documents Locker is a personal vault application that helps you organize sensitive information such as website credentials, email accounts, social media logins, bank details, card information, government document images, secure notes, and scanned documents.

Because the App handles highly sensitive information, privacy is not a secondary feature — it is the foundation of the product. This document is written for:

• Everyday users who want to understand what happens to their data
• Google Play Console reviewers who require a clear, public Privacy Policy URL
• Regulators and auditors who expect transparent data practices

02 Who we are

When this policy says “we” or “developer,” it refers to the publisher listed above — the person or entity responsible for listing the App on Google Play.

03 Summary for users (quick read)

If you only read one section, read this:

• Vault content is local. Credentials, notes, bank details, card details, document images, and similar entries you create are stored in the App’s on-device database and local storage.
• We do not sell your data. We do not sell, rent, or trade your personal information to data brokers or advertisers.
• No third-party ads. The App does not integrate advertising SDKs for showing ads.
• Biometric unlock is optional and device-bound. Biometric templates remain managed by Android / your device vendor — not uploaded to us.
• Backup is disabled at the app level. Android Auto Backup for this App is configured off (allowBackup="false") to reduce accidental cloud copies of vault data through the OS backup channel.
• You can delete everything. Uninstalling the App removes app-private storage on your device (subject to normal Android behavior). You can also delete individual items inside the App.
• Optional network features. If enabled, the App may use the internet for convenience features such as loading website favicons; that does not upload your passwords to us.

04 Information we process

“Process” means any operation on data — including storing it on your device when you create an entry. Below is a complete breakdown of categories relevant to the App.

4.1 Information you provide (vault content)

You may voluntarily enter or import the following types of information. This data is stored on your device for the purpose of providing the vault features you request:

4.2 Information created by the App on your device

• App preferences: onboarding completion flag, security category lock toggles, UI settings, and similar configuration.
• Local database records: structured storage of the items listed above, including timestamps or internal IDs used only for app operation.
• Cached images / icons: e.g. website favicons or document images saved for offline display.

4.3 Device & permission-related data (not harvested for advertising)

Depending on the features you use and permissions you grant, the App may access:

• Photos / media / files you select — only when you choose an image or document to attach (e.g. government document photo, card image).
• Camera capture — only when you intentionally scan or photograph a document (where the feature is available).
• Biometric authentication signals — success/failure result from the system biometric prompt; not the biometric template itself.
• Clipboard — only if you use paste helpers you trigger yourself (e.g. pasting into a secure note).

We do not use these accesses to build advertising profiles, track you across other apps, or create a dossier about you for marketing.

4.4 Information we do not intentionally collect

• We do not require you to create an online account with us to store vault items.
• We do not ask for your contacts list for vault core features.
• We do not request precise location for vault core features.
• We do not run third-party ad networks inside the App.
• We do not sell personal information.

4.5 Automatically collected diagnostics (if enabled in a given build)

Some app builds may include industry-standard crash reporting or performance tooling (for example, libraries used only for build/diagnostics). If a crash reporting service is enabled in a published build, it may receive technical diagnostics such as:

• App version, Android version, device model
• Stack traces and crash timestamps
• Non-content technical state needed to fix bugs

Crash tools are not intended to collect the contents of your vault entries (passwords, card numbers, note text). We configure and use diagnostics to improve stability — not to read your secrets.

05 How we use information

Information processed by the App is used solely to provide and improve the product experience you request:

• Provide vault features — create, view, edit, search, lock, and delete stored items.
• Security controls — optional biometric gate, category lock settings, private storage configuration.
• Document workflows — capture, preview, label, and organize document images.
• Usability — show favicons or labels you associate with websites/apps; remember onboarding and setup state.
• Reliability — diagnose crashes/bugs if diagnostic tooling is present in your build.
• Legal compliance — respond to lawful requests where we actually control relevant data (note: vault contents typically reside only on your device and may not be available to us).

We do not use vault contents for:

• Targeted advertising
• Selling datasets
• Training public AI models on your private entries
• Building credit, employment, or insurance eligibility scores

06 Storage, security & architecture

6.1 Local-first architecture

Documents Locker uses on-device storage technologies common to Android apps, including:

• Room / SQLite database inside the App’s private storage for structured vault items
• App-private internal files for images and document binaries you save
• SharedPreferences for lightweight flags and preferences (e.g. onboarding complete, display name)

Other apps on your phone cannot read this private storage under normal Android security rules.

6.2 Android backup

The App is configured with android:allowBackup="false". This reduces the risk that vault data is automatically included in Android cloud backups associated with your Google account through the standard backup API.

6.3 Security measures

• App-private storage sandboxing provided by Android
• Optional biometric authentication using AndroidX Biometric APIs
• Category-level lock options inside the Security screen
• No intentional transmission of vault entry contents to developer-operated backend for “cloud sync” in the current product model
• Release builds may enable code shrinking / obfuscation (ProGuard/R8) as a standard hardening practice

6.4 What security cannot guarantee

No mobile app can promise perfect security. Risks outside our absolute control include: stolen unlocked phones, malware with elevated privileges, shoulder surfing, compromised accessibility services, or user actions like screenshotting secrets. You remain responsible for physical device security and for deciding what secrets to store.

If your app data is lost, deleted, corrupted, or becomes inaccessible due to device failure, operating system issues, app updates, uninstallation, factory reset, rooting, malware, backup/restore processes, or other user- or device-related causes, we are not responsible for the resulting loss of information. You should keep your own offline backups of important documents and information.

07 Android permissions explained

Android requires apps to declare permissions. Below is a transparent explanation of permissions relevant to Documents Locker and why they exist. Exact permission prompts can vary by Android version.

We do not request permissions for SMS reading, call logs, continuous background location, or contacts for the core vault product described in this policy.

08 Biometrics in depth

When you enable biometric unlock, Documents Locker uses Android’s official biometric prompt (fingerprint, face, or other modalities supported by your device and OS settings).

What we receive

• A success or failure result for the authentication attempt
• Possibly the fact that biometrics are available / enrolled on the device

What we never receive

• Your fingerprint image or face map
• A copy of biometric templates stored in the device’s secure hardware / TEE

Biometric templates are managed by the operating system and device manufacturer security modules. Disabling biometrics in Android settings or removing enrolled fingerprints stops biometric unlock for the App.

09 Third parties, network requests & processors

9.1 Developer-operated servers

In the current product model, vault entries are not uploaded to a developer cloud for multi-device sync. That means we typically cannot see the passwords or documents you stored locally.

9.2 Optional / utility network calls

If network access is available, the App may contact third-party endpoints solely for user-facing convenience, for example:

• Website favicon retrieval (e.g. public favicon services) when you enter a domain — the request may include the domain/hostname you typed, not your password.
• Image loading libraries used to display remote icons you requested.

Those third parties process only the technical request needed to return an icon or resource. Do not put secrets in URLs or hostnames.

9.3 Google Play & Android platform

When you download the App from Google Play, Google processes installation, updates, payments (if any), abuse detection, and basic distribution analytics under Google’s Privacy Policy. That processing is controlled by Google, not by the vault contents of this App.

9.4 No advertising SDKs

We do not integrate third-party ad networks (such as banner/interstitial ad SDKs) into Documents Locker for the purpose of showing ads or building ad profiles.

9.5 Future features

If we later introduce optional cloud backup, account login, or paid subscriptions, we will:

• Update this Privacy Policy before or at launch of the feature
• Update the Google Play Data safety form
• Explain what leaves your device and provide meaningful controls where required

10 Children’s privacy

Documents Locker is not directed to children under 13 (or under 16 where applicable law sets a higher digital consent age). We do not knowingly collect personal information from children.

If you are a parent or guardian and believe a child has stored personal data in the App on a shared device, you can delete the items in-app or uninstall the App. If you believe a child provided information directly to us through a support channel, contact us and we will take reasonable steps to delete it.

For Google Play Families / Designed for Families programs: this App is intended as a general productivity/security utility for adults managing personal credentials, not as a children’s app.

11 Data retention & deletion

11.1 On-device retention

Vault items remain on your device until you delete them in the App or remove the App. We do not set a server-side retention period for vault contents because those contents are not hosted on our servers in the current model.

11.2 How to delete data

• Delete individual items using in-app delete actions for that category (email, notes, docs, etc.).
• Clear app data via Android Settings → Apps → Documents Locker → Storage → Clear data (removes local database and preferences).
• Uninstall the App, which removes app-private storage under normal Android behavior.

11.3 Support communications

If you email us for support, we may retain your email and message as long as needed to resolve your request and for legitimate record-keeping (typically no longer than necessary).

12 Your rights & choices

Depending on where you live (for example GDPR in the EEA/UK, CCPA/CPRA in California, or other laws), you may have rights such as access, correction, deletion, portability, restriction, or objection.

Because vault data lives on your device, the most effective way to exercise many rights is directly in the App:

• Access / portability: view or export items using in-app features where available; otherwise, you already possess the data on-device.
• Correction: edit entries inside the App.
• Deletion: delete entries, clear app data, or uninstall.
• Withdraw permission: revoke Android permissions in system settings at any time.
• Opt out of biometrics: disable biometric unlock / remove biometrics in device settings.

For requests about information you sent us by email (support tickets), contact hemantmarkhande99@gmail.com. We will respond within a reasonable period required by applicable law.

13 International users

The App may be used worldwide via Google Play. Local storage remains on the device wherever you are. If you contact us by email, your message may be processed in the country where the developer operates or where email infrastructure is hosted. We take reasonable steps appropriate to the nature of support data.

14 Google Play Data safety mapping

Use this section when filling the Play Console Data safety form. Align the form with your actual published APK/AAB. The table below reflects the local-first vault design of Documents Locker.

15 Changes to this Privacy Policy

We may update this Privacy Policy to reflect product changes, legal requirements, or clearer wording. When we make material changes, we will update the “Last updated” date at the top of this page. Where required by law or Play policy, we may provide additional notice in the App or store listing.

Continued use of the App after an updated policy becomes effective constitutes acceptance of the revised policy, to the extent permitted by applicable law.

16 Contact us

Questions, privacy requests, or security concerns about Documents Locker are welcome. We aim to respond promptly and transparently.

Related document: Terms of Service.