Privacy Policy
Last updated: August 18, 2026
This policy explains what Vtypes does with your data. It covers the desktop application for Windows, the Vtypes keyboard for Android, and this website.
Which parts apply to you depends on how you dictate. Vtypes has two engines, and they are different in the way that matters most here.
- Your own key. You configure a speech provider and a language model, and every dictation goes straight from your device to them. There is no Vtypes account, no Vtypes server in the path, and nothing for us to receive. This is the free tier, and it is how Vtypes has always worked.
- Vtypes Cloud. A subscription that runs those two steps on servers we operate, using our provider accounts, so you need no key of your own. Here your audio does reach us. What we do with it — forward it, return the text, and keep none of it — is section 3.
1. What we collect
With your own key: nothing. Vtypes has no telemetry, no analytics, no crash reporting, no advertising and no advertising identifier. Your copy of the application talks to no service of ours, so we receive no audio, no transcripts, no screen or field contents, no settings and no identifier for you or your device.
With Vtypes Cloud: your audio and the settings that shape the request, for exactly as long as the request takes. What we keep afterwards is described in section 3 and amounts to two counters.
There is no sign-in either way. Vtypes has no account: a subscription is proved by the purchase itself, and we never learn your email address, your name or your Google account.
This website is served as static files. It sets no cookies and runs no analytics.
2. What stays on your device
Unless you are using Cloud, all of it.
- Audio. On the desktop it is held in memory while you hold the shortcut and discarded after transcription. On Android it is written to the app's private storage while the dictation is in flight and deleted as soon as the dictation finishes, unless you switch on "keep audio", which is off until you turn it on.
- Transcripts. Kept on the device if you keep history — a local database on the desktop, the five hundred most recent dictations on Android. You can clear history in the application, and uninstalling removes it.
- Context. The text Vtypes reads to build the post-processing prompt — the focused window on the desktop, the field you are dictating into on Android — is used for that one request and not retained.
- API keys. Stored on the device, in your operating system's credential storage where available. They are sent only to the provider they belong to.
Nothing in that list is readable by other applications: on Android it lives in the app's private storage, and the app does not back it up to the cloud.
3. When data leaves your device
With your own key
Only to a service you pointed Vtypes at yourself, and only with your own key.
- Transcription. Your audio goes to the speech-to-text endpoint you configured.
- Post-processing. The transcript, your chosen style and vocabulary, and — if you have enabled context — the context text go to the language model you configured.
The request goes directly from your device to that provider. We are not a party to it and have no access to your account with them. What that provider does with the data is governed by their privacy policy, not this one — read it before you configure one, particularly if you dictate confidential material.
With Vtypes Cloud
Your dictation goes to a Vtypes server first, and from there to the same kind of provider — ours instead of yours.
What we receive. The recording, and the settings that shape how it is written: your chosen style, the dictation language, your vocabulary list, the name you set if you set one, and the surrounding field text if you have context switched on.
What we forward, and to whom. The recording goes to Groq for transcription; the transcript and those settings go to Groq for post-processing. They are the only third party in this path, and the only place a Vtypes host name for this service appears in the source is one file, so the claim is checkable rather than merely stated.
What we keep. Two counters and an identifier: how many seconds of audio your subscription has used in the current period, how many requests it has made, and an identifier derived from your purchase by a one-way function with a secret we hold. That identifier cannot be turned back into your purchase, your account or you. We do not store your audio, your transcript or the text we return. They exist while the request is being served and are gone when it ends.
What our logs contain. The size of the recording, how long each step took, an outcome code, and the first few characters of that identifier. No transcribed or generated text, no vocabulary, no field context, no name.
What we can see. We are not claiming that we cannot read your dictation while we are serving it — the service has to hand your audio to a speech model and read the text back. We are saying we keep none of it. If that distinction matters for what you dictate, use your own key, where we are not in the path at all.
If you configure nothing
- The desktop application can transcribe on the device with a local model and post-process with a local one, so it can run without sending anything anywhere.
- The Android keyboard has no on-device model. It dictates either with a key you supply or with a Vtypes Cloud subscription; without one of the two it cannot dictate at all.
4. Reading context
Vtypes can read text you already have on screen and use it to disambiguate what you dictated. It is off until you turn it on, in the application's settings.
On the desktop it reads the visible text of the focused window, through the operating system's accessibility interface — the same interface screen readers use.
On Android it reads only the field you are dictating into: up to two thousand characters either side of the cursor, through the standard input-method interface. It never reads a password field, it never reads an application you have put on the exclusion list, and before any of it is sent, card-shaped runs of digits and lines that label a secret — password, api key, token and the like — are replaced with [REDACTED]. That redaction happens on your device, before the text goes anywhere, including to us.
Treat the capability with the caution it deserves. If what is on screen is something you would not paste into a hosted model, turn context off, or use a local post-processing model on the desktop, which keeps the text on the machine.
5. What the Android keyboard does not do
It has no letter keys and no typing surface, so there is nothing for it to record: it does not log keystrokes, and it cannot see what you type on any other keyboard. It does not read your screen, your other applications, your contacts, your files, your location or your clipboard.
It asks for two Android permissions and no others — the microphone, to hear the dictation, and network access, to reach either the provider you configured or Vtypes Cloud.
6. Children
Vtypes is not directed at children. Every provider it can be pointed at requires an adult account under its own terms, and the Android listing is marked for adults.
7. Deleting your data
There is no account to delete. Clearing history in the application removes stored transcripts; uninstalling removes everything Vtypes has kept on the device, including your saved keys.
If you have used Vtypes Cloud, what remains on our side is the identifier and the two counters described in section 3 — no content. Write to the address below and we will delete that row; cancelling the subscription stops it being written to.
8. Payment
A Vtypes Cloud subscription is bought through the platform's own store, which handles the payment and tells us only that a subscription is valid. We never see your card, your billing address or your email address.
9. Changes
If this policy changes, the date at the top changes with it. Because we hold no contact details for you, we cannot notify you individually; the current version is always the one on this page.
10. Contact
Questions about this policy: [email protected].