Legal

Cookie Policy

Last updated: September 2026

This policy explains how Vetrixo uses cookies and other browser storage or access technologies. These technologies are described separately where they are not cookies.

1. Who we are

Vetrixo is operated by VETRIXO LTD, a company registered in England and Wales under company number 17444709. Its registered address and correspondence address is 71-75 Shelton Street, Covent Garden, London, United Kingdom, WC2H 9JQ. Contact us at hello@vetrixo.co.uk.

2. Cookies and other technologies

Cookies are small text files stored on a device. Other technologies can also store information or access information on a device, including local storage, session storage, IndexedDB, cache storage, pixels, scripts and device identifiers. The technology and its purpose matter; not every script uses a cookie.

3. Public homepage

The public homepage does not load Firebase and its own code does not use cookies, local storage, session storage or IndexedDB. It does not use Session Replay, Sentry release-health or BrowserSession tracking, pageview or visitor measurement, behavioural monitoring or profiling. It does use Sentry error monitoring and application performance tracing.

The homepage loads the Sentry browser library for error monitoring and application performance tracing. Monitoring may include technical information such as browser and device details, page paths, error stack traces, navigation breadcrumbs, performance timings and random event or trace identifiers held in browser memory. Click, input, keypress, console, form, fetch and XHR breadcrumbs are discarded before transmission. Session Replay, Sentry Logs and Sentry Application Metrics are not enabled.

Sentry is configured not to send default personal information, and Vetrixo applies additional redaction before error or tracing events are sent. Vetrixo is configured to redact sensitive prescription, identity, authentication, QR, passkey, Didit, email, phone and address data. The current Sentry configuration does not intentionally set or use cookies, local storage, session storage or IndexedDB. A browser request to Sentry necessarily provides standard network information, including the source IP address; Sentry's account-level IP handling and retention must be confirmed from the production provider settings.

4. Prescription verification and pharmacy fulfilment pages

The pharmacy page's own code does not use cookies, local storage, IndexedDB, Cache Storage or a service worker. It sends verification and fulfilment requests to Vetrixo's same-origin server endpoints. Prescription and access credentials, supplying-premises details, quantities supplied and request identifiers are held in browser memory only for the workflow and are sent only to those endpoints. A correction credential returned after a supply is recorded is also held in browser memory only and is discarded when the page is closed or reloaded.

For safe retry handling, the page stores a pending fulfilment request identifier, prescription identifier and a one-way submission fingerprint in session storage. The fingerprint is derived from the supplying-premises details, the name or initials of the person supplying and the quantities but does not contain those values in readable form. This record is removed after a successful fulfilment and otherwise expires when the browser tab session ends.

The pharmacy page also loads the Google Firebase Authentication browser library so that a pharmacy that has chosen to sign in to an optional Vetrixo pharmacy account is recognised on the page. Firebase Authentication may use IndexedDB or other browser storage to keep that sign-in session, as described for the authenticated application below. An account is not needed to verify a prescription or record supply. When a signed-in pharmacy records supply, its sign-in token is sent to Vetrixo's server endpoint in a request header so that its saved premises details can be applied.

The page loads the Sentry browser library from Sentry's CDN for error monitoring and application performance tracing. The same redaction and restricted-breadcrumb configuration described above applies. Session Replay, Sentry Logs, Sentry Application Metrics, automatic session tracking, client reports and feedback injection are disabled. The page does not contact Google Fonts.

5. Authenticated Vetrixo application

The Vet Portal and other authenticated or transactional parts of Vetrixo use Google Firebase and may use cookies or browser storage, including local storage, session storage or IndexedDB, for authentication, session continuity, security, fraud prevention and core prescription-workflow functionality. The exact storage used can depend on the Firebase service, browser and production configuration.

Authenticated pages also load the same restricted Sentry error monitoring and application performance tracing, alongside the Firebase application storage described here.

6. Purposes and consent

Storage or access that is essential to provide a service requested by a user may be used for authentication, security, fraud prevention, session continuity and core functionality. Vetrixo treats the restricted Sentry configuration as technical fault detection and application performance diagnosis rather than behavioural analytics. The current Sentry configuration does not intentionally use cookies or browser storage; its technical processing is addressed under legitimate interests in the Privacy Policy. Whether a particular use qualifies for an exception from consent depends on its actual purpose and operation and is kept under review.

If Vetrixo enables non-essential analytics, visitor measurement, behavioural monitoring, Replay or other non-exempt storage or access technologies, they must not be activated before any consent required by law has been obtained.

7. Third party services

Google Firebase supports hosting, the pharmacy page's same-origin server endpoints and the authenticated application's authentication, data and server-side functionality. Sentry is used for technical error monitoring and application performance tracing. Other providers may support identity verification or security functions within the authenticated service. Their use is limited to the relevant service purpose and is also described in the Privacy Policy.

8. Managing browser storage

You can inspect or remove cookies and browser storage through your browser settings. Blocking storage that is necessary for the authenticated application may prevent account access or prescription workflows from operating correctly.

9. Changes to this policy

We may update this Cookie Policy from time to time. The latest version will be published on Vetrixo.

10. Contact

Questions should be sent to hello@vetrixo.co.uk.