blablaType Privacy Policy
2026-06-13
This policy explains what data the blablaType service processes, why it is needed, what happens to your voice and text, and how to exercise your rights. We wrote it in plain language because you should understand every clause without a lawyer.
The core principle of the service: we process audio and text only to deliver your result, and we do not store them after processing. Details for each feature are below.
For any questions about personal data, write to privacy@blablatype.app. General questions about the service go to support@blablatype.app.
1. Who processes the data
Data controller: the blablaType service, website blablatype.app. Contact for personal data matters: privacy@blablatype.app.
This policy covers the blablatype.app website (including the free web dictation widget and the transcription page), the blablaType desktop app for Windows, and the user accounts connected to them.
2. Dictation in the desktop app
When you hold the dictation key and speak, the audio is sent over a secure connection (HTTPS) to the blablaType server and then to an STT provider for speech recognition. The recognized text is returned to the app and typed at your cursor.
Audio is not stored after processing. The recognized text is not stored on the server either: it exists only as long as needed to return it to you.
The app's text features (speech cleanup, on-the-fly translation, voice editing commands) process only text that has already been recognized. That text is sent to a text processing provider, the result is returned to you, and after that the text is not stored on our servers.
Your corrections dictionary (words you corrected so the app remembers them) is stored locally on your device. Its terms travel with each recognition request as an accuracy hint and are not kept on the server.
3. Web dictation widget on the site
The free dictation widget on the homepage runs on your browser's built-in speech recognition (the Web Speech API in Chrome and Edge). It requires no registration.
Audio from the widget never reaches blablaType servers. It is processed by the browser's speech engine: in Chrome that is a Google service, in Edge a Microsoft service. Processing of that audio is governed by the policies of the respective browser vendor, not by this policy.
To track free usage of the widget, we store an anonymous session token and a usage counter in your browser (see the section on localStorage and cookies).
4. The Compare feature on the site
The Compare feature shows the difference between your browser's recognition and blablaType's recognition. For this, the audio is sent over HTTPS to the blablaType server and then to an STT provider, the same as for dictation in the desktop app.
Audio is not stored after processing. The recognized text is returned to you and is not stored on the server.
5. File transcription
On the transcription page, you upload an audio or video file (mp3, wav, m4a, ogg, mp4, mov) and receive text. The file is sent to the blablaType server and to an STT provider for recognition.
The uploaded file and the resulting text are not kept longer than needed to process them and deliver your result. Once the result is delivered, the file and the text are deleted from our servers.
For paid transcription, we keep records of your minute balance and per-minute deductions: this is required for accurate billing.
6. Account and subscription data
To run the desktop app, we store account data: your email, a hashed device identifier, and your trial or plan status. This is needed for sign-in, subscription checks, and preventing abuse of the free trial.
Payments (once enabled) are handled by Lemon Squeezy as the merchant of record. Bank card data never touches blablaType servers: we do not receive, process, or store it. Lemon Squeezy passes us only the information required to activate and account for your subscription.
7. Crash reports and diagnostics
The desktop app may send crash reports so we can find and fix bugs. Sending diagnostics is optional.
Personal data is scrubbed from reports before they are sent. Crash reports are kept for a limited period needed to investigate the bug, then deleted.
8. What we do not store
Your dictation audio, Compare feature audio, and transcription files are not stored after processing.
Recognized dictation text and the output of text features (cleanup, translation, commands) are not stored on the servers: they are returned to you and deleted.
We do not use the content of your speech or text for advertising and do not sell data to third parties.
9. localStorage and cookies
The site stores four entries in your browser's localStorage: bbt-theme (your chosen theme), bbt-lang (language choice), bbt-anon (an anonymous session token for tracking free quotas), and bbt-dw-visits (a usage counter for the web widget). These entries stay in your browser and do not identify you as a person.
As for cookies, the site uses Google Analytics 4 (_ga, _ga_*) solely for traffic analytics, with no advertising purposes. Cloudflare may set technical cookies to protect the site.
A detailed description of each entry and how to disable them is provided separately, see the Cookie Policy.
10. Subprocessors
To run the service, we engage third-party providers that process data on our behalf: Groq, Inc. and ElevenLabs (speech recognition), OpenAI (processing of recognized text: cleanup, translation, commands), Cloudflare (CDN and static hosting), Namecheap (VPS hosting for the backend), Google (GA4 analytics; speech recognition in the web widget is performed by your browser), Lemon Squeezy (payment processing, connected once payments are enabled).
Each subprocessor receives only the data needed for its function. For example, the STT provider receives audio for recognition but does not receive your email.
11. Retention periods
Audio and text from recognition features: not stored after processing and delivery of the result.
Account data (email, hashed device identifier, plan status): for as long as your account exists. The corrections dictionary lives locally on your device.
Transcription balance data and deduction history: for as long as the account exists, to keep billing and refunds accurate (a refund of the unused balance is available on request within 14 days of a top-up).
Crash reports: a limited period needed to investigate the bug.
localStorage entries: in your browser until you delete them. Cookie lifetimes are listed in the Cookie Policy.
12. Your rights
You can request access to the data we hold about you, have it corrected, or have your account deleted entirely along with its associated data. To do so, write to privacy@blablatype.app from the address your account is registered to.
You can disable crash report sending in the app settings at any time, clear localStorage in your browser, and restrict cookies (see the Cookie Policy).
We respond to personal data requests within a reasonable time and free of charge.
13. Changes to this policy
We may update this policy as the service evolves, for example when adding new features or changing subprocessors. The current version is always published on this page, with the last updated date shown at the top.
For material changes affecting how your data is processed, we will make an effort to notify you in advance: on the site, or by email if you have an account. By continuing to use the service after changes take effect, you agree to the updated policy.