Privacy and data location

slotmirror is software that you run in your own Cloudflare account. There is no slotmirror service between your calendars and your deployment.

What is stored

• The email address of each user and, for Microsoft accounts, the tenant ID.
• OAuth tokens for each connected account, encrypted with AES-256-GCM. The key is the secret TOKEN_ENCRYPTION_KEY.
• The names of the calendars and the rules.
• An activity log with times, counts and error codes, without event content. Entries older than 90 days are deleted.
• A session cookie and a language cookie in the browser.

What is not stored

Event titles, descriptions, locations and attendees are read during a sync and kept only in memory. They are not written to D1 or to Durable Object storage. Blocks in a target calendar contain only what the detail level of the rule allows. The default is “Busy”.

Where data is processed

On Cloudflare Workers, D1 and Durable Objects in your Cloudflare account. At Microsoft and Google when calendars are read and written.

Keep data in the EU

1. Create the D1 database in the EU:

   pnpm wrangler d1 create slotmirror --jurisdiction=eu

2. Set DATA_JURISDICTION=eu. The Durable Objects then run in the EU. They hold the tokens and run the sync, which reads event contents.

Set it before the first account connects

Neither setting can change for existing data. If you change DATA_JURISDICTION later, every account is disconnected.

Delete data

• Each user can delete their own data under Delete my data in the account menu.
• Admins can delete other users on the admin page.

Both remove the accounts with their tokens, the rules, and the blocks those rules wrote from today on. Past blocks stay in the calendars. Activity entries stay until the retention period ends.

The /privacy page

Each deployment has a /privacy page. It shows PRIVACY_CONTACT as the contact of the operator. Google requires this page for a published OAuth app.