Legal · draft
Cookies policy
Last updated: 24 October 2026
Draft, not legal advice
This text is a working draft prepared for the product build. It has not been reviewed by counsel and is not a substitute for jurisdiction-specific advice. No billing or public generation launches before review.This page describes what this site and the product actually store in a browser today. It is short because very little is stored: the marketing site is a static build with no analytics and no advertising pixels.
1. Marketing site (vividprop.io)
This static site sets no analytics, advertising or preference cookies. Fonts are self-hosted at build time, so no third-party font request is made. The language and currency selectors work from the URL and a server-side country header, not from a cookie.
Our host and CDN may set strictly necessary infrastructure cookies, such as bot-management and load-balancing identifiers. These are not used to build a profile and are not read by our application code.
2. Product (app.vividprop.io)
- Session cookie: an HttpOnly, SameSite session cookie issued by the authentication layer. It keeps you signed in and is required to use the product. Deleting it signs you out.
- Security records: session and device records are stored server-side, not in the browser, and are used to revoke access.
3. Internal panel (panel.vividprop.io)
The panel is a separate identity system with its own cookie prefix and secret. It is not reachable from this marketing site and sets no cookie unless a staff member signs in.
4. What is not here yet
There is no analytics product, no advertising pixel, no session recording, no A/B testing tool and no consent-management platform. If that changes, this page and the privacy policy change first, and consent is requested before any non-essential cookie is set.
5. Controlling cookies
Every browser lets you block or delete cookies. Blocking the session cookie means the product cannot keep you signed in; there is no fallback. Questions about this page: [email protected].