Meeting privacy
Understand chat retention, encryption keys, and browser requirements before sharing a meeting.
You can choose end-to-end encryption when starting an instant meeting. This choice also changes chat retention: regular meetings retain chat for the organizer to review, while encrypted meetings do not save chat history.
Choose what to retain
Consider whether you need chat after the call and whether participants' browsers support encryption.
| Mode | Required to join | Chat history |
|---|---|---|
| Regular meeting | A valid meeting link | Saved chat is available in the organizer's history and search. |
| End-to-end encrypted meeting | The complete link with its key, and a supported browser | Chat is not saved and cannot be recovered through history search. |
An encrypted meeting is not a meeting without records. The meeting itself, organizer information, and attendance records remain part of meeting management. No saved chat does not mean no retained metadata.
Separate the data involved
Consider each type of information instead of treating privacy as one setting for the whole product.
| Information | What to understand |
|---|---|
| The meeting link | Anyone who receives it may be able to join while the meeting is open |
| An encrypted link's key | The complete link includes the material participants need to decrypt the call |
| Live chat | Participants exchange it during the call; encryption changes whether Meet retains it |
| Meeting and attendance records | These remain distinct from chat retention |
| Calendar invitations | Their email-based access rules do not form a Meet admission list |
End-to-end encryption protects communication between participating clients. It does not prevent another participant from writing down or otherwise capturing information they can access during the meeting.
Keep the key in the link
The encryption key is in the URL fragment, after #. Copying only the domain and meeting code removes the key, so participants cannot decrypt the call as intended.
Share the complete invitation link without shortening it by hand or deleting its fragment. Anyone with that full link also has the key, so handle it as a meeting access credential.
If a participant can open the meeting page but cannot join the encrypted call, compare the completeness of the link before replacing devices. Moving the code alone into another browser is not enough.
Resolve an encryption error
If the link is malformed or its key cannot be read, ask the organizer to resend the complete link. If the browser lacks the required encryption support, use a supported browser before joining.
Removing the key does not bypass an encryption error. If the group decides to use a regular meeting, the organizer should create a new one and make its chat retention clear to participants.
Distinguish calendar protection from meeting encryption
Protection of stored Calendar event fields and Meet's end-to-end encryption are separate mechanisms. Adding a meeting link to an event does not establish that the meeting is end-to-end encrypted. Check the meeting mode shown when creating or joining it.
Set expectations before the call
Tell participants whether chat will be retained and where final decisions should be recorded. In an encrypted meeting, no history search can recover messages that Meet deliberately did not save.
For regular meetings, chat saving is separate from live delivery and can fail independently. Use Chat and reactions to understand that boundary before relying on the history as a complete record.