Privacy Policy

Last updated: 10 November 2026

Core performance analytics

When enabled, PostHog collects pseudonymous page, event, ticket and performance metrics to improve discovery and report sponsored-event performance. This is not marketing consent.

Google Analytics cookies

Off unless you accept. When on, Google Analytics sets cookies to count visits and pages viewed. Turning it off stops Google Analytics in this browser and removes its cookies. Turning off core performance analytics above also pauses it.

1. Who we are

whatnightout is a nightlife and music event discovery platform operating in the UK. We operate the website at whatnightout.uk and the whatnightout mobile application (together, the “Service”), covering cities across the United Kingdom.

In this policy, “we”, “us”, and “our” refer to whatnightout. “You” and “your” refer to you as a user of the Service.

2. What data we collect

We collect the following categories of personal data:

Account data

When you create an account, we collect your email address, display name, and authentication provider details. You may sign in using Google, Apple, or an email and password. Authentication is handled by Google Firebase, which stores your credentials securely. We receive your email address, display name, and a unique user identifier from Firebase. We do not receive or store your password.

Preferences and activity

When you use the Service, we store your preferences and activity to personalise your experience. This includes your selected city, genre preferences (up to 10), saved events, followed venues, and recently viewed events. This data is associated with your account and stored on our servers. Saved events made before signing in are stored only in your browser’s local storage on this device, until you create an account — at which point they are migrated to your account so you can access them across devices.

User-submitted content

If you submit an event for inclusion on the platform, we collect the event details you provide (name, date, venue, description, genres, ticket link, and price). If you upload an event image, it is stored by Cloudinary, a third-party image hosting service.

Paying to promote an event

If you pay to promote an event, the payment is processed by Stripe. Your card details go directly to Stripe; we never receive or store full card numbers. From Stripe we receive confirmation of the payment, the amount and the payment and refund references. Stripe holds the payer’s card details, name and email; we don’t store the payer’s name. With the order we keep the package, the event, whether you bought as an individual or a business (and the organisation name, if you gave one), and when you accepted the promotion terms. We use this to run your Ad, make refunds and keep billing records.

Usage and analytics data

When core analytics are enabled, we collect pseudonymous information about how the Service is used — pages visited, features used, search queries, filter interactions, performance measurements and general engagement patterns — so we can understand which areas to improve. PostHog processes product analytics on EU servers in Frankfurt, Germany. If you sign in, PostHog product analytics are associated with your Firebase user identifier so we can measure retention; we do not send your email address to PostHog.

For storage and access whose sole purpose is strictly statistical measurement needed to understand and improve the Service, we intend to rely on the statistical-purposes exception to PECR introduced by the UK Data (Use and Access) Act 2025. That exception does not automatically cover every analytics use: identified retention measurement and sponsored-event performance reporting are assessed separately. We rely on legitimate interests (UK GDPR Article 6(1)(f)) for the associated personal-data processing and provide the objection control below, but legitimate interests do not replace any PECR consent requirement. These newer exception boundaries remain subject to legal review. We do not use PostHog analytics for advertising or sell analytics data.

You can object using the Core performance analytics control above. Turning it off immediately prevents PostHog from sending further measurements from this browser. Turning it back on restores it. This preference is separate from the optional Google Analytics cookie choice.

Separately, if you accept the cookie banner, we also use Google Analytics to count visits and pages viewed. It is off unless you accept, and you can change your choice with the Google Analytics cookies control above.

Search and Ask on the homepage

When you use Ask in the homepage search, we send your question, and a list of matching public events, to Anthropic (Claude) to find the best matches. We do not send your name, email address or account details, and we do not store your question with personal details. Anthropic handles what we send under its own data policy. To keep Ask fast and cheap, an answer to the same question may be reused for up to 15 minutes. We keep only counts, such as how many questions were asked. Ordinary search on the homepage is not sent to Anthropic.

To stop automated abuse, Ask is protected by Cloudflare Turnstile. Its check loads when you open the homepage search, so Cloudflare receives your IP address and signals from your browser at that point, to tell people from bots.

Event submission emails

We use your verified account email to send submission receipts and moderation decisions. If you choose optional marketing emails, we may send marketing from whatnightout, including paid promotion offers and reminders to list your next event. We record your email preference, the wording you agreed to, when you agreed and where you made the choice. You can withdraw this separate marketing consent in your profile or through the unsubscribe link in a marketing email. Submission status emails continue after you unsubscribe from marketing.

Weekend Drop emails

