Last updated: February 26, 2026
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.
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 / Storage | Purpose | Duration | Type |
|---|---|---|---|
sb-[ref]-auth-token | Authenticates your session with CalendarPipe. Set and managed automatically by Supabase. The exact cookie name includes your project reference ID. | Session (JWT-based) | Essential |
csrfSecret | Protects form submissions from cross-site request forgery (CSRF) attacks. | Session | Essential |
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 |
ph_<token>_posthog(localStorage) | Stores anonymous analytics identifiers and session data for PostHog product analytics. Used to understand how CalendarPipe is used and improve the service. Never sent as an HTTP cookie. | Persistent (no expiry) | Analytics |
Supabase automatically manages session cookies for authentication. The exact cookie name includes your project reference ID (e.g., sb-[ref]-auth-token).
CalendarPipe uses PostHog for product analytics to understand which features are used and where users encounter friction.
PostHog stores a single localStorage item (ph_<token>_posthog) containing an anonymous identifier and session metadata. This is NOT an HTTP cookie — it is never sent to the server with network requests.
You can manage and delete cookies through your browser settings. Most browsers allow you to:
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.
To clear analytics data, open your browser's developer tools, navigate to Application → Local Storage, and delete any keys starting with ph_. This will reset your anonymous analytics identifier. CalendarPipe will continue to function normally.
If you have questions about this Cookie Policy, contact us at:
CalendarPipe
privacy@calendarpipe.com