Cookie Policy

Cookies set by this domain: none

Not one, of any description. Not first party, not third party, not a session cookie that disappears when the tab closes.

A single local storage entry does get written. It holds which of the two buttons on the storage slab was pressed, so that the slab stays out of the way afterwards. That entry is the sum total of what delyavia.com leaves behind in a browser.

The list of things that are therefore absent is long and worth stating: nothing for advertising, nothing for measurement, no pixel, no beacon, no attempt at fingerprinting, and no component belonging to another company that could write anything of its own. That is not a promise about good intentions. It follows arithmetically from a site whose stylesheet, script, two typefaces and every last photograph are requested from delyavia.com and from nowhere else.

The entry, in detail

`dv_notice_winter_1`

• Type: local storage entry, which is a different mechanism from a cookie
• Written by: delyavia.com, and nothing else has the ability to
• Contents: a single word, `all` or `bare`, matching the button pressed
• Purpose: keeping the storage slab closed after it has been answered once
• Lifetime: indefinite, ending the moment site data for this domain is cleared
• Ever transmitted: no, because local storage is not attached to network requests
• Required for the site: no, its absence simply brings the slab back next visit

That is the complete inventory rather than an example of the sort of thing kept.

Why the mechanism matters

The difference is not a technicality worth waving away.

Cookies move. Once one is set, the browser attaches it to every subsequent request made to that domain, quietly and continuously. That behaviour is the reason cookie rules exist at all.

Local storage stays put. A script running on the page puts it there, a script running on the page reads it back, and it never leaves the device unless something deliberately picks it up and sends it. In this case nothing does.

Which is why the slab is phrased as a notice and not as a request for consent. The rules covering advertising and tracking storage find no subject matter here. Both buttons produce the identical result for a reader's privacy; they exist separately only so the recorded answer matches the one actually given.

Involvement of other companies

While a page is being read: none whatsoever.

Typefaces are served from this domain instead of from a font supplier. Nothing arrives from a content delivery network. There is no embedded map, no video player, no comments, no sharing button and no social component anywhere on the site, and those are the ordinary doorways by which somebody else's storage arrives on a page that believed it had none.

Exactly one outside service is touched, exactly once, and only in response to an action: sending either form passes the typed contents to a relay, which forwards them to the publisher's mailbox. That single request carries the message and writes nothing back into the browser. Send nothing and no request ever leaves delyavia.com at all.

Hosting logs are a separate matter

A network address and a small amount of technical detail accompany every request a browser makes anywhere on the internet, and the hosting company records those in logs with a short life. No website can prevent this, because that information is precisely what routes the request to a server.

Those records sit on the provider's machines rather than on a reader's device, and nothing running on this page can read them. They are dealt with properly in the Privacy Policy.

How to confirm all of this

None of it requires taking anybody's word.

Open the browser developer tools, usually via the F12 key, and go to the storage panel. Local storage for this domain will show the one entry named above. The cookie list for this domain will be empty.

Then switch to the network panel and reload the page. Every single request will be addressed to delyavia.com. That observation settles the entire question, since storage belonging to another company can only follow a request sent to that company.

Clearing it

Clearing site data for delyavia.com removes it. Deleting the individual key from the storage panel achieves the same thing with more precision. A private window throws it away when the window closes.

A browser configured to refuse storage altogether also works: the script continues without it, and the only observable consequence is that the slab reappears on every visit. No part of this site is gated behind storage, because there is nothing to remember. No login, no saved preference, no cart contents.

Should the list ever get longer

Bringing in advertising, measurement, or tracking of any other kind would mean rewriting this page in advance of a single item arriving in a browser. Each item would be named, along with the company behind it, what it holds, how long it lasts and how to decline it, and the slab would turn into a genuine consent request rather than a notice.

The revision date at the head of the page marks when this was last accurate. If it looks old, that is because nothing has moved.

Where to raise something

Everything on this page, and every other privacy matter for this site, goes to [custodian@delyavia.com](mailto:custodian@delyavia.com). By post: Delyavia Imprint LLC, 500 Seneca Street, Buffalo, NY 14204, United States.