Data practices

Privacy policy

This policy describes Calendar Dispatch, the personal calendar integration operated by the owner of shanks.cloud, and this informational website.

Calendar information accessed

With account-holder authorization, the private connector reads approved Google Calendar and Microsoft 365 calendars. It uses event identifiers, titles, start and end times, all-day dates, calendar time zones, cancellation state, availability and privacy classifications to prepare agendas and detect overlaps. Google calendar-list access is used during operator setup to identify the intended shared calendar.

The current event reader does not request event descriptions, attachments, attendee lists or conferencing details. Private or confidential events have their titles and identifiers redacted in the connector's output while retaining scheduling information.

Permissions and use

Information is used to provide the requested calendar briefings, scheduling assistance and operational troubleshooting. The current Google authorization includes event read/write permission and read-only calendar-list access. That Google permission is broader than the application's current behavior: the connector enforces an approved-calendar list and exposes read-only tools, not event creation, editing or deletion.

Calendar Dispatch's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The application does not sell calendar data or use it for advertising.

Processing and sharing

The private service processes calendar information on the operator's host. Briefings, including event titles and times, are sent to the Discord destination selected by the operator and are visible to people with access to that destination. Discord processes and stores these messages under its own terms and privacy policy.

When calendar information is used in a conversation with the operator's assistant, relevant content may also be processed by the configured assistant and model providers. Scheduled briefing generation itself uses a deterministic reader, not a language model. The operator must consider the selected destination and provider settings before sharing calendar information.

Storage and retention

Provider authorization credentials are kept separately from this website in the operator's secret-management system, Doppler, and used by the private service. Credentials are not embedded in the public Worker. The operator's administrative access to the host and deployment can access runtime credentials.

The private host retains the latest generated briefing and report, and operational records used for troubleshooting. Latest-report files are replaced by subsequent runs; previous messages, conversation history, diagnostic artifacts or backups can remain until removed. There is no automatic deletion period promised here. Discord and other service providers apply their own retention rules.

Public website

This website serves informational HTML pages through Cloudflare. Its application code sets no cookies, embeds no analytics or third-party scripts, collects no form submissions, and makes no calendar API calls. Cloudflare may process connection information such as IP addresses and request metadata to deliver and protect the site.

Your choices and contact

You can revoke the application's Google authorization through your Google Account connections. Revocation prevents future authorized reads but does not delete briefings already delivered or retained copies. Contact the operator using the support email shown on the OAuth consent screen or your existing direct contact to request disconnection, access to retained information, correction or deletion of operator-held copies. Provider-held copies are subject to the applicable provider's controls.

This is a personal-use integration, not an open-registration service. Changes to its data practices should be reflected in this policy before the changed processing begins.