VeilX Privacy Policy

Effective date: 2026-08-25 · Last updated: 2026-08-25 · Applies to VeilX for Android, version 1.0.5 and later (com.veilx.app)

中文版本 ↓

VeilX is a private messaging application built on the open Matrix protocol. It is designed for teams that need to protect confidential business communications. VeilX operates no servers of its own. Your messages travel to a Matrix server (a "homeserver") that you or your organization chooses and controls — not to us.

This policy explains, precisely and completely, what data the app handles, what stays on your device, and which third parties your device contacts while you use VeilX.

1. Who we are

LOCKMERE AI LABS LLC, a limited liability company organized under the laws of the State of Wyoming, United States, with a registered address at 30 N Gould St, Ste R, Sheridan, WY 82801 ("we", "us", the "Developer"), publishes VeilX.

Privacy contact: service@lockmere.io

Your use of VeilX is also governed by our Terms of Service, which set out the licence, the disclaimers that apply to the app's protective features, and how disputes are resolved.

Our role, and the role of your server operator

This is the most important thing to understand about VeilX:

• The Developer is not a party to your communications. We do not run a messaging service, we do not host your account, and we have no technical means to read, retrieve, or delete your messages.
• The operator of the Matrix homeserver you sign in to — you, your employer, or a third party you selected — is the entity that actually stores your account and message data. Under the GDPR that operator is the controller for that data; under U.S. state privacy laws it is the business. Their own privacy notice, not this one, governs what happens to data on that server.
• This policy covers the VeilX application software: what it stores on your device, and what network requests it makes.

Where VeilX comes from

VeilX began as an internal project at Lockmere AI Labs. We built it for ourselves — a small team whose ordinary work involves client material and unreleased projects that we are professionally obliged to keep private, and that we would rather not route through a platform whose business depends on retaining it.

Because it was written for our own use, it was built without a backend from the very first commit. There was no one to collect data for, and no reason to. That is not a policy we adopted later; it is simply how the software is shaped.

In time, people we work with saw it, asked whether they could use it too, and kept asking. Publishing on Google Play is our answer to them. Nothing about the design was loosened to reach a wider audience: there are still no servers of ours behind the App, and it still collects nothing — for exactly the reason it never did.

2. Data the Developer collects: none

The VeilX app sends no data whatsoever to the Developer. Specifically, VeilX contains:

• No advertising SDKs and no advertising identifier access.
• No analytics, telemetry, or usage measurement of any kind.
• No crash- or error-reporting service.
• No developer backend — there is no VeilX account, no VeilX server, and no VeilX API. Sign-in happens directly against the homeserver address you type in.

VeilX also does not read your contacts or address book, does not request or read any device or advertising identifier (IMEI, Android ID, Advertising ID), and does not scan your files outside the media you explicitly pick to send.

No developer-side account exists. Installing VeilX does not create an account with us. You sign in to a Matrix server of your own choosing, and that account belongs to you and that server's operator, not to us. There is therefore no account with the Developer to close or delete.

No automated decision-making or profiling. We do not carry out automated decision-making that produces legal or similarly significant effects concerning you (Art. 22 GDPR), and we do not profile you, score you, or build behavioural segments. The app's automatic lock triggers described in §6 evaluate device signals on your own device and produce no decision about you as a person.

3. Data stored on your device

VeilX is local-first. The following is created and kept on your device only, and is never transmitted to the Developer:

Android system backup is disabled for VeilX (allowBackup="false"), so this data is not copied into Google Drive backups.

Notifications. Message notifications are posted with Android's VISIBILITY_SECRET flag, which means that on a secured lock screen VeilX shows nothing at all — not the sender, not a preview, not even that a message arrived. Notification content is generated on your device and is never sent anywhere.

4. Data sent to your Matrix homeserver

When you sign in and use VeilX, the app communicates with the homeserver address you entered. That server receives:

