Proton's AI push: what the 404 Media report means for users
404 Media reports that Proton's CEO and CTO are pushing staff to write most code with AI, and that a request for pentesting drew a 'loser thinking' reply. What was reported and on what evidence, what Proton said, what it changes for your encrypted mail, how to check Proton's audits and export your data, and a checklist for judging any privacy provider.
Proton sells privacy on trust: that it can’t read your mail, and that it builds its software carefully enough for that promise to hold. This week, reporting from inside the company raised questions about the second half of that. On 26 October 404 Media reported that Proton would “re-interview” staff about how they use AI, with jobs at stake. On 29 October it published a longer investigation into how Proton’s leadership is pushing the company to build with AI, including a reply from CEO Andy Yen that called a request for security testing “loser thinking”. Proton didn’t dispute the reporting, 404 Media says.
If you use Proton Mail, Drive, Pass or VPN, or you’re choosing a privacy provider, you have three questions. What was reported, and how solid is it? Does any of it touch the encryption that protects your data? And what can you check or do yourself? This piece answers them from the reporting, Proton’s own statements and Proton’s security documentation. It’s a news explainer, not a recommendation to stay or leave.
The short answer
- What’s reported: 404 Media spoke to eight current and one former Proton employees and reviewed Slack chats, meeting recordings, internal documents and a manifesto by the CTO. It reports that leadership is pushing staff to write most code with AI, that the CTO said AI wrote 90% of Proton’s code in October, and that the CEO dismissed a request for a few days of pentesting as “loser thinking”. This is one outlet’s reporting; other outlets have repeated it without adding documents of their own.
- What Proton says: a spokesperson didn’t dispute 404 Media’s reporting and said Proton had “sometimes been too blunt or too slow in explaining ourselves to our people”. On Reddit, Proton confirmed the re-interviews, published the staff email, and said it is “not doing layoffs and using AI as an excuse”.
- What it changes technically: nothing reported so far alleges a vulnerability, a breach or a change to Proton’s encryption. Our analysis: the risk the reporting raises is about process, not cryptography. Proton’s end-to-end encryption runs in its client apps, so the care that goes into that code, whoever or whatever writes it, is what your privacy depends on.
- What you can do: read Proton’s published audits (its dated audit posts for Pass and Drive are from 2023, its VPN audit links were updated in December 2025 and the no-logs audit is from 2026, and the Mail reports it links carry no date on its page), watch its open-source repositories and security advisories, keep exports of your mail, calendar and contacts, and judge any provider by the checklist at the end.
What did 404 Media report about Proton?
404 Media’s investigation, “Manifestos, Fear, and ‘Loser Thinking’: Inside Proton’s AI Reckoning”, was published on 29 October 2026. Its evidence, in its own words: it “spoke to eight current and one former Proton employees and reviewed Slack chats, meeting recordings, and an AI manifesto written by the company’s CTO”, and it quotes “one internal document obtained by 404 Media” and another “seen by 404 Media”. Most of the article is public; the end is for paying or signed-up members, and we haven’t read that part. Everything below comes from the public part.
The main points, all as reported by 404 Media:
- The pentest exchange. In Proton’s security Slack channel at the end of August, an employee urged the company “to at least take a few days to pentest newly written code before pushing it live”. Yen replied: “That’s bullshit and loser thinking. Of course it’s possible to be fast and secure. … Stop thinking always of how to be slower, and focus more on how to be faster.” He told the team to “stop lovingly handcrafting all our code and use AI more”. In the same conversation an engineer wrote: “AI won’t magically solve our problems, because security is low in our prioritization at present.”, and 404 Media adds that “one employee stressed that engineers still strive to build in a secure way.”
- How much code AI writes. “Ninety percent of code at Proton in October was written by AI, the company’s CTO Bart Butler said in a meeting, according to audio 404 Media obtained.” Multiple employees said much of it is written with Anthropic’s Claude.
- The CTO’s manifesto. Butler posted what 404 Media calls a self-described AI manifesto to Slack in September. It told engineers “Your old job is gone”, called not adopting AI an “existential threat to the success of the mission itself”, and said Proton needs to reach a point where most code is reviewed by AI rather than humans. Replying to an employee, Butler wrote: “It’s supposed to be provocative, because it needs to be.”
- Hiring and tracking. Yen told staff in Slack: “This will be the last year that we hire engineers, and starting next year we hire what we used to call product managers, to build things with AI.” 404 Media reports that Proton set up an email address for staff to flag blockers to AI adoption, and installed software that tracks how much code is AI-generated.
- Internal AI use. An internal document says Proton, which first banned AI internally, now approves it for uses including processing financial data, drafting responses on Reddit and LinkedIn, and writing code “except when that source code contains information that would give immediate advantage to a competitor” or relates to “innovation or R&D”.
- The business case. An internal document says Proton isn’t on track for its annual recurring revenue target “Due to insufficient velocity” and that “By all metrics that matter, we’re an underperforming company.”
- Culture. 404 Media describes “a culture of fear” in which employees hesitate to raise security concerns. When a senior employee suggested supporting staff who fall behind instead of re-interviewing them, Yen replied: “we already know more or less who is behind. If we were giving up on them, we would not bother with this process.” The employee called that messaging “fear-based”. Yen eventually replied: “If you are making the accusation that this is a financially driven decision and you don’t trust me when I tell you it’s not, then I think this might not be the place for you.”
Three days earlier, 404 Media had reported that Proton told staff on Monday 26 October it would re-interview employees about their AI use, citing an internal email that called the interviews “consequential”. Tom’s Guide and TechRadar followed on 27 October with Proton’s public reply. French outlet Next summarised the investigation on 30 October.
What has Proton said in response?
Proton has answered in three places. None is from Yen or Butler personally; we found no public statement from either on the 29 October report as of 30 October.
To 404 Media
“In response to detailed questions from 404 Media, a Proton spokesperson did not dispute any of our reporting or characterization of what’s happening inside of the company,” 404 Media writes. The spokesperson said: “It’s clear that some people at Proton are unhappy with our direction, or misunderstand it, and many people are anxious. In our determination to move fast, we have sometimes been too blunt or too slow in explaining ourselves to our people. We will work on that, as their questions are the ones we most need to answer.”
On Reddit
Reddit blocked our attempts to read the thread, so these quotes come from Tom’s Guide; TechRadar quotes the same comment’s “not doing layoffs” line. The comment came from the official Proton_Team account on r/ProtonMail. Proton said it is “not doing layoffs and using AI as an excuse”, that it faces a talent shortage and is hiring across the company, and that “AI is changing the tech industry, and we, like everyone else, need to evolve our ways of working to remain effective in our industry, and to deliver features faster to users.” It said it is “assessing how colleagues are adapting to these tools, what support they need, and who can help lead this work”, and offering “the support that is necessary, to those who need it, to succeed.”
According to Tom’s Guide, Proton also posted the email itself, which it says went to some of its staff. The email says re-interviews will “assess how people are adapting to AI and whether they have the capabilities and approach needed for Proton’s next phase”. They run from 4 to 11 November, are led by interviewers from outside each person’s team, and follow interviews Yen held with more than 40 senior leaders. Their results feed a review that “may lead to changes in roles, responsibilities, and continued employment” (quoted by TechRadar). Not everyone will be invited, and being invited isn’t itself an outcome.
To Next
Next says that, asked about the climate of fear and pressure, Proton didn’t deny it, and quotes a spokesperson in French. Our translation: “Times of great change are frightening, and the tech industry as a whole has to deal with this transition. We haven’t always communicated our intentions as well as we could have, but Proton is committed to helping our colleagues retrain and reskill for the future.”
How people have reacted
Some reaction has been sharp. Ben Werdmuller, who writes about technology and journalism, wrote that “Services like Proton need to exist”, but that “A move-fast culture of bullying that apes startup-land and calls caution ‘loser thinking’ does not instill confidence”, and that journalists “should think twice before using it.” Next reports anger on r/ProtonMail, especially among paying subscribers, many of whom say they have cancelled or plan to. We haven’t counted cancellations and can’t verify them.
The case for Proton rests on what hasn’t happened. TechRadar’s view was that “for Proton VPN and Proton Mail users, nothing changes for now.” Proton says it is hiring and supporting staff through the change. Proton isn’t alone in tying jobs to AI use: TechRadar points to similar moves at Shopify, Duolingo, Meta and Google. The question the reporting raises is whether Proton’s review and testing keep pace.
What’s confirmed, what’s alleged, what’s disputed
| Claim | Status | Basis |
|---|---|---|
| Proton is re-interviewing staff on AI use, 4–11 November, with possible effects on roles and employment | Confirmed | Proton’s Reddit statement and the email it posted there (via Tom’s Guide); also 404 Media, TechRadar |
| Proton wants staff to use AI more, to ship features faster | Confirmed | Proton’s Reddit statement |
| CEO called a request for a few days of pentesting “loser thinking” | Reported, not disputed | 404 Media (Slack messages); Proton didn’t dispute it |
| CTO said AI wrote 90% of October’s code | Reported, not disputed | 404 Media (meeting audio) |
| CTO manifesto: most code to be reviewed by AI, not humans | Reported, not disputed | 404 Media (Slack post) |
| “Last year that we hire engineers” | Reported, not disputed | 404 Media (Slack). Proton told Reddit it is hiring across the company |
| Software tracks how much code is AI-generated | Reported, not disputed | 404 Media |
| Proton is behind its revenue target | Reported, not disputed | 404 Media (internal document) |
| The re-interviews are about cutting staff or money | Disputed | Proton: “not doing layoffs and using AI as an excuse”; Yen internally: not “a financially driven decision”. Employees told 404 Media they feared for their jobs |
| Security work is being deprioritised | Disputed inside Proton | One engineer: “AI won’t magically solve our problems, because security is low in our prioritization at present”; another employee: engineers “still strive to build in a secure way”; Yen: “possible to be fast and secure” |
| A vulnerability, breach or weakened encryption | Not alleged | None of the reporting we read claims one |
“Reported, not disputed” means one outlet, 404 Media, reports it from documents, recordings or sources, and Proton didn’t challenge it when asked. No second outlet has published the documents independently. 404 Media’s account doesn’t say whether any release actually went out without a pentest, only how the request was answered.
Timeline: Proton’s AI turn
| Date | What happened |
|---|---|
| 2015 | Proton open-sources the Proton Mail web app (Proton) |
| 18 July 2024 | Proton Scribe, a writing assistant in Proton Mail; Proton says it can run entirely on your device and doesn’t train on your inbox |
| 23 July 2025 | Lumo chatbot launches; Proton says it keeps no logs of conversations, doesn’t train on them, and runs open-source models in Proton’s European datacenters |
| 5 May 2026 | Post-quantum encryption (opt-in) for new mail, with older mail to be re-encrypted later |
| 30 June 2026 | Lumo 2.0; Proton says more than 10 million people have used Lumo |
| 18 August 2026 | Yen tells Wired Proton was “reluctantly pulled in” to AI and “I would probably prefer a world where AI didn’t exist, but it’s here” |
| Late August 2026 | The “loser thinking” exchange in Proton’s security Slack (404 Media) |
| September 2026 | The CTO’s AI manifesto posted to Slack (404 Media) |
| October 2026 | The CTO says AI wrote 90% of the month’s code (404 Media, meeting audio) |
| 26 October | Staff email announces re-interviews; 404 Media reports it |
| 27 October | Tom’s Guide and TechRadar report Proton’s Reddit reply |
| 29 October | 404 Media publishes its investigation |
| 4–11 November | Re-interviews scheduled |
Before this reporting, Proton’s public AI story was about products: Scribe, Lumo and the privacy promises around them. In the Wired interview Yen said: “if the privacy companies do not find a way to step in to build privacy-first AI, we are essentially ceding the future to tech companies that don’t have the best interests of users at heart.” We found no public statement from Proton about using AI to write its own code before 404 Media’s report.
Does any of this affect your encrypted data?
Nothing reported says Proton’s encryption has changed or been broken. To see what the reporting could touch, it helps to know which parts of Proton protect what.
What Proton encrypts end to end, and what it encrypts at rest
Proton uses two kinds of encryption, and its documentation explains the difference with two cases:
- End-to-end encryption, for mail between Proton users and password-protected mail to anyone else: “The email is encrypted on the sender’s device using your public encryption key before being transferred to the Proton Mail server”. Proton never sees the plaintext.
- Zero-access encryption, for mail from outside providers such as Gmail: “When it arrives at Proton Mail, our servers can read that email because Gmail doesn’t support end-to-end encryption. But after receiving the email, we encrypt it immediately using your Proton Mail public encryption key.”
Proton says message bodies and attachments are stored encrypted with your key, but “Subject lines in Proton Mail messages are not end-to-end encrypted” (Proton support). Lumo is different again. Saved chats can only be decrypted on your device, but chatting with Lumo isn’t end-to-end encrypted. Asked by Wired whether Lumo’s privacy was a promise from Proton rather than a technical guarantee, Yen agreed: “a promise is not as good as a mathematical guarantee, but a promise made by the right people is still actually quite substantial.”
Where code quality matters
In end-to-end encryption, your app does the encrypting. That makes the client code (web, desktop and mobile apps) the part your privacy most depends on. Proton said as much in 2019, answering a paper by researcher Nadim Kobeissi: for its web app, “any web service provider can change the application that is delivered to end users. This includes potentially providing a malicious application that could compromise the encryption” (Proton). Proton’s answer was that this applies to every web app, and that it also ships native apps on every platform.
Our analysis: who wrote a line of code, a person or a model, doesn’t change Proton’s cryptographic design: OpenPGP, keys you control, zero-access storage. What could matter is a bug in the code that applies that design. That could be an app that mishandles a key, leaks data before it’s encrypted, or a server that keeps outside mail in plaintext longer than it should. Review and security testing are how such bugs get caught, whoever wrote the code. That’s why the reported exchange about pentesting, and the manifesto’s aim of having AI rather than humans review most code, are the parts of this story that bear on users. Neither shows that anything went wrong. They’re signals about process, and the evidence that would settle the question is future audits and advisories. Our guide to reviewing code written by AI agents covers what teams that ship agent-written code do about review.
What doesn’t change
Proton says stored mail, calendars and files are encrypted with your public key, and “only you can decrypt it using your private key” (Proton). Our analysis: that design limits what a bug on Proton’s servers alone could expose in the bodies and attachments of mail already stored, though subject lines and metadata aren’t end-to-end encrypted. The apps you sign in with, which unlock your keys, are where bugs would matter most, and the web app is itself served by Proton’s servers, as Proton’s 2019 answer acknowledged. The legal protections are separate from the code: Proton’s transparency report says only Swiss authorities can compel it to hand over data, including foreign requests passed through Swiss authorities. Lumo, Scribe and other AI features are separate products you can leave switched off.
How to check Proton’s security yourself
Proton publishes more than most providers, and you can watch it over time rather than take anyone’s word.
Open-source apps
Proton says “All Proton apps are open source” and links the code from its open-source page: Mail and Calendar (WebClients and the ProtonMail organisation), Drive, VPN, Pass, Authenticator, Wallet and Lumo. It also maintains the OpenPGP.js and GopenPGP encryption libraries. You don’t need to read code to use this. Commit history is public, so researchers can see what changed and when; code review appears to happen internally and isn’t visible on GitHub.
Published audits
These are Proton’s published audits, with the dates Proton gives:
| Product | Auditor | Date | Proton’s summary of the result |
|---|---|---|---|
| Proton Pass apps, extensions and API | Cure53 | May–June 2023 | All issues fixed except one medium-severity Android issue that the platform prevents fixing (Proton) |
| Proton Drive mobile apps | Securitum | Carried out 2022, published March 2023 | “no outstanding vulnerabilities” (Proton) |
| Proton VPN apps | Ruben Santamarta, independent researcher | Links updated December 2025 (no audit date given) | Reports linked from Proton VPN |
| Proton VPN no-logs infrastructure | Securitum | Fifth annual audit, 2026 | No logging of browsing, DNS or identifiable connection metadata found (Proton VPN) |
| Company security controls (SOC 2 Type II) | Schellman | July 2025 | Attestation completed (Proton) |
The open-source page also links audit reports for Proton Mail (web and desktop) and Calendar. The reports are hosted on Proton Drive share links, and the page doesn’t give their dates. Proton also says it holds ISO 27001 certification. All of these were published before the late-August exchange 404 Media describes, so none of them tells you about code written since then. The next audit of Mail and its apps is the one to watch.
Bug bounty and advisories
Proton’s bug bounty pays up to USD 100,000. Critical issues pay USD 25,000–50,000, high USD 2,500–25,000 and medium USD 1,000–2,500; low-severity findings are case by case with no reward by default. A bounty is a standing invitation for outside researchers to test the newest code. Fixes and known issues appear on Proton’s security advisories page.
What Proton doesn’t publish
We found no schedule or results of Proton’s internal penetration tests on its site, and no warrant canary on its transparency page or anywhere on proton.me, as of 30 October. That isn’t unusual: most providers don’t publish internal pentests. But it means outsiders only learn about testing from published audits and advisories.
How to export your Proton data
Keeping a copy of your data is good practice with any provider, whatever you decide about Proton.
- Mail: the Proton Mail Export Tool is “available for everyone” on free and paid plans. It saves decrypted mail with its metadata “as EML and JSON files”, which can be imported into mail apps such as Thunderbird or Outlook, Proton says. Large mailboxes can take hours.
- Calendar: in Proton Calendar, go to Settings → All settings → Proton Calendar → Import/export, choose the calendar and click Download ICS (Proton).
- Contacts: in Contacts, select all, click “…” and choose “Export selection as .VCF”; contacts are decrypted in your browser (Proton).
- Ongoing access in a desktop mail app: Proton Mail Bridge gives IMAP access on paid plans.
If you decide to move, our email providers comparison covers 14 services on encryption, price, custom domains and standards. Of the 14, only Tuta also encrypts mail end to end by default, and it encrypts subject lines as well. If you use your own domain, moving is mostly a matter of changing DNS records. A @proton.me address can’t come with you, so a custom domain is worth setting up even if you stay.
How to judge any privacy provider’s security
Whatever you make of this story, the same questions apply to every provider that asks for your trust:
- Independent audits, with dates. Who audited what, when, and is the report published in full? An audit from three years ago says little about this year’s code.
- Published penetration tests or a public audit schedule. Is testing ongoing, or a one-off before a launch?
- A bug bounty with real payouts. Are its scope and reward table public?
- Open-source clients. Can you or a researcher read the code that does the encrypting, and does it match what ships?
- Security advisories. Does the provider publish fixed vulnerabilities, or only good news?
- Transparency reports. How many legal requests, from where, and what was handed over?
- A warrant canary, if the provider’s jurisdiction makes one meaningful. Few providers keep one, so its absence alone isn’t a red flag.
- How the company handles criticism. Does it engage with researchers and reporters, or dismiss them? Proton’s response this week, which didn’t dispute the reporting and promised better communication, is part of that record. So is what it does next.
FAQ
Is Proton Mail still safe to use?
Nothing reported so far shows a vulnerability, a breach or any change to Proton Mail’s encryption. Mail between Proton users is still encrypted on your device, and stored mail is still encrypted with your key. The reporting raises questions about how carefully new code will be reviewed and tested as Proton moves to AI-written code, and Proton’s next audits will be the evidence on that.
Did Proton say AI writes 90% of its code?
Not publicly. 404 Media reports that Proton’s CTO, Bart Butler, said in an internal meeting that 90% of Proton’s code in October was written by AI, based on audio it obtained. Proton didn’t dispute 404 Media’s reporting.
What did Andy Yen mean by “loser thinking”?
According to Slack messages 404 Media reviewed, Proton CEO Andy Yen used the phrase in late August, answering an employee who asked for a few days to pentest new code before release. He wrote that “it’s possible to be fast and secure” and urged staff to use AI more. Proton hasn’t publicly commented on the exchange specifically; its spokesperson said Proton had “sometimes been too blunt or too slow in explaining ourselves to our people.”
Is Proton laying off staff over AI?
Proton says no. It told Reddit users it is “not doing layoffs and using AI as an excuse” and that it is hiring. Its staff email says re-interviews on AI use, from 4 to 11 November, feed a review that “may lead to changes in roles, responsibilities, and continued employment.”
How do I export my Proton Mail?
Use the Proton Mail Export Tool, available on all plans, which saves decrypted mail as EML files plus JSON metadata. Export calendars as ICS files from Calendar settings and contacts as a VCF file from Contacts. Our email providers comparison covers where else you could take them.
Is Proton’s code open source?
Yes. Proton publishes the source of its apps, including Mail, Calendar, Drive, Pass, VPN and Lumo, on GitHub, and links audit reports from its open-source page. Proton’s dated audit posts for Pass and Drive are from 2023, and the Mail reports it links show no date on that page, so none can be shown to cover code written since the AI push described in the reporting.
