BabelCast is private by default.
We designed BabelCast so the sensitive parts (your audio, your transcripts, your audience) stay yours. Here’s how.
Data handling
By default, BabelCast processes sessions live without retaining session audio or transcripts. Short-lived operational logs exist only to run and secure the service.
Account-less listeners
Listeners join with a code and an optional PIN. No account, no personal data required to tune in.
Scoped access tokens
Access is granted through short-lived, capability-scoped tokens: the minimum needed to join or host, and no more.
Access control
Org roles, host PINs, and capability-based authorization keep hosting and management in the right hands.
Organization data separation
Organization data is separated by row-level access controls in our database. We run on reputable cloud providers and keep vendor specifics off the public page by design; subprocessors are listed on request.
Voice cloning, when it ships
Voice cloning is not available yet. When it ships, it will require the speaker’s explicit consent, and we will treat voice data as sensitive.
Compliance posture
We support language-access requirements such as Title VI for schools and public bodies, and we build toward the controls education and enterprise buyers expect. We hold no formal certifications yet. Where certification is still in progress, we say so plainly rather than overclaim.
Questions, answered.
Security questions or a DPA?
Our team is happy to walk through data handling, sign a DPA, or answer a vendor questionnaire.