Legal notice
and privacy

This page brings together everything that governs the use of uttera.ai and the service behind it. It is written to be understood, not to avoid being understood.

• 1. Who operates this
• 2. Terms of use of the site
• 3. Terms of the service
• 4. Prohibited uses
• 5. Cloned voice and recordings
• 6. Privacy policy
• 7. Data processing agreement
• 8. Cookie policy
• 9. Changes and governing law

1. Who operates this

In compliance with article 10 of Spanish Law 34/2002, on information society services and electronic commerce (LSSI-CE):

2. Terms of use of the site

2.1 Purpose and acceptance

These terms govern access to and use of the uttera.ai website and its subdomains. Browsing the site means accepting them. If you don't agree with them, don't use it.

2.2 Access

Access to the site is free and requires no registration. The documentation, the prices, the blog and the public demo are available without an account. An account is only needed to use the API and to subscribe to a plan.

Uttera is not responsible for the cost of your internet connection or for the equipment you use to access it.

2.3 Proper use

You agree to use the site in accordance with the law and with these terms. The following is expressly prohibited:

• Using it for unlawful purposes or in ways harmful to Uttera or to third parties.
• Introducing or spreading malicious code, or anything that could damage the systems.
• Unauthorized access, penetration attempts, vulnerability scanning, or mass automated extraction of content.
• Reproducing or transforming the site's content without authorization, except as allowed by the license of the published code.

2.4 Intellectual property

The texts, the design, the "Uttera" trademark and the logos are the property of Uttera or of its licensors.

The engine code is a different matter, and it's worth saying so here: the transcription and synthesis servers are published at github.com/uttera under the Apache 2.0 license, and you may use, modify and deploy them under that license, including commercially. The third-party models used with them carry their own licenses, stated in each repository.

2.5 Links

The site links to third-party pages (GitHub, Stripe and others). We are not responsible for their content or their policies, and a link implies neither endorsement nor a commercial relationship.

2.6 Availability

We make a reasonable effort to keep the site up and current, but the website itself carries no availability commitment. The availability commitment for the service — the SLA — depends on your plan and is in the documentation.

3. Terms of the service

3.1 What the service is

Uttera is an API that transcribes audio, generates speech from text, translates and summarizes recordings. It is subscribed to in plans with a monthly allowance of credits and billed per second of audio processed.

3.2 Your account and your key

Using the API requires an account and at least one key. The key is yours and it is your responsibility. Anything done with it is deemed done by you and billed to your account.

• Don't write it into source code, or into a configuration file that ends up in a repository, or into a phone system's dialplan.
• If you think it has been compromised, revoke it from your account page: the cut is immediate.
• You can restrict each key to specific IP addresses. It's the cheapest defense there is and almost nobody uses it.

3.3 Billing

Payments are handled by Stripe Payments Europe, Ltd. Uttera never sees or stores your card details.

Credits are assigned per billing cycle and do not carry over from one cycle to the next. If you exhaust the allowance, the service keeps serving you as billable overage, and the response tells you so with the X-Credits-Overage header.

You can change or cancel your plan at any time from your account. Cancellation takes effect at the end of the current cycle; there is no minimum term.

3.4 Service level

The availability commitment depends on the plan and is published in the documentation. The free, startup and developer plans carry no SLA, and that is also stated on the pricing page before you subscribe.

3.5 Limitation of liability

Uttera provides an automated audio processing service. The results are automatic and may contain errors: a transcript can get things wrong, a summary can omit something relevant, and an acoustic estimate can be incorrect.

You are responsible for reviewing the output before making decisions based on it, especially where those decisions affect people. To the extent permitted by law, Uttera's liability is limited to the amount invoiced in the twelve months preceding the event giving rise to it, and does not extend to lost profits or indirect damages.

3.6 Suspension

We may suspend an account that breaches these terms, that puts the service at risk, or whose use is manifestly unlawful. Unless urgency or the law prevents it, we will give notice first and say why.

4. Prohibited uses

What follows isn't a defensive lawyer's list: it's what we don't want done with this. Using Uttera for the following is prohibited:

5. Cloned voice and recordings under Spanish law

This section exists because it's where most people get themselves into trouble without knowing it, and because we'd rather explain it than hide behind "the customer is responsible".

5.1 Whose voice you may clone

Yes, with peace of mind:

• Your own voice. To dub yourself into a language you don't speak, so you don't have to re-record a voiceover every time a sentence changes.
• Someone who has given you written permission, for a specific and bounded use: a hired voice actor with an express assignment, a colleague who agrees to voice the internal assistant.
• A voice that belongs to no real person, or one licensed for the purpose.

No:

• The voice of an actor, a presenter or a politician because public material exists. Accessible is not authorized.
• The voice of a customer or an employee because you have it recorded from a call. Recording for quality assurance is not collecting a voice model.
• The voice of a recognizable person, to make it look like they said something they didn't.

The practical test, which is almost always right: would the person that voice belongs to be comfortable seeing what you're about to generate with it? If the answer is "they'll never find out", you have your answer.

5.2 Which recordings you may process

Uttera processes the audio you send it; it does not check where it came from, and that check is yours.

