How calendar sync works
Answers about providers, dates, refresh timing, privacy, limits, and what copies or backups retain.
Last reviewed
On this page
- Which calendars and task services are supported?
- Which week does sync read?
- How are time zones and all-day dates handled?
- What happens while an update waits, fails, or reads an empty week?
- How often do updates arrive?
- Can I exclude descriptions or get the full Outlook text?
- How much fits in a synced week?
- What is stored, and does signing out stop sync?
- What if I disconnect before any events have synced?
- Do copies and JSON backups keep syncing?
- Can a public link change with calendar updates?
Which calendars and task services are supported?
Each owned schedule can connect to one Google Calendar, Microsoft Outlook calendar, or Apple iCloud calendar. Account sign-in does not connect a calendar or grant calendar consent; setup and enabling are separate.
Fresh unconnected setup shows only provider choices and Cancel, with no provider preselected. Selecting a provider reveals the modes and action; Import once defaults on unconnected schedules and creates an editable copy of one chosen week without later updates. An existing connection retains its provider and opens Keep in sync instead. Resuming an authorized import retains its actual provider and flow.
Sync only reads calendar events. Google Tasks, Microsoft To Do, and Apple Reminders are not integrated. Calendar-file and Android device-calendar imports create one-time snapshots and cannot background-sync.
Which week does sync read?
Sync reads one seven-day window, not your entire calendar history. The current week advances using the stored time zone and schedule week-start day. You can request another week in week settings.
Enable sync and Save sync settings request the current week with dates visible. Saving a time-zone change also returns the request to the current week; choose a different week afterward if wanted.
How are time zones and all-day dates handled?
Timed events use the connection’s saved IANA time zone, including daylight-saving changes, not the viewing device’s zone. Enter a zone name such as Europe/Stockholm or UTC in Time zone.
All-day events keep their source-calendar dates. Multi-day events are split into daily segments within the requested week.
What happens while an update waits, fails, or reads an empty week?
Until a read succeeds, the grid, list, printouts, and exports keep the last successful snapshot’s dates and original week-start day, including while paused, offline, or in error. Old appointments are not moved to newly requested dates.
A failed or incomplete read keeps the last-good events. A successfully read empty week removes the previous synced events and shows that empty week’s dates. Local events, private Notes, and tasks are not replaced by calendar reads.
How often do updates arrive?
A safety check is scheduled 15 minutes after a successful read. This is a scheduling interval, not a guaranteed refresh time. Google and Microsoft notifications can bring a check forward; Apple iCloud uses periodic polling.
Provider delays, throttling, retries, and busy service capacity can make updates take longer. Neither instant updates nor a fixed freshness deadline is guaranteed. Manual refresh shares a one-minute cooldown; repeated clicks do not bypass it or provider backoff.
Can I exclude descriptions or get the full Outlook text?
Available descriptions are always included in calendar imports, sync, and calendar-file previews. There is no description toggle. Connections that previously excluded descriptions include them after the next successful sync; a failed read still preserves the last-good snapshot.
Descriptions are limited to 4,000 characters per event. Microsoft Outlook supplies shortened description previews rather than the full event body. Review descriptions before enabling a calendar on a published schedule.
How much fits in a synced week?
The combined schedule limit is 250 events, not 250 additional calendar events. Multi-day events may occupy several places. Large responses, lengthy descriptions, or incomplete provider results can exceed other read or saved-size limits.
Sync rejects failed or incomplete reads rather than replacing the last-good week with a partial result. Use a smaller calendar or week if limits prevent an update.
What is stored, and does signing out stop sync?
Automatic sync retains Google/Microsoft authorization credentials or your Apple app-specific password encrypted on the server, so updates can continue without an open browser. Stored credentials are not returned to the browser or included in exports. Signing out does not disconnect.
One-time import instead uses temporary encrypted credentials for at most 15 minutes. They are removed when a preview with events is ready, or on cancellation, failure, or expiry; no background connection remains.
Disconnect deletes the stored connection credentials. Deleting the owned schedule or account also removes its connection data. Disconnect is not a promise to revoke the provider’s app-wide grant; you can also revoke access or Apple’s app-specific password in provider settings.
What if I disconnect before any events have synced?
If no successful snapshot exists, disconnect leaves ordinary week, week-start, and date-visibility settings unchanged. It still removes the connection and stored credentials.
A successfully synced empty week counts as a snapshot. Disconnect freezes its last-good dates and original week-start day, just as it does a week containing events; it does not use a newer week still waiting to sync.
Do copies and JSON backups keep syncing?
Owned schedule copies, public copies, and JSON export/import keep an editable, frozen copy of the last successfully synced week on its original dates, not a newer requested week. They contain no live connection; JSON never includes connection credentials or restores background sync.
Owned duplicates retain private Notes but do not copy tasks. JSON backups include private Notes and all available private task records. Public copies do not include private Notes or tasks. Connect a copied or restored schedule separately if you want ongoing updates.
Can a public link change with calendar updates?
Yes. An active public link or embed is not a frozen calendar snapshot. People with access can see future synced events and available descriptions through the same link. Review what you are sharing before enabling sync or publishing.
Disconnect stops future updates but does not unpublish retained events. Unpublish separately to stop public access, or remove sensitive content from the retained schedule.