Privacy, without hand-waving

We need your free and busy times. Not your life story.

Set Meet Go shares time ranges such as “busy from 10:00 to 11:00” with a meeting. It does not put event titles, notes, attendees, locations, or calendar credentials into shared meeting data.

Exactly what each connection can access

One-time check or keep updated

A one-time check uses short-lived provider access or credentials entered for that check. When browser security permits it, Set Meet Go’s server never sees the request. If you select Keep this calendar updated, the connection belongs to your signed-in account. Credentials or refresh tokens are encrypted at rest and decrypted only by the sync worker while fetching new availability, normally about every six hours.

The relay is not end-to-end encryption

Many CalDAV and calendar-feed servers do not permit browser requests. Our fallback relay accepts only restricted HTTPS reads, pins validated public addresses, blocks redirects and private networks, limits response size and time, and does not persist credentials or response bodies. It handles plaintext transiently, so we do not call this end-to-end encrypted.

What other people see

Other participants see whether a candidate works, is preferred, conflicts, or is still unknown. They never receive your calendar connection or event content. Availability and meeting responses are ordinary hosted data protected by TLS and access controls; they are not E2E-encrypted.