Privacy Policy
IntelliScribe AI · last updated September 6, 2026
IntelliScribe AI is a Chrome extension that turns speech into text and checks spelling and grammar as you type, with a companion web app at intelliscribe-app.netlify.app. This policy covers both. It explains what data they handle, where it goes, and how you can delete it.
Summary
- By default your audio and your text are processed entirely on your device. Nothing is uploaded.
- Cloud features are opt-in and use your own API key for the provider you choose.
- History (and, so you need not paste them twice, your own API keys) are synced to an account only if you sign in.
- We do not collect analytics, do not track browsing, and do not sell or share data.
What the extension processes
Microphone audio
When you start dictation or a recording, the extension captures your microphone. Audio is converted to text by a Whisper speech-recognition model that runs inside the extension on your computer (WebGPU/WebAssembly). Audio is held in memory only for the duration of the recording and is discarded afterwards. It is not stored and not transmitted — unless you have enabled a cloud provider (below).
Speech model download
The first time you use local transcription, the model files (neural-network weights) are downloaded from huggingface.co and cached in your browser's storage. This request contains no personal data. You can delete the cache from Settings → Transcription → Model & speed.
Writing checks
When writing checks are on for a page, the extension reads the text of the field you are typing in — and only that field — to underline spelling and grammar mistakes and offer fixes. The dictionaries, word lists and rules ship inside the extension and run on your device. Nothing from the field is transmitted or stored, apart from the words you deliberately add to "Your words" (kept in your settings). Writing checks never run on password or payment fields, and banking sites and school portals are excluded even if you allow checks on all sites.
The same applies to the full-page Writing Pad in the extension and to the Write tab of the web app: the checker runs in your browser (the web app fetches its word lists from our own site once), and what you write is not sent anywhere and not saved by us.
Dictation history
Text you dictate is saved on your device (chrome.storage) together with the title and address of the page you dictated on, so you can find it again in the History tab. This stays on your device unless you sign in (below). You can delete entries individually or clear everything in Settings → General → Data & privacy.
Right-click AI actions (Fix grammar, Rewrite, the tone options, Shorten, Summarize) save the text you selected and the result to that same history, so you can find and reuse them. The same rules apply: on your device unless you sign in, and you can delete any entry from History.
Optional cloud providers
If you enter an API key for Google Gemini, Groq, OpenRouter, Anthropic (Claude) or OpenAI in Settings, then:
- recordings longer than your chosen threshold (or any recording, if you choose cloud transcription), and
- text you send to an AI action — Fix grammar, Rewrite, tone changes, Shorten, Summarize, Key points, or the result chat
are sent over HTTPS to that provider (generativelanguage.googleapis.com, api.groq.com, openrouter.ai, api.anthropic.com or api.openai.com) using your key, and are subject to that provider's privacy policy. Your key is stored only in the extension's local storage on your device and is sent only to the provider it belongs to. Remove the key in Settings to stop all cloud processing.
Optional account and sync
If you sign in (Google, or email and password), the extension stores your saved transcripts and dictation history (text, title, cleaned text, summary, key points, page title and address, timestamps) in our database, hosted on Convex (convex.cloud), linked to your account, so they are available on your other computers. Any API keys you have entered are stored in the same private account record so your other computers can use them too; they are sent only to your own signed-in devices and to the provider each key belongs to. Your email address is used only to identify your account. Every database function checks the signed-in user and returns only that user's rows; nobody else, including other users, can read them. Without signing in, nothing is sent to our database.
Signing in from the extension opens our web app in a browser tab. When you finish signing in there, the page passes the session to the extension and nothing else; the extension accepts it only if you asked for it from the side panel moments before.
The web app
The web app (intelliscribe-app.netlify.app/app/) works without an account: its Write tab, history and settings stay in your browser's local storage. Sign in and the same sync rules as above apply. Our public pages load their typefaces from Google Fonts, which means Google receives the usual web request (your IP address) when a page opens; the web app itself and the extension ship their own fonts and make no such request.
Settings
Preferences (colour scheme, dictation quality and language, writing rules, allowed sites, thresholds) are stored locally with chrome.storage / localStorage.
What the extension does not do
- No analytics, telemetry, crash reporting or advertising.
- No reading of web pages beyond the text field you are typing in, and only while writing checks are on for that page.
- No selling, renting or sharing of data with third parties.
- No remote code: all code ships in the extension package.
- No web-app sign-in that the extension did not ask for: a session is accepted only after you click "Sign in in your browser", and then only from our own site.
Deleting your data
- Local data: Settings → General → Data & privacy → Clear local data (history, settings, keys); Settings → Transcription → Model & speed → delete the model cache; or uninstall the extension, which removes all extension storage.
- Synced data: delete items from History, remove a key in Settings (the account copy is updated at once; a second computer that still holds the key keeps it until you remove it there too), or email the address below to have your account and all its rows deleted.
Children
The extension is not directed at children under 13. Schools deploying it for students should keep the default (no account, no API key), in which case no data leaves the device.
Changes
We will update this page and the "Last updated" date when the policy changes.