Source
Encryption & access control — found from sitemap — Element
Checked for Element on 1 Oct 2026
- Page
- https://element.io/en/features/end-to-end-encryption
- Checked
- 1 Oct 2026, 15:35 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:b0fdf7cf78913c5cef981464770447d6dbe3fb1340e983c6adf598dd619aa892
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
E2ee default Report an error
“Element is designed to protect users and their privacy by using the highest grade end-to-end encryption by default. Messages can only be decrypted by participants in the conversation.”
-
E2ee third party protection Report an error
“Even if a server or network is compromised, a third party is unable to view the encrypted data.”
-
Encryption basis Report an error
“Element uses the encryption implemented within the Matrix open standard.”
-
Encryption protocols Report an error
“It is based on Olm, an implementation of the Double Ratchet protocol popularised by Signal, and Megolm which extends Olm for government-level and nationwide scalability.”
-
Per device decryption Report an error
“Messages are decrypted per-device rather than per-user as it adds an extra layer of resilience.”
-
SSO e2ee Report an error
“Single Sign-On (SSO)”
-
Encrypted search Report an error
“Search functionality within encrypted rooms”
-
Antivirus encrypted rooms Report an error
“Anti-virus protection for encrypted rooms”
-
Dlp encrypted Report an error
“Data loss prevention in an encrypted environment”
-
Audit bots moderation retention Report an error
“Audit bots, moderation and data retention”
-
Unencrypted rooms Report an error
“Ability to create unencrypted rooms”
-
Cross signed device verification Report an error
“Adding extra security, Element uses cross-signed device verification”
1 fact read from this page is not shown because it could not be confirmed on the page as captured.