If you sign up for the Weekend Drop, we collect your email address, your city, up to three genres you choose, whether you told us you are a student, and a record of your consent: the wording shown when you pressed Subscribe, its version, when you agreed and the page you signed up on. You do not need an account. We rely on your consent and use this information only to send the Weekend Drop and to choose events that suit your city and taste.

Signing up subscribes you straight away. We send a welcome email to the address you gave us, with a “Not you?” link that removes the address if someone else entered it. If you unsubscribed before, we instead email you a link to confirm that you want to start again, and send nothing else until you do. After that we usually send one email a week about nights out in your city. Alongside our event picks, it may include offers and giveaways from whatnightout and clearly labelled promoted or sponsored events. Promoters, venues and other partners never receive subscriber email addresses. Links in the email carry campaign (UTM) tags so we can see which picks are useful; they never contain your email address.

You can stop the Weekend Drop and take your address off the list at any time with the unsubscribe link in the welcome email or any later email, or your mail app’s unsubscribe button. Every weekly Weekend Drop email links to a page where you can change your city, genres or student setting. When you unsubscribe, or an address bounces or marks an email as spam, we stop sending and keep a suppression record of the address, the reason and your consent history, so we can honour that request and never email you again by mistake.

You can also tell us in your own words what you’re into. This is optional. We keep that text while you are subscribed and delete it when you unsubscribe. We use Anthropic (Claude), an AI provider that processes it for us, to turn the text into preferences such as genres, budget and nights, and to choose and explain your picks. We send Anthropic the text and your city, never your email address. The same applies to replies you send to a Weekend Drop email and to any 👍 or 👎 feedback you give on your picks.

Technical data

When you access the Service, our servers automatically collect standard technical data including your IP address, browser type and version, operating system, device type, referring URL, and pages visited. This data is used for security, abuse prevention, and to ensure the Service functions correctly.

Cookies and local storage

The website uses cookies and browser local storage. See Section 6 below for a detailed breakdown of the cookies we use.

3. Legal basis for processing

Under the UK General Data Protection Regulation (UK GDPR), we process your personal data on the following lawful bases:

  • Contract: Processing your account data, preferences, and activity is necessary to provide you with the features of the Service you have signed up for (saved events, follows, personalised recommendations, event submissions), and to take payment for, run and refund any event promotion you buy.
  • Legal obligation: We keep billing records for promotions for as long as tax law requires.
  • Legitimate interest: We process technical data (IP address, browser type) for security, abuse prevention, and to maintain the performance and reliability of the Service. We also rely on UK GDPR Article 6(1)(f) for anonymised and identified analytics used to understand usage, retention and sponsored-event performance, subject to your right to object. Only storage and access used solely for strictly statistical service-improvement measurement is treated as potentially within the UK Data (Use and Access) Act 2025’s statistical-purposes exception to PECR; we do not claim that exception automatically covers identified retention or sponsor reporting, and this position remains subject to legal review.
  • Consent: Optional Google Analytics cookies are only set if you accept the cookie banner. Optional promoter offers and event-listing reminders rely on your separate consent, as does the Weekend Drop email. You may withdraw consent at any time without affecting prior processing.

4. How we use your data

We use your data for the following purposes:

  • To provide and operate the Service, including displaying events, venues, and search results
  • To personalise your experience, showing relevant weekend picks based on your genre preferences, city selection, and activity
  • To maintain your saved events, followed venues, and other saved preferences
  • To process and display event submissions you make and email you about their progress
  • To take payment for, run and refund event promotions you buy, and to keep billing records
  • With your consent, to send marketing emails from whatnightout, including paid promotion offers and event reminders
  • To send push notifications about new events at venues you follow (mobile app only, with your permission)
  • To understand how the Service is used and to improve it, using aggregate analytics
  • To detect and prevent fraud, abuse, and security incidents
  • To comply with legal obligations

We do not use your data for automated decision-making or profiling that produces legal or similarly significant effects.

5. Data sharing and third parties

