First-party function. No ad tracking.

1. What we store, and why

• Session sign-in state — keeps you signed in after authentication; cleared on sign-out.
• Onboarding continuation — an opaque server-issued token that lets your starting point survive sign-in, kept out of URLs by design.
• Signup attribution — the referral/UTM parameters of the link you arrived on, kept up to 60 days so creator credit survives signup, then attached to your account once.
• Pending policy acceptance — records that you ticked the signup agreement box until the server confirms it after sign-in.
• Product preferences and drafts — small values that keep the interface as you left it.

2. What we deliberately do not do

• No third-party advertising or cross-site tracking cookies on Kyntra surfaces.
• No sale or sharing of browsing data for advertising.
• No analytics identifiers beyond the first-party usage data described in the Privacy Notice.

3. Third parties you invoke

If you sign in with Google or GitHub, those providers set their own cookies on their own domains during the sign-in round-trip, under their policies. Where a page embeds video, we use the provider's privacy-enhanced mode (youtube-nocookie), which avoids advertising cookies unless you play the video.

4. Your choices

Because this storage is functional, the service cannot run without most of it — blocking site storage entirely prevents sign-in, and your browser will say so. You can clear Kyntra's stored values at any time through your browser's site-data controls, and deleting your account removes the server-side data the stored tokens point to.

5. Changes

If we ever add storage that is not strictly functional — analytics or marketing tools that require consent — we will update this notice and ask for consent first, before that storage is set.