• Recording a conversation you are part of is not a crime in Spain. Distributing it can be, and processing it for purposes other than those that justified it also has consequences.
• Recording a conversation between others, where you are not a party, is a crime (art. 197 of the Criminal Code).
• Recording calls in a company requires informing both parties in advance, having a legal basis and a defined retention period. If you also record your employees, see arts. 89 and 90 of the LOPDGDD.
• Special category data. A clinical recording is health data (art. 9 GDPR). Processing it is not prohibited — it is done every day — but it requires its own legal basis and, frequently, an impact assessment.

5.3 The duty to disclose generated audio

Since 2 August 2026, article 50 of Regulation (EU) 2024/1689, the AI Act, has been in application. As it affects you as a user of Uttera:

• If you generate audio that imitates a real person and could lead someone to believe it is authentic — what the Regulation calls a deep fake — you must disclose it clearly and visibly.
• If the synthetic audio informs the public on matters of public interest, the same applies.
• If your system converses with a person, that person must know they are talking to a machine, unless it is obvious.

That duty is yours, because you are the one publishing. Ours, as providers of the system that generates the audio, is to enable technical marking of synthetic content: article 50(2) requires outputs to be marked in a machine-readable format and the marking to be detectable.

5.4 Our marking timeline

These are the dates, so you can plan around them:

In July 2026 the European Commission published interpretive Guidelines — not binding — and there is a Code of Practice on Transparency of AI-Generated Content that providers may sign up to.

Once marking is in place, we will publish here and in the documentation how we mark and how it is verified, so that you can check an audio file we generated on your own. Until then, this page says what there is.

6. Privacy policy

This explains what we do with your data: your account and your browsing. What we do with the audio you send us is a different matter and goes in section 7, because there we are not the controller but the processor.

6.1 Controller

6.2 What data we process, for what, and on what basis

6.3 What we do NOT do

• No profiling and no automated decisions with legal effects on you.
• We do not sell or share your data with anyone.
• We don't send you marketing unless you ask for it. The only automatic emails are service ones: access, billing and account notices.
• We use no third-party analytics. There is no Google Analytics, no pixels, no trackers.

6.4 Who else is involved

These are all the third parties involved, and there are no others:

There is no third party anywhere in the audio path. Transcription, translation, summarization and synthesis all run on our own machines, in Spain.

6.5 Where the data is

On our own infrastructure in Andalusia, Spain. There are no international data transfers other than sign-in with Google or GitHub, which only exists if you choose that way in, and Stripe's, within the EU.

6.6 Your rights

You can exercise your rights of access, rectification, erasure, objection, restriction and portability by writing to support@uttera.ai. We will respond within one month.

Two of them are already handled without you having to ask:

• Portability (art. 20): your data is available in machine-readable form at /cuenta/datos.json, from your own account and immediately.
• Erasure: you can delete your account from the account page. Only the billing data the law requires us to keep is retained, blocked.

If you believe we haven't handled your request properly, you can complain to the Spanish Data Protection Agency (aepd.es). We'd appreciate hearing from you first, so we can try to fix it.

7. Data processing agreement

This section is the one that matters if you're a company and you're going to send us recordings containing other people's data.

7.1 Who is who

With respect to the audio and text you send us, you are the controller and Uttera is the processor (art. 28 GDPR). We process that data solely to provide you the service and following your instructions, which are the requests you make to the API.

This serves as a data processing agreement. If you need a signed contract — many organizations require one — write to us and we'll sign it.

7.2 What we do with that content

• It is processed and discarded. Audio is handled in memory and discarded when we answer. The transcript, the analysis and the summary travel in the response and are not stored.
• The only thing written is the audio we generate, kept for one hour in an exact-match cache, with effective deletion on expiry. You can disable it on every request, and then nothing is written.
• We do not train models on it, nor aggregate it into statistics, nor "anonymize" it for reuse, nor review it by hand.
• There are no sub-processors in the audio path.

7.3 Security and obligations

• All traffic is encrypted in transit. Keys are stored as cryptographic hashes.
• Staff with access are bound by a duty of confidentiality.
• We will notify you without undue delay of any security breach affecting your data, with what we know and what we are doing.
• At the end of the relationship there is nothing to return or destroy as regards the content, because none is retained.
• We will assist you, within reason, with impact assessments and with rights requests you receive from your own data subjects.

8. Cookie policy

8.1 Summary

We use no analytics cookies, no advertising cookies, and no third-party cookies. That's why you won't see a cookie banner: there is nothing to consent to. The only two things we store in your browser are technical and necessary for the site to work, and they are exempt from consent under art. 22(2) of the LSSI.

8.2 What there is, exactly

If you only browse the public site — home, documentation, blog, pricing — absolutely nothing is stored except your theme preference, if you change it.

8.3 How to remove them

From your browser settings, like any other. Note that if you block the session cookie you won't be able to stay signed in.

8.4 If this changes

If we ever add analytics, there will be a banner and there will be prior consent, and this table will say so before it happens. While this page says there is none, there is none.

9. Changes and governing law

We may modify these terms. Changes are published on this same page with their date. If a change is substantial and affects you as a customer, we will notify you by email with reasonable advance notice before it takes effect.

These terms are governed by Spanish law. For any dispute, the parties submit to the Courts of Madrid, unless the law imposes another venue — in particular, if you are a consumer you keep yours.

If you are a consumer resident in the European Union, you may use the European Commission's online dispute resolution platform: ec.europa.eu/consumers/odr.

Last updated: 15 September 2026