Privacy policy

Calsync is a private calendar availability utility operated by Michal Trzcinka. Questions or deletion requests can be sent to michal@trzcinka.pl.

Google account access

Each account independently authorizes access through Google OAuth. Calsync uses the account email and verified identity to check that the intended account signed in. Its Calendar permission allows reading and editing events on calendars owned by that account.

Information used and stored

The service reads calendar events to determine availability, including event times, recurrence information, cancellation, free/busy settings and the account holder's invitation response. It stores minimal event identifiers, recurrence identifiers, start and end times, calendar time zones, sync cursors, generated-block mappings and operational state in AWS DynamoDB. Source meeting titles and descriptions are not stored in the sync database.

OAuth refresh tokens and client credentials are stored in encrypted AWS Systems Manager Parameter Store values. Access is limited through AWS account permissions. Operational errors are sanitized rather than logging event contents.

How availability is shared

Calsync creates a separate private Busy event on each other configured calendar using that destination account's credentials. Copies contain availability times and opaque technical metadata; they do not include source meeting titles, descriptions, attendees, locations, meeting links or source-account identifiers. Existing calendar sharing settings are not changed. Google Workspace administrators may retain access allowed by their organization's policies.

Google processes calendar and authorization data, and AWS hosts the service and its stored state. Calsync does not sell Google user data or use it for advertising or AI model training. Its use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Retention and removal

The service maintains a rolling availability window. Completed historical mappings are normally pruned after 30 days and old snapshots are replaced. Fully past generated calendar blocks remain unless explicitly cleaned up. Paused services and retained AWS resources can keep data until the operator deletes it. OAuth credentials remain in Parameter Store until removed.

Access can be revoked in the Google Account third-party connections settings. Revocation stops future access but does not itself delete existing AWS records or calendar copies. The operator can pause synchronization, remove generated blocks with Calsync's cleanup command, and delete retained database records and credential parameters.

This website

These informational pages contain no sign-in form, advertising or analytics scripts. AWS may process network information, such as IP addresses and request headers, to deliver and protect the pages.