A safe messenger has more than one failure mode

X's current Chat help page gives a clearer security picture than a simple encrypted-or-unencrypted label. It says encrypted Chat covers message content, links, media, files, reactions, and group messages. It also lists limits. Metadata such as recipients and creation time is not encrypted, message requests can begin unencrypted, and the current design is not forward secure.

Forward secrecy is the limit I would underline. X says that if a registered device's private key is compromised, an attacker could decrypt all encrypted Chat messages sent and received by that device. Planned private-key rotation may improve protection for future messages, but old messages encrypted under an exposed key version remain a separate problem. Encryption at rest does not erase the consequences of a key theft.

Device handling matters for the same reason. X says there is no limit to the number of devices that can use Chat. Logging out removes messages and keys from the current device, while other signed-in devices are unaffected. Anyone reviewing an account after a lost phone should inspect every active device, not stop after changing one setting on the replacement phone.

This does not make Chat useless. It makes the risk model specific. Ask whether the conversation is encrypted yet, which metadata remains visible, how many devices can recover the history, and what happens after a private key is exposed. The independent WexChat Pro safety guide keeps those questions separate from marketing language. WexChat Pro is not affiliated with X Corp.

“Safe enough” depends on the conversation, the devices, and the recovery path. The label alone cannot decide it.

The stated protections and limits come from X's current About Chat help page.