Does using the framework make us compliant?
No framework can do that on its own. It gives you the parts: the officer console, customer link, recording, masking, review steps and evidence trail. Whether a deployment meets your regulator’s rules depends on how you configure, integrate, test and operate it. The India requirement map in the repo shows what the framework does per paragraph and what stays with you; it is a starting point for your compliance team, not legal advice.
Where do recordings and customer data live?
On your servers and storage. Cases, photos, recordings and the activity log are written by the kit server you run. The kit does not use MediaSFU cloud recording, and rooms are created with AI notes off. MediaSFU sees pseudonymous seat names, not the customer’s name or documents.
How is the live call protected?
Media is encrypted on every network hop (DTLS-SRTP) and relayed by MediaSFU’s media servers, which store nothing. Your MediaSFU API key stays on your kit server; browsers only get a seat in their own room. The India preset asks MediaSFU for Asian media servers; that is a placement preference, not a guarantee.
Do customers need an app?
No. The customer link runs in the phone’s browser and is built for mobile data. Phones only allow camera and location on HTTPS, so you serve it from your own domain with TLS.
Can we use it outside India?
Yes. Start with the International ID preset, or copy it into a preset of your own: documents, masking rules, questions, consent text, time zone, allowed countries and storage regions all live in a few JSON files.
What does it cost?
The source is free under the MIT licence. Live calls are billed to your MediaSFU account at our published rates; hosting, storage and any vendors you connect bill you directly.