Scheduling tools differ sharply in how much of your calendar they need to see, and the minimum a scheduler needs is only your free and busy blocks. Google publishes a dedicated scope for that, calendar.freebusy (“View your availability in your calendars”), distinct from calendar.readonly, which can “see and download any calendar you can access”.

Why access level matters more than features

Most comparison pages rank schedulers on integrations and price. For anyone who connects a work calendar, the sharper question is what happens to event titles, attendee lists and locations. A tool that only needs availability never has to ingest those. The ranking above therefore rewards vendors that say what they request, and does not reward silence.

What the platforms publish

Microsoft’s getSchedule free/busy API lists Calendars.ReadBasic as the least-privileged delegated permission and does not support personal Microsoft accounts, per Microsoft Learn. That is one reason schedulers treat Outlook.com and iCloud users differently from Google or Microsoft 365 users, and why hand-marked availability or public feeds exist as fallbacks.

Privacy and price pull in different directions

The tools with the most polished paid booking pages (Calendly, SavvyCal) say least on their pricing pages about permissions, while the one that states its model most explicitly, WhenMeet, is a group scheduler rather than a payments-and-routing platform. Cal.com sits in between, with open-source code and data-residency options but a hosted permission model you must check yourself.

What we could not verify

We did not audit OAuth flows, and WhenMeet’s site does not name the exact scopes it requests. Its pricing also appears different from earlier descriptions of it as having no paid tier, so confirm the current plan on its site before budgeting.