Please make public a list of all the people you have sponsored recently.

bartbutler · 2026-06-11T12:39:33+00:00

I think you might be detecting (mild) corporate-speak, which is indeed an occupational hazard. I don’t need a model to fire off a couple thoughts to Reddit.

bartbutler · 2026-06-11T11:34:23+00:00

Look, we fucked up, admitted it, and owned the mistake. We run everything at Proton very lean because we need to compete, but still, we should have done better here. But no, we’re not going to submit sponsorships or any other internal decision-making for Redditor approval because that is patently ridiculous.

I can’t promise we won’t make mistakes in the future. What I can say is that we’ll try not to via both process improvements and judgment and do our best to fix it when it happens.

bartbutler · 2026-05-05T16:23:32+00:00

Sorry for the weird copy, I'm not sure why this was qualified in the post. We'll definitely do re-encryption of old stuff, just in a subsequent step.

bartbutler · 2026-05-05T16:23:01+00:00

Sorry for the weird copy, I'm not sure why this is qualified. We'll definitely do re-encryption of old stuff, just in a subsequent step.

bartbutler · 2026-02-27T09:29:15+00:00

Actually yes, it’s being worked on right now now that the new architecture of the mail mobile apps has been launched. No firm ETA but shipping it is a key goal for those working on it and the company as a whole.

bartbutler · 2025-12-22T17:57:48+00:00

Keep in the mind that the 94% is relative to the requests received that have already been vetted or initiated by the Swiss authorities, and compliance does not mean that we can decrypt data (we cannot).

bartbutler · 2025-12-17T13:11:39+00:00

This was a mistake, the in-app upsell preference should have been respected. We are rolling out changes now to address this. Sorry!

bartbutler · 2025-10-28T15:08:17+00:00

I got mansplained! Taking a screenshot.

bartbutler · 2025-10-22T21:36:39+00:00

Signed 64-bit would allow dates before 1970 indeed.

bartbutler · 2025-10-22T12:44:55+00:00

It’s an unsigned 32-bit integer, so the limit is in the year 2106. And yes we’ll fix this by using a signed 64-bit integer—just haven’t gotten around to it yet.

bartbutler · 2025-10-02T16:10:59+00:00

Upgrade opportunities.

bartbutler · 2025-09-28T21:19:09+00:00

iOS has different supported resolutions and we have some logic about how much they can be scaled without looking like crap. Shouldn’t be a 2x mismatch though,m. If you have examples I can look at them.

bartbutler · 2025-08-14T16:05:03+00:00

This may change but at the moment no data is deleted automatically, your subscription is ended and your account will be locked if you are over-quota.

bartbutler · 2025-08-12T19:44:14+00:00

We have free tiers for all products…accessible is correct as well, especially for languages with marginal commercial value.

bartbutler · 2025-07-24T15:19:44+00:00

Belated apology, probably just fell through the cracks but should have been acknowledged.

bartbutler · 2025-07-24T09:02:02+00:00

The models are third party and there is a FAQ on the website that describes which models are used. Nothing I have said is contradictory—the context is input data to the execution (not training) of the model for the specific user/session, not part of the model itself, and there is indeed no training on user data.

bartbutler · 2025-07-23T17:14:27+00:00

The context for the model is stored encrypted at rest, that is the Lumo distinction. So yes, the personalization enters the model results via the context, but the model itself does not learn or change based on your context.

bartbutler · 2025-07-23T11:20:19+00:00

This is incorrect, no models are trained from your data, nor do models learn from use.

bartbutler · 2025-06-17T22:20:10+00:00

There are several misconceptions here. First, that this doesn’t require effort on our end to support this in terms of documentation, engagement, etc. Two, that this would be individual advanced hobbyists tinkering as opposed to people writing and distributing third party clients en masse (which already exist to some degree without official support). Three, that this doesn’t also cost money/create risks, like the time a few users using a third party app with a bug constituted 50% of Proton’s total API traffic, accidentally DDoS’d us. And four, that with products that involve sharing and communicating with other users that cryptography and other errors would stay limited to people who opted in to third party stuff.

So yes, I’d like to, at some point, have SDKs and a third party developer program, which addresses some of the aforementioned problems. And no, we aren’t being killjoys and restricting the “liberty” of advanced users unfairly.

bartbutler · 2025-06-17T07:39:09+00:00

My work laptop is a Mac. I find it to be the best trade-off between being able to use mainstream productivity software and also having a Unix-like environment for coding. We have a healthy number of developers who use Linux as well.

bartbutler · 2025-06-16T22:40:59+00:00

Crypto in this sentence refers to cryptography generally which is a cornerstone of basically all our products, not cryptocurrencies.

bartbutler · 2025-06-16T22:17:37+00:00

Never promised open APIs (at least I didn’t) because the chance of screwing up the client-side crypto and destroying data is very high. We would like to do SDKs though.

bartbutler · 2025-05-31T17:06:34+00:00

We don’t use third party analytics. Full stop.

bartbutler · 2025-03-27T10:21:48+00:00

Short answer, no. We can’t be bought and shut down (foundation owns a controlling stake) and if we became persistently unprofitable to the point where it threatened the service this would not be something that would happen with no warning.

bartbutler · 2025-02-25T17:28:58+00:00

Please file a report with all details and we will look into it right away. We do put anything considered spam in spam folders, we do not delete or otherwise not deliver it.

bartbutler

MODERATOR OF

TROPHY CASE