Skip to main content
A cloned voice is built from real speech recordings of a real person. Before you use one — your own, an employee’s, or anyone else’s — you need that person’s clear consent. This page explains why, and gives you a practical checklist.
This page explains the general legal landscape around voice cloning in the EU. It is not legal advice. Talk to your own counsel about your specific situation, especially before cloning anyone’s voice for commercial use.
A voice identifies a person almost as reliably as a fingerprint, and the law treats it accordingly:
  • It’s personal data. Under the GDPR, a voice recording used to identify someone is biometric data — a special category under Article 9 that may not be processed without a clear legal basis, and in practice that basis is the person’s explicit consent.
  • It’s protected by personality rights. In the EU and most other jurisdictions, a person has the right to decide whether their voice is recorded, published, or imitated. Cloning someone’s voice without permission can expose you to injunctions and damages, independent of GDPR.
  • Performers have their own rights. If the voice belongs to a professional speaker, actor, or voice performer, their recordings are typically also covered by neighboring/performers’ rights — separate from the personality-rights protection above, and usually running for decades after the recording is made.
  • Copyright doesn’t apply to the voice itself. Copyright protects a specific recording or performance, not the sound of a voice in the abstract — so it’s not a substitute for consent, and it doesn’t give you permission to clone a voice just because you own a recording of it.
Consent that will hold up needs to be:
Extra care applies when the voice belongs to a minor — consent must come from a parent or legal guardian.

​
Labelling AI-generated audio

Since August 2026, the EU AI Act requires that AI-generated or manipulated audio realistic enough to be mistaken for a real recording of a person — a “deepfake” — is disclosed as artificially generated. In practice, that means telling your customers or audience when they are hearing a cloned voice rather than the person themselves. Two narrow cases soften this: in evidently artistic, creative, satirical, or fictional work the disclosure only has to exist in a way that doesn’t spoil the piece, and the duty doesn’t apply where the use is authorised by law to detect, prevent, investigate, or prosecute criminal offences.
1

Get consent before you clone

Have the voice owner (or their guardian, for a minor) agree in writing to the specific purpose, product, and duration of use — before you create the clone, not after.
2

Document and store it safely

Keep the signed consent somewhere durable and access-controlled. You may need to produce it later.
3

Limit the purpose

Use the clone only for what was agreed. A new use case — a new product, a new market, a public campaign — needs its own consent.
4

Make withdrawal easy

Give the person a clear way to withdraw consent, and have a process ready to delete or deactivate the cloned voice when they do.
5

Label the output where required

If the audience could mistake the cloned voice for the real person, disclose that it’s AI-generated.
Need a consent form or usage agreement template? Contact support — we don’t publish sample contracts in these docs, since the right wording depends on your jurisdiction and use case, but our team can point you to a starting template.

​
Where cloned voices are used in Famulor

Once you have consent, open the assistant’s Voice tab, go to the voice library, and select Clone a voice. Upload or record a clean sample; the finished voice then appears under Cloned voices — private to your workspace, never shared with anyone else — and can be picked like any other library voice. Voice cloning is a plan feature. Open Clone a voice directly; the creation button shows Create · free while your allowance remains, then Create + X credits. The charge is made once for a successful creation. Stored voices have no plan capacity limit or recurring storage charge. The standard plans include a one-time allowance per workspace: Prepaid 0, Plus 1, Pro 3, Agency 5 free creations. An upgrade increases the total allowance; renewals, plan changes and deleting voices never reset the number already used. Whitelabel plans may define their own allowance. Voice Cloning and Extra Cloned Voice Slots are no longer offered as new add-on purchases. Existing purchase records remain available. Calls using a cloned voice consume the normal usage credits. To delete a cloned voice, open the voice library and select the trash icon next to its heart. Enter the exact voice name and confirm that deletion is permanent. The voice is removed from speech generation and its saved previews are cleaned up. The dialog waits for the deletion result; remove any assistant or test assignments first.

​
API and MCP lifecycle

Voice cloning is an asynchronous, workspace-scoped workflow. Use the following sequence with a user-bound credential:
1

Check availability

Call GET /api/v1/voices/clone/capability before collecting audio. It returns availability, sample constraints, the lifetime free allowance and the current creation price in credits.
2

Prepare and upload samples

Check GET /api/v1/voices/clone/capability for sample_constraints — max_files (the number of audio files currently accepted), max_bytes_per_file (the maximum size, in bytes, of each sample), and max_duration_seconds (the maximum length of each sample in seconds, or null when no duration limit applies). All three can change over time, so don’t hardcode them. Send metadata for that many files to POST /api/v1/voices/clone/uploads. The response contains an opaque job id and one short-lived upload destination per file. For each destination, use PUT with multipart FormData: append cacheControl with 3600, append the audio Blob in an unnamed file field, and send x-upsert: false. Do not log or share these short-lived URLs.
3

Submit with consent

Call POST /api/v1/voices/clone with the returned id, a display name, an optional language, and consent: true. The documented job_id field is a temporary alias for id; if both are supplied, they must match.
4

Poll and manage

Poll GET /api/v1/voices/clone/jobs/{jobId} until the job is ready or terminal. List ready clones with GET /api/v1/voices/clone, retrieve one with GET /api/v1/voices/clone/{cloneId}, and remove one with DELETE /api/v1/voices/clone/{cloneId}. A clone assigned to an assistant must be removed there first.
The six MCP equivalents are get_voice_clone_capability, create_voice_clone_upload, submit_voice_clone, get_voice_clone_job, list_voice_clones, and delete_voice_clone. Public responses contain only opaque platform IDs and customer-facing status data.
The legacy clone_voice MCP tool is available only through 2026-09-30. It requires consent: true and accepts at most 700 KiB of decoded audio across all samples. New integrations should use the six lifecycle tools above.
Send expected_credits with POST /api/v1/voices/clone or submit_voice_clone, using the displayed pricing.next_creation_credits from the capability response. Set it to 0 to accept only a free creation. If the price increases or the last free creation is used elsewhere, refresh the price and confirm again. Retry the same job ID after an interrupted request; a successful job is charged only once. The legacy clone_voice tool also requires expected_credits.