APPDEVS · LOCKVEXA

Privacy Policy

Effective 12 November 2026

This policy explains how AppDevs handles information in Lockvexa. Contact appdevs.net@gmail.com about privacy or account data. Features and availability can differ by platform, build and region.

Local vault and recovery

Selected files, thumbnails and vault metadata are encrypted on your device. Private camera and recorder features operate when you choose them. The vault PIN/password and recovery secret protect local keys; they are not sent to AppDevs. Biometric matching is handled by your device. AppDevs cannot recover your vault without your recovery key.

Readable temporary copies may be needed for playback, sharing or export. Lockvexa attempts to remove its private temporary files on lock and startup. Secure deletion of physical flash storage and copies outside the app cannot be guaranteed. Android screenshot protection and the iOS app-switcher cover have platform limitations.

Imports, exports and other providers

Move requests original deletion only after a verified encrypted copy is saved. Keep original leaves the source visible. Your operating system or provider can deny removal. Deletion may sync through iCloud or another provider, and Recently Deleted may retain a copy. Exported or shared files are readable outside Lockvexa and may be accessible to other apps or cloud services.

Optional Android app protection and Home launcher

App protection uses Usage Access to detect launches of apps you explicitly select and Display over other apps to show a blocking privacy overlay. Authentication takes place inside Lockvexa. An ongoing notification lets you stop protection. Lockvexa does not read protected apps' screens, messages, passwords or content. The selected package identifiers are stored locally using authenticated encryption and an Android Keystore key; they are not sent to Firebase, RevenueCat, AdMob or AppDevs.

Lockvexa Home is an optional default launcher chosen through Android settings. It can hide up to 100 selected apps from its own app drawer and search in the current Android profile. Phone, Settings, Home apps and Lockvexa remain accessible. Viewing or changing the hidden list and opening a hidden app require fresh vault authentication. Installed-app choices and searches stay on the device. Apps can still appear in Android Settings, Recents, notifications, links or another launcher. Android can stop app protection; it is not a replacement for system security. Changing the launcher does not uninstall an app or delete its data.

Optional cloud account and encrypted backup

If you opt into cloud services, Firebase processes account identifiers, email address, optional profile name, authentication and security information. If you choose Google sign-in on Android, Google and Firebase process the account identifier, email and basic profile information needed to authenticate you. Lockvexa does not request Google Drive, Google Photos or Contacts access for sign-in, and your Google password is entered only in Google’s own sign-in interface. This account infrastructure may be shared with other AppDevs apps. Linking providers or changing a shared profile can affect that identity.

Encrypted backup transfers ciphertext and protected inventories to Google Firebase/Cloud Storage. The service also receives information needed to operate backups: opaque account/device/backup identifiers, platform, byte counts, object checksums, timestamps, consent, subscription quota and job status. Recovery public keys and encrypted key wrappers are included; usable private vault keys are not. Network services may process IP addresses and technical request information. Cloud sign-in alone cannot decrypt a backup.

Subscriptions

Google Play or Apple handles payment details. RevenueCat processes store receipts, transaction/subscription identifiers, product, renewal, refund and entitlement status. It may associate an anonymous customer ID or your cloud account ID with purchases to restore access and verify quota. AppDevs does not receive your full payment-card details. Test Store purchases in development builds are simulated.

Ads and privacy choices

Free builds may show Google AdMob banners on Settings and Help and a labeled native ad among static Security Tips after required consent checks. An optional rewarded ad in Appearance can unlock the Midnight cosmetic theme for 24 hours; skipping never restricts normal use or access to vault files. Theme selection and reward expiry are stored locally. Ads do not appear on Home, file galleries, vault authentication, file transfers, recovery or the launcher app drawer. Lockvexa does not send vault files, filenames, folder names, search terms, PINs or recovery secrets to the ad SDK. AdMob and its partners may process device/advertising identifiers, IP/network information, approximate location inferred from IP, ad interactions, SDK performance diagnostics and consent choices. Non-personalized ads can still involve technical identifiers or local storage. Privacy choices are available in Ads & privacy choices where required. Premium removes app ad requests while its entitlement is active.

Notifications, diagnostics and support

Notification categories default off. If enabled, Firebase processes an installation identifier, platform and notification preferences. Reminders may include timezone, weekdays and time. Push messages use generic templates without private filenames or media. Delivery is best effort. The local activity log uses coarse encrypted events and is normally retained for 90 days.

If you contact support, we receive what you voluntarily send, such as your email and optionally app/OS diagnostics. Do not send private media, PINs, passwords or recovery keys. We do not automatically attach these to support requests.

Retention and deletion

• Local vault files remain until you delete them, reset the vault or remove the app. Vault Trash normally retains recoverable items for 30 days.
• Pending cloud backups expire after 24 hours. Verified versions normally expire after 90 days, except the newest verified version, which remains until you explicitly delete it or delete Lockvexa cloud data. Cleanup can be delayed by retries or outages.
• Deleting local files does not erase historical cloud versions, exported copies, provider copies or store transaction records. Each must be managed separately.
• Lockvexa cloud deletion removes its backups, device registrations and preferences through retryable cleanup. Minimal revocation/security records may remain to reject older sessions; billing-event deduplication records expire after 90 days. Provider security logs and legally required store records follow their own retention.
• A shared AppDevs sign-in identity used by other apps may remain. Contact support for a request concerning the entire shared identity.

Use the app account deletion control or request deletion outside the app. Cancelling a subscription and deleting cloud data are separate actions. Existing backup restore and access to local files do not require renewing Premium.

Providers, transfers and your choices

We use Google/Firebase for hosting, authentication, storage, integrity checks and optional messaging; RevenueCat for subscription verification; Google AdMob for ads; and Apple/Google Play for platform services and payments. These providers may process information in countries outside your own. We do not sell your vault content or use it for advertising. You can manage permissions in device settings, cloud opt-in and notification preferences in Lockvexa, ad choices where available, and subscriptions through your store.

Provider information: Firebase privacy, Google privacy, Google advertising, RevenueCat privacy, Apple privacy.

For AppDevs' broader services, see the AppDevs company privacy policy. This page describes Lockvexa-specific processing.

Children and changes

Lockvexa is not directed to children under 13. If you believe a child has provided cloud account information, contact us. We will update this page when data practices change and identify the effective date. Where required, material changes will be explained in the app or a renewed choice will be requested.