Privacy notice

Last updated: 14 November 2026

How Pulse Stagecraft uses personal data, for organisers and for attendees.

In short

This summary helps you find your way. It does not replace the notice: the numbered sections are what count.

  • If you run a conference in Studio, we decide how your account data is used. If you bought a ticket or registered, the organiser of that conference decides, and we handle your details for them.
  • We use data to run the service, bill organisers, keep the service secure and meet the law. We do not sell personal data.
  • Analytics cookies run only if you agree, and you can change your mind at any time.
  • Some of the services we use are outside the UK. We protect data sent abroad as the law requires.
  • Each kind of data has a set time we keep it, shown in section 8.
  • You can ask for a copy of your data, ask us to correct or erase it, and object to how we use it. Attendees ask the organiser first.
  • If you are unhappy, tell us first. You can also complain to the Information Commissioner’s Office.

1. Who this notice is for

Pulse Stagecraft is a Pulse Ventures company, provided by Pulse Ventures AI Ltd, trading as Pulse Ventures. We are a company registered in England and Wales (company number 15797681). Our registered office is 20 Wenlock Road, London, N1 7GU. You can write to us at hello@pulseventures.co.uk.

This notice covers two groups of people. Organisers are the people and companies who sign in to Studio to run a conference. Attendees are the people who buy a ticket, register, or sign in to watch a conference that an organiser runs on Stagecraft. We explain below what we do with each group’s data and which of us decides how it is used.

We follow the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018.

2. Who is responsible for your data

  • For organisers, Pulse is the controller. We decide why and how we use the details of the people who use Studio.
  • For attendees, the organiser is the controller. The organiser decides why a ticket buyer’s details are collected and how they are used. Pulse is the organiser’s processor: we store and handle the details on the organiser’s instructions, under the Data processing addendum.
  • For analytics on our own website, on Studio and on the conference sites we host, Pulse is the controller. These analytics count visits to improve the platform. We do not give them to organisers as attendee records.
  • Payment providers, such as Stripe, are responsible for the payment details they collect on their own pages. They are separate controllers for that data and use it under their own privacy notices.

If you are an attendee and want to use your rights, ask the organiser first. Their name is on the conference site and on your ticket email. We will help the organiser answer you.

3. What personal data we use

About organisers and their team:

  • Your name and email address, and the sign-in method you use. Our sign-in provider, Kinde, holds your sign-in record and gives us your name, email address and a user number.
  • Your workspace name, your role in it and when you were invited or last used it. If a colleague invited you, they gave us your email address and chose your role.
  • Which version of the terms you accepted and of this notice you were shown, and when. We keep this record for six years, then review it.
  • Billing details: the name and email on the account, a billing address, and a tax number if you enter one. Stripe holds your card details. We do not see them.
  • How you use Studio, such as the pages you open and the changes you make, recorded in logs that help us run and secure the service.
  • Records of staff access. When a member of our staff opens or searches for your workspace or conference to give support, we record who looked, when, and which workspace or conference.
  • Records of attendee data exports and deletions: who did it, for which workspace or conference, when, and how many records. These never hold an attendee’s name or email address.
  • Messages you send us.

About attendees, on the organiser’s behalf:

  • The name and email address given when buying a ticket or registering, and any answers to the organiser’s own questions.
  • The order: which ticket, the price, a promotion code if used, the order reference and its status. For a bank transfer, the reference the organiser records.
  • The pass issued, and when it was used to view paid sessions or recordings.
  • A sign-in link and a sign-in cookie. We store a scrambled form of the link, not the link itself.
  • Live chat and session comments, only where the organiser has switched them on.
  • Messages sent through the organiser’s contact form, which we pass to the organiser.
  • Speaker names, photos and other details that the organiser adds to the conference site.

About everyone who visits a page:

  • Your IP address and browser details, which our host records when it serves a page.
  • Counters that limit repeated requests, such as repeated sign-in emails. We store only a scrambled form of the address. A counter stops counting after at most one hour, and we delete expired counters soon after.
  • Cookies and similar technology, as section 7 explains.

Where we get it. Most of this data comes from you. Some comes from others: a colleague who invites you to a workspace gives us your email address and role, an organiser who adds you as a speaker gives us your details, Kinde gives us your sign-in details, and Stripe tells us whether a payment succeeded.

4. Why we use it, and our legal reason

