This private technical proof tests connections to Google Calendar and Microsoft calendars. It is not a full calendar planner or a production service.
The proof requests access to list calendars and to read and change events. Its write controls are restricted to disposable entries created through this proof. Calendar names are used for selection. Event reads request identifiers and times, not personal event titles; personal titles are not returned or cached. Reads return total event counts and the times of saved proof entries.
Cloudflare Workers runs the proof. Cloudflare D1 stores encrypted access and refresh tokens, short-lived OAuth state, proof event identifiers and times, and an operation history. Tokens are encrypted with an application key held as a Worker secret. Calendar names are not saved in D1. Operation history and proof metadata remain until the operator removes the proof database; this spike does not have automated retention deletion. The browser session lasts two hours.
The proof does not sell data, use it for advertising, or send calendar data to an LLM. Worker observability logging is disabled in the supplied configuration. Cloudflare and the calendar providers still process requests to operate their services.
Delete all staged and created proof entries before using Disconnect. Disconnect removes the proof's stored provider tokens and pending OAuth state; it does not revoke consent at the provider or remove the operation history. You can revoke the application's access separately in your Google Account or Microsoft account/application settings.
Contact the proof operator: gather-plans-support@googlegroups.com
An operator can issue a private, one-use connection link that expires after 15 minutes. Its random token is stored only as a hash in D1 and sent in a URL fragment, then removed from browser history when opened. Anyone holding an unused link can redeem it, so share it only with the intended account holder. Redemption creates a separate restricted 30-minute session: it can connect the specified provider, list that connected account's calendars, and save selected source and destination calendar IDs. It cannot use the operator controls or run event tests. Selected IDs and connection-session metadata are stored in D1; expired session records are removed when later invitations are created. Calendar consent and stored tokens persist after this page session expires until cleanup/disconnect or provider revocation.
This notice describes the proof only and requires review before any wider or production use.