Cookie Policy

Effective date: 2026-10-31

The current VI Engine app uses a small number of browser storage mechanisms. Customer and FounderSpace authentication now rely on HttpOnly cookies, while localStorage and sessionStorage are reserved for workspace selection, short-lived presence flags, and other non-secret UI state.

Your choice

Necessary storage is always on. Analytics (PostHog, with masked session replay) stays off until you accept Analytics. Your choice and its date are stored in localStorage under vi-cookie-consent and in the vi_consent cookie, which the viengine.social website shares with the app so you are asked only once. Use Cookie settings in the footer to change it; that updates both. Withdrawing consent stops PostHog straight away. If storage is unavailable, the choice lasts only for this page. Scrubbed Sentry error reporting remains active; Sentry replay, browser tracing and logs are disabled.

First-party cookies

NameWhy it existsCurrent behavior
__sessionKeeps you signed in. It holds your short-lived access token and the refresh token that renews it.Set by the backend as an HttpOnly, Secure, SameSite=Lax first-party cookie, so page scripts cannot read it. It lasts up to 60 days and is cleared when you sign out or delete your account.
vi_consentRemembers your cookie choice (necessary only, or necessary plus analytics) and when you made it, so the website and the app ask once.A readable first-party cookie on .viengine.social, SameSite=Lax and Secure, kept for up to 180 days. It holds no personal data, for example v1:analytics:1793664000.
vi_refRemembers which partner introduced you to VI Engine, so that partner is credited if you later subscribe.Set only when you arrive through a partner link. A first-party cookie holding the partner's short code and nothing else, kept for up to 180 days and read only to credit that partner when you sign up.
vi_founderspace_sessionInternal FounderSpace session cookie established after internal credentials are verified.Set by the backend as an HttpOnly cookie scoped to /api/admin so the frontend does not need to persist raw FounderSpace credentials.

Other browser storage used by the app

  • localStorage stores selected workspace context and cached UI state such as billing or onboarding snapshots.
  • Signup marketing attribution is kept in first-party localStorage under vi_signup_attribution_v1 for up to 90 days. UTM campaign parameters and referrer may be captured always; ad click IDs (fbclid/gclid) are captured only after you accept non-essential cookies and are removed from our backend after 90 days. Attribution is attached to a new account so we can measure which campaigns bring signups. If you accepted analytics cookies and your browser does not send Do Not Track or Global Privacy Control, a verified signup is also reported once to Meta (Conversions API) with a hashed email address, a hashed account ID, your IP address, browser and click ID, so we can measure our own ads.
  • sessionStorage stores lightweight presence flags, temporary form state, and other non-secret session hints.
  • Only after you accept Analytics, configured PostHog uses first-party browser storage for product analytics. Its session replay records the rendered app and ordinary page text so we can support customers; passwords, one-time codes, payment fields and contact details typed into forms stay masked, and sensitive regions are explicitly masked. Replay is disabled on authentication, billing, settings, connections and inbox pages and respects Do Not Track and the PostHog opt-out. URLs with query strings or identifier-like path segments are not recorded.

Storage and security boundaries

  • No customer access or refresh token is stored in browser-readable storage.
  • No raw FounderSpace admin credential is persisted in localStorage or sessionStorage.
  • When PostHog is configured, its analytics storage is separate from authentication and is not used for route gating.

Third-party pages

Official social-platform authorization pages, identity providers, or payment/check-out pages may set their own cookies while you are on those domains. Those cookies are controlled by the third party, not by this frontend.

Contact

Questions about browser storage or cookies? Email privacy@viengine.social.