Skip to content

Legal centre

Cookie Policy

Exactly what we store in your browser, why it's there, and how to turn off what isn't essential.

Last updated: 4 August 2026

1.What cookies and similar technologies are

Cookies are small files a site stores in your browser. VaultYou also uses local storage and session storage, which work the same way from a privacy perspective: they let the app remember something between page loads. This policy covers all three.

2.What we use, and why

Strictly necessary — always on. Your authenticated session is stored in your browser so you stay signed in across refreshes and tabs. Without it you would have to log in on every page. We also store small preference values, such as which conversion events have already been recorded, so we don't count the same action twice.

Analytics — production only. We use Google Analytics 4 to understand which pages are used and where people get stuck. It records page views, approximate location derived from IP address, device type and referrer. Analytics is not loaded in development environments.

What we don't use. No advertising cookies, no remarketing pixels, no cross-site tracking networks, and no selling of any data collected.

3.Third-party cookies

Cookies may be set by these providers when you use VaultYou:

  • Our authentication and database provider — session and security tokens (strictly necessary).
  • Google Analytics — measurement identifiers (analytics).
  • Google Sign-In — only if you choose to sign in with Google.

4.Managing cookies

You can clear or block cookies and storage in your browser settings at any time. Blocking strictly necessary cookies will sign you out and prevent VaultYou from working.

To opt out of Google Analytics specifically, install the Google Analytics opt-out browser add-on, or enable your browser's "Do Not Track" / tracking-prevention setting.

5.Changes to this policy

If we add a new category of cookie — for example if we ever introduce a support chat widget — we will update this page and the "last updated" date before it goes live. Read this alongside our Privacy Policy.