Cookie Notice
Last updated July 23, 2026
This page lists everything Vusion stores on your device and why. We keep this deliberately small. If you only browse the public pages without signing in, we set no cookies at all. We use no advertising, retargeting, or campaign-tracking cookies anywhere.
Cookies we set
All of these are strictly necessary. They exist only to sign you in and keep that session working. There is no working signed-in experience without them, so they are not subject to consent. They are all first-party and are set only as part of signing in and keeping you signed in.
| Name | Purpose | Duration |
|---|---|---|
| authjs.session-token | Keeps you signed in after you log in. | Your session |
| authjs.callback-url | Returns you to the page you started from after sign-in. | Sign-in flow |
| authjs.csrf-token | Protects the sign-in form against cross-site request forgery. | Sign-in flow |
| auth_redirect_check | Prevents sign-in redirect loops. | 5 seconds |
| auth_redirect_count | Counts redirects so a loop can be broken. | 10 seconds |
| authjs.pkce.* / state / nonce | Secures the sign-in handshake (PKCE, state, and nonce) when you sign in with an external provider such as Google. Named with a __Secure- prefix in production. Cleared once sign-in completes. | Sign-in flow |
Storage on your device
The app also uses your browser's local and session storage. This is not a cookie and is never sent to a server. It stays on your device to remember your workspace between visits: your recent generations and assets, canvas and editor state, tool settings and presets, and one-time onboarding flags. It also holds a short-lived analytics session identifier that is cleared when you close the tab. You can clear all of it at any time from your browser's site-data controls.
Analytics
We use first-party, self-hosted, cookieless analytics. By default it stores nothing on your device and sends data only to our own servers, never to a third party. When you are signed in, your analytics activity is associated with your account so we can understand how the product is used per account, and interactions such as page views and clicks are recorded. Our legal basis is our legitimate interest in operating, securing, and improving the service. This processing is described in full in our Privacy Policy.