Privacy Policy

Last updated: August 14, 2026

1. Overview

This Privacy Policy explains what information myCalSync (the "Service") collects, how we use it, and the choices you have. The Service is a private calendar-synchronization tool operated for a limited set of invited users.

2. What myCalSync does

myCalSync reads your busy/free time from connected Google and Microsoft calendars and creates placeholder "blocker" events on your other connected calendars, so your availability stays consistent across them.

3. Information we collect and process

Calendar data. Through Google and Microsoft OAuth, we read calendar event details (timing and busy/free status) for the calendars you connect, and create and manage blocker events on your behalf.
Account information. Your email address and the calendars you have connected.
Sign-in information. If you sign in with email and password, we store a salted password hash, never the plaintext password. If you sign in with Google, we store your Google account identifier.

4. What we store

OAuth refresh tokens, encrypted at rest (AES-256-GCM).
Calendar and event identifiers required to keep mirrors in sync.
Your user account record (email address and a password hash and/or Google identifier).

5. How we use this information

We use this information solely to provide the Service: to read your availability and write blocker events. We do not use it for advertising, and we do not sell it to anyone.

6. Data sharing

We do not sell or share your data with third parties. Calendar data is exchanged with Google and Microsoft solely through the OAuth permissions you grant; those providers process that data under their own privacy policies.

7. Data security

Data in transit is encrypted with TLS.
OAuth tokens are encrypted at rest; passwords are hashed with scrypt.
The Service is a private instance with no public sign-up; accounts are provisioned by an administrator.

8. Cookies

A single session cookie is used to keep you signed in (signed, httpOnly, 30-day lifetime). We do not use tracking or analytics cookies.

9. Data retention and deletion

Your data is retained while your account is connected. Removing an account deletes its stored credentials and metadata. You may request access to, correction of, or deletion of your data by contacting the administrator.

10. Third-party services

The Service relies on the Google Calendar and Microsoft Graph APIs. Your use of those services is subject to their own terms and privacy policies.

11. Changes to this policy

We may update this Privacy Policy from time to time. Changes take effect when posted on this page.

12. Contact

Questions about this policy can be directed to the administrator at fahad.qureshi@digitaleratechnology.com.

Back to sign in