Cookie Policy
How Kalcend uses cookies, local storage, and similar technologies — and how you control the ones that aren't essential.
Last updated: 5 November 2026 (v2.2)
What we use
We use cookies and browser local storage for two purposes: to make the Service work (strictly necessary) and, only with your consent, to understand and improve how the product is used (analytics and session replay). Until you opt in via our cookie banner, analytics captures nothing and keeps no identifier in your browser.
Strictly necessary (always on)
These are required for the Service to function and cannot be switched off. They do not require consent.
| Technology | Purpose |
|---|---|
| __Host-kalcend-session cookie (30 days) | Keeps you signed in; holds a random session ID only |
| __Host-kalcend-oauth cookie (10 minutes) | Completes Sign in with Google securely |
| aws-waf-token cookie | Shows that your browser passed our bot check on sign-in pages |
| Local storage (profile, drafts, UI state) | Remembers your signed-in profile, unsent messages to the Builder and interface preferences |
| Cookie-consent choice | Remembers your analytics preference |
Analytics & session replay (consent required)
These start only after you accept analytics in the cookie banner; until then PostHog captures nothing and keeps no identifier in your browser, only a note that analytics is off. They help us see how the product is used so we can improve it. Session replay can record your interactions within the app, with form inputs masked.
| Provider | Purpose | Region |
|---|---|---|
| PostHog | Product analytics and session replay | United States |
Managing your consent
You can accept or decline analytics when you first visit, and change your mind at any time via "Cookie settings" in the site footer. Declining stops PostHog from capturing; the strictly-necessary technologies above remain active.
We may update this Cookie Policy as our tooling changes. Material updates will be reflected here with a new version above.