Record calls and live streams with consent enforced in the SDK, an auditable trail and single-call erasure — server-side or on-device, archived to storage you control. GDPR- and ISO-minded recording, on your own infrastructure.
Recording won’t start until every participant agrees — enforcement lives in the SDK, not just the UI.
Archive each participant server-side to storage you own, or capture locally — both gated by consent.
One call permanently removes a recording — the database row and the objects in your storage.
Consent grants and start/stop events are written to an audit log — show who agreed, and when.
Recordings live in your object storage, in your region — nothing is routed through a third party.
The same consent-gated recording covers 1:1 and group calls and live broadcasts.
Yes — enforcement lives in the SDK, not just the UI. A recording will not start until every participant has agreed, and the consent exchange happens over a signalled channel so it’s reliable across devices.
Both. Server-side recording archives each participant to storage you own; on-device recording captures locally. Either way the SDK gates it behind consent.
A single call permanently deletes a recording and its stored objects — the database row and the files in your object storage — so you can honour an erasure request in one step.
Yes. Consent grants and recording events are written as an auditable trail, so you can show who agreed and when a recording started and stopped.
It’s built with them in mind: consent before capture, an audit trail, right-to-erasure and data residency on infrastructure you control. Your DPO owns the policy; the SDK gives you the controls to enforce it.
One platform for messaging, streaming and calls — talk to us and we'll help you scope it for your product.
Pool