← Back to SyncBusy
Privacy Policy
Last updated: November 16, 2026
SyncBusy ("we", "us", "the service") syncs events between your personal calendar (Google Calendar or iCloud) and your work Google Calendar. This policy explains what data we access, how we use it, and how you can control it.
What we access
When you connect your accounts, we request the following access:
- Email address. We request your Google account email address to identify your account and prevent duplicate sign-ups. We use Google's OpenID Connect protocol for this. The same sign-in tells us whether the account belongs to a company's Google Workspace, so setup can ask whether it's really your personal calendar. We also compare addresses so the same Google account can't be connected as both your personal and your work calendar.
- Personal calendar (Google) — read-only by default; write only with reverse sync (Pro). We read event times, titles, and status (accepted/declined/free) to determine when you're busy. We don't change anything on your personal Google Calendar unless you enable reverse sync (Pro) and grant write access. Google's permission for that covers events on all the calendars in that account, but we only create, update, and delete events on the single calendar you designate as the reverse-sync target. We never modify your own events.
- Personal calendar (iCloud) — read-only by default; write only with reverse sync (Pro). When you choose iCloud as your personal calendar, we connect to Apple iCloud Calendar via the CalDAV standard using an app-specific password you generate at appleid.apple.com. We read your event start times, end times, titles, and free/busy status. If you enable reverse sync (Pro), we additionally create, update, and delete events on a single iCloud calendar of your choice that you designate as the reverse-sync target — and only on that calendar. The app-specific password can be revoked at any time at appleid.apple.com → Sign-In and Security → App-Specific Passwords.
- Work calendar — read and write. We create, update, and delete "busy block" events on your work Google Calendar that mirror your personal schedule. We never modify your other work events. We only read them if you enable reverse sync (Pro): then we read their times, titles, guest list, and your response, so we can copy meetings you've accepted to the personal calendar you chose. If you also turn on "Also copy events with no other guests", events you added for yourself (holds, focus time, out-of-office) are copied too, and with "Also copy events marked Free", events set to show as Free are copied as well.
- Event locations (travel time, Pro) — only if you turn it on. When you enable travel time padding, we also read the location field of your personal events so we can estimate how long it takes to get there from the home address you entered.
What we store
- OAuth tokens (Google accounts) — encrypted at rest with AES-256-GCM. These allow us to access your calendars on your behalf. We never see or store your Google password.
- iCloud credentials — for iCloud connections, we store your Apple ID email address and the 16-character app-specific password in encrypted form (AES-256-GCM). We never store your main Apple ID password.
- Event mappings — for each synced event, a record linking the personal event's ID to its busy block's ID, along with its start and end times and a fingerprint of its title, so we can tell when an event has changed. We don't store the title itself. The fingerprint is a keyed one-way hash: it lets us check whether a title changed, but it can't be turned back into the title. If you choose the naming option that shows event titles, the title appears on the event in your calendar, and we still don't keep it. If you enable reverse sync (Pro), we keep a similar record for each copied work event: its IDs, times, and a fingerprint of the title on the copy. These records are protected by Google Cloud's standard encryption at rest, not by the additional AES-256-GCM encryption we apply to credentials.
- Calendar URLs — for iCloud users, the public CalDAV URLs of the calendars you've selected for sync (forward and, if reverse sync is enabled, the single reverse target). These contain no credentials.
- Sync configuration — your preferences (naming style, sync range, pause settings, travel mode, and which work events reverse sync copies).
- Home address (travel time, Pro) — if you enable travel time padding, the home address you enter is encrypted at rest with AES-256-GCM. Clearing the field or deleting your account removes it.
- Travel time cache (travel time, Pro) — the estimated padding (in minutes) for each place you travel to, keyed by a one-way hash of your home address, travel mode, and the event location, so we don't recompute it on every sync. The location itself is never stored in readable form. Entries are refreshed after 30 days and deleted with your account. Each event mapping also records how many minutes of padding were applied.
- Email address — from your Google account (and/or Apple ID for iCloud users), used to identify your account in the dashboard and to send you the account emails described below.
- Setup question — if the personal calendar you connect first is a Google Workspace account, we store a yes/no note that setup is asking whether it's really your personal calendar. We don't store the company or its domain. The note is cleared when you answer, connect a different personal calendar, or connect your work calendar.
- Connection status — if a calendar connection stops working (for example, you removed SyncBusy's access or your password changed), we store a short note saying which connection and when, so the dashboard can show a Reconnect button and we email you only once. It is cleared when you reconnect.
- Email log — a record of each account email: which kind, when, whether it was delivered, and the details it mentions (such as your plan's renewal date). It does not include your address or the email itself, and it is deleted with your account.
- Referrals — your referral code, which account referred you, whether that referral has counted yet, the reason if it won't count, the date of your first payment if you were referred, how many of your referrals have counted, and the total credit you've earned. People you refer see none of this, and you only see how many of them have counted, not who they are.
- Referral cookie — opening a referral link stores the code in a cookie for up to 30 days, so the discount can reach your account once you've signed up. It's removed as soon as it has been used. It isn't used for analytics or advertising.
- Setup-link token — if you use the "continue in another browser profile" option during setup, we briefly store a one-way hash of that single-use link's secret so it can be validated and revoked. It stops working within 30 minutes, and the stored hash is cleared when the link is used or replaced by a newer one.
What we do NOT store
- Event descriptions, attendees, or attachments
- Event locations in readable form (travel time padding stores only a one-way hash, see above)
- Your Google password
- Any data from calendars other than the ones you connect
- Your calendar content, OAuth tokens, or passwords in any analytics event (see "Analytics" below)
- Advertising identifiers, or any data for ad targeting
How data is protected
- OAuth tokens, iCloud credentials, and your home address (if entered) are encrypted with AES-256-GCM before being stored in Google Cloud Firestore.
- All traffic is encrypted in transit via HTTPS/TLS.
- Session cookies are signed with HMAC and marked HttpOnly, Secure, and SameSite.
- The service runs on Google Cloud Run with no persistent local storage.
- Our database has automatic backups, used only to recover from a failure and kept for up to 14 days. Credentials stay encrypted in them.
Analytics
We use Google Analytics 4 to understand how many people visit SyncBusy, which pages they land on, and which product actions (like starting setup or running a sync) get used. This applies only to the hosted syncbusy.dev service — a self-hosted instance never loads Google Analytics or sends any data to Google, regardless of configuration.
- Nothing loads until you accept the cookie banner shown on your first visit. Declining, or not answering, means no analytics script runs and no data is sent.
- What's collected: page views, the page you arrived from (referrer/traffic source), and named product-usage events (e.g. "sync started," "settings saved"). Page addresses are trimmed first, so one-time links such as a "continue setup" link never reach Google.
- If you buy Pro: which plan, the amount paid, and Stripe's reference for that checkout. Never your name, email address or card details.
- What's never collected: your calendar events, titles, attendees, locations, OAuth tokens, or passwords. Nothing about the contents of your calendars ever reaches Google Analytics.
- You can revoke consent at any time by clearing your browser's site data for syncbusy.dev.
Emails we send
The hosted service sends a few account emails, only about your own account:
- a welcome email when both calendars are first connected;
- a confirmation when Pro is turned on, and a note when a Pro subscription ends;
- a notice when a calendar connection stops working, sent once per problem.
These go to your account's email address and contain no calendar content: no event titles, times, or attendees. We don't send marketing or newsletters. Payment receipts and failed-payment notices come from Stripe. A self-hosted instance never sends email through SyncBusy.
When an account finishes setup, SyncBusy's maintainer also gets a short internal note with that account's personal and work email addresses, so we know when someone new joins. It contains no calendar content.
Third-party services
SyncBusy uses these services to operate:
- Google Calendar API — to read personal events, write busy blocks to work calendars, and, if you enable reverse sync (Pro), read work events and write copies to the personal calendar you chose
- Apple iCloud Calendar (CalDAV) — to read personal events from iCloud, when you choose iCloud as your personal calendar provider
- Google Maps Routes API — only if you enable travel time padding (Pro): your home address, the event's location, and your travel mode are sent to Google to estimate travel time. See Google's Privacy Policy.
- Google Cloud Firestore — to store user data
- Google Cloud Run — to host the service
- Google Analytics 4 — to measure site traffic and product usage on the hosted service, only after you accept the cookie banner. See Google's Privacy Policy.
- Amazon Simple Email Service (SES) — to deliver the account emails above. It receives your email address and the email's text. See the AWS Privacy Notice.
- Stripe — to process Pro payments. Stripe receives your email address and payment details; SyncBusy never sees or stores your card number. If you earn referral credit while on the Free plan, Stripe receives your email address so it can hold the credit for you. See Stripe's Privacy Policy.
We do not share your data with any other third parties, and we do not sell data or use it for advertising.
Data retention and deletion
Your data is stored as long as your account is active. Signing out does not delete anything. If you start setup again and finish it on a new account with the same Google address, we delete the unfinished account you left behind: one that never had both calendars connected and has no plan, payment, referral or synced events. We delete only its records; your calendars and the new account are not touched. To delete your account and its data at any time, use the delete buttons on your dashboard. When you delete your account:
- Busy blocks: "Delete Account & Remove Busy Blocks" also removes the busy blocks SyncBusy created on your work calendar. "Delete Account Only" leaves them there, and you can delete them yourself.
- Reverse sync copies (Pro): events copied to your personal calendar are not removed, whichever button you use, and neither is the calendar itself. You can delete them yourself. The same applies if you turn reverse sync off.
- Access: we revoke our access to your Google accounts, except one that another SyncBusy account of yours still uses, so that account keeps working. For iCloud, we delete your stored app-specific password, and you can revoke it at appleid.apple.com.
- Stored data: your OAuth tokens, iCloud credentials, event mappings, travel time cache, configuration, email log, and referral records are permanently removed from our database right away.
- Backups: deleted data can remain in our automatic backups for up to 14 days, then it's gone.
- Payments: any active Pro subscription is cancelled with Stripe. Stripe keeps its own payment records under its privacy policy. Unused referral credit is lost. If you never paid and Stripe only held your credit, we delete that Stripe record too.
Google API Services User Data Policy
SyncBusy's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Changes to this policy
If we make material changes, we'll update the date at the top of this page. For significant changes, we may notify users via the dashboard.
Contact
Questions about this policy? Contact us at support@syncbusy.dev.