Retranscript
Privacy policy
Last updated 25 October 2026
Retranscript records your calls on your Mac and keeps the recordings, transcripts and answers as files in your Documents folder. This page says exactly what leaves your Mac, to whom, and what we, Defsquare (the publisher named in the legal notice), keep about you. It applies to the Retranscript app for macOS, to Retranscript credits and to retranscript.app.
1. Who is responsible for what
Your recordings are yours. You decide what to record and what to ask the models; the files stay on your Mac. For the personal data in them, the voices and words of the people in your calls, you are the controller under the GDPR, and section 7 says what that asks of you.
We are responsible for your credits account, this website, the usage statistics the app sends, and the app’s update checks. For those, Defsquare is the controller, and you can reach us at jeremie@defsquare.com.
With credits, we are your processor for the audio and text that pass through our gateway on their way to the model. The terms of that processing are section 6 of the terms of service.
2. What stays on your Mac
Everything the app makes: the recordings (an .m4a per call, and the two tracks if you keep them), the transcripts, the edited copies and the answers to your prompts, in Documents › Retranscript or the folder you chose; your settings and your prompts, in the app’s preferences; your keys and your account token, in the macOS Keychain; the activity log, in your Library folder. None of it is sent to us. Deleting a recording in the app moves its files to the Trash; deleting the app leaves your files where they are.
3. What leaves your Mac, and to whom
| What | Goes to | When |
|---|---|---|
| The audio of a recording, in parts of a few minutes | the transcription model you chose: Google (Gemini) with your Gemini key; OpenRouter and the provider it routes to, with your OpenRouter key or with credits | after the recording is saved and its countdown is over, or when you click Transcribe |
| The transcript, with the title of the calendar event, the attendees’ names and email addresses as your calendar has them, and your own name | the text model of the prompt: Anthropic with your Anthropic key or your Claude Code sign-in; OpenRouter and the provider it routes to, with your OpenRouter key or with credits | when you click Ask, or after each transcription if you turned that on |
| Your account token and the request | our gateway, which forwards the audio or the text to OpenRouter | with every request paid with credits |
| Usage statistics, anonymous (section 5) | our gateway | shortly after launch and every ten minutes, while the switch is on |
| A request for the update feed | Cloudflare R2, where the feed and the app’s disk images are kept | once a day, unless turned off; never during a call |
Nothing else leaves your Mac. The app has no analytics library, no advertising identifier and no crash reporter. The permissions macOS asks for (microphone, system audio, calendars, automation of your browser to read its tabs’ addresses) are used for what they say and nothing is sent because of them.
The models’ providers process what they receive under their own terms. OpenRouter keeps, by default, metadata about each request and may let a provider keep the prompt for a time; in your OpenRouter account’s privacy settings you can require zero data retention, after which the app sends only to providers that keep nothing once they’ve answered, and the app says which models qualify. With your own OpenRouter key on its Business or Enterprise plans, you can choose in Settings › Models to keep every request in the European Union or in the United States. Google deletes each part of the audio from its servers as soon as it’s transcribed, under the Gemini API terms. With credits, requests go through OpenRouter: your Retranscript account has no retention or region setting of its own yet.
4. Retranscript credits
When you sign in for credits, we keep:
- Your email address, which is your account, and the label the app gave each Mac you signed in from (“Jérémie’s MacBook”), with a hash of its token. The code we email you is kept for fifteen minutes, with the number of attempts.
- Your balance and its ledger: each purchase (Stripe’s session reference, the pack, the date), each free credit and its expiry, each refund, and each request’s model, time, provider cost and charge. Never the audio or the text of a request.
- The network address the sign-in came from, for thirty days, after which the gateway forgets it. It serves one purpose: free credit is given once per mailbox and to at most three accounts from one address, and a referral between two accounts on the same network doesn’t count.
- What Stripe tells us about a payment: that the session was paid, or refunded. Stripe, as seller of record, keeps your card details, your receipt and your billing address under its own privacy policy; we never see your card.
The legal basis is the contract between us for the account, the ledger and the payments, our legitimate interest in not giving the free credit twice for the network address and the mailbox rules, and our legal obligations for the accounting records. A new account’s creation also sends the person who operates the service an internal notice with its address and its free credit, so that abuse is seen.
Emails (the sign-in code, the invitation you may forward to someone you refer) are sent through Resend. We write nothing to the person you refer: the invitation goes to your own address, and you forward it.
5. Usage statistics
While Share anonymous usage statistics is on in Settings › General (it is unless you turn it off), the app sends us, at each launch, which version of Retranscript and of macOS it runs, on which chip, in which language, and which kinds of model access are set up; after each transcription, prompt and update, whether it succeeded, which model and route it used and how long it took. Never a recording, a transcript, a name, a file name, an email address or an error’s text.
These events are keyed by a random identifier the app made on your Mac, never by your account, and the gateway sees the country of the network address, not the address. Turning the switch off also deletes the identifier. We keep one row per installation (first and last seen, launches, version, macOS, chip, country) to know how many Macs run which version, and each event as a log line for three to seven days. The basis is our legitimate interest in knowing whether the app works; since the identifier is stored on your Mac, the switch is the way to say no.
6. This website
The site runs no advertising or third-party scripts. It exists in seven languages: its first page opens in your browser’s language when that is one of them, read from the request as it arrives and not kept, and the footer lets you choose another. Choosing one sets the site’s only cookie, lang, which holds that choice for a year and nothing else; the site sets no cookie otherwise. It may use Cloudflare Web Analytics, which counts page views, referrers and load times without a cookie or an identifier. Cloudflare, which serves the site, sees visitors’ network addresses in the ordinary course of serving it and keeps its own logs under its privacy policy. If you leave your email address on a waiting list, it goes to Resend to be kept there until you ask us to remove it or we write to you.
7. Recording other people
The people in your calls appear in your recordings and transcripts: their voices, their words and, when the recording is named after a calendar event, their names and email addresses. Retranscript doesn’t announce itself in the call. It’s for you to tell them, before or as the recording starts, and to get their consent where the law requires it: in France, consent is presumed when the recording is made openly and nobody objects (Code pénal, art. 226-1); in Germany and Switzerland everyone must agree (§ 201 StGB, art. 179ter CP); in a dozen American states, California among them, everyone’s consent is required; the call platforms’ terms also ask that participants be told.
The app helps with that: a notice before your first recording, and a message you can copy into the call’s chat with one click, in the Mini Recorder while recording. Section 3 of the terms says more. Afterwards, the files are yours to keep safely, to delete when they’ve served their purpose, and to show a participant who asks what you kept about them. A company that records its staff’s calls informs them, and its employee representatives where the law requires it.
8. Sub-processors
The companies that process personal data on our behalf:
| Company | For | Where |
|---|---|---|
| Cloudflare, Inc. | hosting of the website, the gateway, its database and logs, the update feed; web analytics | United States, with servers worldwide including the European Union; certified under the EU-US Data Privacy Framework |
| OpenRouter, Inc., and the model providers it routes a request to | the models, for requests paid with credits (the content, in transit) | United States and the providers’ own countries |
| Stripe Payments Europe, Ltd. | selling the credit packs, as seller of record | Ireland, with Stripe, Inc. in the United States |
| Resend, Inc. | the sign-in codes, the invitations, the waiting list | United States |
Where a transfer leaves the European Union, it relies on the EU-US Data Privacy Framework when the company is certified under it, and otherwise on the European Commission’s standard contractual clauses in our agreement with that company. With your own keys, the providers you chose receive your data directly under their terms, and no sub-processor of ours is involved.
9. How long we keep things
| Data | Kept |
|---|---|
| Account, tokens, balance, grants | while the account exists; deleted within thirty days of its closure |
| Purchases and refunds, as accounting records | ten years, as French commercial law requires (Code de commerce, art. L123-22) |
| Request entries in the ledger (model, time, cost) | while the account exists |
| Sign-in codes | fifteen minutes, and the sign-in’s row for a short time after |
| Network address of a sign-in | thirty days |
| Usage events, as log lines | three to seven days; the per-installation row, anonymous, indefinitely |
| Internal notices of new accounts | one year |
The audio and text that pass through the gateway are kept for the duration of the request only, in memory.
10. Your rights
You may ask us for a copy of what we hold about you, to correct it, to delete it, to limit its use, to receive it in a portable form, and you may object to a processing based on our legitimate interest. Write to jeremie@defsquare.com; we answer within a month. You may also complain to the data protection authority of your country, in France the CNIL.
For what is in your recordings, the request goes to you, their controller: we hold no copy and can’t act on it.
11. Children
Retranscript is a tool for work and isn’t meant for people under fifteen. We don’t knowingly open an account for one.
12. Changes
When this page changes, the date at its top changes with it, and account holders are emailed when a change concerns the data we keep about them. The previous versions are in the history of this page.