# EchoEnvo Privacy Policy

Version 2026-11-05 · Draft, not yet in effect

This policy explains what personal data EchoEnvo collects, why, who receives
it, how long we keep it, and your rights. Voice data gets its own section
(section 5), because a voice can identify a person.

## 1. Who we are

The controller of your personal data is **Thrones AI Limited**, company
number 17183864, 128 City Road, London EC1V 2NX, United Kingdom ("EchoEnvo",
"we"). Contact: **privacy@echoenvo.com**.

Our representative in the European Union under Article 27 GDPR is
**{{EU_REPRESENTATIVE}}**.

If you use EchoEnvo for a business and upload videos of other people, you are
usually the controller of their data and we process it for you under our
[Data Processing Addendum](/legal/dpa.md). For the purposes in section 3 marked
*(our purposes)* — security, abuse prevention, billing and the protected
voices list — we are the controller.

## 2. What we collect

| Category | Examples | Source |
|---|---|---|
| Account | email address, name if you give it, organisation, sign-in and passkey records | you |
| Payment | billing name and country, card brand and last 4 digits, invoices; full card details stay with Stripe | you, Stripe |
| Content | videos and audio you upload, their transcripts and translations, dubbed results | you |
| Voices | voices heard in your videos; voice samples taken from them for a voice clone; the clone model | your content |
| Voice templates | a numeric representation of a voice used to check it against the protected voices list (section 5) | your content, people who ask for protection |
| Records | your confirmations and consents, the text version you agreed to, what was delivered to whom, abuse reports | you, us |
| Technical | IP address, approximate country (from Cloudflare), browser, error and security logs | your device |
| Communications | emails with support, reports you send us | you |

We do not use advertising trackers or analytics cookies in the app.

## 3. Why we use it and our legal basis

| Purpose | Legal basis (UK GDPR / EU GDPR) |
|---|---|
| Providing EchoEnvo: transcription, translation, synthesis, editing, delivery | performance of our contract with you (Art 6(1)(b)) |
| Creating and using a clone of **your own** voice | contract, and your explicit consent for voice data (Art 9(2)(a)) |
| Cloning **another person's** voice for you | that person's consent, which you obtain and confirm (section 5.3) |
| Checking a new clone against the protected voices list *(our purposes)* | your explicit consent (Art 9(2)(a)) |
| Keeping the protected voices list *(our purposes)* | the explicit consent of each person on the list |
| Text and voice checks against misuse *(our purposes)* | legitimate interests in preventing fraud, impersonation and harm (Art 6(1)(f)) |
| Keeping records of consents, confirmations and deliveries; handling abuse reports *(our purposes)* | legitimate interests and establishing or defending legal claims (Art 6(1)(f), Art 9(2)(f)) |
| Billing, tax, preventing payment fraud *(our purposes)* | contract and legal obligation (Art 6(1)(b), (c)) |
| Blocking access from mainland China *(our purposes)* | legitimate interests and legal obligation |
| Service emails (dub ready, files about to be deleted, receipts) | contract |
| Security and keeping the service running *(our purposes)* | legitimate interests |

You can object to processing based on legitimate interests (section 9).

**We do not use your content, results or voice to train machine-learning
models.** See section 6 for what our providers may do.

## 4. Automated decisions

Two checks run automatically and can stop an action:

- **text check**: a language model reads the transcript and edited lines and
  stops a dub before charging if the text is political campaigning or clearly
  harmful;
- **voice check**: when you create a voice clone, we compare the sample with
  the protected voices list and stop the clone if it is too similar.

These checks do not have legal effects on you beyond refusing that action.
You can always ask a person to review a decision at support@echoenvo.com.

## 5. Voice data

5.1 **Your voice clone.** When you create a clone of your own voice, we take 20
to 60 seconds of speech from your video and send it to Fish Audio, which
creates a voice model used only for your projects. The clone stays until you
delete it or withdraw your consent; then we delete the model at Fish Audio. A
clone is also deleted automatically when its consent period ends (3 years
after it was created) or if it is not used for 3 years.

5.2 **The protected voices check.** Before creating a clone, we compute a voice
template from the sample — a list of numbers describing the voice — and compare
it with the templates on our protected voices list. **The template of your
sample is not stored**: it is discarded as soon as the comparison is done. If
it matches, we record which list entry matched and how closely, so that a
person can review the refusal.

