Cookies

The short version

dub44 sets one kind of cookie: the one that keeps you signed in. No analytics, no advertising, no third-party trackers. That is why you have never seen a consent banner here — under the ePrivacy Directive, cookies strictly necessary for a service you asked for do not need consent.

What we set

Your browser also keeps small amounts of local storage for interface preferences such as your last-used engine and slider positions. That never leaves your device.

Advertising — only if you allow it

We run ads on Meta, and to know which of them actually bring people here we can load Meta’s pixel. It sets cookies (_fbp, and _fbc when you arrive from an ad) and reports your visit and any purchase to Meta.

It does not load unless you say yes. We ask once, declining takes one click and is no harder than accepting, and the site behaves identically either way — nothing is withheld from you for saying no. Your choice is stored in a cookie called dub44_consent for two years; delete it to be asked again.

What we never set

• No Google Analytics or any other third-party analytics product.
• No social media embeds or share buttons that phone home.
• Nothing at all for advertising unless you have allowed it.
• Our own visit counting uses no cookies whatsoever — a hash that changes daily and cannot be linked back to you or across days.

Payment pages

Checkout is handled by Stripe on their own pages, and Stripe sets cookies there for fraud prevention. Those are governed by Stripe’s own cookie policy, which you can read on their site.

Refusing them

You can block cookies in your browser, but the session cookie is what signing in consists of — block it and you cannot use an account. Nothing is lost by blocking everything else, because there is nothing else.

If this ever changes and we add something non-essential, you will get a proper consent request first. See the Privacy Policy for what we store server-side.