Our purposes and legal reasons as controller
What we doLegal reason
Open your account, sign you in, run Studio, bill you and give you supportContract: we need this to provide the service you asked for
Keep records for tax and accountsLegal obligation
Keep the service secure, stop fraud and abuse, fix faults and send service alertsLegitimate interests: running a safe and reliable service
Send you notices about your account and changes to the termsContract and legitimate interests
Count visits to our website, Studio and the conference sites we host, and record sessions, with analytics cookiesConsent. You can say no, and you can change your mind at any time with the cookie settings
Count page views and measure page speed without cookiesLegitimate interests: understanding how the service is used and keeping it fast
Keep records of the terms you accepted, of staff access, and of attendee data exports and deletionsLegitimate interests: showing what was agreed and who handled data
Defend or bring legal claimsLegitimate interests

For attendee data, the organiser chooses the legal reason. It is usually that the data is needed to sell and deliver the ticket you bought. We do not use the attendee records we hold for the organiser for our own purposes, and we do not sell personal data. Analytics on conference sites are ours, and need your consent, as section 7 explains.

5. Who we share data with

We use the services below to run the platform. Each one handles personal data only to do its job for us and under a contract that requires it to protect the data.

Services that handle personal data for us
ServiceWhat it does for usPersonal data it handlesWhere
Vercel Inc.Hosts the application and serves its pages. Its Web Analytics and Speed Insights measure visits and page speed without cookies, and run without asking.Everything the application handles while it runs, and web request logs, including IP addresses.Our functions run in London. Vercel serves pages from servers around the world.
Neon, Inc.Hosts the database.Accounts, workspaces, conferences, orders, passes, registrations and the records around them.Neon, Inc. is a United States company. The database runs in the Neon region set for our project. We give you the region on request.
Cloudflare, Inc. (R2 storage)Stores the images and videos that organisers upload.Uploaded files, which can show people, such as speaker photos.Cloudflare, Inc. is a United States company. Files are stored in the bucket we set up and served from its global network.
Resend, Inc.Sends our emails: sign-in links, ticket and order emails, invitations and alerts.Email addresses, names and the content of the email.The United States and the European Union.
Kinde LimitedSigns organisers in and out of Studio.Name, email address, sign-in method and the sign-in record of an organiser.Kinde is based in Australia. Sign-in records are kept in the data region set for our Kinde account. We give you the region on request.
Stripe Payments UK Ltd and Stripe, Inc.Bills organisers for their subscription. Takes ticket payments for organisers who connect Stripe.Name, email address, billing address, tax number and payment details of an organiser. A ticket buyer gives payment details to Stripe on its own page.The United Kingdom, the European Union and the United States.
PostHog, Inc.Counts visits and uses of our website, Studio and the conference sites we host, and records sessions, only after you agree to analytics.Pages viewed, device and browser details, recordings of what happens on the page with form fields hidden, and an identifier stored in your browser.PostHog’s European Union host. PostHog, Inc. is a United States company.
Google LLC (Google Analytics and Tag Manager)Counts visits to our website, Studio and the conference sites we host, only after you agree to analytics.Pages viewed, device and browser details, and an identifier stored in your browser.Google chooses the location. Its own terms name the locations.
Ably Realtime LtdRuns live chat and session comments, only for a conference whose organiser switches them on.The name a person chooses for chat and what they write.Ably chooses the location. Its own terms name the locations.

Organisers can connect their own payment account to sell tickets. The provider takes the payment for the organiser. We do not receive card details or ticket money. The providers an organiser can connect are Stripe, PayPal, Paystack, Flutterwave.

We share attendee data with the organiser whose event it is. We also share data when the law requires it, or to protect our rights, and with a buyer if we sell the business, on the same terms as this notice.

When the police, a court or another public body asks us for personal data:

  • We hand it over only when the law requires us to, such as under a court order, a warrant or another legal power, and we check each request first.
  • In an emergency where someone’s life or safety is at risk, we may share what is needed to help, without waiting for an order.
  • We share only the data the request needs.
  • We tell the person concerned, or for attendee data the organiser, before we share it, unless the law forbids it or telling them would put someone at risk. If we cannot tell them first, we tell them once we can.

6. Sending data outside the United Kingdom

Some of the services above run outside the UK, mainly in the European Union and the United States. When personal data leaves the UK, we make sure it has the protection the law requires. For the European Union, we rely on the UK’s adequacy regulations. For a United States company certified under the UK Extension to the EU-US Data Privacy Framework (the UK-US data bridge), we can rely on that certification. For any other service, or where there is no certification, such as Kinde in Australia, we use the ICO’s International Data Transfer Agreement or the UK Addendum to the European Commission’s standard contractual clauses. The table in section 5 shows where each service runs. You can ask us for a copy of the safeguard.

7. Cookies

