Is aggregation more private?

Typically yes — busy intervals without exporting titles across companies.

What is the FreeBusy API?

A Google Calendar API surface that returns busy ranges without exposing event details — ideal for availability checks.

What Is Calendar Aggregation? How It Differs from Calendar Sync

2026-04-02 · Norimitsu Shida · Kiruck Inc.

Résumé

Aggregation reads free/busy across calendars without copying event details. Sync replicates events for a unified view. Aggregation is more private and real-time at query time; sync shows titles across tenants but duplicates data. Tenbin uses Google’s FreeBusy API across up to 10 accounts ($10/mo base) for booking.

Calendar aggregation defined

Query multiple calendars for busy intervals without accessing event titles, descriptions, or attendees for availability purposes.

Calendar sync defined

Copy event records between accounts/providers to mirror a combined view.

Key differences

Privacy: aggregation exposes only busy/free. Sync exposes duplicated event shells. Use cases: aggregation for scheduling; sync for unified viewing. Latency: aggregation at booking time; sync on intervals.

How aggregation works (technical)

OAuth to each Google account → parallel FreeBusy queries → merge busy ranges → offer only slots free across all targets. Tenbin then writes the booked event to the calendar you choose.

When sync wins

Multiple providers (Google + Outlook + iCloud) or when you need analytics on event text — aggregation is not a full read of other people’s meeting titles across tenants.

Aspect	Aggregation	Sync
Data accessed	Free/busy	Full events (often)
Event copying	None	Yes
Privacy	Higher	Lower
Primary use	Scheduling	Unified view

FAQ

Not of event titles — it determines availability. For a merged view of event text, sync tools are the usual path.

← Back to home

Prêt à unifier vos calendriers ?

Connectez Google et partagez un lien.

Essai gratuit