Cookie Policy
Four things are answered here: what onevialtd.com keeps in your browser, what the delivery and security service it uses (Cloudflare) may add, what the robot check on the order form uses, and how to undo your choice.
Does this site set cookies of its own?
No. The site's own code sets no cookies. It has no analytics and no advertising, and its fonts are served from our own domain. One thing on it comes from another party: the robot check on the order form, Cloudflare Turnstile, which is described below and is needed for the form to work. Nothing on the site is optional at present; if an optional tool is ever added, it will be listed on this page and will stay off until you allow it.
What does it store in my browser, then?
One local storage entry named onevia_consent. It is written at the moment you answer the cookie question, not before. Local storage is a place in your browser where a site can keep data; unlike a cookie, it is not sent to the server with each request.
The entry holds your answer, the date and time you gave it, the date it runs out and the date of the policies in force at the time. Its only use is to stop the question returning on every page. It stays for 6 months; the first time you open a page after that, or after these policies change, the site deletes it and asks again. Only this site can read it, in your browser, and it is never sent to us.
Can anyone else set cookies when I visit?
Yes, one party can. Cloudflare, Inc. stands between your browser and our server: it delivers the pages and filters out automated attacks. Depending on how that protection is configured and on the request, Cloudflare may set security cookies of its own. They come from Cloudflare, not from our code, they are not used for analytics or advertising, and they do not depend on the answer you give to the cookie question.
- __cf_bm
- Set where Cloudflare's bot protection is active. It helps tell people from automated traffic and expires after 30 minutes without activity.
- cf_clearance
- Set after a browser passes a Cloudflare security check, so that the check is not repeated on every page. It lasts as long as that check stays valid, a period set in Cloudflare's configuration.
Which of its cookies a request receives is decided by Cloudflare, and you may receive neither of these. Its own list, with purposes and lifetimes, is at developers.cloudflare.com. Your browser's settings for site data show which cookies it actually holds for this site.
What does the robot check on the form use?
The order form is protected by Cloudflare Turnstile. Its script and its frame are loaded from challenges.cloudflare.com when you first put the cursor in the form; if you never touch the form, they are not loaded. The check is strictly necessary for the form: without it a list cannot be sent, so it does not depend on the answer you give to the cookie question.
- Turnstile token
- A single-use value that Turnstile places in a hidden field of the form once the check is passed. It is sent to our server with your list, is valid for a few minutes and is not stored in your browser.
- cf_clearance
- Turnstile sets this cookie for our domain only if Cloudflare's “pre-clearance” option is switched on for the form's widget. By default that option is off, and then Turnstile sets no cookie for our domain.
While the check runs, the Turnstile frame keeps data of its own in your browser under Cloudflare's address, challenges.cloudflare.com, not ours: when we tested the form it was one local storage entry named cf.turnstile.u. That storage belongs to Cloudflare, which decides what it holds and for how long; our code cannot read it. What Turnstile collects and why is set out in the Privacy Policy and in Cloudflare's Turnstile Privacy Addendum.
How do I change or withdraw my choice?
Reopen the cookie question with the button below or with “Cookie settings” at the bottom of any page. You can also delete the entry, and any Cloudflare cookies, in your browser's settings for site data. The site works the same without them.
Where is personal data covered?
In the Privacy Policy.
Version of 6 October 2026