Cookie Policy

SeeFirst seefirst.io Effective Date: 26 August 2026

1. Introduction

This Cookie Policy explains how SeeFirst ("we," "us," "our") uses cookies and similar browser technologies when you visit seefirst.io or use the Service. It should be read alongside our Privacy Policy.

We do not use advertising or third-party tracking cookies for ad targeting.

2. What Are Cookies?

Cookies are small text files stored on your device when you visit a website. They are commonly used to keep you signed in, remember preferences, or support security features.

We also use local storage in the browser for a small number of non-essential product features (see Section 5).

3. Cookies We Use

Essential authentication and session cookies

When you sign in, Supabase Auth sets cookies required to maintain your session and protect your account. Without these cookies, login and authenticated areas of the Service will not work.

These are strictly necessary for the Service to function for logged-in users.

Agency portal context cookie (sf_agency_id)

If you sign in to a white-label client portal, we set a cookie that records which agency's portal you signed into. This is required when the same email address is linked to more than one agency, so the portal shows the correct client's data.

Password-protected report cookie (sf_report_*)

If you unlock a password-protected sales or prospect report, we set a short-lived, HTTP-only cookie so you can view that report without entering the password on every page. This cookie expires after twelve hours.

Payment cookies (Stripe)

When you add or update a payment method during signup or billing, Stripe.js may set cookies or use similar storage on Stripe's domain to process your card details securely. We do not store full card numbers on our servers.

4. Performance and Error Monitoring

These tools are optional. They stay off in your browser until you accept optional measurement in the cookie banner (or change your choice later by clearing site data and revisiting).

Vercel Speed Insights

When allowed, we use Vercel Speed Insights to measure page performance (for example, load timing). This helps us keep the Service responsive. It is not used for advertising.

Sentry (browser)

When allowed, we use Sentry in the browser to capture application errors and limited performance data when something fails. Session replay is only used for error sessions. It is not used for advertising.

Server-side error logging (which does not set browser cookies) may still run so we can keep the Service reliable.

5. Local Storage (Not Cookies)

Some features store a small amount of data in your browser's local storage rather than cookies:

Consent preference: seefirst_consent_v1 stores whether you allowed optional analytics and performance tools.
Product analytics visitor ID: a random identifier (seefirst_analytics_visitor_v1) used only when analytics are allowed, to count anonymous marketing-page events and limit duplicate events per browser per day. This is not used for advertising.
Onboarding UI state: for example, whether a welcome guide has already been shown, so we do not repeat the same prompt.

You can clear local storage through your browser settings. Clearing authentication cookies will sign you out.

6. Cookies We Do Not Use

We do not use:

Advertising or retargeting cookies
Social-media tracking pixels for ads
Third-party marketing analytics cookies (for example, Google Analytics advertising tags)

7. Managing Cookies and Preferences

On SeeFirst-branded pages, a cookie banner lets you choose Essential only or Accept optional. Essential cookies (sign-in, portal context, report unlock, Stripe payment) always work.

White-label client portals do not show the SeeFirst cookie banner; those surfaces rely on essential cookies only for portal function.

Most browsers also let you block or delete cookies. Blocking essential cookies will prevent you from signing in or using authenticated parts of the Service.

To reset optional preferences, clear site data for seefirst.io (or remove seefirst_consent_v1 from local storage) and reload the page.

8. Changes to This Policy

We may update this Cookie Policy from time to time. When we do, we will update the Effective Date at the top of this page. Material changes may also be described in our Privacy Policy or communicated by email where appropriate.

9. Contact Us

For questions about this Cookie Policy, contact us at:

Email: hello@seefirst.io Website: seefirst.io