Legal

Cookie & Tracking Policy

Every cookie, browser storage key and outside request Veyra actually makes, listed by name. The list is short: the cookies exist to sign you in, and there is no analytics, advertising or tracking technology anywhere on the site or in the application.

Last updated: 23 September 2026
Analytics: None
Advertising: None

The short version

Three cookies, all strictly necessary. They keep you signed in. Nothing else uses a cookie.
One stored preference. Whether you chose the light or dark theme, kept in your browser.
No analytics, no advertising, no tracking. No analytics package, tag manager, advertising pixel, session recorder, fingerprinting or cross-site tracking of any kind is loaded by this site.
One outside request. The two typefaces the site is set in are served by Google Fonts, which necessarily sees your IP address.

Cookies Veyra sets

These are set by Veyra's own server when you sign in; they are first-party, and none of them is readable by JavaScript running on the page. In production, where the site is served over HTTPS, each name is additionally prefixed with __Secure- and carries the Secure flag. All of them use SameSite=Lax, which stops them being sent on requests started by another website.

Strictly necessary cookies. There are no other categories.
Name	Purpose	Lifetime
better-auth.session_token	Identifies your signed-in session. Without it, every page in the application would ask you to log in again. It holds a random token, not your details.	7 days
better-auth.session_data	A short-lived cache of the session, so a page load does not have to query the database to know you are still signed in.	5 minutes
better-auth.dont_remember	Set by the authentication library when a session is deliberately not persisted, so that closing the browser ends it. Veyra does not currently offer that option, so in practice you are unlikely to see this one.	Until the browser closes

The marketing pages, the homepage and these legal pages, set no cookies at all. You can read every one of them without a cookie being written.

Browser storage

Veyra keeps a small amount of data in your browser's local storage rather than in a cookie, which means it is never sent to the server with your requests.

Local storage keys used by the application.
Key	Purpose	Lifetime
veyra.theme	Remembers whether you chose the light or dark theme on this device, so the correct one is applied before the page paints. If it is absent, Veyra follows your operating system setting instead.	Until you clear it

That is the only key the hosted application writes. Blocking it costs you nothing but the remembered theme.

The offline demo

Veyra can also run as a browser-only demonstration with no server behind it, used for development and for trying the interface without an account. In that mode, and only in that mode; the browser is the database, and these additional keys are written:

Written only by the offline demo, never by the hosted service.
Key	Contents
veyra.inventory.v1	The sample product catalogue and any changes made to it, including any product image added, which is stored in the browser rather than uploaded.
veyra.auth.users.v1	Demo accounts created in this browser.
veyra.auth.session.v1	The demo's stand-in for a session.

Nothing written by the demo leaves your browser, and nothing in it reaches Veyra's servers. It is not a secure store; anything kept there can be read or edited by anyone with access to the browser, so do not put real business data into it. The application tells you which mode you are in on Settings → Data and danger zone.

Outside requests

One third party receives a request when you load a Veyra page: Google Fonts, which serves the two IBM Plex typefaces the site is set in from fonts.googleapis.com and fonts.gstatic.com. Loading a font from another domain necessarily reveals your IP address, your browser's user-agent string and which page asked for it. No cookie is set by those requests, and no account or business data is involved.

If you connect a point-of-sale account, your browser is also sent to that provider's own sign-in page to authorise it. That page is theirs, not ours, and whatever cookies it sets are governed by their policies. Afterwards, the exchange of data happens between Veyra's server and theirs, not in your browser.

No other outside host is contacted. There is no CDN-hosted script library, no embedded video, no map, no chat widget, no social button and no remote image on any Veyra page.

How to clear or block them

Clearing site data for this site in your browser settings removes both the cookies and the stored theme. You will be signed out; nothing stored on the server is lost.
Blocking cookies for this site means you cannot sign in; the session cookie is how a signed-in request is recognised. The marketing pages and these legal pages still work normally.
Blocking local storage only stops the theme being remembered. The application detects this and continues to work.
Ending a session from the server side is done by logging out, or by changing your password, which signs out your other sessions.

Changes

This page is a factual register of what the software does. If a cookie, a storage key or an outside request is added or removed, this page is updated and the date at the top changes with it.

Contact

Questions about anything listed here:

Veyra; operated by Drew Weber

drew.weber2028@gmail.com