vBrief Demo - Cookie / Storage Policy

Last updated: 05/12/2025

This policy explains how the vBrief Demo uses cookies and similar technologies. It does not apply to our main marketing site at vbrief.ai, which is covered by a separate Cookie Policy.

1. Technologies we use

The Demo uses HTML5 local storage in your browser to:

  • remember your current position in the simulated workflow;

  • keep track of the demo project data and any test edits you make;

  • and support the functioning of interactive features.

We do not use:

  • cookies;

  • tracking pixels;

  • device fingerprinting;

  • analytics or advertising technologies.

2. Why we use local storage

Local storage allows the Demo to work as a self-contained simulation without sending your interactions back to our servers. It is strictly necessary for the Demo to function as requested.

Because we only use storage that is essential to provide the Demo you choose to access, PECR does not require us to obtain your consent via a cookie banner. We are still required to explain clearly what we do, which is the purpose of this policy.

3. What is stored

The specific items stored can change as we develop the Demo, but will generally include:

  • configuration and state for the Demo interface;

  • simulated project data and scenario progress; and

  • any content you type or paste into the Demo, including (if you use it contrary to our instructions) personal data or live project information.

All of this data stays in your browser on that device, unless and until you delete it.

4. How to clear storage

You can remove data stored by the Demo at any time by using your browser’s settings (for example “Clear browsing data”, “Clear site data” or similar) and selecting the relevant site.

If you clear this storage, the Demo will reset and any previous changes you made in the simulation will be lost.

5. Changes to this policy

If we change the technologies used for storage or add non-essential features (for example, analytics), we will update this policy and, where required, introduce a consent mechanism before those features are activated.