• Your username and password at sign-in, and thereafter your session token;
• Your messages and uploaded media — end-to-end encrypted, so the server stores ciphertext it cannot read;
• Unencrypted metadata inherent to the Matrix protocol: your user ID, device ID and device name, the rooms you belong to, who you exchange messages with, timestamps, read receipts, typing and presence signals, and your IP address;
• Your profile display name and avatar, if you set one;
• Directory or user searches you perform, and location coordinates you deliberately share in a chat (as an encrypted message).

How long that server keeps this data, who can access it, and where it is located are determined by its operator. Disappearing-message settings in VeilX work by redaction, which asks the server and every participant's client to delete the content; enforcement ultimately depends on the server.

5. Other third parties your device contacts

Beyond your homeserver, VeilX makes the following network requests. None of them go to the Developer, and each is listed with what triggers it and what the recipient can observe. If you enable the in-app proxy, requests marked "proxied" travel through the proxy server you configured, which sees the connection instead.

Each of these parties processes what it receives under its own privacy policy, over which we have no control. We encourage you to review them:

• Your Matrix homeserver operator, and your proxy provider — refer to the notices they give you.
• Element (New Vector Ltd.), for the default call server: element.io/privacy
• OpenStreetMap Foundation, for map tiles and geocoding: osmfoundation.org/wiki/Privacy_Policy
• Alibaba Cloud, for the public DNS resolver used inside the proxy tunnel: Alibaba Cloud privacy policy
• Google, for the connectivity probe and for Play distribution: policies.google.com/privacy

Distribution through Google Play is handled by Google under Google's own terms; the Developer receives only Google's aggregate, anonymous store statistics (installs, ratings, and similar), which are not linked to individual users.

6. Permissions and optional protective features

Permissions

Protective features

These are on-device security features. They are optional, and none of them transmit anything to the Developer:

• PIN lock and encrypted vault. A PIN you choose derives a key using a memory-hard function (Argon2id), bound to the device's hardware security module (StrongBox or TEE where available). The message database and encryption keys are encrypted at rest with it, and the key is erased from memory when the app locks.
• Emergency erase. If enabled, entering a second PIN you designate — the emergency PIN — permanently destroys the local data and keys. This is irreversible. Optionally, and on a best-effort basis, VeilX will then send one alert message — which may include your last known location if you configured that — to a Matrix contact you nominated, over your existing encrypted channel to your own homeserver.
• Automatic lock triggers. If enabled, VeilX locks itself (non-destructively) when a USB data connection appears, when airplane mode is switched on, when the SIM is removed, or when the device enters an area you marked as untrusted. These signals are evaluated entirely on-device and are never reported anywhere.
• Screenshot and screen-recording block for the app window.
• Remote lock or wipe for a lost, stolen, or offboarded device — available only where your organization has deployed and enabled the corresponding service on its own server, and only through a cryptographically signed instruction.

7. Legal bases for processing (EEA, UK, Switzerland)

To the extent the GDPR or UK GDPR applies to the Developer, we rely on:

• Performance of a contract (Art. 6(1)(b)) — processing on your device that is necessary to provide the app's core messaging functionality;
• Consent (Art. 6(1)(a)) — for optional features you switch on yourself, in particular location sharing, untrusted-zone locking, and the emergency alert. You may withdraw consent at any time by turning the feature off or revoking the permission in Android settings;
• Legitimate interests (Art. 6(1)(f)) — responding to a support or privacy request you send us, and protecting the app against abuse.

Because the Developer holds no user data, most processing takes place on your own device or on the servers you selected. Cross-border transfers of message data are determined by where your chosen homeserver is located.

Is providing your data required? You are not under any statutory or contractual obligation to provide personal data to the Developer, and we ask you for none. Providing a username and password to your chosen homeserver is necessary to use VeilX for messaging at all — without an account on some Matrix server, the app has nothing to connect to. Granting the camera, microphone, or location permissions is entirely optional; declining them disables only the corresponding features and has no other consequence.

8. Your rights

