blablaType Subprocessors

2026-06-13

Subprocessors are third party services we engage to process data on our behalf. blablaType would not work without them: speech recognition, text processing, hosting, and payments all run on the infrastructure of these companies. Each subprocessor receives only the data necessary for its specific task and is required to process it under contractual data protection terms.

We publish this list so you know exactly who is involved in processing your data and to what extent. For details on what data we collect and how long we keep it, see the Privacy Policy. If you have questions about this list, write to privacy@blablatype.app.

Groq, Inc.

Purpose: speech recognition (converting audio to text) for desktop dictation and transcription.

What data it sees: audio recordings of your speech, which the blablaType server sends for recognition over a secure connection. The audio is used only to produce text and is not stored after processing. Your account details (email, plan) are not shared with this subprocessor.

ElevenLabs

Purpose: speech recognition, serving as our second STT provider alongside Groq.

What data it sees: audio recordings of your speech, sent for recognition by the blablaType server. As with Groq, the audio is used only to produce text and is not stored after processing; your account details are not shared.

OpenAI

Purpose: processing text that has already been transcribed. This covers speech cleanup (removing filler words, fixing grammar), translation, and voice editing commands.

What data it sees: only the transcribed text that needs processing. The audio of your speech is never sent to this subprocessor: by the time of processing, it has already been converted to text by another provider.

Cloudflare

Purpose: CDN and hosting for the static part of the blablatype.app website, as well as protection against attacks.

What data it sees: technical data about requests to the site, including your IP address, like any CDN provider in the traffic path. Cloudflare may set its own technical cookies for bot protection; see the Cookie Policy for details.

Namecheap

Purpose: VPS hosting for the blablaType backend. These servers run the backend that handles recognition and processing requests.

What data it sees: as a hosting provider, Namecheap supplies the infrastructure on which the service processes data. The host has no direct access to the contents of your requests: data travels over secure connections, and audio and text are not stored on the servers after processing.

Google

Purpose: website traffic analytics via Google Analytics 4. We use it only for statistics, with no advertising features.

What data it sees: anonymized data about site visits (pages, referral sources, technical browser parameters), collected via the _ga and _ga_* cookies. See the Cookie Policy for details.

A separate note about the free web dictation widget on the home page: recognition there is performed by your browser's built-in engine (a Google service in Chrome, a Microsoft service in Edge). This happens directly between the browser and its vendor; audio from the widget never reaches blablaType servers and is not shared with our STT subprocessors.

Lemon Squeezy

Purpose: accepting payments for subscriptions and transcription balance top-ups. Lemon Squeezy acts as the merchant of record, that is, the formal seller for your purchase.

What data it sees: the payment details you enter at checkout, including card data, plus the email used to link the purchase. Card data is processed on the Lemon Squeezy side and never touches blablaType servers.

This subprocessor becomes active once payments are enabled in the service. Until payments are active, no data is shared with it.

Updates to this list

We may add, replace, or remove subprocessors as the service evolves. When the list changes, we update this page and the last updated date at the top.

This list was last updated on June 13, 2026. If you have questions about any subprocessor or want to know more about how your data is processed, write to privacy@blablatype.app.