Cookie Policy

This Cookie Policy explains how the viggoVet group (“viggoVet”, “we”, “us”) uses cookies and similar technologies on our public website (viggo.vet) and our platform. The viggoVet entity responsible for your region is identified in our Legal Entities document. This Policy supplements our Privacy Policy, which explains how we handle personal data more generally.

1. What cookies are

A cookie is a small text file stored on your browser or device. Cookies let a site recognise your device, remember your preferences and session, keep you signed in, and understand how the site is used. We also use similar technologies such as local storage, pixels, and software development kits, which we refer to together as “cookies”. Cookies cannot run programs or deliver viruses.

2. The two environments we operate

• Our public website (viggo.vet): a WordPress site that uses essential cookies plus, with your consent where required, analytics and marketing cookies provided by us and third parties.
• Our platform (the signed-in application): uses mainly strictly necessary, session-based cookies to keep you logged in securely and to operate the service. We do not run advertising cookies inside the platform.

3. Categories of cookies we use

• Strictly necessary: required for the site or platform to work, including login, session continuity, security, load balancing, and remembering your cookie choice. These do not require consent.
• Functional: remember preferences and enable features such as in-app messaging and live chat.
• Analytics: help us understand how the website and product are used, on an aggregated basis, so we can improve them.
• Marketing / advertising: help us measure campaigns and reach relevant audiences. We use these only on the public website and only with your consent where required.

Consistent with our Privacy Policy, we never use cookies to train AI models on your data, and we do not sell your personal data.

4. Consent and how to change your choices

In regions that require consent (including the EEA, UK, Switzerland, and similar), non-essential cookies are set only after you accept them through our consent banner, which is provided by CookieYes. You can change or withdraw your choices at any time by reopening the cookie settings from the link in our website footer. Withdrawing consent does not affect cookies already used while consent was in place. Strictly necessary cookies are always active because the service cannot function without them.

5. Cookies on our public website

Our public website uses a small set of essential cookies, listed below, and, only with your consent where required, a changing set of non-essential cookies described in the next section.

Essential cookies (always active)

Durations are provider defaults and may vary by configuration.

6. Non-essential cookies (analytics, personalisation, chat, and lead attribution)

On the public website we also use non-essential cookies and similar technologies for: analytics and product/usage insight; personalisation; customer messaging and live chat; and lead attribution and marketing measurement. We test and change the specific tools we use for these purposes from time to time, so the individual providers and cookie names are not fixed.

For that reason we do not keep a fixed vendor list in this document. The current, authoritative list of the exact non-essential cookies in use at any time, with their providers and durations, is always available in our cookie preference centre (powered by CookieYes), which you can open from the link in our website footer. These cookies are set only after you consent where consent is required, and you can change or withdraw your choice there at any time.

What stays constant: whichever tools we use, non-essential cookies remain consent-gated where the law requires, we never use cookies to train AI models on your data, and we do not sell your personal data. If a page embeds third-party media (for example a video), that provider may set its own cookies when the media loads, and its own policy then applies.

7. Cookies on the platform

Inside the signed-in platform we use only strictly necessary and functional cookies and local storage to keep you authenticated and the service working. We do not run advertising or cross-site marketing cookies inside the clinical platform. These items are first-party and many are HttpOnly (not readable by scripts) for security. They include:

• Authentication and session: a session identifier, an authentication token, a cross-site request forgery (CSRF) protection token, your data-region preference, and, if you choose them, two-factor-authentication and “remember me” cookies.
• Federated sign-in: where you log in with Google, a Google Sign-In state value is used to complete authentication.
• Billing: on payment and billing pages, Stripe sets a fraud-prevention cookie.
• Interface preferences: values that remember your interface settings, such as theme and menu state, and limited local storage the application needs to function (for example language, selected clinic, and permissions for the current session).

We can provide the current technical list on request.

8. Third-party providers and their policies

Some cookies are set by third parties that process data under their own privacy and cookie policies. The non-essential providers we use change over time as we test tools, so we list the current providers (with links where available) in our cookie preference centre rather than fixing them here. Where a provider acts as our processor it is bound by data-protection terms; where it acts as an independent controller, its own terms govern. Our stable, essential providers include CookieYes (consent), Stripe (payments), and our website and hosting infrastructure.

9. Managing cookies in your browser

In addition to our consent tool, all major browsers let you block or delete cookies. Disabling cookies may affect how the website and platform work. See your browser’s help pages (Chrome, Firefox, Safari, Edge, Opera) for instructions.

10. Do Not Track and Global Privacy Control

Because there is no common industry standard for “Do Not Track”, our website does not respond to DNT signals. Where required by law, we honour recognised opt-out preference signals such as Global Privacy Control.

11. Changes to this Cookie Policy

We may update this Policy to reflect changes in our practices, the tools we use, or the law. We will post the updated version with a new effective date and, where appropriate, ask for renewed consent.

12. Contact

Questions about cookies: the contact form at viggo.vet/legal/contact. For how we handle personal data generally, see our Privacy Policy.