Privacy Policy

    Last updated: October 23, 2026

    CalOverlap (“we”, “us”) helps you find times that work across several scheduling links. This policy explains what information we handle when you use caloverlap.com, why, and the choices you have. We collect as little as we can, and we don’t sell or rent personal information.

    Information we handle

    Scheduling links you enter

    When you search, the links you paste (Calendly, Cal.com, Google Calendar, or HubSpot) and the time zone you select are sent to our server. We use them only to look up the public availability shown on those booking pages, the same information anyone with the link can see, and to calculate the overlapping times. We don’t store your links or results. If a lookup fails, the link involved may appear in our server error logs, which we use only for troubleshooting and which our hosting provider deletes automatically after a short period.

    Google sign-in

    Signing in is optional and is only needed to use HubSpot and Google Calendar links. When you sign in with Google, Google shares your name, email address, profile picture, and Google account ID with us. We use this to keep you signed in, to unlock signed-in features, and to keep a simple account record: your Google account ID, name, email, profile picture URL, when you first signed up, when you last visited, and how many times you’ve signed in. This record is stored in our database (hosted by Neon) and lets us count registered users and contact you about your account if needed. Your active session is kept in a secure, signed cookie in your browser (see Cookies below). We don’t request access to your Google Calendar, contacts, or any other Google data.

    CalOverlap’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

    Analytics

    We use Google Analytics to understand how the site is used, for example which pages are visited and how often searches are run. Google Analytics uses cookies and collects information such as your approximate location, device, and browser. If you’re signed in, we also send a pseudonymous user ID: a one-way, keyed hash of your Google account ID. It lets us count returning users without sending Google Analytics your name or email, and it can’t be reversed into your identity without a secret key held only on our server. You can opt out of Google Analytics with the Google Analytics opt-out browser add-on.

    Product analytics and session replays

    We use PostHog to understand how people use the app so we can improve it: for example, how many searches find an overlap, which platforms are used together, and where people get stuck. We record events such as searches (the number of links and which platforms, never the links themselves), sign-ins, and clicks. PostHog may also record session replays, a reconstruction of how you moved through the page. Text you type or paste, including scheduling links, is masked and never recorded, as is your name when signed in. If you’re signed in, PostHog sees the same pseudonymous user ID described above, not your name or email. PostHog uses cookies or local storage to recognize returning browsers.

    Error monitoring

    We use Sentry to detect and fix errors in the site. When an error occurs, Sentry may receive technical details such as your browser, device, the page you were on, and your IP address.

    Third-party content

    • Fonts are loaded from Google Fonts, which receives your IP address when the page loads.
    • The how-to video is hosted by Loom. Nothing is loaded from Loom until you click play; after that, Loom’s privacy policy applies.
    • When we look up availability, requests go from our server to Calendly, Cal.com, Google Calendar, or HubSpot. Those services see our server, not your browser.

    Cookies

    • co_session: set only when you sign in. Keeps you signed in for up to 30 days. It can’t be read by scripts on the page, and signing out deletes it.
    • Google Analytics cookies (such as _ga): used to distinguish visitors, as described above.
    • PostHog cookies and local storage (names starting with ph_): used to recognize returning browsers for product analytics.

    You can block or delete cookies in your browser settings; the site works without them, except for sign-in.

    Service providers

    We rely on a few providers to run CalOverlap: Vercel (hosting), Neon (database), Google (sign-in, analytics, and fonts), PostHog (product analytics), Sentry (error monitoring), and Loom (video). They process information on our behalf or under their own privacy policies, and may process it outside your country.

    Retention and your choices

    • We keep your account record while your account is in use. To have it deleted, email us from the address you signed in with. Signing out removes your session from your browser.
    • You can revoke CalOverlap’s access to your Google account at any time from your Google Account connections.
    • Analytics and error data are kept according to the retention settings of Google Analytics, PostHog, and Sentry. To ask about or request deletion of information associated with you, contact us below.

    Depending on where you live, you may have rights to access, correct, delete, or object to the processing of your personal information. Contact us and we’ll help.

    Children

    CalOverlap isn’t directed at children under 16, and we don’t knowingly collect their information.

    Changes to this policy

    If we change how we handle information, we’ll update this page and the “Last updated” date above.

    Contact

    Questions or requests: info@caloverlap.com