Data controls
Request a workspace or likeness-data review.
During controlled beta, deletion requests are handled by the workspace team so we can confirm the account, scope, and downstream artifacts before action.
What to include
Provide the account email, the relevant creator or private identity name, the request type (access, correction, removal, or account closure), and a concise description of the affected workspace data.
Likeness withdrawal
If a real creator withdraws permission, pause new generation and distribution first. Then request review of the identity, references, model weights, queued work, and stored exports connected to that permission.
Scope review
We will confirm that the requester is authorized and identify relevant account-scoped records. Some operational, security, or legally required records may need limited retention.
Your own copies
Account-owned compute, local machines, RunPod volumes, and third-party services can retain independent copies. Review and remove those materials directly as part of a complete deletion process.
Do not include passwords, API keys, payment details, private media, or highly sensitive information in an initial request. Confirm the request from the account email instead.