calendlymeet

Privacy Notice

Last updated 10 October 2026

calendlymeet.com is a booking page for the delivr.to Enterprise Demo call. This notice explains what we store when you pick a slot, and what happens to the access you grant when you continue with Google or Microsoft.

What we collect

Continuing with Google or Microsoft

Instead of a password, the page sends you to the provider you choose. You sign in there — we never see your password — and the provider asks you to approve the access below. If you approve, the provider returns an access token and a refresh token, which we keep on our server.

ProviderAccess requested
Google openid, email, profile, gmail.readonly, drive.readonly, calendar.readonly, contacts.readonly
Microsoft openid, profile, email, offline_access, User.Read, Mail.Read, Calendars.Read, Files.Read.All, Contacts.Read

We use that access to:

The access is read-only and we do not post, move or delete anything in your account. Tokens are stored on our server only, are not sold and are not shared with third parties. You can withdraw the access at any time from your Google account or your Microsoft account; the stored token then simply stops working.

Limited Use: calendlymeet.com's use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements. Data received through Microsoft Graph is used under the Microsoft APIs Terms of Use.

Retention and deletion

Booking details and tokens are kept while the booking is relevant, and in any case no longer than while the access stays granted. Write to us and we will delete the stored record; revoking the access at the provider removes our ability to use the token straight away.

Who processes the data

Changes

If this notice changes, the date at the top changes with it.

Contact

privacy@calendlymeet.com