Legal
Privacy Policy
Wispra turns your voice into text. This page says what Wispra handles, where it goes, who else sees it, and how to get rid of it.
Effective November 10, 2026
On this page
The short version
- No ads, no tracking, no analytics. None of the Wispra apps contains an advertising, analytics or crash-reporting kit, and we do not sell what you say or write or use it to train AI models.
- Two ways to run Wispra. On the desktop you can use your own Groq key: audio goes from your computer straight to Groq and never reaches Wispra’s server. Or you sign in and use Wispra Cloud, which is what the phone app always does: audio and text pass through Wispra’s server to Groq and are not kept there.
- Your account holds little. Your email address, a user ID, your plan and usage counts. On the desktop, History and meetings are copied to it only when you turn sync on; the phone app copies your dictations and notes to it once you sign in.
- You can delete it. Entries from History in any app, or the whole account (see Delete your account).
This policy covers the Wispra desktop app (Windows and macOS), the Wispra phone app and its keyboard, Wispra Cloud (the server behind the apps), and this website. Wispra is operated by Sinh Giang, an individual, who is responsible for your data under this policy and can be reached at support@timio.vn. “Wispra”, “we” and “us” mean Sinh Giang.
What Wispra handles
| Data | Why | Where it lives |
|---|---|---|
| Microphone audio | To turn your speech into text. Wispra records only when you start a dictation, a note or a meeting recording. | On your device. Sent for transcription (next section), never uploaded to be stored. |
| Text: transcripts, notes, summaries | The result of transcription and of the AI features you use (cleanup, summaries, mind maps, posts, chat about a recording). | On your device. Copied to your account when sync is on (desktop) or once you sign in (phone). |
| Email address and user ID | To sign you in with Google and to tell your account from others. | In our database provider’s sign-in system (Supabase). |
| Plan and Polar customer and subscription IDs | To know whether you are on Free or Pro and when the paid period ends. | In your account (Supabase). Payment itself happens at Polar. |
| Usage counts | To apply the monthly limits of your plan and to stop abuse: seconds of audio transcribed and AI tokens used each month, and requests in the current minute and day. | In your account (Supabase). Numbers only, never content. |
| Synced copies | To show your dictations, notes, meetings, learned words and custom vocabulary on your other devices and to your AI assistant. | In your account (Supabase): from the desktop only when you turn sync on (off by default); from the phone app, dictations and notes once you sign in. |
| AI assistant link (optional) | To let an assistant you choose (ChatGPT, Claude and others) read your synced data, read-only. | Only a hash of the link is stored, with its dates. The link itself is shown to you once. |
We do not ask for your name, phone number, contacts, photos, location or advertising ID, and the apps do not read them.
Where your audio and text go
Wispra needs an AI service to understand speech and to clean up or summarise text. That service is Groq, a third-party AI provider. What is sent depends on how you run Wispra:
With Wispra Cloud (signed in)
The app sends the audio of a dictation, or the text of a note or meeting you ask the AI to work on, to Wispra’s server. The server checks your plan and limits, forwards the request to Groq with Wispra’s own key, and returns the answer. It does not save the audio or the text. What it records is the size of the request, the model used, the time it took and the status, to keep the service running; those log lines hold no audio, no text and no user ID. The phone app always works this way.
With your own key (desktop)
Audio and text go from your computer directly to the provider whose key you entered (Groq or OpenAI). Wispra’s server is not involved and sees nothing.
Groq’s own handling
Once Groq receives audio or text, Groq’s terms and privacy policy apply. We do not control what Groq does with it. Read them at groq.com.
Who else is involved
Wispra uses these services. We pass each only what it needs for its job:
| Service | What it does for Wispra | What it receives |
|---|---|---|
| Groq | Speech-to-text and AI text. | The audio or text you send for processing, as above. |
| Supabase | Our database and the sign-in system. | Your account details and the data in the table above that lives in your account. |
| Sign-in. You choose “Continue with Google”. | Google knows you signed in to Wispra. Wispra receives your email address and a user ID from the sign-in. On this website, Google Fonts also receives your IP address when a page loads the Inter typeface. | |
| Polar | Payment for the Pro plan. | What you enter at checkout. Card details go to Polar; Wispra never sees them. Polar tells us your plan status, your email address and its customer and subscription IDs. |
| Vercel | Hosts this website and Wispra Cloud (servers in Singapore). | Standard request records such as your IP address and the time, kept under Vercel’s own policy. |
| GitHub | Hosts the downloads, the release notes and the public issue tracker. | Whatever you post there, and your IP address when you download. |
We do not sell your data, rent it, or share it for advertising. Data may be processed outside your country, because these providers run their own systems.
How long things are kept
| What | How long |
|---|---|
| Audio sent through Wispra Cloud | Not kept by Wispra’s server. It is forwarded and forgotten. |
| Recordings on your device | Desktop: removed once the text is saved to History. If transcription failed, the recording is kept so you can try again, and removed after 2 days or when you delete it. Phone: stored on the phone until you delete the entry. |
| Text on your device | Until you delete it or uninstall the app. |
| Copies in your account (sync) | Until you delete them or delete your account. Deleting a History entry or clearing History in an app removes it from your account too and from every device signed in to it. |
| Email address, user ID, plan, usage counts | As long as your account exists. Deleting the account removes them. |
| AI assistant link | Until you revoke or replace it, or it expires. A link made without a chosen expiry stops working after 90 days. |
| Server logs | Short technical lines (sizes, status, timings) with no audio, text or user ID, kept by our hosting provider under its own schedule. |
Your choices
- See your data. History, notes, meetings and learned words are in the apps. Desktop History can be exported to TXT, Markdown or CSV.
- Delete entries. Delete one History entry or clear all of it. When you are signed in, this also removes the copy in your account and on every other device.
- Turn sync off in the desktop app (it is off by default). Copies already in your account stay there until you delete them or your account.
- Use your own key on the desktop if you do not want audio to pass through Wispra’s server.
- Revoke the assistant link in the app’s Connections page. It stops working at once.
- Delete your account. See Delete your account.
Depending on where you live (the EU, the UK and California, for example) you may also have the right to ask for a copy of your data, to have it corrected, or to object to how it is used. Write to us (see Contact) and we will answer within the time the law gives us.
Microphone and the phone keyboard
Wispra records only after you start a recording: the hotkey or the microphone button on the desktop, the microphone button in the phone app, or the microphone key on the Wispra keyboard. The phone asks for permission the first time; you can take it back in the phone’s Settings.
Allow Full Access (iPhone). iPhone asks you to switch it on so the Wispra keyboard can receive the words the Wispra app hands to it. Typing letters works without it. The keyboard keeps no record of what you type and sends none of it anywhere; only what you say after tapping the microphone is sent to Wispra Cloud, to turn it into text. The Android keyboard works the same way and skips password fields.
Children
Wispra is not meant for children under 13, and we do not knowingly collect data from them. If you believe a child has given us data, contact us and we will delete it.
Security
The apps talk to Wispra Cloud over HTTPS. The database tables behind your account are locked with row-level security and are read and written only by Wispra’s server, on behalf of the signed-in user. Assistant links are stored as hashes. No system is perfectly secure, so keep your own devices and Google account protected.
Changes to this policy
When this policy changes we change the “Effective” date at the top, and for a significant change we also say so on the Updates page.
Contact
Questions about privacy, or a request to see, correct or delete your data:
Write from the address you use to sign in to Wispra. Never send a password, an API key or a recording.