Cookie policy

Last updated: September 2026

The short version

DeviceBench sets no cookies. Not for analytics, not for advertising, not for sessions, because the site has no accounts, no ads and no server that receives anything of yours. That is why you see no cookie banner: under the ePrivacy rules a consent banner is required only for cookies and similar storage that are not strictly necessary for something you asked for, and there is nothing of that kind here.

Analytics without cookies

Page views are counted by Plausible Analytics, which is cookieless by design. It stores nothing on your device, uses no persistent identifier, does not track you across sites, and is hosted in the EU. We see aggregate counts of pages, referrers, countries and browser types, never an individual visitor. Because it neither sets nor reads anything on your device, it falls outside the consent requirement.

What the site does store in your browser

Two preferences, both set only by your own action and readable only by this site, live in your browser's local storage:

Neither value identifies you, neither is sent anywhere, and both are strictly necessary for the feature you turned on. They therefore need no consent. You can remove them at any time by clearing site data for devicebench.io in your browser.

Model files your browser caches

Running a browser model for the first time downloads its weights from the publisher (Hugging Face for WebGPU models, Google for Chrome's built-in model). Your browser keeps those files in its cache so the model does not download twice. That cache holds model weights, not anything about you, and clears with your browser's site data.

Third parties

Every page loads one third-party script, Plausible's analytics snippet, from plausible.io. It sets no cookies. The lab additionally fetches the WebLLM library from the jsDelivr CDN (esm.run) the first time you run a WebGPU model, and only then; it is a code library, sets no cookies and is cached like any other file. No other third-party scripts, embeds, fonts or pixels are loaded on devicebench.io.

If this changes

If DeviceBench ever adds something that does need consent, this page will say so, a consent control will appear before that thing loads, and the privacy policy will be updated in the same release. The date at the top reflects the last material change.

Contact

DeviceBench is a product name of, and is operated by, Elowin Labs LLC. Questions about this policy: hello@elowinlabs.com.