Most SMS services store your messages the way an email provider stored mail in 2005: in a database the company can read. Anyone with access to that database, whether an employee, an attacker or someone holding a court order, can read your texts too. A zero-access encrypted SMS inbox works differently. Messages are sealed with a key the provider does not hold, so the stored copy is unreadable to the company that keeps it. This guide explains what that means in practice, how it works, and, just as important, what it cannot do for you.
What "zero-access" actually means
"Zero-access" describes who can read your data at rest, meaning while it sits on the provider's servers. In a zero-access design, stored messages are encrypted with a key tied to your account that the provider cannot use on its own. The company still runs the servers, stores the encrypted data and delivers the service, but it cannot open what it stores.
That is a narrower promise than it sounds, and it helps to separate three ideas that often get mixed together:
- Encryption in transit. The connection between your browser or app and the server is protected (HTTPS/TLS). Almost every service does this. It says nothing about how data is stored.
- Encryption at rest with a provider-held key. The database is encrypted, but the provider holds the key and can decrypt whenever it wants or is required to. This protects against a stolen disk, not against the provider.
- Zero-access encryption. The stored data is sealed with a key only the customer holds. The provider cannot read it, and so cannot hand over readable copies.
None of these is the same as end-to-end encryption, where only the sender and the recipient can ever read a message. For SMS, that distinction matters a lot.
The honest part: SMS is not end-to-end encrypted
SMS was designed decades ago for the GSM network, and it has no end-to-end encryption. When someone texts your number, the message travels through the sender's carrier, the carrier's SMS centre and the mobile network that serves the receiving SIM. The radio link between a phone and a cell tower may be encrypted, but the carriers along the way handle the message as readable text. They can see it, they may log it, and they can be legally compelled to intercept it. Weaknesses in the signalling networks that route SMS between carriers have also been abused to redirect or read messages.
So the message is readable at several points before it ever reaches the inbox provider's server. No inbox design can change that, however strong its encryption. What a zero-access inbox changes is the part of the journey the provider controls: what happens once the text arrives and is stored.
How a zero-access SMS inbox works
The details vary between providers, but the flow usually looks like this:
- Arrival. An SMS reaches the SIM or number assigned to you. On a physical-SIM service, that SIM sits in a gateway device connected to the provider's systems.
- Sealing. The message is encrypted with your account's key as it is stored. From that point the stored copy is ciphertext.
- Storage. The database holds only the sealed version. There is no separate plaintext log of message content.
- Reading. When you sign in, your key is used to open the sealed data for your session, so the inbox looks like any normal messaging screen.
Two details are worth understanding. First, the message is necessarily readable for the brief moment between arrival and sealing, because it arrives from the carrier as plain text. Second, while you are signed in, your key is in use so the screens can show your messages. Zero-access protects the stored archive. It is not a guarantee that a fully compromised live system could never see anything.
Content is only half the story: metadata
A message's text is not the only sensitive thing about it. When it arrived, whether it was read, and the names of attached files can reveal a lot. Early "encrypted inbox" designs often sealed the message body but left everything around it readable.
On crypton.sh, message text was already sealed with the customer's encryption key, and a later update extended the same seal to conversation and message times, message status, attachment file names and types, and activity details. The metadata update post lists exactly what was sealed and what the service still keeps to operate, such as your own numbers, the phone number a thread is with, and billing records, which are kept for 7 years.
What a zero-access inbox protects against
Because the provider cannot open stored messages, several common risks shrink considerably:
- Database breaches. If an attacker copies the message database, they get ciphertext rather than a readable archive of your texts.
- Insider access. Staff with database access cannot browse your conversations.
- Legal requests for stored content. A provider cannot hand over what it cannot read. Crypton's law enforcement page states that message content is sealed to a key only the customer holds and that a valid order cannot obtain it, while the account identity, assigned numbers and billing records can be provided.
- Data reuse. Unreadable data cannot be mined for advertising or analytics.
What it does not protect against
This is where many privacy products get vague. A zero-access inbox does not:
- Hide messages from carriers. As covered above, the sender's carrier and the networks in between can see SMS content in transit.
- Protect the sender's copy. The person or service that texted you still has the message on their side.
- Make the account anonymous by itself. Records the service needs to run, such as which number is assigned to which account and payment records, still exist and can be requested under the law of the provider's jurisdiction. Providers that publish a transparency report let you see how often that happens; Crypton's transparency report lists requests by year and whether data was provided.
- Protect a compromised device or password. If someone can sign in as you, they see what you see. Strong, unique credentials and two-factor authentication still matter.
- Make you undetectable. It is a storage protection, not a way to avoid being identified, and not a tool for bulk messaging or abuse.
Comparison: how different inboxes handle your texts
| Inbox type | Provider can read stored messages? | Carrier can read in transit? | Stored content available to a legal request? |
|---|---|---|---|
| Typical SMS app or cloud inbox | Yes | Yes | Yes |
| Encrypted at rest, provider-held key | Yes, if it chooses or is required to | Yes | Yes |
| Zero-access encrypted SMS inbox | No | Yes | Content and sealed metadata, no; account and billing records, yes |
| End-to-end encrypted messenger (e.g. Signal) | No | No, carriers only see encrypted traffic | Very little |
The table shows the real takeaway: if both sides can use an end-to-end encrypted messenger, that is the stronger choice for private conversations. A zero-access SMS inbox is the right tool when the other side only speaks SMS: banks, delivery services, sign-up codes and people who will not install another app.
When a zero-access SMS inbox makes sense
- Receiving verification codes on a number that is separate from your personal one, without building a readable archive of every service you have signed up for. If the codes matter, note that many services reject VoIP numbers; our guide to physical SIM vs VoIP numbers explains why.
- A second number for business or selling online, where texts from strangers should not sit in a database anyone can browse.
- Long-running numbers where years of message history accumulate. The longer the archive, the more it matters who can read it.
If you want to verify a provider's claims before trusting it, look for three things: a clear statement of what is sealed and what is not, a law enforcement or data request policy that says what can and cannot be handed over, and a transparency report. Vague promises of "military-grade encryption" without those details tell you very little.
FAQ
Is a zero-access SMS inbox the same as end-to-end encryption?
No. End-to-end encryption means only the sender and recipient can read a message anywhere along its path. SMS cannot offer that, because carriers handle it as readable text. Zero-access covers how messages are stored once they reach the inbox provider.
Can my mobile carrier still read my SMS?
Yes. The sender's carrier and the network serving the receiving number can see SMS content in transit. A zero-access inbox cannot change that. For conversations that need to stay private end to end, use an end-to-end encrypted messenger.
What happens if the provider's database is stolen?
The attacker gets sealed data. Without the customer's key, message content and sealed metadata stay unreadable. Unsealed records, such as account and billing data, could still be exposed, so it helps to know which fields a provider seals.
Can the provider hand my messages to the police?
Not in readable form, if the design is truly zero-access. It can still be required to provide what it does hold, such as account identity, which numbers were assigned and billing records. Check the provider's law enforcement policy for specifics.
Do I need to do anything to turn encryption on?
That depends on the provider. Where sealing is built in, as with the metadata change described above, nothing on screen asks you to do anything. Your part is to protect your sign-in, because anyone who can log in as you can read what you can read.
