SparkVoxSparkVox

Cookie Policy

Last updated: August 2026

This Cookie Policy explains exactly what SparkVox stores in your browser, why, and what your options are. We have kept this as minimal as possible by design.

1. Cookies on the app (app.sparkvox.io)

The SparkVox application uses strictly necessary cookies for authentication and billing, plus first-party PostHog analytics cookies after you sign in. We do not run advertising scripts or marketing analytics (PostHog or Google Analytics) inside the app.

Authentication cookies (Supabase)

Cookies prefixed sb- manage your login session. They expire when your session ends or after the configured session timeout.

Fraud prevention cookies (Stripe)

__stripe_mid and __stripe_sid are set by Stripe when you add a payment method to detect fraudulent activity. They are not used for advertising.

Product analytics cookies (PostHog)

PostHog may set first-party cookies on .sparkvox.io (for example ph_phc_*) to attribute in-app usage events after you sign in. Limited anonymous pageview events may also occur before sign-in (for example on the signup page). See our Privacy Policy for the legal basis.

2. Cookies on the marketing site (sparkvox.io)

The marketing website uses a cookie consent banner for PostHog and Google Analytics 4. Those tools load only after you accept. Declining or dismissing the banner keeps them off.

The Meta Pixel is not controlled by that banner. It loads on sparkvox.io and app.sparkvox.io to measure SparkVox ad performance and set ad-attribution cookies (for example _fbp) on .sparkvox.io. Signup and trial-start events fire in the app after you leave the marketing site.

PostHog (product analytics)

PostHog sets first-party cookies (for example ph_phc_*) on .sparkvox.io to count visits, page views, button clicks, and UTM attribution. Used for product improvement only - not advertising.

Google Analytics 4 (aggregate traffic)

Google Analytics sets first-party cookies (for example _ga, _ga_*) to measure aggregate traffic and page performance on sparkvox.io. We do not use GA4 for advertising or remarketing.

Meta Pixel (ad measurement)

The Meta Pixel loads scripts from connect.facebook.net on sparkvox.io and app.sparkvox.io and may set Meta cookies (for example _fbp) to measure page views, signup, trial starts, and ad attribution for SparkVox campaigns on Meta platforms. It is not gated by the marketing cookie banner. Meta processes this data under its own terms; see Meta's Privacy Policy.

3. Local Storage (Not Cookies)

We also use your browser's localStorage and sessionStorage for functional items that are not cookies but are worth disclosing:

  • Cookie consent choice - stores whether you accepted or declined PostHog and Google Analytics 4 on sparkvox.io (sparkvox_cookie_consent). The Meta Pixel is separate and not controlled by this choice.
  • Marketing chat history - Sparky keeps a short offline copy in localStorage (up to 7 days) and stores your active conversation id in sessionStorage. Full message text is stored on SparkVox servers when you send your first message (and when you submit the optional email follow-up form).
  • Referral welcome modal flag - a one-time flag that records whether you have dismissed the referral welcome modal, so it is not shown again on subsequent visits.
  • UTM / referral attribution - stored in sessionStorage during a browser session when you land with campaign parameters, so attribution survives in-app navigation to signup.
  • In-app UI preferences (app.sparkvox.io) - Help drawer state, recent global search selections, and per-channel Post Analytics date-range preferences, so the app remembers your last view when you return. Functional only - not used for tracking or advertising.

4. How to Control Cookies

On sparkvox.io, use in the site footer to change your PostHog and GA4 choice at any time. Accepting enables those tools; declining opts out and reloads the page so no new PostHog or GA4 data is collected. The Meta Pixel continues to run regardless of that choice.

You can also clear cookies and localStorage data at any time through your browser settings. Note that clearing Supabase auth cookies will log you out. Clearing localStorage will remove your cookie consent choice, chat history, and modal preferences.

5. Changes to This Policy

We may update this policy if we add new functionality that requires additional storage. Any material changes will be communicated by email or in-app notice.

6. Contact

Questions about cookies or local storage? Email [email protected].