How does SyncThemCalendars protect my privacy?

SyncThemCalendars protects privacy in two ways: it limits how your data is used, and it lets you hide event details before they are copied. According to the site, your data is used only to copy events between your calendars — "Nothing else, ever." Separately, you can hide any field of a copied event — title, description, location and more — behind a simple "Busy" block. These protections apply to the syncs you create between Google, Outlook and iCloud calendars; they do not replace the privacy settings of those calendar providers themselves.

What data SyncThemCalendars uses

The service's stated data-use rule is narrow: it uses your data only to copy events between the calendars you connect. The site expresses this as a commitment rather than a configurable option:

• Purpose limitation — data is used to perform the copy between your calendars.
• No secondary use — the site states nothing else is done with it, "ever."
• Your data stays yours — the company frames this as ownership remaining with you.

This matters because syncing inherently means a third party touches your event data. The relevant question is whether that access is scoped to the sync task. SyncThemCalendars says it is.

Hiding event details behind "Busy"

The privacy feature you control directly is field-level hiding. When you create a sync, you can choose to hide the details of any field in the copied event — title, description, location and more — and show a "Busy" block instead.

A concrete example: you keep a personal Google Calendar and a work Outlook calendar. You want colleagues to see that you are unavailable on Tuesday at 2 p.m., but not that the block is a medical appointment. With detail hiding enabled, the copied event appears as "Busy" on the target calendar, so the time is reserved without exposing the content.

This is useful when:

• You sync a personal calendar into a shared or work calendar.
• You want free/busy visibility without revealing event content.
• Different people have access to the source and target calendars.

One-way vs. two-way sync and what it means for exposure

Sync direction affects how far your event data travels. The site lets you choose whether calendars mirror events both ways or only copy from one to another. If privacy is the priority, a one-way sync from a private calendar into a more widely shared one limits the copy to a single direction, and combining that with "Busy" hiding keeps the shared calendar from carrying your event details at all.

Trust signals

The site points to a track record rather than a technical audit:

User reviews on the Google Workspace Marketplace describe the practical value of syncing — for example, one reviewer wrote about syncing an Outlook calendar to Google Calendar so it would appear on both desktop and phone, and another about syncing a shared webcal with a personal iCal. These are usability reports, not independent privacy audits, so treat them as evidence of longevity and adoption rather than proof of security practices.

What to check before relying on it

• Provider settings still apply. Hiding details in a copied event does not change what Google, Outlook or iCloud store or share on their own.
• Field-level hiding is per sync. Decide which fields to hide when you set up each sync, since the choice is part of the sync configuration.
• Trial terms. The site offers a 14-day free trial with no credit card required; pricing details are listed under "Simple pricing that scales with you" on the site, so confirm current terms there before committing.

If your goal is to keep availability visible while keeping event content private, the combination of a one-way sync and "Busy" hiding is the most direct use of the features described. If your concern is how a third-party service handles your data generally, the site's stated position is that data is used only for the copy operation — a claim you can weigh alongside the provider-level controls you already have.