Privacy

Last updated 20 August 2026.

This page explains what we do with the information you share with Socialise, why, and the choices you have. We have tried to keep it plain. If anything is unclear, email us and we will explain.

Who we are

Socialise Events Ltd is the controller of the information this page describes: company number 17273016, registered office 71-75 Shelton Street, Covent Garden, London WC2H 9JQ. We run community events and are building an app that helps people make real-life friends, based in Bristol. For anything about your data, contact us at support@socialise.events.

Socialise is for adults. You must be 18 or over to use this site or book an event through it.

What we collect

• Your answers to our survey, when you choose to fill it in.
• Your name and email address, when you book an event, buy us a pint, join the newsletter, or otherwise give them to us.
• Where you came from (for example a link tag like "instagram"), so we know which channels reach people.
• A record of the payment, if you book a paid event or buy us a pint.

You can complete the survey without giving your name or email. Leave those blank and your response stays anonymous. None of this is an identity check: we do not verify who you are, and we do not run DBS or other background checks on anyone who books an event.

Why we use it, and our lawful basis

Different things we do rest on different lawful bases, because they are different in kind.

• Consent. Filling in our survey and joining the newsletter are both things you opt into, and you can withdraw that consent at any time. Withdrawing it does not undo what we already did with your consent before you withdrew it.
• Contract. When you book an event, we use your name, email and payment details to take the booking and let the host know who is coming. We need this to provide what you asked for.
• Legitimate interests. We pass your name to the host of an event you book, so they know who to expect. Our interest is running the event properly; a host cannot host people whose names they don't have. You can object to this at any time by contacting us, and we will consider your objection.
• Legal obligation. We keep payment records because the law requires it, for tax and accounting purposes.

Beyond running a booking, we also use survey answers to understand our community and market, and to learn the words people use so we sound like real people rather than a brand.

Who handles it for us

We use a small number of trusted services to store and process this information on our behalf:

• Google Forms holds your survey responses.
• Kit runs our newsletter, if you opt in. Kit sends a confirmation email first, so you are only added once you confirm.
• Stripe processes card payments, whether you book a paid event or buy us a pint. See the next section.
• Supabase and Cloudflare host the systems that store event and booking records.
• Meta receives a measurement signal from this site, but only if you say yes to cookies. See the next section.

We do not sell your information, and we do not share it with anyone beyond the services above and the host of an event you book.

Cookies and measuring our ads

Nothing that tracks you runs on this site until you say yes to it. The first time you visit, a banner asks. Say no and nothing loads, on that visit or any after it. Your answer is stored on your own device so we do not ask twice, and no cookie is needed to remember it.

If you say yes, we load the Meta Pixel. We advertise our events on Instagram, and without it we cannot tell which ads led to somebody actually booking, which means we cannot tell whether the money is worth spending. What it sends is that a page was viewed, that a checkout was started, and that a ticket was bought, with the amount. It also sets cookies in your browser that Meta can use to recognise you across other sites, which is the part worth knowing before you decide.

When you buy a ticket, our own server tells Meta about that sale too, rather than relying on your browser to do it. The reason is dull but honest: browsers block this often enough that the numbers stop being usable, and a measurement we cannot trust is one we would end up spending against blindly.

One piece of personal information goes with it, and only one. Your email address is turned into a scrambled one-way code before it leaves us, so Meta can check it against its own scrambled copy and tell us the sale came from an ad. Meta cannot turn that code back into your address, and we never send the address itself. Nothing else about you goes: not your name, not your phone number, not your date of birth, not where you live, and nothing about your card. We have turned those off at the source rather than trusting ourselves to remember.

We do not upload contact lists to Meta and we do not use this to build advertising audiences from people who have booked with us.

Saying yes also loads Google Analytics, which counts visits and shows us which pages people actually use and where a booking gets abandoned. It is the plainer half of the same question: Meta tells us whether an ad worked, Google tells us whether the page it landed on did. It sets its own cookies, your IP address is shortened before it is stored, and none of the personal information you give us at checkout is sent to it.

Changed your mind? Use the Cookie choices link at the bottom of any page. It forgets your answer and asks again straight away, and the page reloads so anything already running stops.

Where your information is stored

Google, Kit, Meta, Stripe, Supabase and Cloudflare all move some data outside the UK as part of running their services. Each one covers this in its own data processing agreement, using the standard contractual clauses approved for this purpose together with the UK's International Data Transfer Addendum, and Stripe and Kit also rely on the UK extension to the EU-US Data Privacy Framework for transfers to the US where they are certified under it. These are the safeguards UK data protection law requires before information can leave the country, and they are the same ones almost every company our size relies on, because almost none of them run their own UK-only infrastructure.

Booking an event

This site books events. Free events ask only for your name, so the host knows who is coming. Paid events also take a card payment: your card details go directly to Stripe, our payment processor, and never reach our own servers. We see that a payment succeeded, the amount, and the email you gave for a receipt, if any. We do not see or store your card number, expiry date, or security code. Our payment policy and refund policy have the detail.

How long we keep it

We are a young company and have not run enough events yet to know our own patterns, so instead of picking numbers we cannot back up, here is the test we apply to each kind of information:

• Survey answers stay with us while they are still informing what we build, and we delete or anonymise them once they are not.
• Booking and attendance records stay with us while a complaint about that event could still reasonably arrive.
• Incident and ban records stay with us while the ban is in force, along with the reason for it.
• Payment records are the one exception with a fixed number: six years from the end of the financial year they fall in, because company law sets that period, not us.

Outside of that, you can ask us to delete your information at any time and we will, unless we have a legal reason to keep it.

Your choices and rights

Under UK data protection law, you can:

• Ask to see the information we hold about you.
• Ask us to correct it, if it's wrong.
• Ask us to delete it.
• Ask us to restrict how we use it while a query is sorted out.
• Object to us using it, where we rely on legitimate interests.
• Ask for a copy of it in a portable format, where we rely on consent or a contract.
• Withdraw consent whenever you like, for anything we do on the basis of consent. This does not undo what we already did with it before you withdrew.

Every newsletter email has an unsubscribe link too. To exercise any of these rights, contact support@socialise.events.

If you are not happy with how we have handled your information, you can also raise it with the Information Commissioner's Office at ico.org.uk.