calsync connects exactly one Google account: the operator's own. It is not offered to anyone else, so it processes no other person's account.
With the https://www.googleapis.com/auth/calendar scope,
calsync reads, creates, changes and deletes calendar events in the Google
calendars the operator has explicitly paired with calendars in his Radicale
server. Events can contain details of other people, such as attendees'
names and e-mail addresses, when those are part of an event.
Synchronised events are stored in the operator's Radicale server. The OAuth token Google issues is stored on the same server, in a directory readable only by the dedicated system account that runs the sync, and is included in that server's encrypted backups. The OAuth client secret is kept encrypted in the server's configuration.
No data is sold, shared with third parties, used for advertising or analytics, or used to train AI models. Data received from Google APIs is used only to synchronise these calendars, in line with the Google API Services User Data Policy, including its Limited Use requirements.
Access can be revoked at any time at myaccount.google.com/permissions. Stopping calsync and deleting its token file removes its stored credentials; events already copied remain in whichever calendar holds them until deleted there.
Contact: personal@hugo-berendi.de