QuickCalAI Privacy Policy

Last updated: November 16, 2026

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:

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.

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

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

Contact

For privacy or support questions about QuickCalAI, email charleskealey360@gmail.com. The project repository is github.com/Ckealey23/quickcal-ai.

Back to QuickCalAI