Cookie Policy
Last updated: August 2026
This Cookie Policy explains how Whats Going On London Ltd, trading as What's Going On (company number 17107610) (“we”, “us”, “our”) uses cookies and similar technologies when you visit our website at whatsgoingon.london (the “Service”). This policy should be read alongside our Privacy Policy.
1. What are cookies?
Cookies are small text files that are placed on your device (computer, tablet, or mobile phone) when you visit a website. They are widely used to make websites work more efficiently, provide a better user experience, and supply information to the website operator. Cookies can be “persistent” (remaining on your device until they expire or you delete them) or “session” cookies (deleted when you close your browser).
In addition to cookies, we also use localStorage, a browser feature that allows websites to store small amounts of data on your device. Unlike cookies, localStorage data is not automatically sent to our servers with each request.
2. Types of cookies we use
We categorise the cookies and similar technologies on our Service into two types:
- Essential cookies & storage — These are strictly necessary for the Service to function. They enable core features such as user authentication, security, and remembering your preferences. You cannot opt out of these as the Service would not work without them. No consent is required for essential cookies under UK law.
- Privacy-friendly analytics — We use Vercel Analytics and Speed Insights, which are cookieless and collect only aggregate performance and usage data (page views, Web Vitals). They do not use persistent identifiers or track individual users across sessions. Because they are fully cookieless and do not process personal data, they do not require consent under GDPR or the ePrivacy Directive.
- Consent-based analytics (PostHog) — With your consent, we use PostHog (hosted in the EU) to understand how the site is used. PostHog stores a persistent identifier on your device. It is loaded only after you grant product analytics on the cookie banner, and never if you reject.
- Session replay (separate consent) — We may record a small sample of visits so we can see where the site is confusing. This is a separate choice from product analytics: you can allow us to count page views while refusing replay, using Preferences on the cookie banner. Text you type is masked. Replay never starts unless you have specifically granted it.
3. Cookies and technologies in detail
3.1 Essential cookies
| Name | Purpose | Duration | Type |
|---|---|---|---|
sb-*-auth-token | Supabase authentication session token. Maintains your logged-in state and secures your account. | Session / up to 7 days | Essential |
3.2 Mapbox (map functionality)
We use Mapbox GL JS to provide the interactive map that is central to the Service. Mapbox may set cookies and make network requests to load map tiles and related assets. These are necessary for the core functionality of the Service.
| Name | Purpose | Duration | Type |
|---|---|---|---|
| Mapbox tile cache cookies | Caches map tiles for performance. May include telemetry data sent to Mapbox for service improvement. | Varies | Essential (core functionality) |
For more information, see the Mapbox Privacy Policy.
3.3 Vercel Analytics & Speed Insights (no consent required)
We use Vercel Analytics and Vercel Speed Insights, privacy-friendly services provided by Vercel Inc. These do not set any cookies and do not use persistent identifiers. They collect only aggregate data — page views, visitor counts, and Web Vitals performance metrics — without tracking individual users across sessions.
Because these services are fully cookieless and do not process personal data, they are loaded without requiring consent, in accordance with GDPR and the ePrivacy Directive.
For more information, see the Vercel Analytics Privacy Policy.
3.4 PostHog analytics (consent required)
With your consent, we use PostHog, an analytics service hosted in the European Union, to understand how visitors use the site. PostHog stores a persistent identifier in your browser's localStorage and records events such as page views, searches, and clicks. A small sample of visits may also be recorded as a session replay (a reconstruction of the pages you viewed and interactions you made) to help us find usability problems; text you type is masked in these recordings.
These are two separate consents. Session replay only ever starts if you have specifically allowed it — choosing product analytics alone means we count page views and clicks but never record your screen. You can set them independently under Preferences on the cookie banner.
PostHog is loaded only after you grant product analytics on the cookie banner. If you reject, or withdraw consent later from this page, PostHog is not loaded and any previously stored PostHog identifiers stop being used. Requests to PostHog are proxied through our own domain.
For more information, see the PostHog Privacy Policy.
3.5 localStorage items
We use your browser's localStorage to store preferences and cached data locally on your device. This data is never sent to our servers automatically. The following items may be stored:
| Key | Purpose | Type |
|---|---|---|
wgo-cookie-consent-v2 | Records your cookie consent choice (accepted, rejected, or not yet decided). The key was versioned in August 2026 when PostHog analytics was introduced, so that everyone is asked again under the updated notice. | Essential |
ph_* | PostHog analytics identifier and session state. Only created after you grant product analytics on the cookie banner; see section 3.4. | Analytics (consent required) |
wgo-consent-anon-id | A randomly generated anonymous identifier used solely for maintaining an audit trail of consent decisions. Not linked to your account or any personal data. | Essential |
wgo-dark-mode | Stores your dark mode preference (enabled or disabled). | Essential (preference) |
wgo-recent-searches | Caches your recent search queries locally for convenience. Never sent to our servers. | Essential (preference) |
wgo-tour-seen | Records whether you have completed or dismissed the first-time onboarding tour, so it is not shown again. | Essential (preference) |
4. Affiliate links
Some “Get tickets” links are affiliate links. Following one does not set any additional cookie on whatsgoingon.london, and it does not change your cookie preferences here. The ticketing platform may set a cookie on their own website to attribute the sale, governed by their cookie policy rather than ours. See our Affiliate Disclosure for detail.
5. How to manage cookies
When you first visit our Service, a cookie banner will inform you about our use of cookies and similar technologies. You can accept all, reject all, or choose which categories to allow under Preferences — product analytics and session replay are set separately, and both are off unless you turn them on. You can change your choice at any time by clicking the “Cookie Settings” link in the footer of any page, or by clearing your browser's stored data for our site.
You can also control cookies through your browser settings. Most browsers allow you to:
- View and delete existing cookies
- Block all cookies or only third-party cookies
- Set preferences for certain websites
Please note that blocking essential cookies may prevent the Service from functioning correctly, including the ability to log in.
For instructions on managing cookies in your browser, visit your browser's help pages:
To clear localStorage data, open your browser's developer tools (usually F12), go to the Application or Storage tab, and delete the relevant entries under Local Storage for our domain.
6. Changes to this policy
We may update this Cookie Policy from time to time to reflect changes in our practices or for legal, regulatory, or operational reasons. We will update the “Last updated” date at the top of this page. We encourage you to review this policy periodically.
7. Contact us
If you have any questions about this Cookie Policy or our use of cookies and similar technologies, please contact us at hello@whatsgoingon.london.