01
No cookies observed in ordinary public-page delivery
Current status
0 observed cookie types · 0 analytics or advertising technologiesApplication and public production responses inspected on 24 August 2026.Levyloom's page code does not set a cookie. During our latest audit, the current levyloom.com and www.levyloom.com pages returned no Set-Cookie response header and placed no cookie in the browser. No cookie is required to view the site in its current public configuration.
The site does not use local storage, session storage, analytics identifiers, advertising cookies, tracking pixels, session replay, third-party embeds, or a service worker to recognise or profile visitors. There is therefore no cookie-consent banner in the current configuration. This is a point-in-time statement, not a promise that the technology can never change. Any future technology that requires consent must remain off until a visitor has been given the required information and a valid choice.
02
What cookies and similar technologies are
A cookie is a small piece of data that a website asks a browser to store on a device. Cookies may last only for a browsing session or remain until a set expiry date. They may be set by the website you visit or by another service used on that website.
Similar technologies can store or access information through other browser features. The same privacy and consent principles may apply where they perform a comparable function, even if they are not technically called cookies.
03
Current technology audit
Scroll horizontally to see all columns
| Category | Technology | Purpose and duration |
|---|---|---|
| Cookies in ordinary page delivery | None observed · Vercel-hosted public pages | A response-header and browser audit on 24 August 2026 found no cookie on either public hostname. Re-audit is required after any hosting, protection, analytics, application, or delivery-configuration change. |
| Section navigation | URL fragment and native browser history · limited Levyloom first-party code | Records the page section a visitor chooses so native navigation, the back button, and shareable section links work as requested. First-party code may replace a retired section fragment with its current destination. The fragment remains in the URL or browser history until changed or cleared, contains no user identifier, and is not sent to Levyloom in an ordinary web request. |
| Adaptive presentation | CSS media queries and limited matchMedia checks · Levyloom first-party code | CSS adapts the layout to the viewport. First-party code checks reduced motion, forced colours, viewport size and supported data-saving preferences to control finite entrance effects and the silent About video. Playback also responds to section and page visibility. The About video plays once per page visit. A pause choice lasts only while the page is open, including an Escape-key stop, without cookies or browser storage. These signals are not retained or sent as preference data, or used to identify or profile visitors. The browser requests only the selected local video size when playback is eligible. |
| Preference or functional cookies | None | Not applicable |
| Analytics or performance cookies | None | Not applicable |
| Advertising or social-media cookies | None | Not applicable |
| Local or session storage | None | Not applicable |
| Pixels, fingerprinting, or session replay | None | Not applicable |
Vercel hosts and delivers this website. It may process routine network and request information to deliver, secure, and troubleshoot the service, but our latest public-page audit found no cookie or analytics request. ReadVercel's privacy notice for information about its handling of service data.
UK consent exceptions are assessed from the visitor's perspective and are purpose-specific. A provider's product description does not by itself decide whether a technology is exempt. If a future technology stores information or accesses a visitor's device, Levyloom must document why its use is within an applicable exception—or disable it or obtain valid consent before use. See theICO guidance on storage-and-access exceptions.
We recheck the deployed site
Optional hosting, deployment-protection, analytics, application, or security features can change this position. The public origin must be re-audited after any DNS, CDN, firewall, challenge, hosting, analytics, or application change, and this table must be updated if a cookie or similar technology is introduced.
What is not a cookie
Your browser may cache public files such as HTML, styles, scripts, and images to load the page efficiently. A hosting or security provider may also create routine server logs when responding to a request. Those processes do not place a cookie on your device, although server logs may contain personal information such as an IP address and are covered by our privacy notice.
The website uses URL fragments for static section links. First-party code may replace a retired section fragment with its current destination so old links still reach relevant content. The fragment stays in your browser and is not sent to Levyloom as part of an ordinary web request. It is not stored in a cookie or web-storage API.
04
Consent and future changes
Levyloom will not introduce a non-essential cookie or similar technology unless its owner, purpose, information use, provider, and duration have been assessed and documented. Where consent is required, the technology must remain off until a visitor makes a clear choice, rejecting must be as easy as accepting, and a way to change the choice must remain available.
If the technology changes, this policy and the audit table must be updated at the same time. The “Last updated” date will show when that happened.
05
Your controls and questions
Most browsers let you inspect, block, or delete cookies through privacy settings. No known Levyloom-domain cookie is currently required to view the public site.
If you observe a Levyloom-domain cookie or storage entry that is not described here, please take a screenshot or note its name, domain, and time, then email admin@levyloom.com. It may come from a hosting configuration, browser extension, security product, or a change that needs investigation.