What each setting does

Connecting accounts, choosing a direction, and building your first sync.

• Direction: one-way or two-wayPush copies one way and never touches the source. Mirror goes both ways. How to tell which one you need, and what changing it later deletes.

Appearance, filters, per-calendar exceptions, and the sync-wide settings.

• Appearance: how copied events lookEvery setting that decides what a copy looks like when it lands: title, availability, privacy, colour, guests and reminders.
• Filters: which events get copiedWhich events enter a sync at all: the RSVP filter, working hours, Google's special event types and exclude rules — plus what tightening one deletes.
• Sync details: name, history, and how far aheadThe sync-wide settings: a sync's name, how much history it copies on its first run, and how far ahead it reaches.
• Calendar exceptions: different settings per calendarSet a shared default for a sync, then override it for one destination calendar. What you can vary, what you can't, and which way round it works.

Diagnose what happened before you change anything.

• What SYNCDATE decides on its ownThe moments the product acts without asking: two calendars changing one event, an account that stops letting us in, a downgrade that removes copies, an AI agent's limits, and a calendar that isn't yours to write to.

What each plan allows, and what the product will not do at all.

• Plans and limitsThe five numbers that limit a setup, what each one means, and which one actually stops people.
• What SYNCDATE can't doThe limits no plan removes: syncs don't chain, special event types are Google-only, feeds are read-only, and colour is approximate between providers.