Naven
Answers
Is Google Chat end-to-end encrypted?
Not by default. Google Chat messages are encrypted in transit and at rest on Google's servers, but Google holds the keys, so it is not end-to-end encrypted. Organisations on certain paid Google Workspace plans can turn on client-side encryption, where the organisation controls the keys; personal Google accounts cannot.
Three kinds of encryption get mixed up.
Encryption in transit protects a message on its way between your device and the server, so somebody on the same Wi-Fi cannot read it. Almost every modern service, Google Chat included, does this.
Encryption at rest protects data stored on the service's disks. Google Chat does this too, but Google holds the keys, so Google's systems can read the messages when they need to, for example to search them, scan them for spam and malware, or produce them for a court order or a Workspace administrator.
End-to-end encryption means only the people in the conversation hold the keys, so the service carrying the message cannot read it. Signal and WhatsApp work this way by default. Google Chat does not.
Client-side encryption. Google Workspace Enterprise Plus, Education Standard and Education Plus customers can turn on client-side encryption for Chat. The organisation's own key service controls the keys, and Google cannot read the content. It is managed by administrators, it limits some features, and it is not available on personal accounts.
Should it matter to you? If your main concern is that nobody but the recipient can ever read a message, choose an end-to-end encrypted app such as Signal. If you are on a school or work account, remember that the organisation can usually see your chats whatever the encryption.
Naven is also not end-to-end encrypted, and says so plainly: it screens every message against published rules before it is sent, which a service that cannot read messages is unable to do. That trade-off suits families and young people; it does not suit someone whose first need is secrecy.