We never sell your personal data. We share data with the following third-party services solely to operate the Service:

  • Google Firebase (Google LLC, USA): provides user authentication. Firebase receives your email address, display name, and authentication credentials. Google’s privacy policy applies to data processed by Firebase.
  • PostHog (EU, Frankfurt, Germany): provides analytics. Acts as our data processor — PostHog cannot reuse your data for any purpose other than running analytics for whatnightout. Data is processed exclusively on EU servers. We do not feed analytics into advertising or share it with third parties.
  • Google Analytics (Google Ireland Limited): measures visits, only if you accept analytics cookies. Google signals and ad personalisation are switched off. We share aggregate Google Analytics reports with our advertising partner Raptive so it can assess the site.
  • Awin (affiliate network): runs the affiliate links to See Tickets. When you follow one, your browser passes through Awin, which receives your IP address and browser details as any website does and records the click with our event reference and which button was used. Awin and See Tickets may then set their own tracking cookies so a ticket sale can be credited to us. Those cookies are set on their sites, not ours, so our cookie banner does not control them; you can block or delete them in your browser settings. We send Awin no account details. Awin handles this data under its own privacy notice.
  • Resend: delivers event submission, optional promoter and Weekend Drop emails. We share the recipient email address and message content, and retain delivery status to manage failures and avoid duplicate sends.
  • Stripe (Stripe Payments UK Ltd): processes payments for event promotion. You enter your card details on Stripe’s checkout page, so they go directly to Stripe; we never receive full card numbers. We share your account email address, the order and its amount with Stripe. From Stripe we receive confirmation of the payment, the amount and the payment and refund references. Stripe holds the payer’s card details, name and email; we don’t store the payer’s name. Stripe also uses payment data under its own privacy policy, for example to prevent fraud and meet its legal obligations.
  • Cloudinary (Cloudinary Ltd): hosts images uploaded with event submissions. Image files are stored on Cloudinary’s servers.
  • Anthropic (Anthropic PBC, USA): answers questions typed into Ask on the homepage, and turns optional Weekend Drop preferences, replies and feedback into preferences and picks. We send the question or text, your city and a list of matching public events, never your email address or account details. Anthropic handles this under its own data policy.
  • Cloudflare (Cloudflare Inc., USA): Turnstile checks Ask requests for bots. It loads when you open the homepage search and processes your IP address and browser signals.
  • Vercel (Vercel Inc., USA): hosts our website. Page requests pass through Vercel’s edge infrastructure.
  • Render (Render Services Inc., USA): hosts our backend API. Data submitted through the Service is processed and stored on Render’s infrastructure.
  • Apple & Google: distribute the mobile app via the App Store and Google Play. Push notifications on the mobile app are delivered via Apple Push Notification Service and Google Firebase Cloud Messaging.

We may also disclose your data if required by law, regulation, or legal process, or to protect the rights, safety, or property of whatnightout, our users, or the public.

6. Cookies and local storage

Our website uses cookies and browser local storage. The mobile app does not use cookies.

Strictly necessary

  • Authentication cookies: Set by Firebase to maintain your signed-in session. Without these, you would need to log in on every page visit.
  • Admin session: A short-lived cookie used solely on admin tooling, scoped to /admin.
  • Cookie choice: wno-improve-opt-in and wno-improve-v remember whether you accepted or rejected Google Analytics cookies, for up to a year, so we don’t ask again on every visit.
  • Pending account-deletion marker: If you request account deletion, we store a pseudonymous fingerprint of your Firebase user ID and the request time in local storage, with a same-site cookie as a fallback. It contains no raw user ID and exists solely to keep analytics blocked if deletion completes but the browser loses the response or Firebase sign-out fails. We clear both copies when Firebase confirms that the old account is signed out or a different account is established. Local storage has no fixed expiry; the fallback cookie has a maximum lifetime of ten years so an unresolved deletion cannot silently resume analytics.

Preferences (appearance exception)

  • City preference: Remembers the city you last selected so you land on the right page next visit.
  • UI state: Local storage holds your view mode (map/list), recently viewed events, and similar UI choices. This data stays in your browser and is not sent to our servers.

Analytics and statistical measurement

  • PostHog cookies: Used to measure how the site is used, improve it, understand retention and report sponsored-event performance. We treat only storage and access used solely for strictly statistical service-improvement measurement as potentially eligible for the UK Data (Use and Access) Act 2025 statistical-purposes exception to PECR. Identified retention and sponsor reporting are not described as automatically exempt; we rely on legitimate interests (UK GDPR Article 6(1)(f)) for personal-data processing, provide an objection control, and keep the PECR position under legal review. PostHog runs on EU servers (Frankfurt), acts only as our data processor, and we never feed this data into advertising or sell it. We no longer record sessions.

Optional (your choice)

  • Google Analytics cookies: Only if you accept the cookie banner, Google Analytics sets _ga cookies to count visits and pages viewed. Turning them off with the control at the top of this page stops Google Analytics in this browser and removes those cookies.

Following an affiliate ticket link (for example to See Tickets through Awin) can also lead those sites to set their own cookies; see Awin in Section 5. Our cookie banner does not control them.

