Is Matrix / Element end-to-end encrypted?
Only partly. Matrix end-to-end encryption (Olm/Megolm) is available everywhere and modern Element / Element X clients encrypt new direct messages by default and pre-select 'Enable end-to-end encryption' when you create a private room (you can still untick it). But encryption is a per-room property: unencrypted rooms can be created, large public rooms are commonly left unencrypted, and a room cannot be retroactively encrypted. Because coverage depends on the room and the operator, this is 'partial' rather than always-on like Signal. (Separately, Element is making verified-device-only E2EE mandatory from October 2026, tightening encryption hygiene going forward.)
End-to-end encryption protects message contents — but not necessarily metadata. Matrix / Element's metadata model is Weak: homeservers can see room membership, sender/device IDs, timestamps, reactions and (in unencrypted rooms) content; for federated rooms this metadata is mirrored to every participating homeserver.. Compare it directly with RVNT, which is E2EE by default with a post-quantum handshake and no central server: RVNT vs Matrix / Element.