Privacy

This deployment of slotmirror is operated by NetCero. Contact: michael.jauk@netcero.eu.

slotmirror mirrors busy times between calendars. It is open-source software that each operator runs in their own Cloudflare account.

What is stored

• Your email address and, for Microsoft accounts, the tenant ID and object ID, to identify you and your connected accounts.
• OAuth tokens for each connected account, encrypted with AES-256-GCM.
• The names of your calendars and the rules you create.
• An activity log with times, counts and error codes, without event content. It is deleted after 90 days.
• A session cookie and a language cookie in your browser.

What is not stored

Event titles, descriptions, locations and attendees are read during a sync and not stored. Blocks in a target calendar contain only what the rule's detail level allows; the default is Busy.

Where data is processed

On Cloudflare Workers, D1 and Durable Objects in the operator's Cloudflare account, and at Microsoft and Google when calendars are read and written.

How to delete your data

Disconnecting an account deletes the blocks slotmirror wrote for it, then its tokens. If blocks cannot be removed, the calendar name, the calendar ID, the block title, the block count, the period and the marker stay for 90 days, so that you can delete them by hand. The calendar ID of a primary Google calendar is your email address. To delete your user and all its data, use “Delete my data” in the account menu.

Google user data

slotmirror's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Data is used only to show and mirror busy times as configured by you, and is never sold, used for advertising or read by humans.

There is no tracking, no analytics and no advertising.