GenetixBayEST. 2009
ENFRJoin the waitlist
Menu
Draft: under legal review. Last updated
Cookies and analytics · GenetixBay

No tracking cookies. Here's what we do use.

Short and honest: what our site stores in your browser, what our network provider may set, and how our cookieless visit counter works.

The short version

  • Our public site sets no cookies of its own. There's no cookie banner because there are no tracking cookies to agree to.
  • Cloudflare, our network provider, may set a security cookie to tell people from bots. It's strictly necessary and isn't used for advertising.
  • A few small notes live in your browser's storage: your theme, referral codes, and how you arrived (deleted when you close the tab).
  • We count visits without cookies, using a visitor ID that changes every day. No IP addresses are stored.
  • When accounts open, the app uses one sign-in cookie. That's it.

Cookies

Public site: we set no cookies. Cloudflare, which protects and delivers our site, may set a strictly necessary security cookie (such as __cf_bm or cf_clearance) when it needs to tell people from automated traffic. These last from 30 minutes to about a day, and Cloudflare uses them only for security.

App (when accounts open): one cookie, __Host-gb_session, keeps you signed in. It can't be read by scripts, is sent only over secure connections to our own domain, and ends after 7 days without use or 30 days at most.

We don't use advertising, social-media or third-party analytics cookies.

What we keep in your browser

These are stored in your browser's local or session storage, not as cookies, and never leave your device except as noted:

gb-theme

Light, dark or another theme you picked. Kept until you clear it.

gb-ref-in

The referral code in a link you followed, so the person who invited you gets credit if you join or pledge.

gb-code

Your own referral code after you join, so we can show your place in line and your share link.

gb-attr (session only)

How you arrived: campaign tags, the site that linked to us and your first page. Sent with the sign-up or pledge form, then deleted when you close the tab.

When accounts open, the app also keeps unsent post drafts on your device so you don't lose them.

How we count visits

Our own counter runs on our own server. For each page view it records the page, the time, your country, a device type (phone, tablet or desktop), screen width, the site that sent you (without the part after the “?”), time on page, scroll depth and the buttons you press. It doesn't store your IP address or your full browser details, and it skips bots.

To count unique visitors, it makes a one-way hash of your IP address, browser details, the date and a secret key. The date changes the ID every day, so we can't follow you from one day to the next. Our privacy policy has the full list.

One more thing: fonts

Our typefaces are served from our own servers, along with the rest of each page, so loading a page doesn't contact any font service. Our public pages make no requests to third-party font or analytics services.

Your choices

  • You can clear cookies and site storage in your browser settings at any time. The site still works; you'll just see the default theme.
  • Blocking storage stops referral credit and theme memory, nothing else.
  • If your browser sends a Global Privacy Control or Do Not Track signal, we honour it: we don't sell or share data, and there's no cross-site tracking to switch off.

[COUNSEL: whether visitors from the EU or UK need a consent prompt for the session attribution note.]