Cookie policy

24 September 2026

This website sets no cookies. It also writes nothing to your browser's storage and loads nothing from anyone else's server. That is why you were never shown a consent banner: there is nothing here to consent to.

What we checked

This is a claim worth being specific about, because plenty of sites make it loosely. On every page of duskline.io:

• no cookie is set by us, first-party or otherwise;
• no third party is in a position to set one, because the pages load no third-party resources at all — the fonts, images and stylesheets all come from this domain;
• nothing is written to localStorage, sessionStorage, IndexedDB or the cache API;
• there is no analytics script, no advertising pixel, no tag manager, no session recorder, no A/B testing tool and no embedded chat widget;
• there is no fingerprinting: the pages do not read your fonts, canvas, audio stack, battery or device list.

The pages carry a content security policy that enforces most of this at the browser level — it permits only this site's own images, fonts and manifest and blocks everything else, so a third-party tracker could not load even if one were added by mistake. You can read it in the page source.

What the site does store

Ordinary browser caching of the pages, images and fonts, so a second visit is faster. That is the browser's own cache, not a cookie: it holds no identifier, it says nothing about you, and clearing your browsing data removes it. The caching rules are set out in the site's server configuration — HTML is always revalidated, images are held for thirty days, and the font files, whose names describe their exact contents, for a year.

What a server log is, and is not

Our host records each request to the site — IP address, time, URL, status code, user-agent. That is a server-side log, not a cookie, and it is not something we place on your device or can read back from it. It is covered by the privacy policy.

Why this matters for a demonstration

If you are evaluating DuskLine, you may be asked by your own compliance team what the vendor's website does with visitor data. The answer is: nothing. No record is created that identifies you as having read this page, and no profile of your visit exists to be handed to anyone.

If this changes

If we ever add something that sets a cookie or stores an identifier — a measurement tool, a support widget, an embedded video — this page will say so before it goes live, and anything that is not strictly necessary will ask for your consent first, with refusing as easy as accepting.

Contact

Questions about this page: contact@duskline.io.