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. Build a local pre-publication record, confirm who gave permission, and inspect what the provider retains and 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.
Five-step review
Make the publication decision traceable
- Define the exact use. Record the people, intended context, audience, destination, duration, and approval owner for this specific project.
- Confirm permission and media rights. Verify permission for every altered likeness and the right to use and modify every source and target asset.
- Review sensitive context and the finished export. Pause unresolved sensitive uses and inspect the final identity, context, trial watermark, and visible account information.
- Document the disclosure decision. Check current destination-platform rules and keep disclosure close to realistic media when viewers could be misled.
- Export a record and complete human review. Download the local checklist record, retain supporting permission separately, and have the named owner make the final publication decision.
A checklist records a decision; it does not create the underlying right. Keep signed permission, asset licenses, client approvals, and any qualified advice outside this browser tool.
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.
Disclosure decision
Match the review depth to the audience and context
| Destination | Minimum documented decision | Escalate when |
|---|---|---|
| Private draft | Permission and asset rights still apply; record who can access the file | The draft could leave the intended group or contains sensitive material |
| Internal or client review | Name the approval owner, permitted reviewers, and deletion path | The client cannot confirm likeness or source-media rights |
| Organic public post | Review whether a viewer could mistake the edit for a real appearance, event, statement, or endorsement | The destination rule, permission scope, or disclosure placement is unclear |
| Paid ad or endorsement | Confirm the approved claim, channel, territory, duration, paid placement, and final-result approval | Any likeness, advertising, contractual, or platform requirement is unresolved |
| Sensitive or high-impact context | Pause and obtain qualified review before generation or publication | The edit touches minors, intimacy, fraud, politics, health, finance, crime, harassment, or identity verification |
Disclosure is not a substitute for permission. A visible label can help a viewer understand that media was altered, but it does not authorize the likeness, source asset, message, or distribution.
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.
Official sources and evidence boundary
Use a source for the question it actually answers
- EU Artificial Intelligence Act summary - describes provider marking and deployer disclosure duties for certain AI-generated and deepfake content. Roles, exceptions, application dates, and other laws still matter.
- TAKE IT DOWN Act, Public Law 119-12 - addresses specified nonconsensual intimate depictions and digital forgeries in the United States; it is not a general likeness-release rule for every face swap.
- YouTube altered or synthetic content disclosure guidance - requires creator disclosure for realistic content that meaningfully changes what a real person appears to say or do, among other listed cases. Other destinations have their own current rules.
- C2PA Content Credentials Explainer 2.4 - explains tamper-evident provenance and explicitly warns that provenance alone cannot establish whether content is true, accurate, or factual.
- DeepSwapAI Privacy Policy, Terms, and Trust Center - current product-specific retention, training-use, account, and acceptable-use statements.
Do not turn one rule into a global answer. Laws, platform policies, contracts, likeness rights, copyright, and advertising requirements can apply at the same time and change by location and use.
Consent and disclosure questions
What the checklist can and cannot establish
Does a public social media photo give permission for a face swap?
No. Public visibility does not by itself establish permission to alter a likeness, change its context, or distribute the edited result.
Does completing this checklist prove legal consent?
No. The checklist is a planning and review record, not a release, signature, identity verification, legal opinion, or proof that permission was valid.
When should a realistic face swap be disclosed?
Document a disclosure decision whenever viewers could reasonably mistake the result for a real appearance, statement, event, or endorsement, and check the current rules for the destination and jurisdiction.
Do Content Credentials prove that a face swap is true or consented?
No. C2PA Content Credentials can provide tamper-evident provenance assertions, but the C2PA specification says provenance alone does not establish whether content is true, accurate, factual, or properly consented.
Does the consent planner upload or save my entries?
No. It has no media input, account request, network request, analytics event, or server save. Entries remain in the current browser tab unless you download a local JSON or CSV record.
How this guide was made
Checked against product code, policy, retention operations, and primary sources
The DeepSwapAI Product Team reviewed the current media-readiness client, generation flow, 24-hour cleanup job, account-deletion endpoint, complete-email watermark entitlement behavior, Privacy Policy, Terms, Trust Center, support routes, local planner code, and the official sources listed above. The planner was designed as a local decision record with explicit evidence limits, not a release or automated legal decision. Product controls and public guidance were reviewed on July 22, 2026; see the verification methodology.
Finish the rights review before uploading
Use one permitted photo for the smallest representative test only after the permission, source-media, sensitive-use, export, and disclosure decisions are complete.