Nexus cookie policy.

Last updated: 23 July 2026.

Privacy-first statistical measurement

We use a random identifier in sessionStorage under nexus.analyticsSession to count sessions, page views and aggregate journeys. It expires when the browser session ends. Raw server-side session state is retained for no more than 24 hours and is then removed; only aggregate statistics remain. We do not store IP addresses, complete user-agent strings or permanent visitor identifiers.

You can opt out at any time. That preference is stored locally as nexus.analyticsOptOut so the website can remember your choice. No consent banner is used.

We have designed this limited measurement around the ICO’s statistical-purpose exception ↗, including clear information and a simple opt-out. This policy should be kept under legal review as guidance changes.

Local browser storage

The website uses limited browser storage to remember a pricing-currency choice and whether you dismissed the launch-offer banner.

Referral URLs are reduced to their origin and path before storage, so query strings and fragments are not retained. Sanitised campaign labels supplied in links, such as source and standard UTM labels, may be stored to measure the effectiveness of a link.

Server logs are not cookies

Our hosting and security infrastructure may create routine server logs when a page is requested. These can include an IP address, browser information, request time and requested page. Logs do not place information on your device and are handled as described in our privacy policy ↗.

Third-party websites

Links to services such as Revolut and Discord take you to another provider’s website. Those providers may use their own cookies or similar technologies under their own policies. Nexus does not control storage set after you leave this website.

Protected video access

After a correct access code is entered, Nexus sets a short-lived, HttpOnly cookie scoped only to that video’s streaming API. It authorises playback and cannot be used for advertising or cross-site tracking. The cookie is cleared whenever the watch page loads so the code is requested again.

Protected Video Hubs use the same approach, with a cookie scoped only to that hub’s collection of streaming APIs. One correct hub code authorises the ordered videos in that collection for the current visit.

Temporary, privacy-preserving security records are used to rate-limit incorrect code attempts. They use a one-way network hash and are automatically removed.

Managing browser storage

You can remove the saved preferences through your browser’s privacy or site-data settings. Blocking browser storage may prevent the website from remembering your selections, but the rest of the public website should continue to work.

If our use changes

If we materially change the analytics or introduce advertising or other technologies, we will update this policy and provide any choices required before those technologies are used.

Contact us

Questions about cookies or privacy can be sent through our contact page ↗.