Cookie Policy
This page explains how ShapKit uses cookies and similar storage on the marketing site and authenticated app.
Template sample text only. Replace with counsel-reviewed policies before production use. Contact details, jurisdiction, and data practices must match your deployment.
Overview
Cookies are small files stored on your device. We use them to keep you signed in, remember locale preferences, protect against abuse, and—if you enable them—measure marketing performance. This template describes typical ShapKit behavior; update it when you add analytics or consent banners.
What we use
Essential cookies include session and authentication tokens, locale selection, and CSRF or security cookies required for forms. Functional cookies may remember UI choices. Analytics or advertising cookies are off by default in the stock template unless you integrate third-party scripts.
Categories
Strictly necessary: required for login and checkout return flows. Preferences: language and theme where stored in cookies. Analytics: optional page views or events if you configure tools such as privacy-friendly analytics. Marketing: only if you explicitly add pixels or ad networks.
Third-party cookies
Payment providers, OAuth login partners, or embedded widgets may set their own cookies when users interact with them. Review Stripe, Google, GitHub, or other providers you enable and link to their policies from your production site.
Your controls
You can clear cookies in browser settings; doing so may sign you out. Where required by law, implement a consent banner before non-essential cookies. ShapKit does not override browser "Do Not Track" signals unless you add tooling that does.
Updates
We may revise this Cookie Policy when we change tracking practices. Post the effective date at the top of your legal pages when you customize this template for production.