Privacy policy
Last updated 15 October 2026
dinome works on your computer. It has no servers and no accounts, it collects no analytics, and its developer receives none of your data. Your meetings leave your computer only when you choose: to your own Google Drive, to a folder your sync app uploads, or to ChatGPT or Claude to polish a transcript or write a summary.
Who makes dinome
dinome is made by Mario Semeš (mariosem.es). Questions about this policy or your data: dinome.support@mariosem.es. This policy covers the dinome desktop app for Windows and its Chrome extension.
What dinome keeps on your computer
- Meetings: the transcript and its polished version, the names of who spoke (as Meet shows them), your notes, the summary and, unless you turn off Keep meeting audio, the recording of your microphone and of the call, with a copy of the others' voices cleaned of noise (Clean voices).
- Settings and logs, which the app uses to run and to help you report problems.
- Your API keys and your Google sign-in, if you add them, encrypted with Windows' protection for your user account.
They are stored in %APPDATA%\dinome, or in the folders you choose in Settings → Storage. You can delete a meeting at any time; it goes to the
recycle bin.
The Chrome extension
When you start notes in a Google Meet call, the extension captures the audio of that tab and of your microphone, and reads from the Meet page who is speaking and when you are muted. It sends this only to the dinome app on the same computer (127.0.0.1), and to nothing on the internet. Your microphone is ignored while Meet shows you as muted.
Transcription, polishing and summaries
The speech recognition runs on your computer, and so does cleaning the voices of noise. Nothing is uploaded to transcribe a meeting.
Transcripts are polished and summaries written on your computer too, unless you choose ChatGPT or Claude in Settings. Then, to polish a meeting's transcript or
summarize it, the transcript (and for a summary, your notes; never the audio) is sent to OpenAI or Anthropic with your own API key, under their terms.
Requests to OpenAI are made with store: false.
Google Drive
If you choose Connect Google Drive in Settings → Backup, dinome signs in to your Google account in your browser and talks to Google directly.
What dinome can access
-
Only the files and folders dinome itself creates in your Google Drive (Google's
drive.filepermission). It cannot see, open or change anything else in your Drive. - Your account's name, email address and storage use, to show them in Settings.
What dinome does with it
- Makes a dinome folder in your My Drive and copies your meetings there (transcripts, notes, summaries and recordings), filed by date, with one readable document per meeting.
- Reads them back to restore your meetings on another computer, and to play older meetings whose recording you chose to keep only in Drive.
- Moves a meeting's copy to Drive's trash when you delete the meeting in dinome.
- Shares a meeting's document only when you use Share: with anyone who has the link, or with people you invite (Google emails them). The audio is never shared. You can stop sharing at any time, in dinome or in Drive.
Where your Google data goes
Between your computer and Google only. dinome has no server in between, and the developer never receives your files, your account details or your sign-in. The sign-in is kept on your computer, encrypted.
Removing access
Sign out in Settings → Backup revokes dinome's access. You can also remove it at myaccount.google.com/connections. The files in your Drive stay yours, to keep or delete.
dinome's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Backup to a synced folder
Instead of connecting Google Drive, you can back up to a folder that a sync app uploads (Google Drive for desktop, OneDrive, Dropbox). dinome only writes files into that folder; the sync app uploads them, under its own terms.
Other connections
- Setup downloads: the speech engine (Python and libraries, from GitHub and PyPI), the speech models (Hugging Face), and, if you use them, llama.cpp and a summary model (GitHub, Hugging Face), the voice model for recognising speakers (GitHub) and the denoiser for Clean voices (GitHub).
- Updates: dinome asks git.mariosem.es for the newest version when it starts and every four hours. Like any website, that server sees your IP address; nothing else is sent.
What the developer receives
Nothing. dinome has no analytics, telemetry or crash reporting. If you write to support, your email is used only to answer you, and what you choose to attach (for example a log) only to fix the problem.
This website
This website sets no cookies, has no analytics and loads nothing from other sites; its fonts are hosted here.
Changes
When this policy changes, this page is updated with a new date, and important changes are mentioned in dinome's release notes.