Cookie Policy
Every cookie we set, what it does, and how to change your mind.
This is version 1.0, archived on 26 July 2026. It is kept for reference and is not the current document — read the current version.
- Version
- 1.0
- Effective
- 26 July 2026
- Applies to
- Drentova Group Ltd
- History
- 1 version
How we use cookies
Necessary cookies are always on. Everything else waits for you to say yes, and you can change your answer whenever you like.
A cookie is a small file a site stores in your browser. Under the Privacy and Electronic Communications Regulations we may only set cookies that are strictly necessary without asking you first. Everything else — analytics and marketing — is set only after you agree.
When you first visit, we ask you to accept, reject or choose. Rejecting everything optional does not limit your use of the site in any way.
Cookies we use
This table is generated from the tags actually enabled on the site, so it cannot list something we have switched off — or omit something we have switched on.
Strictly necessaryalways on
Required for the site to work. These are set without consent because the site cannot provide what you asked for without them.
| Cookie | Set by | Purpose | Retained |
|---|---|---|---|
| drentova_consent | Drentova(first-party) | Remembers which cookie categories you accepted, so you are not asked again on every page. | 180 days |
| payload-token | Drentova(first-party) | Keeps a signed-in administrator authenticated. Only set if you sign in to the content management system. | Session |
Google Tag Manager is enabled but sets no cookies.
Changing your choice
Use “Cookie preferences” in the footer of any page to reopen the banner and change your answer. You can also delete cookies through your browser settings at any time; doing so will make us ask you again on your next visit.
Cookies set by other Drentova products
Each Drentova product runs the same consent mechanism. Where a product is on a subdomain of https://drentova.com, your choice carries across it. Where a product has its own domain, your browser keeps that decision separate and the product will ask you once — this is a limitation browsers impose deliberately, and working around it would be the cross-site tracking consent exists to control.
How to contact us
- Privacy and data protection
- [email protected]
Change log
- v1.0 · 26 July 2026First published version.