We use these cookies:

  • Sign-in cookies, set by our sign-in provider Kinde, so that Studio knows who you are. They last until you sign out or your session ends. They are needed to run the service.
  • A workspace cookie that remembers which workspace you chose, for up to 30 days. It is needed to run the service.
  • A cookie called stagecraft_terms_agreed that remembers which version of our terms you agreed to in this browser, so Studio does not send you to the agreement page each time, for up to 400 days. It is needed to run the service.
  • An attendee cookie (stagecraft_attendee, followed by the conference) that keeps an attendee signed in to one conference, for up to 30 days. It is needed to run the service.
  • A cookie called pulse_consent that remembers your cookie choices for about six months (182 days). It is needed to respect your choice.
  • Analytics cookies from PostHog and Google, only if you agree. Studio and the conference sites ask first. Before you agree, PostHog does not run. If you agree, PostHog may also record your session, with what you type in form fields hidden.
  • Vercel Web Analytics and Speed Insights measure visits and page speed without cookies and without storing anything on your device. They run without asking. If you do not want them, write to us and we will tell you how to block them.

An organiser can add their own trackers to their conference site. Those are the organiser’s responsibility, and the site asks visitors first.

8. How long we keep data

How long we keep data
DataHow long
Organiser account and workspace dataWhile the account is open. After closure, we delete it when you ask us to, within one month of your request. We keep invoices, terms-acceptance records and audit records as this table shows
Invoices and payment recordsSix years after the end of the tax year, as tax law requires
Attendee dataAs the organiser instructs while the account is open. We delete it within 90 days after the account closes
Conference content: pages, speakers, sessions, sponsors, and uploaded images and videosWhile the account is open. We delete it, with the stored files, within 90 days after the account closes
Sign-in linksUsable for 15 minutes. A daily clean-up deletes expired links, with the email address they were sent to
Request countersExpire after at most one hour, then deleted in routine clean-ups
Server and security logsUp to 30 days, as set by our host
Records of staff access to a workspace, of terms accepted, and of attendee data exports and deletionsSix years, then reviewed. These records cannot be changed or deleted before then
Database backupsOur database host keeps a rolling restore history of up to 7 days. Deleted data leaves the backups as that history rolls over

9. Your rights

You have the right to:

  • be told how your data is used, which this notice does
  • ask for a copy of your data
  • ask us to correct data that is wrong
  • ask us to erase your data, where the law allows
  • ask us to restrict how we use it
  • receive your data in a common format, where the law allows
  • withdraw your consent at any time, for example in the cookie settings

Your right to object. Where we rely on legitimate interests, you can object at any time. We will then stop, unless we have strong legitimate grounds that outweigh your interests, or we need the data for a legal claim.

To use a right over data we control, write to hello@pulseventures.co.uk. We reply within one month. For attendee data, write to the organiser. If you write to us about attendee data, we will pass your request to the organiser and tell you that we have.

We do not make decisions about you by automated means that have legal or similarly significant effects. You must give your name and email address to open an account or buy a ticket. Without them we cannot provide the service.

10. Complaints

If you are unhappy with how we have used your data, write to hello@pulseventures.co.uk. We reply within one month, as we do for a request about your rights, and tell you what we found and what we will do. For attendee data, complain to the organiser first.

You can also complain to the Information Commissioner’s Office, the UK regulator for data protection. The ICO may ask you to raise the matter with us first. Its website is ico.org.uk, its helpline is 0303 123 1113, and its address is Information Commissioner’s Office, Wycliffe House, Water Lane, Wilmslow, Cheshire, SK9 5AF.

11. How we protect data

We protect personal data with encryption in transit, encryption of payment keys at rest, access limited by role, separation between organisers, scrambled sign-in links, and logs of staff access. The Data processing addendum lists the measures. No system is perfectly secure. If a breach affects your data, we will tell you as the law requires.

12. Children

Studio is for adults: everyone in an organiser’s workspace must be 18 or over.

  • To buy a ticket, register or sign in to a conference yourself, you must be 13 or over.
  • A child under 13 can still go to an event: a parent or guardian books for them, using the parent or guardian’s own details.
  • If we learn that we hold details a child under 13 gave us themselves, we delete them, in the same way as any request to delete a person’s data (section 9), within one month of learning of it.
  • An organiser who runs an event for children, or collects children’s details, is responsible for doing so lawfully.

13. Changes to this notice

We may update this notice. The “Last updated” date shows the latest version. When this notice changes, we show organisers the new version in Studio and ask them to confirm that they have read it.

14. How to contact us

Write to hello@pulseventures.co.uk, or to Pulse Ventures AI Ltd, 20 Wenlock Road, London, N1 7GU.

We have not appointed a data protection officer, because the law does not require one for us. Write to hello@pulseventures.co.uk about any data protection question.