Who runs this

This site is run by Brett Jenkins, a sole trader in the United Kingdom who also trades as TidyLabs and runs the seemy.beer tap sign. Nobody else is involved. Brett is the data controller for the purposes of UK data protection law, of 52-56 Standard Road, London, NW10 6EU. For anything about your data, email [email protected].

This notice covers codes.seemy.beer and nothing else. The board you are reading it from is not commercial: nothing is sold here, there are no adverts, no affiliate links and no arrangement of any kind with PerfectDraft or AB InBev. The other sites are run by the same person but are separate from this one, and they are not all like it — one of them sells subscriptions. Each has its own notice covering what it does, and this page should not be read as describing any of them:

• seemy.beer/privacy and /terms for the sign itself.
• tracker.seemy.beer/legal for the price tracker.
• tidylabs.co.uk/privacy for the controller behind all of them — your rights, how to complain, and where data goes are set out there in full.

One thing genuinely is shared, and it is worth knowing: the cookie recording that you passed the age check is set for the whole of seemy.beer, so passing it here means you are not asked again on the others. Nothing else crosses between them.

Why we are allowed to do this

Our lawful basis is legitimate interests. The interest is keeping a small open board usable: stopping it being scraped, spammed, or emptied by a script, and being able to shut out somebody who repeatedly posts abuse. Nothing here is used for advertising, profiling, or anything sold on. If you think that balance is wrong in your case, you can object, and the next section says how.

The short version

There are no accounts. We never ask for your name or your email address. The age check does ask for your date of birth, but only to do the sum, and it is thrown away immediately. We never store your IP address, though we do keep a one-way hash of it, which the section below explains properly. What we keep beyond that is the codes people share and enough counting to stop the site being scraped or spammed.

What we store

When you share a code, we save:

• The code itself, and what you wrote to describe it.
• A tidied version of that description, produced automatically (see below).
• When it was shared, when it expires, and how many people have revealed it.
• The country you were in, as a two-letter code and nothing narrower. Cloudflare works it out from your connection and tells us; we never see the address itself. It is kept to help us spot spam and abuse, and only when you share a code, never when you read the board.

When you reveal or report a code, we save that it happened and when. That is what enforces the limits on how much any one person can do here, which is what stops the board being emptied by a script. We do not publish the exact numbers, for the obvious reason.

How we tell one visitor from another

Not by storing your IP address. We store a one-way hash of it instead, which is a fixed-length scramble that cannot be turned back into the address it came from. There are two, and they behave differently, which is worth twenty seconds of your time.

The first is mixed with a secret that changes every day. It does the counting described above, so it can tell that one person has done something fifty times today, and it cannot tell that today's visitor is yesterday's. At midnight everyone becomes a new number.

The second is recorded only when you share a code, and it does not change daily. It exists so that somebody who repeatedly posts abuse can be recognised and blocked, which the first hash makes impossible by design. It is still one-way and it is still not an address, but it is stable, so we treat it as information about a person rather than about nobody. Blocks normally run for a set number of days and then lift by themselves, though a serious one can be left open ended. Either way it follows an address rather than a person, so it also stops applying once yours changes, and the page you land on will tell you which kind you have.

We do not store your date of birth. The age check keeps only that it passed and when. The date you type does the sum and is then thrown away.

Cookies

Three, none of them for advertising:

• smb_codes_sess keeps you signed in to the anti-spam check for 30 minutes so you are not challenged on every click. It holds a random id and hashes of your address and browser, nothing readable.
• smb-age remembers that you passed the age check, for 12 months if you tick the box and until you close the browser if you do not. It is shared with the rest of seemy.beer so you are not asked twice.
• smb-age-block remembers for 24 hours that an under-18 date was entered.

Who else sees anything

• Cloudflare hosts the site and runs the anti-spam check. They see your IP address because they serve the page. Their spam check is told your address so it can do its job.
• Anthropic receives the description you type, and only that, so it can be tidied into a consistent format. Not the code, not anything about you.
• Google serves the two fonts this site uses, which means your browser contacts Google to fetch them and Google sees your IP address as a result. Nothing is sent to them about what you do here.

Our visitor statistics are Cloudflare's, which use no cookies and do not fingerprint or follow anyone between sites.

How long we keep it

Codes stop being offered 36 hours after they are shared. The rows behind the site are kept beyond that so the board keeps working.

We used to say here that once the daily secret had rotated, an old row could not be matched to anyone including us. That was not true and it has been corrected. The daily part of the hash is the date, and we hold the secret it is mixed with, so we could in principle work backwards. Nobody outside can, and we have no reason to, but the honest position is that all of these hashes are information about a person for as long as we keep them, and we treat them that way.

Your rights

You can ask for a copy of what we hold about you, to have it corrected or deleted, to restrict what we do with it, or to object to us doing it at all. Email [email protected] and we will answer within a month.

There is a genuine catch, and it is better said than hidden. We hold no name, no email address and no IP address, so for almost everybody we simply have no way to find "your" rows, and the law does not require us to start collecting more data in order to go looking. The one exception is a block: if you are blocked and you email us from the same connection, we can match that and lift it.

If you are unhappy with how we have handled something, you can complain to the Information Commissioner's Office at ico.org.uk/make-a-complaint or on 0303 123 1113. You can do that without asking us first, though we would rather you gave us the chance to put it right.

Where the data goes

The companies named above are in the United States, so some of what we process leaves the UK. Each is covered by the UK's approved transfer safeguards, either the UK Extension to the EU-US Data Privacy Framework or the International Data Transfer Addendum in their standard terms.

Getting in touch

Email [email protected] and we will answer. If you want something you shared taken down, say which code and it will go.

Last updated 5 August 2026.