Privacy policy
Last updated: 30 September 2026
This page is available in English only. The English version applies.
1. Who we are
TranscribeLab (the browser add-on and the website) is made by MB Makery, company code 307770736, V. Nagevičiaus g. 3, LT-08237 Vilnius, Lithuania. Write to us at support@developers911.com.
For your account (your e-mail, your plan, your usage) MB Makery is the data controller. For the recordings you make, you decide what is recorded and why; we process that sound and text for you, to give you the service.
2. What we collect
| What | When and why |
|---|---|
| Your e-mail address | When you sign in with a code. To sign you in, to send the code and important messages about your account and payments. |
| Sign-in with Google or Apple | If you sign in with Google or Apple, we keep only the provider's name, your account id there, the e-mail address it gives us and the time, and never your name, your photo or the provider's tokens. |
| An install id | A random id made when you install the add-on, with the browser name, the add-on version and the language of your browser. To count the free transcripts and keep your recordings together before you sign in. |
| The sound you choose to transcribe | A tab you record, your microphone if you switch it on, or a file you upload. Only while it is turned into text; it is deleted once the text is ready. |
| The text of your recordings | Transcripts, speaker names you set, titles, summaries, follow-up e-mail drafts, your questions and the answers, share links, and your personal word list. |
| The site of a recorded tab | Only its host, for example meet.google.com, never the full address. To show where a recording came from. |
| Usage counts | How many transcripts, how many minutes or hours, how many YouTube videos and questions. To apply the limits of your plan. |
| Plan and payment status | If you buy Pro: the plan, its dates, whether it renews, and a customer id from our payment provider. We never see or store your card number. |
| Technical data | Your IP address, used by our server to block abuse (limits on how many requests one address can make). Server logs hold ids, sizes, durations and error codes only. |
The website uses one cookie, tl_session, to keep you signed in. Your browser also remembers the language you picked (tl-lang). We use no advertising cookies and no outside analytics.
3. What we never do
- We never keep your audio after the text is ready.
- We never use your audio or your text to train AI, and we use speech services that do not train on it.
- We never store the full address of a page you record, only its host.
- We never write your transcripts, questions or answers into our logs.
- We never download audio from YouTube. YouTube videos are read from their captions, or recorded from your own tab while they play.
- We never sell your data and we show no ads.
4. Why we may use it (legal grounds)
- To give you the service you asked for (contract): sign-in, transcripts, summaries, search, sharing, your plan.
- To keep the service safe (legitimate interest): limits against abuse, fixing errors.
- Because the law says so (legal obligation): payment and tax records.
5. Who helps us (processors)
These companies process data for us, only to run TranscribeLab:
- Server hosting (Hostinger): stores the database and runs the server.
- Speech to text (Soniox or OpenAI, depending on the language): turns the sound into text. The sound is sent to them only to be transcribed.
- OpenAI: writes summaries, follow-up e-mails and answers from the text.
- E-mail delivery: sends your sign-in codes and account e-mails.
- Stripe and Link (Stripe's checkout): take payments for Pro as the seller of record, handle taxes and receipts. Your card details go to them, not to us.
- Google Fonts: our pages load their fonts from Google, which sees your IP address. Some pictures on our home page are loaded from Unsplash in the same way.
Some of these companies are in the United States. Where data leaves the European Economic Area, it is protected by the European Commission's standard contractual clauses or the EU–US Data Privacy Framework.
6. How long we keep it
- Audio: deleted as soon as the text is ready. A cancelled recording is deleted at once.
- Transcripts, summaries and answers: until you delete them or delete your account.
- Share links: until you turn them off; they stop working at once.
- Sign-in codes: valid for 10 minutes, then useless.
- Server logs: a short time, at most 30 days.
- Payment records: as long as tax law requires.
- After you delete your account: we keep only a one-way fingerprint (hash) of your e-mail address and the number of free transcripts it used, so that deleting the account and signing up again does not start the free transcripts over. Nothing else is kept, and the fingerprint cannot be turned back into your address.
7. Your rights and how to delete
Delete any recording on its page (the bin button). Delete your whole account on the Account page: this removes your recordings, summaries, answers, share links, word list, every add-on install linked to you and every session, and it cannot be undone. Only the fingerprint described in section 6 remains.
Under the GDPR you may ask to see your data, correct it, delete it, limit or object to how we use it, and get a copy to take elsewhere (every transcript can also be exported as a text or subtitle file). Write to support@developers911.com; we answer within one month.
You may also complain to a data protection authority: in Lithuania the State Data Protection Inspectorate (vdai.lrv.lt, L. Sapiegos g. 17, LT-10312 Vilnius), or the authority where you live.
8. Recording other people
A voice is personal data. When you record a call, you must tell everyone in it; in some countries and US states everyone must agree first. Before your first tab recording TranscribeLab shows these rules and asks you to accept them, and it gives you a ready message to paste into the meeting chat. You are responsible for having the right to record and upload what you do.
9. Children, security and changes
TranscribeLab is not meant for children under 16.
Everything travels over encrypted connections. Sign-in tokens are stored only as fingerprints (hashes), so a copy of our database cannot be used to sign in as you.
If we change this policy in an important way, we will tell signed-in users by e-mail before the change applies.