Privacy

Quill has no servers. There is no account, no analytics, and no telemetry. Nobody but you can see your meetings, because there is nowhere for them to go.

Last updated 26 July 2026

What the Chrome extension reads

The extension exists to notice that you are on a call and to relay two buttons — start and stop — to the Quill app running on your own Mac. To do that it reads:

• The URL and title of tabs on the supported meeting sites, to tell a meeting apart from a calendar page or a landing page.
• The numeric tab ID, so a recording is tied to the tab that started it.
• Whether the page is showing in-call controls — for Google Meet, the presence of the hang-up button. This is a structural check on the page, not a reading of its contents.

What it never reads

• Meeting chat, captions, or participant names.
• Page text, form fields, cookies, or credentials.
• Your browsing outside the meeting sites listed below. The extension has no access to any other site.

The extension never touches your microphone or camera. Audio capture is done by the Quill app on your Mac, under macOS's own microphone and system-audio permissions, which you grant separately and can revoke in System Settings.

Where your data lives

Audio, transcripts, and notes are written to folders on your Mac that you choose during setup. Transcription runs on-device. The extension talks to one address and one address only — http://127.0.0.1:8787, a loopback address that never leaves your computer.

The one step that reaches the internet is the last one: Quill hands the finished transcript to Claude Code to write your note, which sends it to Anthropic under Anthropic's privacy policy. Everything before that is local. If you do not want that step, run meet stop --no-process and keep the transcript alone.

What is stored in Chrome

The extension keeps your preferences — the local server address, which meeting sites are enabled, and whether it may prompt automatically — in chrome.storage.sync. If you are signed into Chrome, Google syncs that between your own browsers. It holds settings only, never meeting content.

Permissions, and why each one exists

• storage — saves the preferences described above.
• tabs — lets the background worker follow a meeting tab as it opens, changes, and closes. activeTab would not work, because a call often continues in a tab you are not looking at.
• Host access to meet.google.com, *.zoom.us/wc/*, teams.microsoft.com, teams.cloud.microsoft, and *.webex.com — detects calls on those sites and draws Quill's panel there.
• Host access to 127.0.0.1:8787 — reaches the Quill app on your own machine.

The extension does not request <all_urls>, scripting, microphone, camera, downloads, or history.

Consent

Quill records every participant on a call, not only you. In many places that requires their consent, and many employers require it whatever the law says. Asking is on you.

Changes

Quill is open source. Every change to this policy and to the code behind it is public in the repository. Questions go in the issue tracker.