Skip to main content
Veyrova

Cookies and local storage

Last reviewed

Most sites open this page to explain a banner. This one opens it to explain why there isn't one.

1.What this website stores

Nothing. This site sets no cookies of its own, sets nothing in local storage or session storage, and loads no third-party script, font, map, video or social embed that could set one on its behalf.

Fonts are served from this domain rather than from a font provider, so opening the page does not tell anyone else that you did.

The one thing the site sends anywhere is what you type into the beta form, and only when you press the button.

2.Why there is no cookie banner

Consent under the EU ePrivacy rules is required before storing or reading information on your device for anything that is not strictly necessary. This site stores nothing at all, so there is nothing to consent to, and a banner would be theatre: a dialogue asking permission for something that is not happening.

If analytics or any other non-essential technology is added later, a real consent manager comes with it: nothing non-essential loading before a choice is made, refusing as easy as accepting, no pre-ticked boxes, and a way to change your mind from the footer. Until then, this page is the whole story.

3.What the server sees

Ordinary web request information reaches the server and its host in order to deliver the page: the address requested, the browser's user agent, and the connecting IP address.

When you submit the beta form, the IP address is used in memory to limit how many submissions can come from one place in an hour. It is reduced to a number that cannot be turned back into an address, is never written to a log, and is never stored with your email address.

4.What the Veyrova app stores on your device

The app is not this website, and it does store things locally, because it has to work without a connection:

  • Your session. The authentication token that keeps you signed in. Removed when you sign out.
  • A copy of your profile and recent data. So the app opens with your numbers rather than a spinner. Cleared when you sign out, and never shown to a different account.
  • A queue of changes made offline. Meals and sets recorded without a connection, held until they can be sent. Each entry is stamped with the account that made it, so one person's queue can never be sent into another person's account.

None of this is advertising or tracking storage. What the app collects and why is in the privacy notice.

If you find this site setting a cookie, that is a bug and we want to hear about it. The claim on this page is checked against the built site before each release.