Privacy

This page is written in plain language rather than copied from a template. If something here is unclear, that is a defect and we want to hear about it.

The short version

There are no accounts on this site. The only thing we keep on a server about a visitor is a notification subscription—and only if you turn notifications on yourself. We do not track you across sites, we do not sell anything to anyone, and there is no consent banner because there is nothing to consent to.

What is stored in your browser

The theme and the language, both of which you set yourself:

• Theme. Your choice of light, dark or system, so the page does not flash white when you come back. Stored in your browser’s local storage under haydevclub-theme until you clear it.
• Language. The locale you last used, so that the root address sends you to the same language next time. Stored in a cookie named haydevclub-locale for one year.

Neither leaves your browser except the language cookie, which is sent back to our server on each request so that a redirect can honour it. Neither identifies you.

If you use the site as an app, your browser also keeps copies of the pages you have read, so that they open without a connection, a counter that decides when to suggest installing the app, and the notification topics you chose. All of it stays on your device.

The full list, with purposes and lifetimes, is on the cookies and storage page.

Messages you send us

The contact form sends your message to our mailbox as an email and stores nothing on the server. There is no database, so there is no record of it anywhere except the mailbox—the same place a message would land if you wrote to us directly.

The email address you give is used to reply to you and for nothing else. We do not add it to a mailing list, because we do not have one.

Messages stay in the mailbox as long as the conversation is useful. If you want a message deleted, ask, and it will be.

Notifications

Notifications are off until you turn them on and choose topics. When you do, your browser creates a subscription with its push service—Google, Mozilla, Apple or Microsoft, depending on the browser—and gives us an address at that service. We store:

• that address and the keys your browser generates to encrypt messages to it;
• the language and the topics you chose;
• when the subscription was created and when a notification last reached it.

We do not store your name, email, IP address or device model, and the subscription is not linked to anything else about you. The text of every notification is encrypted on our side, so the push service delivers it without being able to read it.

Subscriptions are kept in a database hosted by Neon in Frankfurt. The website can only add and remove them; notifications are sent by a separate process that runs when there is something new.

A subscription is deleted when you turn notifications off on the app page, when the push service tells us it no longer exists—for example after you block notifications or remove the app—and after five failed deliveries in a row. Nothing is kept after that.

Analytics

We measure how fast pages are for real visitors, and—when an analytics provider is configured—how many people read which page. Both are done without cookies and without identifying anyone: no cross-site identifiers, no fingerprinting, no profile.

What is collected: the page path, the referring site, and the performance numbers your browser reports (how quickly the page appeared and responded). What is not collected: your address, the contents of forms, or anything that identifies you personally.

Video and maps

Videos are not loaded until you press play. Until then, YouTube receives no request from this page and cannot know that you were here. When you do press play, the player is loaded from youtube-nocookie.com, and YouTube’s own terms apply from that point.

Maps work the same way: the venue address is text on our page, and a map provider is only involved if you choose to open it.

Server logs

Our server records that a request happened, which route it hit, and whether it failed, together with the version of the code that served it. These records do not contain cookies, form contents, or personal data, and they are kept for a limited time for debugging and security.

Changes

When this page changes in a way that matters, the date at the top changes with it. The history of every version is in the repository.