Charme Dance AI Privacy and Consent: Before You Upload a Photo

Before using Charme Dance AI with a personal photo, decide whose image it is, what the person agreed to and where the finished clip will go. Those questions matter even when the idea is a harmless-looking dance.

This studio supports one consenting adult photo or a text description of a fictional adult. It does not accept celebrities, public figures or children as photo subjects. The output is newly generated footage, so it should not be presented as evidence that the person actually danced at a real event.

Ask about the use, not only the photo

An adult might be comfortable with a portrait in a private chat but uncomfortable with a realistic generated video on a public account. Ask about both the transformation and the audience.

Explain the planned scene in ordinary language: a short synthetic dance, the intended mood and where you want to share it. If the idea changes substantially, check again. A surprise public post is not a good way to discover that you misunderstood permission.

Do not assume that a publicly accessible photograph is available for this use. A social profile, search result or news image does not establish the subject's agreement or your rights to the image.

Choose the least personal input that serves the idea

If the joke does not need a real person's likeness, text mode can create a fictional adult. That avoids uploading a personal portrait and may be a better fit for an imagined character.

If recognition is important, use a clear photograph of yourself or an adult who has agreed. Avoid including unrelated people, private documents, addresses or other unnecessary details in the background.

A useful input shows the face, hair and outfit. It does not need to reveal where the person lives or works. The photo guide explains practical framing choices without asking you to expose more information than the scene needs.

Understand what generation sends onward

Generating a video requires processing the submitted text or image through the configured service providers. Content checks are part of that workflow. Do not assume that a browser upload remains only on your own device after you submit a generation request.

Read the current Privacy Policy for the service's data practices. Do not rely on a competitor's promise or a generic phrase such as “AI is private.” Different products can use different infrastructure and retention rules.

The site should describe its actual behavior rather than invent a twenty-four-hour deletion promise. If a particular retention requirement is essential to your use, establish it before uploading.

Review result visibility deliberately

The studio offers a visibility choice for the generated result. Public visibility permits consideration for a curated public gallery. Private visibility keeps the result out of that public selection flow.

This choice is not the same as publishing the original uploaded image. A source photo and a generated result are different assets. Do not assume that choosing public visibility also sends your video to TikTok or another social platform.

Discuss the choice with the adult subject. If the agreed audience is a private group chat, select the private option and keep your later sharing consistent with that agreement.

Use email access carefully

The site uses email one-time codes rather than an account password. Keep access to the mailbox you choose, because it is how you return to your account and videos.

Do not share a login code with somebody claiming to be support. A code is for signing in, not for proving an order in a chat. Support can investigate using an order or job identifier without asking for your current code.

If the email delivery channel is unavailable, the site should show an explicit error rather than pretend a message was sent. Repeatedly requesting codes is not a useful workaround for a known delivery failure.

Keep payment and generation records separate from sensitive data

A job identifier helps locate a video task. An order identifier helps locate a purchase. Those references are usually more useful to support than sending a complete screenshot containing personal account information.

Never send full card numbers, security codes or a password in a support email. If a screenshot is necessary, remove unrelated personal details first.

A failed task returns the credits it consumed. A payment refund is a separate process. See the refund policy for the current request route, and describe the actual problem rather than assuming every failed task has reversed a charge.

Review the output with the subject

A generated person may have altered expressions, clothing details or body movement. Even a technically successful result can represent someone in a way they do not like.

If you used another adult's photo, show them the whole video before sharing it more widely. Include the sound. A strange spoken phrase or an unexpected musical mood can change the meaning of the clip.

Do not use the output to suggest an endorsement, relationship, attendance or behavior that did not occur. Clear AI labeling is especially useful when the clip resembles a handheld phone recording.

Publish with enough context

A realistic synthetic dance can travel beyond the original caption. Use the destination platform's AI disclosure tools and plain-language context where appropriate.

TikTok explains its labeling approach in its official AI-generated content guidance. Check the current rules for the destination you actually use.

A label is not a substitute for consent, and consent is not a substitute for music permission. Treat the person's likeness, the image rights, the soundtrack and the platform's requirements as separate questions.

An illustrative permission conversation

Imagine you want to make a birthday clip featuring an adult friend. Explain that it will be generated from their photo, not filmed footage. Ask which photo they prefer and whether they want the result kept within the group chat.

Prepare a simple scene and select private visibility. After generation, send the complete clip to the friend for their own decision about sharing. If they dislike it, respect that choice instead of arguing that the software already charged for the request.

This is a hypothetical planning example, not a customer testimonial. It shows how a small amount of clarity can prevent a much more awkward conversation afterward.

Download and retain responsibly

If you want to keep a result, download it and store it somewhere you control. The generation service is not your only backup plan.

If you later want an uploaded asset or result removed, contact the service through the published support route and identify the relevant account and job. Do not post a private file publicly just to explain a deletion request.

Avoid promising another person a retention period that the service has not documented. If your project has a strict data requirement, confirm that the actual service can meet it before uploading.

Frequently asked questions

Can I use a stranger's publicly posted photo?

No. This workflow requires an appropriate permitted adult image. Public availability is not consent.

Does public visibility publish my original photo?

The visibility choice concerns the generated result and its eligibility for a curated gallery. It is not permission to publish the source image.

Can I make a fictional adult instead?

Yes. Choose Text to video and describe an original adult character. Avoid using a real person's name as a shortcut to their likeness.

Is there a password to create?

No. Email sign-in uses a one-time code. Keep the mailbox secure and do not share the code.

How do I begin safely?

Agree on the subject, scene and audience, read the current privacy information, and use the studio below to prepare the input. Check visibility and the thirty-credit default generation cost before submitting.