uttrd

Privacy policy

Last updated: October 11, 2026

This page explains, in plain English, what uttrd collects, who processes it, and how long it is kept. It describes what the app actually does today. uttrd is run from Ontario, Canada.

What we collect

  • Your Google sign-in. If you sign in with Google, uttrd receives your email address, name, profile picture and the account id Google gives it. The account id is what your saved takes, usage and subscription are stored under. Signing in with Google also adds your email address to the mailing list.
  • Your mailing list email. If you join the mailing list, uttrd stores your email address, any name you give, which page you signed up from, and the country your connection came from.
  • Usage records. For each generation, uttrd records the voice and engine, the length of the script and of the audio, whether it was a preview, and your account id if you are signed in. These records do not contain your script text or your IP address.
  • A hashed IP address for usage counters. To enforce usage limits, uttrd keeps counters tied to your account or to a hashed version of your IP address. The hash changes every day and cannot be turned back into your IP address without a secret key that only uttrd holds. To limit abuse, the server holds your IP address in memory only and does not save it to a database.
  • Script text, where it is kept. If you are signed in, each saved take stores its script, its audio, the voice, the speed, the word count and any name you give it. If you are signed out, your scripts and audio stay in your browser and are not saved on our servers. Your browser also keeps the script and style text you are working on, so it is still there when you come back.
  • Shared links. When you share a take, signed in or not, its audio is uploaded and given a public link, along with the voice, the playback speed and an optional sender name. The script is not included.
  • Analytics. uttrd uses PostHog to record page views, clicks, which features are used and recordings of sessions. Events are tied to a random id, and to your account id once you sign in. Text you type is masked in session recordings, and so is script text shown in your takes. For each generation, analytics receives a short fingerprint of the request and its length, not the text. PostHog also receives your IP address with each event. Vercel Analytics counts page views.
  • Subscription status. If you subscribe to Pro, uttrd stores your plan, billing interval, subscription status, renewal date, and the customer and subscription references Stripe gives it. Your card details stay with Stripe and uttrd never sees them.
  • Server logs. Each generation writes a log line with the voice, the length and how long it took, without the script text. If a premium voice returns text instead of audio, up to 200 characters of that text is logged, and it can repeat part of your script.

What is sent to voice generation providers

To make audio, uttrd sends your script text, your delivery instructions (the Tone, Energy and Pacing settings, any effects, or the style text you write) and your chosen voice to the provider behind that voice. Standard voices are made by OpenAI. Premium voices are made by Google Gemini. Your name, email address and account id are not sent to either.

uttrd uses paid accounts with these providers, so your text is not used to train their models. Providers do keep requests briefly for abuse detection and legal compliance.

Who else processes data

  • OpenAI, which generates standard voices and receives your script text and delivery instructions.
  • Google, whose Gemini models generate premium voices and receive your script text and delivery instructions. Google also handles sign-in if you sign in with Google.
  • Stripe, which processes payments and subscriptions. It receives your email address, a reference to your uttrd account and your payment details.
  • Vercel, which hosts uttrd, its database, saved and shared audio files, and server logs, and provides basic page analytics.
  • PostHog, for product analytics and session recordings.
  • Resend, which sends mailing list emails and receives your email address and name to do it.
  • Zoho, for email to and from support@uttrd.app.

How long it is kept

  • Saved takes are kept until you delete them. Each account keeps its newest 100 takes, and older ones are removed automatically along with their audio.
  • Takes made while signed out stay in your browser, up to the 25 most recent, and are cleared when you come back on a later visit. The script you are working on stays in your browser until you clear it.
  • Shared links and their audio do not expire. Deleting a take does not delete a link you shared from it.
  • Usage records, usage counters, account details and subscription status are not deleted automatically.
  • Mailing list entries are kept until you ask for them to be deleted. Unsubscribing stops the emails and marks your entry as unsubscribed.
  • Session recordings are kept for 30 days. Other analytics and server logs are kept under PostHog's and Vercel's standard retention.

Your choices and deleting your data

  • You can use uttrd without signing in.
  • You can delete any saved take from your library or your recent takes. That removes its script and audio from our storage.
  • You can unsubscribe from the mailing list with the link in any email.
  • You can manage or cancel a Pro subscription from your account page.
  • To delete anything else, email support@uttrd.app from the address you use with uttrd. That covers your saved takes, usage records tied to your account, your subscription record, your mailing list entry, analytics tied to your account and any shared link. Stripe keeps its own records of payments under its own privacy policy.

Contact

Questions about this policy or your data: support@uttrd.app. The terms of use cover the rest.

Changes to this policy

uttrd may update this policy as the app changes. Changes are reflected in the "last updated" date at the top of this page.

Back to the app