Current first-party cookie
| Name | Why it exists | Current behavior |
|---|---|---|
| vi_access_token | Mirrors the current customer access token so Next.js middleware can gate protected routes before the app finishes loading. | Set by frontend code after login or refresh, written as a first-party cookie, and cleared on logout. In the current frontend code it can be written with up to a 30-day max age even though the underlying access token is short-lived and refreshed separately. |
Other browser storage used by the app
- localStorage stores the customer access token, refresh token, selected workspace, and cached UI state such as billing and onboarding snapshots.
- sessionStorage holds a separate internal authentication value for internal operations tooling.
What the current frontend does not set
- No separate refresh-token cookie in the customer auth flow.
- No dedicated CSRF cookie in the current frontend implementation.
- Analytics and advertising cookies (Google Analytics and the Meta Pixel) are optional and load only after you accept them in the cookie banner.
Optional analytics cookies
On this website, Google Analytics cookies are set only if you accept analytics in the cookie banner. If you decline, no analytics cookie is set and the tag does not run.
- NREUM, NRJS-*: New Relic browser performance identifiers that help us measure page speed and client-side errors. They load only after you accept analytics and are not used for advertising.
- _ga, _ga_*: Google Analytics identifiers that help us count visits and see which pages are used. Retention follows our Google Analytics settings; Google does not receive your name, email or social account data from this website.
You can change your choice at any time using the Cookie settings link in the footer, by clearing this site's browser storage and reloading the page, or by blocking cookies in your browser. See our Privacy Policy for more.
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.