Privacy Policy

How we count visits

We measure how this site is used so we know which events, tickets and merch people actually look at, and so we can tell whether the site is working. We do this ourselves rather than handing it to an advertising company. There is no Google Analytics here, no Meta pixel, and no advertising or third party tracker of any kind.

There are two separate systems doing it, and we would rather name both than describe one and let you assume that was all of it.

1. Our own event tracking

This one tells us what happened on the site. When you open a page or tap something we care about, such as a ticket link or a product, it records that. It stores:

• A random session id, kept in your browser’s storage under the name ts_sid. It is a random number generated on your device. It is not linked to your name, your email, or any account, and we cannot use it to work out who you are.
• The page addresses you open on this site.
• The name of the thing you tapped, for example that a ticket link was opened, plus a small amount of detail about it such as which event or product.
• A rough location, at city level only (city, region, country). Not a street, not a map position.
• Whether you are on a phone, a tablet or a computer.
• The website that sent you here, its address only. For example we would see that you came from Instagram. We do not keep the full link, so if you arrived from a search we never see what you searched for.

2. Breazy Analytics

This one tells us how the site is being used compared with the other sites we run, which the first system cannot see. It stores:

• A cookie named _bza containing no identifier at all. It holds three things: the date you first visited, how many separate days you have visited on, and the date you were last here. Two people who first came on the same day and have been back the same number of times carry an identical cookie.
• A daily counting value. We will be straight about this one, because it is the only part that is genuinely about you rather than about the page. It is a scrambled value worked out from your network address, your browser and today’s date. We do not store your network address, only the scrambled result. It changes every day at midnight and it is scrambled differently on every site we run, so it cannot be used to follow you from one day to the next or from this site to another one. Within a single day it does tie your page views together, which is the only way to count how many people visited rather than how many pages were opened.
• The page addresses you open on this site.
• How many seconds a page was actually on screen. Time while the page is hidden behind another app or tab is not counted.
• A rough location, again at city level only.
• Your device type and which browser you use.
• The website that sent you here, its address only.

What neither one keeps

Neither system stores your IP address. Your IP is used for a moment while the request is being handled, to work out the city and to stop abuse, and then it is gone. Neither one records your name, your email address, your phone number, or your exact location, and neither is shared with an advertising network or sold to anyone.

Page addresses are also cleaned before they are stored. Your ticket links and order links contain a private code that is what proves the ticket is yours, so anything in an address that looks like a code is replaced before it is recorded. We would rather lose a little detail in our own reporting than keep a live ticket code in a list of pages.

Why we are allowed to do this

Both of these run on our legitimate interest under section 11(1)(f) of POPIA, not on your consent. In plain terms: we need to know whether the site works, the information is not sensitive and does not identify you, and we judged that this does not override your privacy. That is a judgement you are entitled to disagree with, which is what the next part is for.

Turning it off

Section 11(3) of POPIA gives you the right to object to this. Unlike the European rules, section 11(4) gives us nothing to weigh your objection against. If you object, we stop. The button below is that objection. It switches off both systems described above, deletes the _bza cookie and deletes the ts_sid session id from this browser. It takes effect immediately, not on your next visit.

If your browser sends a “Do Not Track” signal we honour that too, and nothing is counted. We still offer the button, because a browser setting is not the same thing as you telling us directly.