Local readiness inspection
The browser checks selected file size, dimensions, video duration, and batch totals before upload. This readiness check does not upload the selected media.
Privacy and consent guide
Check permission, retention, and sharing before you upload a face
Face swap safety depends on both the service and the intended use. Confirm who gave permission, what the provider retains, and what the finished file reveals before you generate or share it.
Before upload
Five questions decide whether the workflow should start
| Question | Proceed when | Stop or clarify when |
|---|---|---|
| Do you have permission? | Every real person understands the edit and intended audience | A public photo is your only basis for using the likeness |
| Could the result mislead someone? | The creative context is clear or the edit will be disclosed | It could be mistaken for evidence, endorsement, or a real event |
| Is the context sensitive? | The use is lawful, permitted, and does not exploit or harm the subject | It involves minors, sexual content, fraud, harassment, or deceptive impersonation |
| What happens to uploads? | Retention, deletion, training use, and providers are explained | The policy is vague or contradicts the product interface |
| What will the exported file reveal? | You have inspected watermarks and visible account information | You would not want that information shown to the intended audience |
Permission is specific. Consent to take or post a photo is not automatically consent to alter it, place it in a new context, or distribute the edited result.
Current DeepSwapAI controls
Separate the local check from the generation upload
Generation processing
When a task is submitted, the supplied media is sent to an AI inference provider only to complete that requested generation.
No model training on uploads
DeepSwapAI does not use uploaded content to train AI models.
24-hour media retention
Uploads and generated media are automatically removed from DeepSwapAI servers within 24 hours. Account, order, credit, security, and support records can be retained where needed for service operation, fraud prevention, accounting, disputes, or legal compliance.
Account deletion
A signed-in user can permanently delete the account from account settings. Privacy requests can also be submitted through the official support channels.
Policy evidence
Read the current Privacy Policy, Terms of Service, and Trust Center before relying on these controls.
Requests and reports
Use the channel that matches the issue
Access, correction, or deletion
Use account settings or the privacy request channel listed on the official contact page.
Non-consensual or harmful content
Report the exact URL, describe why the subject did not consent or how the content violates the Terms, and avoid sending private source media unless support requests it.
Copyright concern
Identify the protected work, the disputed material, and the exact location where it appears.
Security concern
Provide reproducible steps and a safe proof of concept without accessing, changing, or retaining another user's data.
How this guide was made
Checked against product code, policy, and retention operations
The DeepSwapAI Product Team reviewed the current media-readiness client, generation flow, 24-hour cleanup job, account-deletion endpoint, watermark entitlement behavior, Privacy Policy, Terms, Trust Center, and support routes. Claims were reviewed on July 13, 2026; see the verification methodology.
Verify the current controls before uploading
Review retention, training use, account deletion, consent rules, and the exact trial watermark disclosure in one place.