1. What Bavio supports
This document is a draft for founder and legal review. It is not legal advice and does not create a commitment until approved and published.
The repository contains recording, media, transcript, and cleanup paths, but not one universal recording behavior for every provider or call. Recording may be enabled, disabled, temporary, or provider-controlled.
2. Applicable law
Recording and transcription rules vary by jurisdiction and context. Some locations require notice or consent from one participant; others require notice or consent from all relevant participants. Customers must obtain advice for their calling footprint.
3. Notice and AI disclosure
Customers should announce recording or transcription where required, identify AI participation where required, and keep notice understandable and timely.
4. Consent and opt-out
Customers must implement the required consent, refusal, pause, opt-out, and human handoff behavior for their use. Bavio does not automatically make a call lawful.
5. Provider behavior
Twilio and other configured providers may determine media callbacks, recording objects, identifiers, and storage paths. Provider behavior and location must be confirmed for each deployment.
6. Retention and deletion
Retention varies by data type and configuration. The repository shows targeted TTS cleanup, not a universal recording deletion schedule. Distinguish database rows, storage objects, backups, logs, and provider copies.
7. Access and security
Limit Workspace access, protect provider credentials, and review who can view recordings and transcripts. Observed tenant checks and selected RLS protections do not replace customer access governance.
8. Sensitive information
Avoid collecting information that is not needed. Configure prompts and handoffs to limit sensitive data and escalate uncertain or high-risk requests.
9. Contact
Privacy requests: [PRIVACY_EMAIL]. Legal review: [LEGAL_EMAIL]. Support: hello@bavio.in.