Promises we can prove.
Our promises, your rights, the laws we answer to, where each certification stands, and who helps us run LMN8.
Five things you can count on.
We can’t read your things
Chats, calls, shares, Cloud files and vaults are locked on your device with keys we never hold.
We keep as little as we can
An encrypted message nobody collects is deleted after 30 days. An encrypted copy of your chat history is kept, so a new device you approve can read it; we hold no key to it, and it goes when you clear the chat, its timer runs out or you delete your account. Everything about an SOS is deleted 24 hours after it ends, unless you choose to save evidence (7 days by default). Ended shares are removed with a signed record; deleted Cloud files stay in Trash for 30 days, then go the same way.
Your data is never sold
LMN8 is paid for by subscriptions. No advertising, no ad trackers, nothing you store is sold or rented.
You choose where it lives
Your data is kept in your region and handled under its local laws. Cloud files are stored in the area you pick, encrypted before they leave your device.
We tell you the limits
Where our servers can see something, like who you talk to, when, and roughly how much, we say so.
Your data, on your say-so.
The rights data-protection laws give you are buttons in LMN8, not letters to a legal team.
- In place
Delete your account
Close your account and its data yourself, any time. No email to us needed.
Delete my account - In place
Download your data
Ask for a copy of what we hold about your account. We confirm it’s you first.
Ask for a copy - In place
Correct your details
Change your name, email and phone number in your account settings, after signing in.
Sign in - In place
Complaints and privacy requests
Write to the Grievance Officer of Softra Globus LLP, Vaibbhav Arora, at grievance@lmn8.app. We acknowledge within 24 hours and resolve within 15 days.
Contact & grievance - Being built
Erasure requests for organisations
Coming with LMN8 Enterprise: people will be able to ask an organisation using LMN8 to erase their data, on a request page the organisation answers and tracks.
For enterprise
What happens when you delete.
Deleting your account is a button in Settings. There is no grace period: your devices are signed out and your shares end at once, our server destroys its half of your keys, and the rest is deleted right after.
Every detail of deleting your accountThe laws and standards we answer to.
Certifications, earned in the open.
LMN8 doesn’t hold any of these yet. Each needs an independent auditor or lab, and we’ll list one here as achieved only once it’s awarded, with who awarded it and when. We will post each stage here: auditor chosen, assessment started, report issued.
- Auditor chosen: not yet
- Assessment started: not yet
- Report issued: not yet
- Auditor chosen: not yet
- Assessment started: not yet
- Report issued: not yet
- Auditor chosen: not yet
- Assessment started: not yet
- Report issued: not yet
- Auditor chosen: not yet
- Assessment started: not yet
- Report issued: not yet
- Auditor chosen: not yet
- Assessment started: not yet
- Report issued: not yet
- Auditor chosen: not yet
- Assessment started: not yet
- Report issued: not yet
- Auditor chosen: not yet
- Assessment started: not yet
- Report issued: not yet
- Auditor chosen: not yet
- Assessment started: not yet
- Report issued: not yet
How we look after our side.
Encryption everywhere
Your content is encrypted on your device. On our side, databases, file storage and disks are also encrypted at rest.
Keys and secrets locked away
Server secrets are encrypted with keys held in AWS Key Management Service, never in plain text in our code.
A firewall in front
Our websites and web APIs sit behind a web application firewall.
Least access for staff
Our admin console uses roles, so each person sees only what their job needs, and every staff sign-in needs a second factor.
A public key log
Every device key is published to a key-transparency log, so a swapped key can’t hide.
An audit trail for organisations
Organisation actions are written to an audit log that can be exported and checked for tampering.
A memory-safe core
The engines that handle your files and keys are written in Rust.
Checked on every change
Code is scanned for leaked secrets and known-vulnerable dependencies as it’s built.
Your region. Your local laws.
We keep your data in your region and follow its local laws. Our main servers run today in AWS ap-south-1; more regions for account data are being added. Your account details, device list, sign-in records and the metadata our servers must see (who talks to whom, when, and roughly how much) are kept there, whichever Cloud region you pick. When you use Cloud, your encrypted files are stored near the area you pick; “near” is a best-effort placement. Only two regions are guarantees: the European Union region keeps files in the EU, and Switzerland, a paid add-on, keeps them in Zurich.
Files are encrypted on your device before upload, wherever they’re stored.
- Asia-PacificBest effort
- Western North AmericaBest effort
- Eastern North AmericaBest effort
- Australia and New ZealandBest effort
- European UnionGuaranteed
- Switzerlandadd-onGuaranteed
The companies we rely on.
These providers handle some account data so LMN8 can work. None of them can read your chats, files or vaults: those are encrypted on your device first. We tell organisations using LMN8 30 days before we add a new one.
| Provider | What for | What data | Where | How it’s protected |
|---|---|---|---|---|
| Amazon Web Services | Servers and databases; the Switzerland Cloud region | Data: Account details and encrypted data | Where: India (Mumbai); Switzerland (Zurich) | Encrypted at rest and in transit; content is end-to-end encrypted |
| AWS SES (Amazon) | Account emails: sign-in links, receipts, notices | Data: Email address, the email itself | Where: India (Mumbai) | Sent over TLS; never your chats or files |
| AWS SNS (Amazon) | SOS text messages to your trusted contacts | Data: Contact’s phone number, the alert text | Where: India (Mumbai) | Texts are plain SMS, so only sent when you start an SOS |
| Cloudflare | Encrypted file storage (Cloud, shares, chat attachments) | Data: Encrypted files, their size | Where: In the region you pick | Encrypted on your device before upload |
| Razorpay | Taking payments | Data: Name, email, payment and mandate references | Where: India | PCI DSS Level 1; we never see card numbers |
| Twilio | Checking a phone number you add | Data: Phone number | Where: Global | Sent over TLS |
| Apple and Google | Delivering notifications to your phone | Data: Device token, an encrypted notification | Where: Global | Notification content is encrypted |
| Cloudflare | Domain name service | Data: None beyond DNS lookups | Where: Global | — |
Found a problem? Tell us.
If you think you’ve found a security issue in LMN8, email us with the steps to reproduce it. We read every report, keep you updated while we fix it, and credit you if you’d like. Please give us time to fix it before telling anyone else, and don’t access other people’s data while testing.
We do not run a paid bug bounty yet.
Checking us for your company?
LMN8 Enterprise is being built. Its security and compliance page covers architecture, controls, residency and where each certification stands.
- Data processing agreementPlanned
- A data processing agreement for organisations is on our roadmap.
- Security documentsPlanned
- Security documents on request, under NDA once they exist.
Privacy you don’t have to take on faith.
Start free, and read every detail of how it works.