• How It Works
  • Demo
  • Pricing
  • FAQ
Sign In
Sign Up

Programmable calendar sync. Write rules to filter, transform, and sync events between Google Calendar and Outlook.

© 2026 CalendarPipe. Built by an indie maker.

Product
  • How It Works
  • Pricing
  • FAQ
Legal
  • Privacy Policy
  • Terms of Service
  • Cookie Policy
Connect
  • Twitter/X
  • GitHub

Cookie Policy

Our cookie policy and how we use them

Last updated: February 20, 2026

1. What Are Cookies?

In Short
Cookies are small files stored by your browser. We use them to keep you logged in and remember your preferences.

Cookies are small text files that a website stores on your device when you visit. They allow the site to remember information about your visit — such as whether you're logged in — so you don't have to re-enter it every time.

In addition to HTTP cookies, web browsers also provide localStorage — a way to store data on your device that persists between sessions but is never sent to the server as part of a network request. This page covers both HTTP cookies and browser localStorage items that CalendarPipe uses.

2. Cookies & Storage We Use

In Short
We use two essential cookies (authentication and CSRF protection) and one localStorage item (theme preference). That's it.

CalendarPipe uses a minimal set of cookies and browser storage — only what is necessary to keep the service working and to remember your preferences.

Cookie / StoragePurposeDurationType
sb-[ref]-auth-tokenAuthenticates your session with CalendarPipe. Set and managed automatically by Supabase. The exact cookie name includes your project reference ID.Session (JWT-based)Essential
csrfSecretProtects form submissions from cross-site request forgery (CSRF) attacks.SessionEssential
theme(localStorage)Stored in browser localStorage, not sent as an HTTP cookie. Used only client-side to remember your light or dark mode preference.Persistent (no expiry)Preference

Supabase automatically manages session cookies for authentication. The exact cookie name includes your project reference ID (e.g., sb-[ref]-auth-token).

3. Analytics (Upcoming)

In Short
We do not currently use any analytics or tracking cookies. If we add analytics in the future, we will update this page first.

CalendarPipe does not currently use any analytics, tracking, or advertising cookies. We do not collect behavioural data about how you use the service.

We may introduce privacy-respecting analytics in the future to understand how CalendarPipe is used and to improve the service. If we do, we will:

  • Update this Cookie Policy before any tracking begins
  • Use cookieless or privacy-first analytics where possible, to minimise reliance on persistent identifiers
  • Never sell analytics data to third parties

4. Managing Cookies

In Short
You can clear cookies in your browser settings. Clearing essential cookies will log you out.

You can manage and delete cookies through your browser settings. Most browsers allow you to:

  • View which cookies are stored and delete them individually
  • Block cookies from specific sites or block all third-party cookies
  • Clear all cookies and site data in one step (usually found under Privacy or History settings)

Essential cookies (authentication and CSRF protection) are required for CalendarPipe to function. Clearing or blocking them will sign you out and prevent you from signing back in until a new session cookie is set.

To clear your theme preference, open your browser's developer tools, navigate to Application → Local Storage, and delete the theme key. Doing so will reset your preference to your system's default light or dark mode setting.

5. Contact

If you have questions about this Cookie Policy, contact us at:

CalendarPipe
privacy@calendarpipe.com