Quill
Home Privacy Terms Support GitHub

Privacy Policy

Effective date: May 13, 2026

Quill is a macOS dictation app. This policy explains what Quill stores locally, what may leave your Mac when you choose to use provider integrations, and how the optional Google Calendar integration works.

No Quill-operated storage server

Quill does not operate a server that stores your transcripts, audio recordings, Google Calendar data, OAuth tokens, or app history. Quill is a local macOS app. App data is stored on your Mac unless you choose to send data to a configured third-party provider or connect Google Calendar.

Local app data

Quill may store the following data locally on your Mac to provide app functionality:

  • Audio recordings and transcript files created by dictation sessions.
  • Run history, including raw transcripts, cleaned transcripts, retry metadata, and related prompts.
  • App context used for transcript cleanup, such as app/window context and screenshot status when context capture is enabled.
  • Settings such as provider configuration, selected transcription language, output language, custom vocabulary, and selected Google calendars.

You can delete run history from within Quill. Deleting history entries also removes associated local audio/transcript files when those files are referenced by the entry.

Transcription and AI provider calls

Quill can use local transcription or provider-based transcription and AI cleanup. Provider calls are made directly from Quill on your Mac to the transcription or AI provider configured in the app. Quill's default OpenAI-compatible provider is Groq, and you can configure another compatible provider in Settings. These provider calls are governed by that provider's own terms and privacy policy.

When you use local transcription, such as Apple Speech or a local Whisper model, audio is processed on your Mac and is not sent to a transcription provider for that transcription.

The data sent to a transcription or AI provider depends on which features you use:

  • Provider-based transcription: when you use API transcription instead of local transcription, Quill sends the audio you record, or a realtime audio stream if realtime transcription is enabled, plus request settings such as the selected transcription model or language.
  • AI cleanup: when transcript cleanup is enabled, Quill sends the raw transcript, cleanup instructions, selected output language, and custom vocabulary you configured so the provider can return cleaned text.
  • Context capture: when context capture is enabled, Quill may send app/window details, visible highlighted text, and screenshot-derived context from the active window so the provider can summarize the writing context for transcript cleanup.
  • Edit Mode: when you explicitly ask Quill to transform text you highlighted in another app, Quill sends that highlighted text and your spoken editing instruction so the provider can return replacement text.

Google Calendar data is separate from these transcription and AI provider calls. Quill does not send Google Calendar event data, selected calendar IDs, or Google OAuth tokens to transcription or AI providers.

Optional Google Calendar access

Google Calendar integration is optional and read-only. If you connect Google Calendar, Quill requests access only so it can show calendars for you to choose from, suggest note titles from calendar events that overlap a live recording, and show local recording reminders based on those events when you enable reminders.

Quill requests these Google OAuth scopes:

  • https://www.googleapis.com/auth/calendar.calendarlist.readonly
  • https://www.googleapis.com/auth/calendar.events.readonly

Quill uses calendar list access to show your calendars in Settings so you can choose which calendars Quill may use. No calendars are selected by default.

For calendars you explicitly select, Quill reads event metadata around live recordings and reminder windows, such as calendar ID, event ID, event title, start and end time, and attendee metadata, including names and email addresses, returned by Google Calendar. Quill uses this data only for calendar-based title suggestions and optional recording reminders.

Quill does not create, edit, or delete Google Calendar events. Quill does not use Google Calendar data for advertising and does not sell Google Calendar data.

Google user data sharing and disclosure

Quill does not operate a server that stores or processes Google Calendar data. Google Calendar API requests are made directly between Quill on your Mac and Google using the OAuth access token stored on your Mac.

The use and transfer of raw or derived user data received from Google Workspace APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Quill does not share, transfer, or disclose Google Calendar data or Google OAuth tokens to transcription providers, AI providers, advertising services, analytics services, data brokers, or other third parties. Google Calendar data is not used to train AI models by Quill.

Google token storage and disconnecting

Google Calendar OAuth tokens are stored locally in the macOS Keychain. Selected calendar IDs are stored locally in app settings. You can disconnect Google Calendar from Quill Settings. Disconnecting removes Quill's stored Google Calendar OAuth token and clears selected calendars.

You can also revoke Quill's Google access from your Google Account permissions page.

Open source and support

Quill is open source. You can inspect the source code at github.com/woosublee/quill. For support, visit Quill Support.

© 2026 Quill.
HomeTermsSupport