Privacy Policy
Quietly (“we”, “our”, or “the app”) is a desktop application for macOS that records, transcribes, and cleans up meetings locally on your Mac. This Privacy Policy describes the limited data the app handles.
1. Summary
- We do not operate any server that stores your meeting audio, transcripts, or notes.
- Speech-to-text, speaker-turn separation, and transcript cleanup all run on your Mac. Audio and transcripts never leave the device unless you copy them out yourself.
- Optional integrations (Google Calendar, software updates, payments) communicate with third parties only for the specific purpose described below, and never carry your meeting content.
-
The app runs no analytics, advertising, or behavioural telemetry — no
analytics or crash-reporting SDK is built into it, and nothing about
your meetings is ever measured. Our marketing website
(
meetquietly.com) uses privacy-friendly, cookieless analytics (Vercel Web Analytics) to count aggregate visits and download clicks; it sets no cookies, identifies no individual, and is entirely separate from the app and your meeting content.
2. Data controller
For the purposes of GDPR and the Personal Information Protection Act of the Republic of Korea (“PIPA”), the controller of any personal data processed under this policy is the operator of Quietly, based in Seoul, Republic of Korea. You can reach us at support@meetquietly.com.
3. Data we process
3.1 Meeting recordings and transcripts
When you start a recording, audio is captured by the Quietly macOS
helper and saved as WAV files in a folder you choose on your Mac
(default: ~/Documents/Quietly). Transcription is run
locally by a bundled whisper.cpp binary using a model
cached at ~/.cache/whisper.cpp. The resulting Markdown
note is written next to the audio file. None of this content is
transmitted to us.
3.2 On-device speaker-turn separation
To split the transcript into speaker turns, Quietly runs
sherpa-onnx locally with a segmentation model (and, as
finer per-speaker labeling rolls out, a speaker-embedding model), cached
at ~/.cache/sherpa-onnx. Audio is processed in a child
process on your Mac; no audio is sent to any external service.
3.3 On-device transcript cleanup
Optional transcript cleanup (removing fillers, fixing broken
sentences, normalising punctuation) is performed by a compact
open-weights LLM that runs locally via llama.cpp. The
model is cached at ~/.cache/llama. Your transcript is
never sent to OpenAI, Anthropic, Google, or any other LLM provider by
Quietly itself.
3.4 Settings and tokens
Application settings (preferred microphone, notes folder path,
calendar preferences) are stored in your application support
directory at
~/Library/Application Support/Quietly. When you connect
Google Calendar, the OAuth refresh token is encrypted with the macOS
Keychain (via Electron safeStorage) before being saved
locally.
3.5 Optional Google Calendar integration
Quietly offers two calendar sources side by side: macOS Calendar (EventKit), which reads your local Apple calendars only and makes no network requests at all, and Google Calendar, which is fully optional. Bot-style auto-join of cloud meetings (Zoom, Meet, Teams) is out of scope; we capture audio locally on your Mac instead.
If you opt in to Google Calendar, Quietly requests the
https://www.googleapis.com/auth/calendar.readonly scope
via the standard Google OAuth loopback flow. The token is used only to
read your upcoming events so the app can pre-populate the meeting
list. Calendar data is held in memory for the current polling cycle
and is not persisted to disk beyond the cached event titles you see
in the app. Calendar metadata is never sent to our servers, because
we do not operate any.
The Google OAuth refresh token itself is stored on your Mac, but
encrypted by Electron safeStorage (which uses the macOS
Keychain) and written to
~/Library/Application Support/Quietly/secrets/google-refresh-token.bin.
settings.json and other plain-text configuration files
do not contain any token. When you disconnect Google Calendar from
within the app, the encrypted token file is deleted immediately.
3.6 Software updates
Quietly checks for new releases by querying our public GitHub
Releases feed (roughly every four hours, plus on launch). The check
exposes your Mac’s public IP address and a generic
User-Agent string to GitHub, but no application data.
3.7 Crash diagnostics
The Electron crash reporter is configured with
uploadToServer: false, so crash dumps are written to
your Mac for your own troubleshooting and are never
uploaded automatically. If you choose to send a diagnostic file to
support manually, it is reviewed and then deleted.
3.8 Paid license activation
When you purchase and activate a paid license, Quietly sends your license key and a device label to our payments provider (Lemon Squeezy) for verification. The device label distinguishes the Mac you activated: it is made up of your computer’s hostname and a short, random install identifier the app generates and stores locally. It is not derived from any hardware property, and is used only to show which Macs are activated and to enforce the per-license device limit (two Macs).
While the app is running it re-validates your license roughly every six hours, and again when your Mac wakes from sleep, by sending the license key and the provider-issued instance ID. Removing the license from a Mac releases that seat using the same two values. No meeting content (audio, transcripts, or notes) is ever part of activation, validation, or deactivation traffic, and all requests go directly to Lemon Squeezy — we operate no intermediary server.
4. Third parties
- Google — only when you opt in to Google Calendar. Subject to Google’s Privacy Policy.
- Hugging Face — first-run download of the speech-to-text, speaker, and cleanup models from public repositories. Standard CDN request; no account required.
- GitHub — release feed for software updates and the speaker-embedding model.
- Lemon Squeezy — our payments provider for paid license checkout and validation. Subject to Lemon Squeezy’s Privacy Policy.
5. Retention
Because your recordings, transcripts, and notes live on your Mac,
retention is controlled by you. Delete the relevant files in Finder
to remove them. Logs in
~/Library/Logs/Quietly are rotated by electron-log and
may be deleted at any time. OAuth refresh tokens are removed when
you disconnect Google Calendar from within the app.
6. Your rights
If you are located in the European Economic Area or the United Kingdom, GDPR gives you the right to access, rectify, erase, restrict, port, and object to processing of your personal data, and to withdraw consent at any time. You may also lodge a complaint with your local data-protection authority.
If you are located in the Republic of Korea, PIPA gives you the right to request notification of how your personal data is processed, to access and obtain a copy of it, to request correction or deletion, and to request suspension of processing.
In practice, almost all of your data stays on your own Mac, so you can exercise most of these rights directly: delete files in Finder, revoke calendar access from within the app or your Google Account page, or uninstall the app. For questions, or to exercise any right that requires our involvement, write to support@meetquietly.com and we will respond within 30 days.
7. International transfers
Quietly does not transfer your meeting content anywhere. The third parties listed in §4 may be located outside your country of residence. By using the relevant optional feature you consent to the limited transfer that feature requires (for example, the round trip between your Mac and Google when you read your calendar).
8. Children
Quietly is not directed at children under 13 (or under 14 in the Republic of Korea). We do not knowingly process personal data of children.
9. Changes to this policy
We may update this Privacy Policy as the product evolves. Material changes will be highlighted in the release notes for the affected version, and on the Korean version of this page at the same time.
10. Contact
For privacy questions, write to support@meetquietly.com.