Vyso cookies policy
Cookies that support auth, speed, and a smoother experience.
Last updated: September 19, 2026. This policy explains how Vyso uses necessary cookies and similar technologies, what choices you have, and how to change them.
1. What are cookies (and similar technologies)
Cookies are small text files placed on your device when you visit a website. We also use similar technologies - local storage, session storage, and SDKs - that work the same way for the purposes of this policy. Cookies can be first-party, set directly by Vyso; third-party, set by a service we use; session, deleted when you close your browser; or persistent, remaining until they expire or you delete them.
2. Cookie categories we use
The categories below describe the browser technologies used by the current Vyso website and why.
| Category | Purpose |
|---|---|
| Strictly Necessary | Clerk authentication and session cookies, plus the vyso_cookie_consent cookie used to remember this choice. These are necessary for account access and consent management. |
| Analytics without cookies | Self-hosted Umami and Vercel Analytics provide aggregate analytics in the current implementation without analytics cookies. They are not optional cookie categories. |
3. Legal basis & consent
Strictly necessary cookies do not require consent because they are essential to providing the Service you requested. The cookie banner records your choice in vyso_cookie_consent, while the current Umami and Vercel Analytics implementations do not set analytics cookies.
If Vyso introduces additional non-essential cookies, the banner and this policy will be updated before they are enabled where consent is required.
4. Managing your preferences
You can change your cookie choices at any time.
- Website: use the Cookie Preferences link in the footer to review the current cookie details.
- Browser controls: most browsers let you block or delete cookies via settings. Blocking strictly necessary cookies will affect sign-in, session continuity, and core features.
- Because the current analytics implementations are cookieless, browser cookie controls do not disable aggregate analytics collection. Contact [email protected] with questions about current analytics processing.
5. Third-party cookies
Clerk may set necessary authentication and session cookies. The current Umami and Vercel Analytics implementations do not set analytics cookies. These providers may process data under their own privacy policies in addition to ours.
6. Changes to this policy
We will update the “Last updated” date above when this policy changes. Material changes will be reflected in the cookie banner so you can review and re-confirm your preferences.
7. Contact us
Questions about cookies or your choices can be sent to [email protected].
For current provider details, see the Subprocessors page.