5.3 **The protected voices list** contains templates only of people who asked
us to protect their voice (or their authorised representatives). We do not
build templates of public figures from public recordings without their
consent. A person can ask to be removed from the list at any time, and we
then delete their template.

5.4 **Other people's voices.** If you clone someone else's voice, you must have
their explicit consent before you start (see [Voice Consent](/legal/voice-consent.md)).
We keep a record of your confirmation and may ask to see the consent. A person
whose voice was cloned can ask us to delete the clone at
echoenvo.com/report.

5.5 **Biometric data retention and destruction policy** (including for
Illinois BIPA and Colorado):

| Data | Destroyed |
|---|---|
| voice template of a clone sample | immediately after the check |
| voice clone model | when you delete it or withdraw consent, when its consent period ends (3 years after creation), or 3 years after its last use, whichever is first |
| protected voices list template | when the person asks, or when the purpose ends |
| record of a matching check (list entry and score; no template) | with other consent records (section 8) |

We do not sell, lease, trade or otherwise profit from voice data or voice
templates.

## 6. Who receives your data

We share personal data only with the providers that run EchoEnvo for us,
listed with their purpose and location in our
[Sub-processor List](/legal/subprocessors.md): OpenAI (transcription and translation),
Fish Audio (speech synthesis and voice cloning), Stripe (payments), Cloudflare
(network and security), Google Workspace (email), and our hosting providers.

At the date of this policy, Fish Audio's public terms allow it to use uploaded
content to improve its models. We are working to obtain a contract that
excludes this, and will update this policy when we do.

We disclose data to authorities when the law requires it, and to a buyer of
our business, who would be bound by this policy.

## 7. International transfers

Some providers process data outside the UK and the EEA, mainly in the United
States. We protect these transfers with the UK–US data bridge or the EU–US
Data Privacy Framework where the provider is certified, and otherwise with the
European Commission's Standard Contractual Clauses and the UK International
Data Transfer Addendum. Ask us at privacy@echoenvo.com for a copy.

## 8. How long we keep it

| Data | Kept |
|---|---|
| source videos, working files, transcripts and translations | until 30 days without activity in the project (we email you 7 days before) |
| dubbed audio tracks | while your account exists |
| dubbed videos (a copy of your video) | as source videos |
| voice clone models and templates | see section 5.5 |
| account data | while your account exists, then up to 6 years for legal claims |
| consent, confirmation and delivery records, abuse reports | at least 6 months, at most 6 years after the last related activity |
| payment and tax records | 6 years after the end of the tax year, as UK law requires |
| technical and security logs | up to {{LOG_RETENTION}} |

When you delete a project, its files are deleted, but the records in the
fourth row stay for the period shown.

## 9. Your rights

You have the right to access your data, correct it, delete it, restrict or
object to its processing, receive it in a portable format, and withdraw
consent at any time (this does not affect processing before withdrawal). To
use them, write to privacy@echoenvo.com. We reply within one month.

If you are unhappy with how we handled your data, please tell us first. You
can complain to the UK Information Commissioner's Office (ico.org.uk) or to the
data protection authority in the EU country where you live.

## 10. Cookies

We use only cookies needed for EchoEnvo to work. See our [Cookie Notice](/legal/cookies.md).

## 11. Children

EchoEnvo is not for anyone under 18, and we do not knowingly collect their
data. Do not upload videos to clone the voice of a child.

## 12. Notices for US residents

**Illinois, Texas, Washington, Colorado and other states with biometric
laws.** Section 5 is our public biometric retention and destruction policy. We
collect voice templates only with written consent, given in the product
before the clone is created, and we destroy them as described in section 5.5.
When a user clones the voice of another person, we ask whether that person
lives in Illinois, Texas, Washington or Colorado. If so, the person gives
written consent directly to us through a consent link before the clone is
created. If the user says no, the user confirms this and is responsible for
the answer ([Voice Consent](/legal/voice-consent.md), B5).

**Washington consumer health data.** We do not intend to collect consumer
health data. Our separate Consumer Health Data Privacy Policy is at
echoenvo.com/legal/health-data.

**California and other state privacy laws.** We do not sell or share personal
information for cross-context behavioural advertising. You may exercise the
rights in section 9 regardless of where you live.

## 13. Changes

We will tell you by email about material changes to this policy before they
take effect. The version and date are at the top.
