Security

1. Encryption in Transit and at Rest

All data sent to and from AIDubWorld, including video uploads and dubbed exports, is encrypted using TLS 1.2 or higher. Uploaded media, transcripts, cloned voice models, and backups are encrypted at rest using industry-standard algorithms.

2. Voice Model & Biometric Data Protection

Cloned voice models are among the most sensitive data AIDubWorld handles. Each customer's voice models are logically isolated from other accounts, encrypted at rest, and are never used to train models shared across other customers. Access to raw voice samples and voice models is restricted to the systems and personnel that need it to operate the dubbing pipeline.

3. Access Controls

We use role-based permissions to restrict internal access to customer data on a need-to-know basis. Access to production systems is logged, and elevated permissions require additional approval.

4. Secure Infrastructure

AIDubWorld runs on established cloud infrastructure providers that maintain physical security, network protections, and redundancy for the underlying hardware. We layer our own application-level security controls on top of that foundation.

5. Monitoring and Logging

We monitor production systems for unusual activity and maintain audit logs to support incident detection, investigation, and response.

6. Vendor Due Diligence

Payments are handled by Stripe, a PCI DSS Level 1 certified payment processor. We do not store full card numbers on our servers. Sub-processors that support our infrastructure and analytics are reviewed for their security and data-handling practices before integration.

7. Data Isolation Between Customers

Customer Content, transcripts, and voice models are logically separated by account. Access controls and application-layer checks are designed to prevent one customer's data, including cloned voices, from being visible to another customer.

8. Regular Security Reviews

We periodically review our security practices, dependencies, and configurations, and aim to deploy relevant patches in a timely manner.

9. Incident Response

In the event of a security incident affecting your data, we aim to investigate promptly, take steps to contain and remediate the issue, and notify affected customers in accordance with applicable law.

10. Reporting a Vulnerability

If you believe you've found a security vulnerability in AIDubWorld, please report it to us privately at security@aidubworld.com before any public disclosure. Include enough detail for us to reproduce the issue, and we'll acknowledge your report and follow up on next steps.

11. Your Responsibilities

Security is shared. AIDubWorld signs you in with one-time email links instead of passwords, so keep your email account secure, restrict workspace access to people who need it, and apply the same principle of least privilege to your own team's permissions. See our Privacy Policy for details on how we handle personal information.

For questions about our compliance posture, reach out through our contact page.