Security and data handling

Deployment models

Self-hosted. The full pipeline runs as a Docker stack on hardware you control. We have no access to your data, and no runtime component of ours sits in the rendering path.

Managed cloud. We operate the GPU and storage. Your decks and presenter footage are stored on our infrastructure, encrypted, and deleted on the schedule below.

Both models run the same pipeline, so you can move between them without re-authoring content.

Data residency

On managed cloud you select a region at onboarding. On self-hosted deployments residency is wherever you run the stack, including air-gapped networks. Two stages are optional cloud calls: script drafting and narration. Both are configured by you, and both can be pointed at models you host yourself. The presenter footage, which is the biometric part, and all lip-sync rendering stay on your hardware and never leave your network.

Encryption

• TLS 1.2 or above for all traffic to and from the service.
• Encryption at rest for uploaded decks, presenter footage and rendered video.
• Signed, short-lived URLs for video download; no public object access.

Access control

Access to rendering infrastructure is role-scoped and individually authenticated. Production access requires multi-factor authentication, is granted on a least-privilege basis, and is logged. Support access to customer content is break-glass only and recorded.

On self-hosted deployments access control is entirely yours — including who may use a cloned voice.

Retention and deletion

• Rendered videos: 90 days in managed cloud, then deleted.
• Source decks and presenter footage: deleted within 30 days of account closure.
• Presenter registration can be deleted at any time, which also deletes undownloaded output.
• Operational logs: 30 days.

See the Privacy policy for the full schedule.

Incident response

We maintain a documented incident response process. Where a breach affects your personal data, we notify affected customers within 72 hours of confirmation and provide the information your own regulator notification requires.

On self-hosted deployments you operate the pipeline, so detection and response inside your network is your process; we support with patches and advisories.

What we never do

• Use your content to train models for other customers.
• Sell or share personal data with advertisers.
• Offer voice cloning on the public cloud tier, where consent cannot be adequately verified.
• Render output using a presenter registered without a consent declaration.