Controlled beta support
Get unstuck without exposing your private materials.
Use this support checklist during beta. It keeps diagnosis focused while protecting account credentials and creator media.
For sign-in or account issues
Share the page address, the time the issue occurred, and any visible error digest. Do not send a password, authentication code, or browser session cookie.
For render or training issues
Share the job ID, selected creator, visible error message, and compute provider. Do not paste RunPod keys, tunnel tokens, or private storage URLs into a support message.
For private media issues
Describe the affected identity or asset name and whether the issue is upload, preview, download, or export. Keep original reference photos out of the initial message unless secure transfer is arranged.
For consent or deletion requests
Use the data-control workflow and include the account email and affected identity name. Ask for a pause of future generation if you need urgent likeness review.
Before broad public launch, configure a monitored support mailbox and a support-response process. For now, use the contact channel provided with your beta invitation and include only the information below.