Security you can explain to your IT team
Meeting roles are decided by our server, not by the app in someone’s browser. Media is encrypted in transit, every meeting can have a waiting room and a passcode, and your account can be protected with two-step sign-in.
Authority comes from the server
Whether someone is host, co-host, presenter or attendee is worked out by our server from the meeting, the invite and the signed-in account — a tampered app can’t simply claim to be host.
- Host and co-host status derived on the server; forged host flags are rejected
- Admission (waiting room, lock, room size) is decided on the server — nobody skips the line
- Webinar attendees join with mic, camera and screen share disabled
- Join attempts are rate-limited — without punishing honest reconnects
You decide who gets in
Waiting rooms, passcodes, meeting lock and host tools presets give you a locked front door and a firm hand inside the room.
- Waiting room — the host admits people
- Numeric Meeting ID with a passcode
- Lock the meeting once everyone has arrived; turn guest access off
- Webinar attendees get a personal join link — the room itself is never public
Less data, kept for less time
We don’t record your meetings. Recordings are saved only on the computer of the person who records, and shared chat files are deleted after 24 hours.
- Local-only recording, with an indicator and announcement for everyone
- Meeting reports visible only to the meeting owner and its hosts
- Caption translation runs on your own device (Chrome on desktop)
- Relay (TURN) credentials are short-lived and issued per session
A practical security toolkit
Encryption in transit
Audio and video use DTLS-SRTP; the website and signalling use HTTPS/TLS. (Not end-to-end encrypted.)
Waiting room & lock
Admit people one by one, then lock the meeting.
Server-assigned roles
Host, co-host, presenter and moderator decided by the server.
Two-step sign-in
Authenticator app (TOTP) or passkey for your account.
See your devices
Sign out of one device or all devices at once.
Consent-based recording
Recording indicator and spoken announcement for everyone.
Questions, answered
Is my meeting encrypted?
Yes, in transit. Audio and video are encrypted with DTLS-SRTP and everything else travels over HTTPS/TLS. Small meetings connect people directly; larger meetings and webinars pass through our media servers, where media is decrypted to be forwarded. KEZAYO does not offer end-to-end encryption today.
Do you store recordings of my meetings?
No. Recording saves a file on the recording person’s computer only. What we do keep is a meeting report (attendance, polls, Q&A, caption transcript and public chat) that only the meeting owner and its hosts can open.
Do you support SSO?
Not yet. Accounts sign in with email and password, and can add two-step sign-in with an authenticator app or a passkey. Talk to us if SSO is a requirement for your organisation.
Do you have security certifications?
Not yet — we don’t hold SOC 2 or ISO 27001 certification today. Found a vulnerability? Please email support@bidua.in.