Data handling

Privacy policy

Effective September 30, 2026.

This policy describes Quill, the private Discord meeting assistant operated by the Quorum team. It covers Quill's meeting workflow and Google connection. Quill is available to invited team members, with Google authorization managed by the operator.

What Quill processes

• Discord speaker audio, account identifiers, display names, relevant team roles, voice-room membership, and meeting timestamps.
• Transcripts, decisions, action items, scheduling intentions, summaries, and any gaps or errors in a recording.
• Configured Calendar attendee addresses and relevant event information, including titles, dates, participants, locations, links, and creation receipts.
• Drive archive file identifiers and upload receipts; local operational records used to recover interrupted work and avoid duplicate posts or events.

Where data goes and why

• Operator's Mac: Quill records audio and runs Whisper locally to create the transcript. Working files and recovery records are stored on this Mac.
• Google Drive: compressed recordings, transcripts, a recording index, and recaps are uploaded to the configured Meetings archive. The archive begins in the operator's personal My Drive. It is private unless the operator explicitly grants access.
• OpenAI through ChatGPT/Codex: transcript text and the context needed to review it are processed to produce recaps and authorized scheduling requests. That context can include speaker identifiers, configured attendee addresses, and Calendar results. Quill's normal workflow does not send raw audio to OpenAI.
• Google Calendar: Quill reads relevant existing events to avoid duplicates and creates authorized new ad hoc team meetings. Calendar invitations expose event details to the configured attendees.
• Discord: recording notices, recaps, action items, Calendar outcomes, and archive links are posted in the configured private team channels. People with channel access can read those messages.

These services process the data they receive under their own terms and the operator's account settings. Quill does not sell meeting data, use it for advertising, or run a model-training feature. This is not a promise about every provider's separate account-level retention or data settings.

Google permissions

drive.file allows Quill to create its archive and manage files created by or explicitly authorized for the app. It does not provide general access to unrelated Drive files. calendar.events allows event access on calendars the operator can access; Quill's implementation limits its work to the configured calendar and attendees, and to new ad hoc meetings. It does not edit or delete recurring meetings.

Google data is used for the archive, scheduling, recap, and recovery features described here. Use and transfer of Google API data is subject to the Google API Services User Data Policy, including its Limited Use requirements.

Recording controls and access

Quill posts a visible notice when recording starts. /quill stop ends the current session, and Quill leaves when fewer than two eligible team members remain. Anyone joining a room while recording is active may be captured. Arrange an unrecorded conversation with the organizer when needed. The operator can pause the bot and scheduled processing, or revoke its Google access in Google Account settings.

Google and Discord credentials are stored in macOS Keychain. Archive access and Discord channel permissions are controlled separately by the operator. A link in a Discord recap does not by itself grant Drive access.

Retention, corrections, and deletion

Local working recordings and transcript files are removed after their required processing finishes and archive uploads are verified. Failed uploads or incomplete operations retain working data for recovery. Operational records, including scheduling evidence excerpts and creation receipts, may remain locally after working-file cleanup.

The Drive archive, Discord recaps, Calendar events, and ChatGPT/Codex conversation records have no Quill-enforced automatic deletion period. They remain until the operator removes them, subject to each service's retention and backup behavior. Deleting a file from one destination does not automatically remove copies or derived notes from the others.

For access, correction, or deletion requests, contact the Quorum Discord server owner through your existing team access. Identify the meeting and requested change. The operator handles the request across the relevant destinations and explains any remaining copies or limitations.

This information site

These static pages contain no account login, meeting data, forms, advertising, analytics scripts, or application cookies. The hosting provider may process ordinary request information, such as an IP address and browser details, to deliver and protect the site.

Changes

Changes to the workflow or its data uses will be reflected here and communicated to the team. A new use requiring additional authorization will be introduced only after that authorization is obtained.