You can also manage cookies through your browser settings. Note that blocking strictly necessary cookies may prevent parts of the Service from functioning correctly.

7. Data retention

  • Account data: Retained for as long as your account is active. When you delete your account through profile settings, we first ask PostHog to erase the person, events and recordings associated with your Firebase user identifier. We only continue to remove your application data and Firebase account after PostHog accepts that erasure request; if it cannot be queued, the deletion fails visibly so it can be retried. PostHog completes an accepted erasure asynchronously, so it may not disappear from its systems at the instant your account becomes inaccessible.
  • Analytics data: Product analytics may be retained for up to 12 months after collection. Signed-in PostHog history can be linked to your Firebase user identifier until the account-erasure workflow above is accepted and completed. Anonymous or aggregate measurements that cannot identify your account may remain subject to the provider’s normal retention schedule.
  • Weekend Drop emails: Subscriptions are kept until you unsubscribe. Sign-ups made under our earlier confirm-by-email process that were never confirmed are deleted 7 days after sign-up. After you unsubscribe, we keep a suppression record so we can honour your request.
  • Billing records: We keep promotion order, payment and refund records for 6 years for tax purposes, even if you delete your account or your event. After you delete your account they are no longer linked to it. Stripe keeps its own payment records under its privacy policy.
  • Technical logs: Server logs containing IP addresses and request data are retained for up to 30 days for security and debugging purposes, then automatically deleted.

8. Your rights under UK GDPR

Under the UK GDPR, you have the following rights in relation to your personal data:

  • Right of access: You can request a copy of the personal data we hold about you.
  • Right to rectification: You can ask us to correct any inaccurate or incomplete personal data.
  • Right to erasure: You can ask us to delete your personal data. You can also delete your account directly from your profile settings at any time.
  • Right to restriction: You can ask us to restrict the processing of your data in certain circumstances.
  • Right to data portability: You can request your data in a structured, commonly used, machine-readable format.
  • Right to object: You can object to processing based on legitimate interest.
  • Right to withdraw consent: Where processing is based on consent (for example analytics cookies or optional emails), you can withdraw consent at any time, using the controls on this page or in your profile settings, without affecting the lawfulness of prior processing.

To exercise any of these rights, please email privacy@whatnightout.uk. We will respond within one month as required by law. If you are not satisfied with our response, you have the right to lodge a complaint with the Information Commissioner’s Office (ICO) at ico.org.uk.

9. Children’s privacy

The Service is a nightlife and event discovery platform intended for users aged 18 and over. We do not knowingly collect personal data from anyone under the age of 18. If we become aware that we have collected data from a person under 18, we will delete it promptly. If you believe a child under 18 has provided us with personal data, please contact us at privacy@whatnightout.uk.

10. International data transfers

Some of our third-party service providers process data outside the United Kingdom:

  • Google Firebase may process authentication data in the United States. Google provides appropriate safeguards through Standard Contractual Clauses (SCCs) and its data processing terms.
  • PostHog processes analytics data exclusively within the EU (Frankfurt, Germany), which is covered by the UK adequacy decision.
  • Vercel hosts our website infrastructure under its data-processing terms.
  • Render hosts our backend API infrastructure on EU-region servers.
  • Resend: delivers event submission, optional promoter and Weekend Drop emails. We share the recipient email address and message content, and retain delivery status to manage failures and avoid duplicate sends.
  • Stripe may process payment data in the United States and other countries under its data-processing terms.
  • Cloudinary may process uploaded images in various locations. Transfers are covered by Standard Contractual Clauses.

Where personal data is transferred outside the UK, we ensure that appropriate safeguards are in place as required by UK data protection law.

11. Data security

We take reasonable technical and organisational measures to protect your personal data. All data transmitted between your device and our servers is encrypted using TLS (HTTPS). Authentication is handled by Google Firebase, which provides industry-standard security including secure credential storage and token-based authentication. Access to our backend systems and database is restricted to authorised personnel only.

While we take security seriously, no method of electronic storage or transmission is 100% secure. We cannot guarantee absolute security of your data.

12. Changes to this policy

We may update this privacy policy from time to time to reflect changes in our practices or legal requirements. The “Last updated” date at the top of this page indicates when the policy was last revised. For material changes that significantly affect how we process your data, we will make reasonable efforts to notify you, for example via a notice on the website or mobile app. Continued use of the Service after changes constitutes your acknowledgement of the updated policy.

13. Contact us

If you have any questions about this privacy policy or how we handle your data, please contact us:

You can also review our Terms of Use for the rules and conditions governing your use of the Service.