Video meeting privacy
A practical privacy checklist for video meetings
Keep a Meeto call focused on the people and material it needs. Decide what to capture, explain recording or AI before it starts, restrict shared links and delete saved meeting material when the purpose ends.
Protect meeting privacy in five steps
- Choose the minimum. Camera, microphone, chat, screen share, recording and AI recap serve different purposes. Turn on only what the conversation needs.
- Keep capture off until needed. A normal browser meeting does not require cloud recording. Recording and AI capture are opt-in and require an eligible paid host.
- Explain the choice. Before capture starts, state the purpose, audience, retention period and participant options. Obtain any consent required by the people and jurisdictions involved.
- Protect links. Treat an invited room, recording or recap URL as access information. Share it through the intended channel and do not paste private links into public pages or support tickets.
- Delete deliberately. Check video, transcript and recap separately. Remove each material when the purpose ends, while respecting any legal preservation requirement.
Read the recording and consent section of the Terms before documenting a policy for customers, students, employees or clients.
What Meeto saves depends on your choices
| Choice | What to expect |
|---|---|
| Browser call without capture | Live media, room and account metadata needed to operate the meeting; cloud recording is not created by the capture service. |
| Cloud recording | Opt-in paid-host capture with a visible indicator; default recording retention is 90 days unless deleted sooner. |
| AI recap | A transcript and summary are generated only when the host enables the feature and the plan allowance permits it; review the result before sharing. |
| Shared link | Anyone who receives an access link may be able to reach the material it points to, so share it only with the intended audience. |
Meeto uses WebRTC (DTLS-SRTP) encryption in transit in transit. It is not end-to-end encrypted. The security overview explains what that means for server-side recording and AI processing.
Set expectations before the call
Invite message
Say whether the call is recorded, whether participants need a camera, and where a confirmed recording or recap will be shared.
Host controls
Keep the recording indicator visible, stop capture when the purpose ends and avoid showing unrelated personal or customer data during screen sharing.
After the call
Limit access, correct or annotate an AI recap before relying on it, and delete video, transcript and recap according to your retention policy.
These controls help a host make a responsible choice; they do not replace legal advice. Use the current Privacy Policy, Terms and your organisation's requirements when the meeting involves regulated or sensitive information.
Frequently asked questions
Is a Meeto video meeting end-to-end encrypted?
No. Meeto uses WebRTC (DTLS-SRTP) encryption in transit, but it is not end-to-end encrypted. The service can process media when server-side features such as recording or AI capture are enabled.
Does Meeto use my meetings to train AI?
Meeto's reviewed product policy says meetings, recordings, transcripts and recaps are not used to train AI. Review the current Privacy Policy and Terms for the complete scope and any changes before documenting your own policy.
How long are recordings and summaries kept?
Cloud recordings automatically expire after 90 days by default, and the owner can delete them sooner. Transcripts and AI recaps can remain after media expiry under the current policy, so delete each material type when it is no longer needed.
What should I tell participants before recording?
Explain what will be captured, why, who can access it, how long it will be kept and how a participant can ask a question or decline. The host is responsible for obtaining the consent required by applicable law and the organisation's policy.
Put it to work
Open your Meeto account to set it up, or explore the working product first.