Every person who gives a business their phone number is trusting somebody they have never met. This page says exactly what Linxi does with that trust — including the parts we have not finished.
Keys, and who holds them
Most platforms encrypt customer data at rest with a key the platform holds for everybody at once. That protects against somebody walking off with a disk. It does not protect against anything else, because the operator can read every customer’s data by design.
Linxi has built a separate AES-256 encryption key for each workspace, itself encrypted before it is stored, so that one customer’s data would not be readable with another customer’s key. This is built but not yet switched on. Today no workspace keys are in use: contact data is encrypted in transit between your browser and Linxi, and is not encrypted field by field where it is stored.
Some secrets are encrypted at rest today, with a key the platform holds: carrier credentials such as Twilio authentication tokens, the access tokens for Google and Meta connections, and tax forms stored for an organisation. Passwords are never stored at all, only a bcrypt hash of them.
What is encrypted today — and what is not
We would rather be exact than impressive. No contact fields are encrypted with a workspace key yet. When field encryption is switched on, contact notes and organisation come first.
Phone numbers and email addresses will take longer. They are how Linxi finds the right contact when a message arrives — and an encrypted value cannot be looked up, so encrypting them today would mean every incoming message started a new conversation instead of joining the existing one. Doing it without that side effect needs a searchable index built alongside the encryption. That work is in progress and this page will change when it lands.
If a security page tells you everything is encrypted, ask which fields and how lookups still work. It is a fair question and it has a real answer.
A record of who did what
Changes to contacts, and opening a contact’s record, are recorded: who, when, from which address, and whether it succeeded. Security changes, such as two-factor and session changes, are recorded too, and sign-ins are recorded separately with device and location. Viewing contact lists, imports, exports, the inbox and campaigns are not logged yet. Nothing is pruned from the log today, so entries are kept for the life of the account, and security records are kept after it (see the Privacy Policy).
The log records the action and the identifiers — never the contents. An audit trail that quietly becomes a second copy of your customers’ messages is a liability, not a control.
Getting data out is the risky moment
An export is the entire list in one file, and it is the single most valuable thing that can walk out of a door. A workspace can already choose settings to require a password before an export, limit exports to admins, and watermark each file. These export controls can be set but are not enforced yet: today an export runs without them. This page will change when they do.
Deleting data, and proving it
When you delete your account, its data is deleted at that moment, not after a waiting period. Payment, billing and security records are kept, as the Privacy Policy explains.
Linxi has also built signed deletion certificates: a fingerprint of the data that was deleted, the time, and an ID, checkable by anybody at linxi.app/verify-deletion. Deletion certificates are not issued yet. The checker works, but no deletion creates a certificate today.
What we will not do
- We will not sell contact data.
- We will not use your contacts to train any AI model, ours or anybody else’s.
- We will not share contact data with advertising platforms.
- We will tell you about a breach affecting your data within 72 hours of confirming it.
The service providers we do use are named in the Privacy Policy, with what each one is used for.
Not built yet, and said so
Zero-knowledge encryption for stored data, where the key never leaves your browser and Linxi cannot decrypt your data under any circumstances, is not built. Per-workspace field encryption, export controls and deletion certificates are built but not switched on, as described above. SOC 2 Type II is not certified; we have not started the audit. There is no bug bounty programme yet.
Each of those is a real thing to want and none of them is true today, so none of them is claimed above.
Reporting something
If you have found a security problem in Linxi, write to team@linxi.app with enough detail to reproduce it. We will confirm receipt and tell you what we are doing about it.
Last updated 19 October 2026.