Cookies

Last updated: May 7, 2026

Krewva uses cookies and local-storage entries the way most modern web apps do: to keep you signed in, to remember a few choices you’ve made, and (only if you opt in) to count which pages convert. We do not use marketing cookies, sell data, or track you across other sites. There is no Facebook pixel, no Google Ads tag, no third-party A/B testing surface.

The cookie banner you saw on your first visit asked you to choose between three categories: essential, analytics, and performance. This page explains each category and lists every entry we set today.

Essential cookies

Essential cookies are required for the site to function. Disabling them would break sign-in, the cookie banner itself, and CSRF protection on form submissions. You cannot opt out of these — if that’s a deal-breaker, you should not use Krewva.

• krewva.cookies.accepted — a date stamp written the moment you click Accept. Lives in your browser’s localStorage. Used purely so we don’t re-show the banner.
• krewva.cookies.preferences — a JSON object recording which non-essential categories you opted into. Read by any analytics module before it does anything observable.
• krewva-session — signed session cookie issued by our backend after you sign in to the app. HttpOnly, Secure, SameSite=Lax. Expires after 30 days of inactivity.
• krewva-csrf — double-submit token used to prevent cross-site request forgery on form posts. Rotates per session.

Analytics cookies

Analytics cookies help us count which pages people read before they sign up. We do this so we know whether the manifesto is working harder than the privacy/security section, or vice versa, when we decide what to write next. The data is aggregated; we never tie a page-view to your account.

• krewva-anon — an opaque per-browser identifier written only after you opt in. It is not linked to your account even if you sign in later. We rotate it every 90 days. Set on the first page-view after consent and not before.

We do not use Google Analytics, Mixpanel, Segment, or any third-party SaaS analytics product on this marketing site. The counter that reads krewva-anon runs on our own backend and writes into our own warehouse. No third party sees it.

Performance cookies

Performance entries collect anonymous samples of how fast pages load and which animations stutter. We use this to find slow surfaces and remove them. The samples are sent only as numbers (page-load duration, layout shift, time-to-interactive); no message content, no inputs, no headers.

• krewva-perf-sampled — a boolean that records whether you were chosen for performance sampling on this visit. Roughly 1 in 5 visits are sampled to keep the dataset representative without slowing every visitor down.

How to revoke

You can change your mind any time. Three ways to revoke:

• From the cookie banner. Clear your localStorage for krewva.com in your browser’s site settings, then reload. The banner reappears and you can re-choose.
• From the JavaScript console. Run localStorage.removeItem("krewva.cookies.accepted"); localStorage.removeItem("krewva.cookies.preferences"); and reload. The banner reappears.
• By emailing us. Mail support@krewva.com with the subject line “cookie reset” and the email address on your Krewva account. We will purge your sample-rate record from our analytics warehouse and confirm within 30 days.

Do Not Track and the GPC signal

We honor Global Privacy Control (GPC) and the legacy DNT: 1 header. If your browser is sending either, Krewva will treat your default state as essential-only and will not show the banner unless you visit a settings page that asks you to opt in by hand.

Cookies inside the Krewva app itself

This page describes the marketing site at krewva.com. Inside the iOS or macOS Krewva app you signed into, the only state we keep client-side is your auth tokens (in the OS keychain, never a cookie) and a small UI preferences object. The same revocation paths above apply: signing out clears tokens, deleting your account clears the preferences object within 24 hours.

Updates to this page

If we add a new cookie or analytics surface, we update this page before we ship the change to production, and we re-show the banner so you can re-consent. Material changes are noted in the changelog too.

Contact

Questions, audit requests, or curiosity: support@krewva.com. The full privacy framework is in the privacy policy.