Built around your voice
Clear controls. Responsible voice workflows.
Understand Mayna account controls, responsible voice cloning and questions to discuss before deployment.
Protect your account and integrations
Use individual accounts and protect API credentials. Keep private keys and integration credentials out of client-side code and public workflow descriptions.
Recording and transcript controls
Enable recording and transcription only when appropriate for your use case. Inform participants and obtain any permissions your deployment requires. Review who can access exports and recordings.
Storage and retention
Production call recordings use Azure Blob storage in the current deployment. Retention requirements, regional hosting and deletion scope should be agreed with the team before rollout; this page does not promise a specific retention period or certification.
Voice cloning permission
Use voices only with authorization. Do not impersonate a person or present generated speech in a misleading way.
Report a concern
Contact security@mayna.ai for a security concern. Use the data deletion page for deletion requests and read the privacy policy for product data information.
Put your next voice workflow into practice
Explore the samples, read the docs or tell us what you want to build.