Verifex uses only strictly necessary cookies. These are first-party cookies required to sign you in securely and to protect authentication requests. They are not used for tracking or advertising.
Cookies we set
| Cookie | Purpose | Type | Duration |
|---|---|---|---|
verifex-csrf | Lets the app validate the x-csrf-token header on protected mutations. | First-party | 24 hours (Secure, SameSite=Lax, readable by the app for the double-submit CSRF check) |
__Secure-next-auth.session-token | Maintains your authenticated session when signed in to the dashboard. | First-party | 24 hours (httpOnly, secure) |
__Secure-next-auth.callback-url | Stores the URL to return to after sign-in. | First-party | Short-lived (secure) |
__Host-next-auth.csrf-token | Cross-site request forgery (CSRF) protection for authentication. | First-party | Session / short-lived (secure) |
What we do not use
The current public application build does not include Google Analytics, GA4, Firebase Analytics, advertising, or third-party tracking cookies, and it does not set an _gacookie. Verifex does not currently operate a consent-management platform. This policy will be updated before any non-essential cookie or tracking technology is introduced.
We may use a first-party, cookieless product-event signal with an allowlisted and scrubbed event vocabulary to understand aggregate product usage. It does not rely on cookies.
Browser storage and error reports
The dashboard also keeps a few settings in your browser's local storage, such as whether you have finished the quick-start guide, dismissed a banner, or collapsed the sidebar, and a short-lived session storage marker used to recover from a failed page load. They stay on your device and are not used for tracking.
If the site or dashboard hits an error, the browser can send an error report to our error-monitoring provider, Sentry, through our own domain. No cookie is involved, and personal details are removed before sending; see /subprocessors.
More information
For how we handle personal data more generally, see our Privacy Policy.