Depending on where you live, you may have rights to access, correct, delete, restrict, port, or object to the processing of your personal data, and to be free from discrimination for exercising them.

• EEA / UK / Switzerland (GDPR, UK GDPR, FADP). Rights of access, rectification, erasure, restriction, portability, and objection; and the right to lodge a complaint with your supervisory authority. In the EEA, find yours through the European Data Protection Board's list of members; in the UK, the Information Commissioner's Office; in Switzerland, the FDPIC.
• California (CCPA/CPRA). See the itemised disclosure below.
• Other U.S. states with comprehensive privacy laws (including Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana and others as they take effect) — equivalent rights, including the right to opt out of targeted advertising and profiling. VeilX conducts no targeted advertising, profiling, or sale of personal data.
• Brazil (LGPD), Canada (PIPEDA), Australia (Privacy Act) and other jurisdictions — equivalent rights under applicable local law.

California disclosure (CCPA/CPRA)

For the twelve months preceding the effective date of this policy, and on a continuing basis, the Developer's collection of personal information through the VeilX app is as follows:

Sources, purposes, and recipients. Because the Developer collects no personal information, there are no sources, no business or commercial purposes for collection, and no categories of third parties to whom the Developer discloses personal information. The Developer has never sold or shared personal information, including that of consumers under 16 years of age, and does not do so.

You may exercise your California rights, including through an authorized agent, by writing to service@lockmere.io.

How we handle requests

We do not charge for these requests and will not discriminate against you for making one. We may need to verify your identity before acting on a request; where we hold no account for you, verification may not be possible and we will say so.

9. Deleting your data

• On your device: sign out, use the in-app storage controls to clear the cache and history, or uninstall VeilX. Uninstalling removes the app's entire private storage, including the encrypted database and keys.
• On the server: contact your homeserver's administrator to deactivate your account and delete server-side data. VeilX cannot do this for you and cannot verify that it was done.
• With us: if you have emailed us, ask us to delete the correspondence and we will do so, unless we are required to retain it by law.

Because installing VeilX creates no account with the Developer (§2), there is no developer-side account for us to delete. Requests concerning app-related correspondence may be sent to service@lockmere.io and will be answered within 30 days.

10. Data retention

The Developer retains no user data. Support and privacy correspondence you send us is kept only as long as needed to handle your request and to keep a record of compliance, and no longer than 24 months. Data on your device stays until you delete it, or until a disappearing-message timer, a lock, or an emergency erase removes it. Data on your homeserver is retained per its operator's policy.

11. Security

VeilX applies end-to-end encryption to message content (via the Matrix protocol's Olm/Megolm implementation), TLS to all network connections, encryption at rest for local data as described in §3 and §6, and hardware-backed key storage where the device supports it. No method of transmission or storage is completely secure, and we cannot guarantee absolute security. If we become aware of a security issue affecting the app, we will seek to release a fix as promptly as we reasonably can and will, where required by law, notify affected users and regulators. This describes how we intend to act; it is not a warranty, and §15 of our Terms of Service sets out what we can and cannot warrant.

12. Children

VeilX is a business communications tool and is not directed to children. Our Terms of Service require you to be at least 16 years old — or older, where your country sets a higher age of digital consent — and VeilX is not intended for anyone below that age. It is likewise not directed to children under 13, to whom the U.S. Children's Online Privacy Protection Act applies. We do not knowingly collect information from children; in fact we collect no information from anyone. If you believe a child is using the app in a way that concerns you, please contact the operator of the relevant homeserver, and us at the address below.

13. Changes to this policy

We may update this policy to reflect changes in the app or in the law. The revised version will be posted at this URL with an updated effective date. If a change materially reduces your privacy protections, we will make reasonable efforts to notify you in the app before it takes effect. Continuing to use VeilX after an update means you accept the revised policy.

14. Contact

LOCKMERE AI LABS LLC
30 N Gould St, Ste R, Sheridan, WY 82801, United States
Privacy enquiries: service@lockmere.io