Klientify Cookie Policy Version: 2.0 Last updated: August 20, 2026 1. Scope This Cookie Policy explains how Klientify uses cookies, local storage, and similar technologies on our public website and product interfaces. 2. What we currently use At the time of this version, Klientify uses the following technologies: - essential authentication and security cookies or tokens required by the framework and sign-in flow, - local storage entries for interface and consent preferences, including theme preferences and the saved cookie-consent selection, - PostHog analytics, loaded only when analytics consent is granted and only on non-admin public routes. Current browser-storage register: - cookie-consent — necessary preference record containing analytics and marketing choices and their timestamp; kept until changed or browser storage is cleared, - theme — interface theme preference; kept until changed or cleared, - selectedAccountId — necessary signed-in workspace selection; kept until changed, sign-out cleanup, or clearing, - storefront-cart:<seller slug> — necessary cart contents; removed when emptied or checkout cleanup runs, otherwise kept until cleared, - klientify-public-conversation-v1 — a private conversation identifier and access token; local state expires after approximately 175 days and the server record after 180 days, - klientify-public-visitor-v1 — first-party public-conversation visitor identifier; kept until cleared, - klientify:pwa-install-prompt:dismissed-at — preference suppressing the install prompt for 14 days, - resizable-sidebar:* and calendar layout keys — product interface preferences kept until changed or cleared. PostHog is configured with in-memory persistence, so Klientify does not intentionally place a persistent PostHog identifier before or after analytics opt-in under the current configuration. Direct private-question and answer URLs are excluded from analytics and replay events. 3. Cookie and storage categories We group these technologies into: - strictly necessary: required for sign-in, session continuity, security, abuse prevention, and core product functionality, - preferences: used to remember interface settings such as theme choice and consent selections, - analytics: used to understand site and product usage trends through PostHog when you opt in, - marketing: a consent category exists in the interface, but no active marketing cookie or marketing tracking vendor is currently loaded by default. 4. Analytics behavior PostHog is configured with EU data residency and is initialized with capturing disabled by default. Analytics only become active after you grant analytics consent. If you later withdraw consent, analytics capturing is disabled again. 5. How consent works When you first visit Klientify, you can: - accept all optional categories, - reject all optional categories, - open Cookie Settings and enable or disable analytics and marketing preferences individually. Your choice is stored locally on your device so that we can remember it. You can update or withdraw your consent at any time through Cookie Settings. 6. Marketing status The Klientify consent interface includes a marketing toggle for future use, but Klientify does not currently load an active marketing tag, advertising pixel, or marketing tracking vendor based on that setting. 7. How to manage cookies You can also control cookies and site data through your browser settings. Blocking strictly necessary technologies may prevent parts of Klientify from working correctly. 8. Third-party technologies Where enabled by consent and applicable configuration, third-party technologies may include: - PostHog for analytics, - infrastructure-level authentication or security mechanisms used to keep the service operational. 9. Changes to this Policy We may update this Cookie Policy to reflect changes in the technologies we use or legal requirements. The latest version is published on this page. 10. Contact Questions about cookies or consent can be sent to: contact@klientify.me.