Privacy and Google Calendar data

Knotlet is a private, single-owner personal knowledge application.

What Calendar access is used for

With the owner’s consent, Knotlet reads the list of accessible calendars and imports events from calendars the owner selects. Imported information includes event titles, descriptions, locations, dates, timezones, recurring-event identifiers and cancellation status. It supports a personal timeline, search and connected knowledge. Knotlet does not create or change Google Calendar events.

Storage and access

Cloudflare hosts the application and its private synchronization service. Supabase stores imported knowledge. Google authorization credentials are stored separately from the knowledge records. Access to imported records requires the owner’s account or an integration the owner has explicitly authorized, such as a connected assistant using Knotlet MCP. Calendar data is not sold or used for advertising.

Performance monitoring

Cloudflare Web Analytics measures page loading and responsiveness. Cloudflare Workers logs and traces help diagnose slow requests and errors. Application spans label authentication and operation names; they do not include record contents. Knotlet does not record session replays.

Control and retention

The owner chooses which calendars to synchronize and can stop synchronization in Settings or revoke access through their Google Account. Disconnecting removes the saved Google credentials and stops further imports. Imported records and history are retained until the owner removes them; existing backups may retain earlier copies. The owner can export their knowledge and manage records through the private workspace.

Knotlet’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Updated 18 September 2026.