Voice is the most personal asset you have.

1 · Who can be cloned

• Yourself, for any purpose.
• People on your team who have signed a written voice-license agreement with you.
• Talent you have hired with explicit, written voice-use rights.
• Voices already in the public domain (e.g. LibriVox recordings, government-released audio).

We will not help you clone:

• Celebrities, public figures, or public-domain personalities without their explicit written permission.
• Friends, family members, or coworkers who haven't signed off in writing.
• Voices scraped from YouTube, TikTok, podcasts, or interviews without the speaker's permission.
• Anyone living or deceased for the purpose of misrepresenting them, defrauding their family, or impersonating them in any communication.

2 · How training data is handled

The active Bloom Voice pilot path runs on the hardware agreed for the engagement. Any support transfer or hosted integration must be documented before it is used.

• Training audio stays on the agreed local machine unless you explicitly approve a documented support transfer.
• Generated audio stays on your machine. We do not maintain a copy.
• Voice profiles are local files. Move them, back them up, or delete them — same as any other file in your project.
• The recorder on bloom-voice.pages.dev stays in your browser and does not upload the recording.

3 · Commercial use

Commercial use is governed by the rights you hold for the source voice and the scope recorded for your Bloom Voice pilot:

• The licensing of any output audio is your responsibility. If you’re cloning a hired voice actor, make sure your contract with them covers commercial use of synthetic audio.
• Any source-code license or handoff rights must be written into the engagement. They are not implied by the public website.
• Internal tools, client products, customer-facing apps, and audiobooks are reviewed against the recorded voice rights and agreed scope before launch.

4 · Required consent flow

Before a new voice profile is trained, the pilot records which of these consent paths applies:

• This is my own voice.
• I have written permission from the speaker, attached or referenced.
• This recording is in the public domain.

If you need a different flow for enterprise compliance, contact us before any profile is created.

5 · Reporting violations

If you believe a Bloom Voice user has cloned a voice without consent, email support@thaliabloom.com with as much context as you can share. We can’t revoke already-distributed code, but we can refuse future sales, disconnect support, and document the case publicly when appropriate.

6 · What we will never do

• Add hidden phone-home telemetry to the local voice workflow.
• Add a license-check that calls our servers.
• Add an automatic update path that lets us change behavior on your machine.
• Sell your audio, your voice profiles, or your generated output to anyone.
• Train our own model on customer audio.