Privacy Policy — SecureMerge Pro

Effective date: October 3, 2026 · Last updated: October 3, 2026 Application: SecureMerge Pro (Android package com.securemerge.pro) Developer: Velrix Lab Contact: velrixlab0101@gmail.com

1. Summary

SecureMerge Pro is an offline document and image toolkit. It merges, splits, compresses, protects, converts, signs and scans documents entirely on your device.

We do not collect, transmit, sell, rent or trade your personal information. The app contains no analytics, no advertising, no crash reporting, no user accounts, and no subscription or payment processing. It requests no internet access, so it is technically incapable of sending your files or data anywhere.

2. Who is responsible for your data

Velrix Lab ("we", "us") is the controller for the limited personal data described in this policy. We do not operate servers and we do not run a backend — all processing happens on your device.

3. Information we collect

3.1 Data you choose to provide

We collect only the files and text you deliberately hand to the app through Android's system file picker:

• Documents and images you select for merging, splitting, compressing, encrypting, converting, cropping, resizing, watermarking or signing.
• Text you create or recognise via OCR.
• Signature strokes you draw on the signature pad.
• Credentials you create — an app-lock PIN, a pattern-lock gesture, and a PDF encryption password.

3.2 Data generated on your device

• Temporary working copies of the files you are editing, held in the app's private cache directory while a task runs.
• Thumbnails and preview renderings of your documents.
• A record of your app-lock settings, including failed-attempt counts and any temporary lockout timer.

3.3 What we do not collect

• No name, email address, phone number, or account credentials.
• No device identifiers (no advertising ID, no IMEI, no Android ID, no MAC address).
• No location, no contacts, no call logs, no browsing history, no installed-app list.
• No files other than those you explicitly select.
• No diagnostic or usage telemetry of any kind.

3.4 Permissions, and why we need them

Because these are the only sensitive permissions the app declares, and camera is not mandatory, the app can be used with no permissions granted at all.

4. Why the app cannot upload your data

SecureMerge Pro does not declare the INTERNET or ACCESS_NETWORK_STATE permissions in its shipped Android manifest. Without INTERNET, the Android operating system blocks all outbound network access for this app, including background work.

This is enforced at build time: our release manifest explicitly removes these permissions, overriding the ones that Google's bundled components would otherwise request. As a result, no document, image, recognised text, signature, or credential can leave your device — not by our choice of configuration, but because the operating system will not permit it.

