Privacy

Last updated: 25 October 2026

GroveScribe is built so that we can’t read your meetings. Recordings, transcripts and minutes are encrypted in your browser before they are saved; our server keeps only ciphertext and never has the key.

We keepYour email, and a password hash, Google account id or Telegram account numberYour wallet, top-ups and invoicesWhen each recording ran and how long, for billingYour saved meetings — encrypted, we can’t open them

We can’t see or don’t keepSound, transcripts, minutes, titles of meetingsYour library passwordIP addressesAnalytics, advertising, trackers

Where a meeting goes

Sound. Your browser sends it straight to our speech recognition provider, Deepgram, with a pass that works for a minute; it doesn’t go through our server. Every request asks Deepgram not to use it to improve its models.
Minutes, recap, chat about a meeting. The transcript goes through our server to a language model (Mistral or Google Gemini) and the answer comes back to your browser. On the way it is never written to disk or to logs. We use the providers’ paid plans, under which they don’t train on it.
Your library. What you save — sound, transcript, minutes, title, speakers — is encrypted in your browser with a key that only your library password (or your recovery code) opens. In a team, with the team’s key that its members hold. We store the ciphertext; neither we nor our storage provider can read it.
Confidential mode. If you turn it on, e-mails, phone numbers, card and document numbers are replaced in the browser right after recognition, before anything goes to a language model.

What we keep

Data	Why
Your email, and a password hash, your Google account id or your Telegram account number	To sign you in and to answer you
If you turn on two-step sign-in: the authenticator app’s secret (encrypted with a key kept outside the database), one-time recovery codes (only their hashes), whether codes by mail or a tap in Telegram are on	To ask for the second step when you sign in
For each device you’re signed in on: its browser and system in two words (e.g. “Chrome · Windows”) and when it signed in	So you can see your devices and sign them out
The name you give in your account	To show your team who said what in a meeting and to know who “I” is in your questions to a meeting
Your wallet, top-ups, invoices, and for each recording: when, how long, the mode (live text or not) and what it cost	To charge for recordings and keep the books
For each saved meeting: who owns it, its team, when it was saved, how long and how big it is — the meeting itself only as ciphertext	To show your library, count storage and delete old meetings when the team asks
Teams: their members, roles, invitations, settings, and a log of what admins did (never what a meeting was about)	To run the team and let its admins see who changed what
Technical figures of each recording: delays, reconnections, and your browser and system in two words. Deleted after 30 days.	To find and fix quality problems
Messages and ratings you send from the app, and the page’s log if you choose to attach it (settings and timings, never the words)	To read them and answer you
Promo codes you redeem and when; a promo link being opened is only counted, with nothing about who opened it	To give a code once per person and see how many people a code reached

That’s all. We don’t store IP addresses and use no analytics or advertising. The legal basis is the contract you enter by using GroveScribe (GDPR Art. 6(1)(b)), and our legal obligations for payment records (Art. 6(1)(c)).

How long

Your account’s data, while the account exists. A team keeps its meetings as long as its admin set (or until deleted). When you delete your account, your email, sign-in and personal meetings are erased at once; the records of past recordings stay without anyone attached, for the books. Payment records are kept as long as Polish tax law requires (5 years). Backups of the database are kept for up to 30 days, encrypted copies of the first of each month for a year.

In a team

When you record in a team’s space, the meeting belongs to the team: the organisation behind it decides what is recorded and how long it is kept, and we process it on its behalf. Its admins see the team’s members, what each recording cost and the team’s log; like us, they can’t open a meeting without the team’s key. A data processing agreement is available on request.

Other people in the meeting

The voices of everyone in a recorded meeting are transcribed. Tell the participants that you record, and get their consent where the law asks for it.

Who else is involved

Our hosting provider, , runs the server (in the EU).
MEGA S4 (data centre in Amsterdam, the Netherlands) stores the encrypted library: ciphertext only.
Deepgram, Inc. (USA) recognises speech. It gets the sound of a recording and returns the text; we opt out of its model improvement programme on every request. The transfer is protected by the EU standard contractual clauses.
Mistral AI (France) and Google (Gemini API) write minutes, recaps and chat answers from the transcript, under paid plans that don’t train on it. Google may process it outside the EU, under the EU standard contractual clauses.
Google, if you choose to sign in with Google.
Telegram, if you sign in with Telegram or link it to your account: we keep only your Telegram account number, not your name, username or photo. Our bot writes to you there only about sign-ins and your requests.
Mailgun (Sinch, mail servers in the EU), which sends our letters: confirming your address, a link for a new password, sign-in codes and alerts. It sees your email address and the letter, never anything from your meetings.

Your rights

You can delete your account yourself (your account, then “Delete my account”); your email and sign-in are erased at once. For a copy of your data or anything else, write to . You can also complain to a data protection authority, in Poland the UODO.

Who we are

GroveScribe is run by a sole proprietorship in Poland. Contact: .