Cookie Policy

Effective date: 17 September 2026

This site sets no cookies. That is a deliberate decision rather than an oversight, and this page explains what it means, what happens instead, and what would have to change before a single cookie appeared.

What a cookie is

A cookie is a small file that a website asks your browser to store and to send back on later visits, which is how a site recognises a returning browser. Cookies are used for useful things such as keeping you logged in, and for tracking, which is how the same advertising follows you between sites.

This site sets none, and permits none

Velox Network sets no cookies of its own, and no third party is permitted to set a cookie through it. Specifically, there is no analytics cookie, no advertising or conversion cookie, no tracking pixel, no social media embed, no video embed, no chat widget, no A/B testing tool and no session identifier. There is nothing to log into, so there is no session to keep.

This is also why you have not been shown a consent banner. Consent banners exist to obtain permission for cookies and similar technologies. With none in use, a banner would be asking permission for something that does not happen, and a site that displays one anyway is describing itself inaccurately.

No cookie name is listed on this page because there is none to list. If you find a cookie set from this domain, something is wrong and the publisher wants to hear about it at info@veloxnetwork.online.

What happens instead

Two things, both described in full in the privacy policy.

Server logs. The hosting provider's server records each request in the ordinary way: the IP address, the user agent string, the URL requested and the timestamp. This happens at the server and involves nothing stored on your device. Those logs are retained for 30 days.

Web fonts. The typefaces used here are loaded from Google Fonts, so your browser makes a request to Google's servers for the font files. That request discloses your IP address and user agent to Google, as any cross-domain request does. It sets no cookie and carries no identifier. Google's privacy policy is at policies.google.com/privacy.

Browser storage and fingerprinting

Nothing is written to localStorage, sessionStorage or IndexedDB by this site, and no data is cached in your browser beyond the ordinary caching of the page, stylesheet, script and font files that any browser performs for any website.

No fingerprinting is performed. The site does not read your canvas, enumerate your fonts or devices, measure your screen for identification, or combine browser characteristics into an identifier. The only JavaScript on the site is a short first-party file that opens and closes the navigation menu, it is readable in full at /assets/main.js, and it neither stores nor transmits anything.

Controlling cookies anyway

Whatever this site does, your browser is the place where cookies are controlled across every site you visit. Every current browser lets you view stored cookies, delete them individually or all at once, block third-party cookies, block cookies from a specific site, and clear everything when the browser closes. The controls sit under privacy or site settings, and the browser's own help pages describe them for the version you are running.

Blocking cookies entirely will break sites that rely on them for logging in. It will have no effect on this site, which works identically either way.

If this ever changes

Should a cookie, tag or similar technology ever be introduced, three things happen in the same change and before it goes live: this page is rewritten to name each cookie, its purpose and its lifespan; the privacy policy is updated to match; and a consent mechanism is put in place so that nothing non-essential is set until you have agreed to it. The effective date at the top of this page would change on the same day.