How we use cookies and browser storage.

Data Insight Out relies on essential cookies and limited browser storage to support sign-in, session continuity, security, billing workflows, saved builder preferences, and aggregate product analytics. We do not use analytics for advertising personalization.

Last updated June 1, 2026

Essential cookies we use

Session cookies: used to keep you signed in, secure your account session, and route you back into your workspace.
Supabase session continuity cookies: used to bridge secure login state between the frontend and the backend.
Operational cookies: used for service behaviors such as admin billing test mode where applicable.
Analytics cookies: used by Google Analytics to understand aggregate traffic, unique users, sessions, referrals, and privacy-filtered product events.

Local storage we use

Temporary app preference state that helps pages stay consistent during a session.
Builder draft or preference state to help preserve in-progress editing during a session.

Browser storage is used to improve continuity and reduce avoidable reloads. It is not a substitute for saving work to the server.

Why we use them

To authenticate users and protect shared workspaces.
To keep critical product features working after page loads and refreshes.
To remember limited product preferences or draft state that you expect the service to preserve.
To support billing and account-management flows when those features are enabled.
To measure aggregate traffic and product funnels without sending uploaded dataset content, project names, file names, email addresses, report text, or project identifiers to analytics tools.

Third-party services

Some browser storage or cookies may also be set by services that power core parts of the product, such as Supabase for authentication, Stripe for billing, or Google Analytics for aggregate traffic and product usage measurement. Those providers process data according to their own notices and agreements in addition to ours.

What we do not use analytics for

We do not send dataset contents, project titles, file names, email addresses, report text, project identifiers, or advertising personalization signals to Google Analytics. Analytics events are limited to page traffic, broad source and device information, and product flow outcomes such as project creation, uploads, publishing, AI generation, billing checkout, and errors.

Managing cookies

You can control cookies through your browser settings. Blocking essential cookies may prevent sign-in, report sharing, billing workflows, or parts of the builder from working correctly.

Questions

If you need more detail about the cookies or browser storage used by the current product version, contact support@datainsightout.com.