Security

Security you can check, not just take on trust

How MediaSFU protects your calls, rooms and data today, written plainly, including what we don’t offer yet.

Last checked 15 October 2026.

Encrypted in transit
TLS for every API call, DTLS-SRTP for every media stream
Recordings leave our storage
72 hours after completion, by default
Staff administration
Behind multi-factor sign-in, with an audit trail
Open about uptime
Public status page with 90-day history

Encrypted media

  • The website, the API, room signalling and webhooks are served over TLS.
  • Every audio, video and screen-share stream is encrypted with DTLS-SRTP between each device and the MediaSFU media server.
  • By default, the media mesh forwards live audio, video and screen sharing between participants without decoding the media content.
  • Media content is decoded or processed for recording, transcription, live translation or AI only when you enable those features for the room.

Access and credentials

  • Every room has its own secret, separate from your account keys.
  • API keys identify your account; keep them on your server. For clients, issue disposable keys that expire after the period you choose and can be revoked instantly.
  • Staff administration sits behind multi-factor sign-in. Staff role changes are accepted only from mediasfu.com and are written to an audit log.
  • Internal service traffic is trusted only from a short registry of MediaSFU server addresses.
  • Internal service credentials are rotated. The October 2026 rotation replaced the credential on every node and retired the old value.

Infrastructure

  • MediaSFU runs on AWS as a global media mesh. Regions can be added or removed in real time, and rooms are placed using your region preferences and available capacity.
  • Media and phone servers reach each other over private AWS networking.
  • Every server is built from an image with host hardening baked in, so a replaced server comes up with the same protections.
  • A standby backend runs in a second availability zone, and DNS fails over to it if the primary stops answering.

Your data

  • Completed recordings are deleted from MediaSFU storage 72 hours after they finish. Deliver them to your own bucket to keep them longer, on your terms.
  • Recording, transcription, translation and AI agents are turned on per room. Nothing is recorded unless you ask for it.
  • Bring your own AI and SIP providers. They bill you directly, with no MediaSFU markup.
  • Webhooks are signed with HMAC-SHA256 of the body, and the send time is inside the signed body, so your server can verify each event and reject stale or replayed ones.
Where each kind of data is processed and kept

Monitoring and transparency

  • Automated checks run around the clock against the API, rooms and phone lines, and alert the team when something fails.
  • The public status page shows what is working now and the last 90 days of history.
  • Billing is audited: every charged minute is itemised in your dashboard, line by line, with CSV export.
See live status

What we don’t offer today

  • A HIPAA Business Associate Agreement
  • Certifications or attestations (SOC 2, ISO 27001, HIPAA, ABDM)
  • A published data processing agreement (DPA)
  • Guaranteed in-country processing

If one of these decides your launch, tell us. It shapes what we build next.

Responsible disclosure

Found a security issue? Tell us first.

Email support@mediasfu.com with “Security report” in the subject. Include what you found, the steps to reproduce it, and the URL, room or API call involved. We read every report and reply to the address you write from.

Please test only against your own account and rooms, don’t access other customers’ data, and don’t degrade the service for others. Give us a reasonable chance to fix an issue before you share it publicly.

Running a security review?

We’ll answer your questionnaire and walk your team through the data flow for your setup.