Third-party libraries bundled in the app (Google's ML Kit text-recognition and Firebase component-registration libraries) include framework code that is normally used for diagnostics. In SecureMerge Pro that code is inactive and incapable of transmitting anything, because the app holds no network permission. We have not enabled, configured or used any of it to collect information.

5. How your information is stored and protected

All storage is local to the app's private directory, which is isolated from other apps and not readable by them.

Encrypted vault. Files you add to the vault are encrypted on your device using AES-256 in GCM mode with HKDF-derived keys (4KB), via the AndroidX Security library, before being written to storage. They are stored as .enc files that cannot be read outside the app.

Encrypted preferences. Your app-lock PIN or pattern, and the app-lock settings, are stored in Android's EncryptedSharedPreferences, with keys encrypted using AES256-SIV and values using AES256-GCM. The encryption key is held by the Android keystore, which on modern devices is backed by hardware.

Other local storage. Drawn signatures and temporary working files are stored in app-private directories. Working files are placed in the operating system's cache directory, which the system may clear on its own.

Deliberate design decisions and honest limitations. We want to be transparent about how we protect data rather than overstate it:

• No screenshot or screen-recording blocking. The app does not set a system flag to prevent screenshots. Content visible on screen, including vault documents, can be captured by your operating system's normal screenshot function or by the recent-apps thumbnail.
• Decrypted files briefly exist unencrypted. When you open a vault document, it is decrypted to a temporary file in the app's cache directory so it can be displayed or shared. That copy is deleted when the action finishes, but the operating system could in principle retain a copy in its own storage. Deleting vault entries removes their encrypted files; deleting the app removes all of its local data.
• Your PIN is stored protected but in a recoverable form. The app-lock PIN is stored in encrypted preferences. The pattern-lock gesture is additionally salted and hashed with SHA-256. An unlocked, rooted or otherwise compromised device is outside our control.
• Signature files and app settings are not themselves encrypted. Signatures and preferences are stored in app-private storage and are excluded from backup, but they are not separately encrypted at rest like vault contents.

Excluded from backup. Your vault, your saved signatures and your app-lock preferences are explicitly excluded from Android's cloud backup and from device-to-device transfer. We also instruct the operating system not to back up this data, so your documents are not copied to your Google account or to a new phone.

6. How we use information

Only to perform the task you asked for, on your device, at the moment you ask for it. Specifically, to merge, split, compress, protect, unprotect, convert, resize, crop, rotate, watermark, sign, scan and export your files, and to authenticate you into the app.

We do not use your files for advertising, analytics, model training, profiling, or any form of automated decision-making.

7. Sharing and disclosure

We do not share your information. There are no third parties to share it with, and no network capability with which to do so.

Two limited exceptions may apply, and in both cases you are the one who causes the transfer:

1. Exports you initiate. When you tap "Save" or "Export," Android's system file picker opens. If you choose a cloud storage provider, an email client, or a messaging app as the destination, that third party receives the file and is governed by its own privacy policy and terms. The transfer happens inside that app after you confirm it. We never see, receive or log where the file went.
2. Deleting originals at your request. If you enable "delete original after securing" when adding files to the vault, the app deletes the source file from its original location — through the storage provider you selected it from. This requires that provider to grant deletion access, and the app reports back if the deletion could not be completed.

We also do not sell, rent or trade personal information, and we have never done so.

8. Data retention

We retain nothing, because we hold nothing.

• Exported files exist only where you chose to save them.
• Temporary processing files are deleted when a task completes.
• Vault files remain encrypted on your device until you delete them or uninstall the app.
• Uninstalling SecureMerge Pro removes all of the app's local data, including the vault, signatures and settings.

9. Your rights and controls

Because we do not collect or hold your personal data, most data-subject rights are satisfied by design — there is nothing for us to disclose, correct, export or delete. Under the GDPR, UK GDPR, the CCPA/CPRA and similar laws, we do not have personal information to sell, share or disclose.

You remain in full control of your data at all times:

• Delete a vault entry — removes its encrypted file from your device.
• Clear all app data — Android Settings → Apps → SecureMerge Pro → Storage → Clear storage, or uninstall the app.
• Withdraw files — close the app without exporting; nothing is retained.
• Revoke camera access — Android Settings → Apps → SecureMerge Pro → Permissions.
• Turn off app lock or biometrics — within the app's Settings and Vault screens.
• Disable device backup for this app — the app already excludes its sensitive directories; you can also disable backup entirely in Android settings.

10. Children

SecureMerge Pro is intended for a general audience aged 13 and older. It is not directed at children under 13, and we do not knowingly collect information from children. Because the app collects no information from any user, it collects none from children.

11. Security

We use industry-standard encryption for data at rest: AES-256-GCM with HKDF key derivation for vault files, and AES256-SIV/AES256-GCM for stored preferences, with keys held in the Android keystore. Data in transit is not applicable because the app performs no network transmission. Access to app-private storage is additionally restricted by the Android operating system's per-app sandbox.

No system is perfectly secure. A rooted, jailbroken or otherwise compromised device, a malicious third-party app with elevated permissions, or physical access to an unlocked device can defeat these protections. We do not claim otherwise.

12. Third-party components

SecureMerge Pro bundles the following open-source and Google libraries. None of them is used to collect or transmit your information:

Their own licences govern those components; their inclusion does not create any data-sharing relationship with you.

13. International transfers

Not applicable. The app does not transfer data across borders, because it does not transfer data at all.

14. Your content and intellectual property

Documents, images, signatures and text you process with SecureMerge Pro remain entirely yours. We claim no rights over them and we have no access to them.

15. Changes to this policy

We may update this policy if the app's functionality or legal requirements change. The "Last updated" date at the top always reflects the current version, and material changes will be described in the release notes or communicated to you in the app. Continued use of the app after an update means the revised policy applies to it.

16. Contact us

If you have questions, requests, or concerns about this policy or the app:

Velrix Lab Email: velrixlab0101@gmail.com Website: No website is currently provided.

Because we hold no personal data, we may not be able to respond to requests for records about you — there will be no records to provide, because we hold none.

Play Console Data Safety — answers matching this policy

Two notes for the Data Safety form's free-text/attestation section:

• Do not claim "no third-party SDKs." Google ML Kit and Firebase component code are present in the binary; they are simply incapable of transmission. If you have checked a box asserting no SDK collects data, be prepared to explain that the absence of the INTERNET permission renders them inert.
• Play reviewers read manifests. If any uploaded build has an INTERNET permission present, the "no data collected" declaration becomes inaccurate.