Cookie policy
Two cookies, both our own, none of them advertising. That is why there is no consent banner here — there is nothing to ask about.
What a cookie is, and why there are almost none here
A cookie is a small file a site stores in your browser and reads back on the next request. Most of the time they exist to follow a person from site to site. We set two, and neither does that.
Both are first-party: they are written by everdawn.net and read by nobody else. Neither is shared with a third party or used for advertising, retargeting or profiling.
The cookies we set
That is the complete list. There is no shorter version of it and no "other functional cookies".
- everdawn-locale — the language you read the site in. The value is only "uk" or "en". It is written only when you press the language switch yourself. Lifetime: 12 months.
- everdawn-pass-ticket — a signed ticket proving you have just come back from the payment page, which is what opens the thank-you page. It carries no username, no email and no payment data. Lifetime: 30 minutes.
The cookies we do not set
We do not sell browsing data and we do not share it with ad networks. Not ever.
- Advertising and retargeting cookies
- Social network and share-button cookies
- Analytics that build a profile of a visitor across visits
- Third-party cookies of any kind
- Pixel tags, web beacons and browser fingerprinting
Analytics without cookies
We use Vercel Web Analytics and Vercel Speed Insights. They count page views and loading speed without cookies and without an identifier that would recognise you between visits.
What we see from them is aggregate: how many views a page had, which country the visitor came from, how fast the page opened. No individual person exists in those numbers.
The host does keep an ordinary request log, and an IP address lands in it. That is not a cookie, but it is personal data — the privacy policy covers it.
Why there is no consent banner
The ePrivacy Directive allows a site to skip asking consent for cookies that are strictly necessary for a service the user explicitly requested.
The language cookie is written only at the moment you press the language switch — that is, when you explicitly ask us to remember the choice. The thank-you ticket exists only because you just paid, and it expires half an hour later. Both fall inside that exemption, so a banner would be an extra click rather than a protection.
If we ever added analytics or advertising that needs consent, a banner would appear and this section would be rewritten the same day.
How to refuse
Cookies can be deleted or blocked in any browser's settings, and you need no permission from us to do it.
Without the language cookie the site works out your language from the browser every time — usually the same answer. Without the ticket the thank-you page will not open after payment, but access is unaffected: the account is whitelisted anyway, and the subscription details arrive by email from Creem.
Local storage and similar technologies
We do not use localStorage, sessionStorage, IndexedDB, persistent identifiers or browser fingerprinting.
The Minecraft client has nothing to do with the site: it connects to the server directly, with no cookies involved.