Revision as of 08:13, 8 July 2024 edit AleksanteriTurunen (talk \| contribs) 10 edits Added more services, more information, more sources, updated outdated information, cleaned up references, and marked services that no longer exist. ← Previous edit		Revision as of 07:49, 9 October 2024 edit undo WikiCleanerBot (talk \| contribs) Bots 1,007,735 edits m v2.05b - Bot T20 CW#61 - Fix errors for CW project (Reference before punctuation) Tag: WPCleaner Next edit →
Line 3: Client-side encryption allows for the creation of applications whose providers cannot access the data its users have stored, thus offering a high level of privacy.<ref name=":9"/> Applications utilizing client-side encryption are sometimes marketed under the misleading or incorrect term ''"zero-knowledge"'',<ref name=":10"/>, but this is a misnomer, as the term [[zero-knowledge proof\|zero-knowledge]] describes something entirely different in the context of cryptography. ==Details== Line 20: ===Examples of services that optionally support client-side encryption=== * [[iCloud\|Apple iCloud]] offers optional client-side encryption when "Advanced Data Protection for iCloud" is enabled.<ref name=":3"/><ref name=":4"/> * [[Google Drive]],<ref name=":6"/>, [[Google Docs]],<ref name=":6"/>, [[Google Meet]],<ref name=":7"/>, [[Google Calendar]],<ref name=":7"/>, and [[Gmail]]<ref name=":7"/> — However, as of Jul 2024, optional client-side encryption features are only available to paid users.<ref name=":8"/> ===Examples of services that do not support client-side encryption===

Client-side encryption: Difference between revisions