Personal data processed
The meeting touches five categories of data:
Fields you pass into the meeting (guest name, phone, intake notes)
are whatever you choose to send. You are responsible for the lawful
basis to collect and transmit them. Don’t include sensitive categories
(health details, financial account numbers, biometrics) unless you’ve
done the legal analysis on your side.
Consent patterns
Camera and microphone permission
Handled by the browser’s native permission prompt. No extra layer is added. When the guest opens the meeting for the first time, the browser shows its standard “allow camera and microphone” dialog.Before-joining disclosure
Regulated industries (finance, health, legal) often require disclosing data collection before the camera or microphone is active. Add a disclosure text to the pre-join screen or to the booking flow so the guest reads it before they join.Recording disclosure
If you enable recording — especially Record on start — inform the guest before the meeting begins. Practical patterns:- Include a note in the invitation message (WhatsApp, email, SMS) and the scheduling confirmation that the session will be recorded.
- Show a line in the pre-join copy reminding the guest that the meeting is being recorded.
- Where two-party consent is required (some US states, certain EU interpretations of GDPR), ask the guest to acknowledge in the pre-join flow before they enter the room.
PCI, HIPAA, and similar
- PCI — we are not a payment processor and do not accept card data through the meeting. Don’t paste card numbers into meeting fields, chat, or intake notes.
- HIPAA — Video is not currently a HIPAA-eligible service. Do not use it to transmit Protected Health Information (PHI).