Effective June 17, 2026 - v2.3
This policy explains what MediaSFU collects, how it is processed, when it is retained, and what controls you have in your dashboard. Clear language, defined boundaries, and no ad-resale model.
We collect the information needed to run your account, rooms, dashboards, support requests, and paid services. We do not build advertising profiles or sell your personal data.
We use data to provide MediaSFU, secure accounts, process billing, support users, prevent abuse, and send service or account notices.
Need an export, correction, or deletion? Contact us and we will handle the request according to your account status, retention requirements, and applicable law.
Purchases, subscriptions, usage, invoices, and payment disputes require a small but important billing record so accounts remain accurate and support can resolve issues.
When you buy credits, start a subscription, add billing details, or request an invoice, we may keep billing contact details, plan history, transaction IDs, tax or business information, invoices, receipts, and account-level usage records.
Card and payment method details are handled by payment processors or app-store providers. MediaSFU does not need to store your full card number to operate the service.
We use billing records to complete purchases, detect abuse, resolve disputes, comply with tax/accounting obligations, and enforce plan or credit limits.
If you contact us about procurement, credits, subscriptions, refunds, invoices, or chargebacks, we keep enough context to respond and maintain a reliable account history.
Refund, credit, and subscription rules are explained in the Terms of Service. This privacy page explains the data we use to process and support those commercial workflows.
Here's what happens to the data you trust us with.
We use service providers only where needed to operate MediaSFU, process payments, secure the platform, host infrastructure, provide support, or deliver configured product workflows.
We only create a signed token from the name you send. No extra identifiers are stored with the call.
Login and session logs stick around just long enough to spot suspicious activity.
Live media never hits disk. Cloud recording is opt-in and expires within 72 hours on our side.
Messages are not saved for Chat, Webinar, or Conference room types. Message saving is supported only for Broadcast rooms when message history is explicitly enabled.
Updated June 17, 2026: how MediaSFU handles provider forwarding, telephony support logging, and deletion controls for AI-powered workflows.
When you enable MediaSFU Translation, Voice Agents, or Vision Agents, media and transcript streams are forwarded only through your configured pipeline providers (for example, speech-to-text, language models, and text-to-speech) to deliver the features you selected.
For phone calls and call-agent sessions, MediaSFU does not retain full call logs by default. Only limited critical summaries or operational events are stored when you explicitly enable telephonySupport (telephony support) or related logging controls.
This applies only to MediaSFU widgets. MediaSFU web agents use session logging by design so both client and support teams can follow live conversation flow and status updates. If this workflow does not fit your privacy requirements, do not enable web agent logging features. Logged items can be deleted directly from your dashboard.
MediaSFU does not log conversation content for custom AI agents you build with MediaSFU SDKs (including voice, vision, or multimodal agents), unless you explicitly enable your own logging features in your implementation.
Where logging is enabled (web agent sessions or optional phone-call logs), you can perform targeted deletion directly from your dashboard. If telephonySupport logging is not enabled, calls pass through MediaSFU without retained trace logs on our side.
When we adjust this page, we log the change, update the version badge, and summarize what matters in product updates.
We read every message. Reach out with anything else you need.