Voice Cloning Policy

Voice cloning overview

Voice cloning and synthetic speech can be useful for accessibility, prototyping, and creative production, but they also create impersonation and consent risks. This policy sets boundaries for lawful, authorized, and non-deceptive use.

Availability and future feature language

Voice cloning is not available unless Ethen explicitly enables it in the product. A policy page can prepare the rules for future use, but it must not imply that a cloning model, voice marketplace, public voice library, or cloning workflow is live. If voice cloning is introduced, the product should show clear status labels, consent requirements, scope limits, and disclosure expectations before any user can create or use a synthetic voice.

Consent requirements

A user may not clone a voice unless they have clear rights and explicit permission from the person whose voice is being cloned. Consent should be specific, informed, and limited by purpose. It should cover who owns or controls the voice, what the synthetic voice may be used for, which providers may process it, whether commercial use is allowed, whether team members can access it, and how consent can be revoked. A broad informal statement is not enough for risky use.

No impersonation or deception

Voice cloning must not be used to impersonate someone, trick a listener, bypass identity checks, create false evidence, or imply endorsement by a person who did not approve the message. Synthetic speech should not be presented as a live call, private voicemail, executive instruction, customer authorization, employee statement, political message, legal instruction, medical instruction, or emergency communication from a real person unless the context is truthful and authorized.

Prohibited misuse

Ethen may not be used for voice cloning connected to fraud, phishing, account takeover, scams, harassment, threats, coercion, workplace abuse, sexual content, non-consensual intimate content, exploitation, stalking, blackmail, political manipulation, voter suppression, fake endorsements, fake customer support, or deceptive fundraising. These restrictions apply even if the generated audio is realistic, funny, internal, experimental, or later deleted.

Minors and public figures

Do not clone the voice of a minor. Do not clone or imitate a public figure, politician, candidate, journalist, celebrity, executive, public official, teacher, medical professional, or other recognizable person in a way that could mislead an audience or create unauthorized endorsement. Parody, education, commentary, accessibility, and creative use can still create real harm when voice identity is involved, so public figure and minor uses require especially strict limits.

Disclosure requirements

Synthetic voice content should be disclosed when a reasonable listener could believe the person actually spoke the audio. Disclosure should be close to the content, understandable to the audience, and maintained when the content is exported, published, embedded, or shared. Internal team labels are not enough if the audio leaves the workspace. If the disclosure would ruin the intended effect, that is usually a sign the use may be deceptive.

Team and admin responsibilities

Teams using any future cloning feature should maintain consent records, limit access to approved users, define allowed use cases, review generated scripts, remove revoked voices, and investigate misuse. Admin controls should not be treated as proof of consent. The person or organization using the feature remains responsible for ensuring that voice rights, workplace rules, union or talent agreements, platform policies, and applicable law permit the use.

Enforcement, reporting, and revocation

Ethen may restrict, suspend, remove, or disable synthetic voice content, voice profiles, projects, or accounts when misuse is suspected or when consent is disputed. Reporting paths should be published before broad availability. Revocation should stop future use where technically possible, but it may not remove every prior export, backup, audit record, provider record, or copy already shared outside Ethen. Final handling should align with the Privacy Policy and Data Retention Policy.

Enterprise brand and employee voice use

Enterprises should obtain documented authorization before cloning employee, executive, or customer voices. Brand voice programs should include review for deceptive use risks and takedown procedures. Do not use cloned executive voices for payment approvals or security verification. Voice is not a strong authenticator for privileged actions. Keep an inventory of approved voice assets and owners.

• Document authorization for enterprise voice assets.
• Do not use clones for privileged authentication.
• Inventory approved voice assets.

Enforcement and reporting

Violations of this policy may lead to content removal, feature suspension, or account action under the Acceptable Use Policy and Terms. Report suspected non-consensual cloning or deceptive impersonation through published support channels. Upcube may preserve relevant records for investigation where required. Third-party platforms may impose additional takedown rules for synthetic media.

• Misuse can lead to enforcement actions.
• Report non-consensual cloning.
• Third-party platform rules may also apply.

Current cloning status

Repo code includes a consent gate for cloning records and states that no actual cloning calls are made. This policy therefore speaks in future-availability terms and does not imply that cloning is live.

• Not available unless enabled: Voice cloning is not available unless the product explicitly enables it.
• Consent gate only: Existing consent records are user-declared and not independently verified by the platform.
• No impersonation: Synthetic voice may not be used to mislead people about who is speaking.
• No minors or public figures: Minor voice cloning and public figure impersonation are not allowed under this policy.

Policy status

This policy is future-ready, but it does not mean voice cloning is live.

• Not enabled by default: Voice cloning is unavailable unless explicitly enabled in the product.
• Strict consent boundary: No cloning without clear rights, consent, and disclosure.

Not legal advice

These pages are product and policy information for public review. They are not legal advice and should be finalized through qualified legal review before they are treated as binding legal terms.

Proof boundary

This policy does not claim voice cloning availability, verified identity checks, biometric guarantees, provider retention guarantees, or final enforcement process.

Allowed path, if cloning is ever enabled

Any future cloning flow must start with rights, consent, scope, and disclosure.

• Confirm rights
• Capture explicit consent
• Disclose synthetic speech
• Report misuse

Frequently asked questions