Well, to some degree it will always happen, no matter how careful the companies are.

Unless it's e2e encrypted (like in Proton Mail or Proton Drive), these incidents will occur. Manage your risk accordingly.

▲

mvdtnz 5 days ago | parent | next [-]

There are very serious drawbacks to e2e encryption that can't be ignored for all use cases. Searching and indexing, reporting, analytics and performance are aspects of a program which become difficult or impossible if all of your data is encrypted everywhere other than the client. It's easy to just wave your hands and say "all data should be e2e encrypted" but it's not that straightforward.

	▲	BinaryIgor 5 days ago \| parent [-]
		Unfortunately, you're right; I guess there is no easy, handle-it-all answer; it all depends on the specifics of a given system

▲

SoftTalker 5 days ago | parent | prev [-]

At some point it has to be unecrypted to be useful. That's where the vulnerability is.

	▲	BinaryIgor 5 days ago \| parent [-]
		Depends whether and to what extend your service provider needs it - for Proton, it's always client only decrypted