QuickCalAI Privacy Policy
Overview
QuickCalAI is a Chrome extension that helps you create and manage Google Calendar events and Google Tasks from text you type or speak, text you highlight, or documents you upload. This policy describes what the extension and its hosted parser handle. It does not claim that all processing stays on your device.
Google account and Calendar / Tasks data
When you choose Connect Google, Chrome’s identity API obtains an OAuth access token for this extension. QuickCalAI uses that token to:
- Create, update, move, and delete events on calendars you own.
- Read calendar lists and event details needed for conflict notices and availability.
- Read free/busy information when event details are not available.
- Create tasks in your default Google Tasks list.
- Read your Google account email so the hosted parser can verify the signed-in account.
Calendar and Tasks writes are sent from the extension to Google’s APIs
(www.googleapis.com and tasks.googleapis.com).
Event and task content you approve or submit can be stored in your Google account
under Google’s own policies.
Text, spoken requests, and documents sent to the hosted parser
Natural-language requests are sent to the hosted service at
https://quickcal-ai.onrender.com (Render). The service worker attaches
your Google access token as a Bearer token so the server can verify the account.
The floating widget does not receive that token.
-
Typed, spoken (after transcription), highlighted, and follow-up text
may be sent to
/parse-eventso an OpenAI model can extract structured event, task, move, delete, or availability fields. -
Microphone audio for voice input is captured in an offscreen document,
kept in memory for the request, and posted to
/transcribe. The hosted service sends that audio to OpenAI’s transcription model and returns text. Audio is not written to disk by the documented backend design. -
Documents (PDF, DOCX, or TXT, up to 2 MB) you choose to upload are
sent to
/extract-documentto read selectable text in memory. Extracted text and your instructions may then be sent to/analyze-documentfor OpenAI-based proposal of events or tasks. Nothing from a document is written to Google until you approve items and ask to create them. Scanned PDFs without selectable text are refused; there is no OCR.
OpenAI API keys stay on the Render service environment. They are not packaged in the extension. The hosted service is designed not to log document contents. It uses in-memory per-account rate limits that reset when the service restarts; it does not use a database for calendar data.
Data stored in Chrome
The extension stores operational state in Chrome storage, including connection and
onboarding flags, draft/retry identifiers for saves, shared conversation state across
tabs, and short-lived document-review text in chrome.storage.session
(cleared when the browser session ends). That storage stays in your browser profile
under Chrome’s controls.
What we do not sell
QuickCalAI is not designed to sell your personal information or to use your Calendar, Tasks, document, or audio content for advertising.
Third parties
- Google — authentication, Calendar, and Tasks.
- Render — hosts the parser, transcription, and document routes.
- OpenAI — language and transcription models called by the hosted service.
Those providers process data under their own terms and privacy policies when requests are sent to them.
Retention
QuickCalAI does not promise multi-year retention of parser request bodies. Render’s disk is ephemeral and the documented backend keeps document and audio payloads in memory for the request. Calendar events, tasks, and extension retry/draft records remain in Google Calendar/Tasks and Chrome storage until you or those systems remove them. Exact provider-side log retention is controlled by Google, Render, and OpenAI.
Your choices
- Disconnect Google from the extension options page to stop API access with the current grant.
- Remove or revoke the extension in Chrome to clear its local storage with the extension.
- Manage or delete Calendar events and Tasks in Google’s products.
- Avoid uploading documents or using the microphone if you do not want that content sent to the hosted parser.
Contact
For privacy or support questions about QuickCalAI, email charleskealey360@gmail.com. The project repository is github.com/Ckealey23/quickcal-ai.