Criptext is an encrypted email service that applies the Signal Protocol to mail between its users, generates each user's encryption keys on the device, and stores the inbox on the device instead of on company servers. The service launched in beta in 2018 with free clients for iPhone, Android, Mac, Windows and Linux. The latest iOS release is version 1.3.2, dated 17 August 2021, and the public Android repository was last updated on 11 August 2021. A Canadian App Store review dated 12 July 2024 reports mail arriving weeks late or not arriving at all. No formal shutdown has been announced, and no public evidence establishes reliable registration and delivery in 2026.
Origins#
Criptext was founded by Mayer Mizrachi. He was born and raised in Panama. The company sold its first product, a secure messaging app, to the government of Panama in 2014. A change of government led to criminal proceedings and an Interpol red notice, and Mizrachi spent six months detained in Colombia in 2016 before the courts threw the case out for lack of evidence. VentureBeat reports that during his detention he learned the government had been collecting email data from Criptext's lawyers, which prompted the shift to an independent email service. The company announced the email app in August 2018 and described it as still in beta, with clients for Android, iOS, Linux and Mac. In a September 2018 interview, Mizrachi said the team was based in Ecuador and New York. The founder is Panamanian by birth and upbringing, and the 2018 record places the team in Ecuador and New York. No current statement of the company's jurisdiction was found.
Encryption design#
Criptext uses the open source Signal Protocol library to encrypt each email from end to end when both sender and recipient use Criptext. The Signal Protocol was developed by Open Whisper Systems in 2013 and combines the Double Ratchet Algorithm with prekeys and a triple Diffie-Hellman handshake. It is the protocol behind Signal itself, and WhatsApp and Google Messages both use it for parts of their encryption. No independent audit of Criptext's implementation was found in the sources checked.
Each email is locked with a unique key that is generated and stored on the user's device alone. Mizrachi described the architecture in a September 2018 interview:
"Criptext does not collect user data in its servers, and all data is stored exclusively in the user's device."
The App Store listing mirror repeats the same claims about device-held keys and a device-stored inbox. The clients are open source, and the code is published under the Criptext organisation on GitHub, so the client behaviour can be inspected. The servers are not open source.
A conventional provider keeps the authoritative copy of every inbox on its own servers. Criptext keeps no such copy. Mail passes through the server only until delivery and is then deleted. The one exception is undeliverable mail, for example when the recipient's device is offline, which the server holds until delivery or for up to 30 days, after which it is deleted. Attachments are encrypted as well, with the encryption keys held on user devices.
Encryption applies only between Criptext users. Mail sent to Gmail, Outlook or any other outside provider is not encrypted in the same way. For outside recipients, Criptext offers two options: send the message through a passphrase-protected link that the recipient unlocks, or turn encryption off and send the mail normally. The first option needs the recipient to take an extra step. The second sends ordinary mail. Mail to any address outside Criptext is therefore not encrypted in this way.
Local inbox storage does not cover metadata. Sender and recipient routing, timestamps, account identifiers and connection data are still needed to deliver mail, and the published material gives no current, complete statement of what metadata is retained. Open source clients allow inspection of the published code, but that does not prove the code in the app stores matches the published repositories, and the server side was never published. The unsend feature works only within 60 minutes and only if the message has not been read. Read receipts are on by default and can be switched off in settings.
Signup and keys#
Signup happens inside the installed desktop or mobile app. The app creates the encryption and decryption keys on the device during signup, and the published signup walkthrough describes no phone number step: the only optional item mentioned is a recovery email address, needed to reset the account password.
Signing in on a new device with only a password does not restore the old mailbox, because the decryption keys for the older mail stay on the other device. The service syncs the mailbox between up to 10 devices, and offers an encrypted backup protected by a passphrase chosen by the user. Two-factor authentication needs approval from a device already signed in. Because the decryption keys stay on the device, a lost device without a tested backup means the older mail cannot be recovered from a password alone.
Maintenance record#
The App Store listing mirror shows version 1.3.2, last updated on 17 August 2021, with the only change note reading "various bug fixes and improvements". The GitHub organisation page shows the Android repository last updated on 11 August 2021 and the iOS source repository last updated in early 2021. The most recent activity on the organisation page is a Python repository updated on 18 January 2023. No release, fix or public statement from the project appears in the public record for 2024, 2025 or 2026.
AliasFleet and the Criptext inbox#
AliasFleet provides managed, persistent forwarding addresses, and the address they forward to has to be a live, maintained mailbox. A Criptext address fails that test on the current evidence, not because its encryption is weak but because its delivery is unverified. Mail sent to an alias forwards to the destination inbox, and if that inbox sits on a service whose apps have not been updated since 2021, the forwarded mail can arrive weeks late or not at all, and no alias setting can fix that. The guide to how email aliases work describes the forwarding chain.
The free tier covers 10 active aliases, 3 personal subdomains and 1 verified destination inbox, with 50 MB of monthly forwarding bandwidth, as listed on the pricing page. The destination inbox needs to be a mailbox the holder opens every day, on a service that still ships updates. Banking follows the same rule in the other direction: a bank account uses a permanent real address kept only for financial accounts, never a masked or relay alias, as described in the piece on a separate email for banking. Password resets, statements and fraud alerts all run through that address, and a dead inbox breaks the recovery path. An address that may already appear in a breach can be checked on Have I Been Pwned before deciding which accounts need a fresh alias.
Delivery reports#
A Canadian App Store review dated 12 July 2024 reports that mail could arrive after weeks, or not arrive at all. That review was not read firsthand; it is reported in a review of the public record published in October 2026. It is a single user report, not a verified service-wide outage.
A published App Store listing and public repositories do not show that a new account created today receives mail tomorrow. No public evidence establishes reliable delivery in 2026.
The company website could not be fetched from the research environment, which is recorded here as a gap in the research rather than evidence that the site is down. The App Store listing is still published, and the GitHub repositories are still public. Delivery can be tested firsthand with a non-critical address: an account is created, a message is sent to a separate mailbox, a reply is sent from that mailbox, and the test is repeated a day later. Repeated delays, or mail that never arrives, show the account is not reliable for important mail.
Maintained providers in the same trust series#
The trust series covers the same safety question for providers that are still maintained. Mailfence is a Belgian service with opt-in OpenPGP encryption and a transparency report that recorded 21 authority requests in the second half of 2025, with 9 complied with. Mailbox.org is a German service with ISO 27001 certification and a BSI C5 attestation, where encryption is also opt-in. Posteo is a German service that collects no personal data at signup and logs no IP addresses, with encryption opt-in as well. All three publish current pricing, policies and transparency figures. The difference between Criptext and these providers is maintenance, not cryptography: no release has appeared since August 2021, and no public statement from the project appears in the record for 2024, 2025 or 2026.
Final assessment#
Criptext's design is documented: Signal Protocol encryption, keys generated and kept on the device, and an inbox stored locally rather than on any server. The latest public release dates from August 2021, and a 2024 user report describes mail arriving weeks late or not at all. No formal shutdown has been announced, and no evidence proves the service is dead. The evidence also does not prove it works. The record supports use as a secondary experiment, with nothing important routed through it and a tested backup in place. It does not support use as a primary mailbox, or as the destination behind forwarding aliases. A Criptext account stays unverified until its delivery has been tested firsthand.
