Privacy

This page describes what txscribe actually does with your data. It is written to be accurate rather than comprehensive, and it is not a substitute for legal advice.

What we store

The files you upload, the transcripts produced from them, and any summaries, translations or corrections you generate. We also store your email address and name from Google sign-in, and a record of how many minutes you have transcribed in the current billing period.

Everyone who handles your data

This is the whole list, not just the ones that touch recordings. Each gets only what the job needs.

• Google Cloud Storage — stores the files you upload and the transcripts made from them.
• Google Cloud Speech-to-Text — does the transcribing. Your recording is sent to it.
• Google Gemini on Vertex AI — produces summaries, translations and answers. The transcript is sent to it; the recording is not.
• Stripe — takes payments. It receives your card details and we never do.
• Resend — delivers email we send you. It receives your email address and the text of that message, and never your recordings, transcripts, or anything made from them.

What we do not do

We do not use your recordings or transcripts to train models, we do not sell them, and we do not share them with anyone other than the processors above. Nobody at txscribe reads your transcripts as a matter of course.

Sharing

A transcript is private until you create a share link for it. A share link is an unguessable URL that anyone holding it can open without signing in — treat it as public. You choose whether the recording itself and the summary travel with the link, or only the transcript.

Share links do not expire. One stays open until you turn sharing off or delete the transcript, and either of those stops it working immediately — including for people who already have the URL. We do not list share links anywhere or allow search engines to index them, but a link that has been forwarded cannot be un-forwarded, so the only reliable way to close one is to revoke it.

How long we keep your recordings

Recordings in an account are kept until you delete them. There is no automatic expiry: a recording you uploaded a year ago is still there, and so is its transcript. That includes transcriptions that failed — they stay in your library, holding the audio you uploaded, so that you can retry or delete them.

This is a deliberate choice rather than an oversight, and it cuts both ways: nothing you rely on disappears without you asking, and nothing you have forgotten about is cleaned up for you.

The trial is the one exception, and it goes the other way. A recording made without an account is deleted automatically, on the clock described below.

Trying it without an account

You can transcribe one recording without signing in. We give that visit an identifier of its own — a random value in a cookie, holding no name, no email address and nothing from your recording — so that we know which transcript is yours to read back. It is not linked to any account, and it is not used to recognise you anywhere else.

What the trial makes is deleted 48 hours after you make it. That covers the file you uploaded, the transcript produced from it and everything stored alongside it, in every place we keep it — the same deletion the button in your library performs, including the seven-day storage delay described above. It runs on a schedule rather than waiting for you to ask, and it happens whether or not you come back.

If you sign in and choose to keep the transcript, it moves into your account and that clock is removed — from then on it is an ordinary transcript of yours, kept until you delete it. If you do not, it goes. Signing in from a different browser cannot reach it, because the identifier that names it lives in the browser that made it.

Counting trials

Transcribing costs us money for each recording, so we limit how many trials can start from one network address — 5 in any 24 hours. To count them we have to be able to tell one address from another.

We do not store your IP address to do it. We store a SHA-256 hash of the address combined with a secret key that only we hold, and a count against that hash. Anyone who obtains that data without the key cannot turn it back into an address. We are not going to pretend it is beyond us as well — we hold the key — but the hash is never attached to your account, your transcript or anything you upload, and nothing we do reads it back as an address. The hash and its counter are deleted once the 24-hour window they belong to has passed, by the same sweep that deletes the trial itself.

How we count visits

We measure our own site ourselves. There is no analytics company involved, no third-party script on any page here, and no advertising pixel — nothing about your visit is sent to anyone. The counts are written to the same database as everything else described above, in our own project.

To do it we give your browser one cookie, named tx_aid. It holds a random value and nothing else: no name, no email address, no account, and nothing whatsoever from a recording or a transcript. Your file names never form part of it either. Alongside it we store, once, where you first arrived from — the campaign tag on the link you followed, if there was one, and the site that linked to you. We keep the first answer and never replace it with a later one.

We ask your browser to keep that cookie for up to 400 days, so that we can tell whether the people who arrive from a particular link are the people who eventually subscribe. Your browser decides whether to honour that, and some browsers shorten it. If you sign in, the value is attached to your account once, so that the same question can be answered about customers.

A count we record is an event name, a time, the random value above and a handful of numbers — how long a recording was, which language, which plan. Your account identifier is not one of them, and cannot be: there is nowhere in that record to put one. So deleting your account removes the only thing that ever connected those counts to you, and what is left is not about anybody.

We do not store your IP address against any of this, and none of it is combined with data from anywhere else. Clearing your cookies removes it, and you will simply be counted as a new visitor.

Deletion

Deleting a transcript deletes the uploaded recording, the transcript, any translations of it, and any share link. The share link stops working at once and the records become unreadable to us immediately.

The stored files themselves are removed on a seven-day delay: Google Cloud Storage keeps a deleted object recoverable for seven days before erasing it, which protects you against an accidental deletion and means the bytes are genuinely gone a week after you ask. We would rather give you that number than write “for a short period”.

Payments

Payments are handled by Stripe. We never see or store your card details; we store only the Stripe customer and subscription identifiers needed to tell which plan you are on.

To set up your subscription we send Stripe your email address, an internal identifier for your account, and the plan you choose. Where tax has to be calculated, Stripe also asks for your billing address and keeps it with your payment details. Stripe never receives your recordings, transcripts or anything generated from them.

Receipts and notices about payments may come from Stripe rather than from us, and those messages are governed by Stripe’s privacy policy.

Email

There is exactly one kind of email we will ever send you, and it is about money leaving your account: what the amount is, what date it lands, and a link to cancel. When the amount is changing — at the end of an introductory month, say — it says that too.

We send no marketing email at all, so there is no list to be on and nothing to unsubscribe from. If you write to us, a person replies from a mailbox — that reply is not part of any of this.

These messages are delivered by Resend, which receives your email address and the text of the message we are sending. It never receives your recordings, your transcripts, or anything generated from them.

Contact

Questions about any of this: support@txscribe.ai.