Data processing addendum

Last updated: 14 November 2026

How Pulse handles attendee data on behalf of an organiser, under the UK GDPR.

In short

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

  • You, the organiser, decide how your attendees’ data is used. We handle it only on your instructions and for no other purpose.
  • The companies we use for the data are listed in section 5. We give you at least 30 days’ notice of a new one, and you can object.
  • We keep the data secure with the measures in section 8, and we tell you within 48 hours of a breach that affects it.
  • We help you answer people who use their rights, and you can export the data from Studio at any time.
  • When your account closes, we delete the attendee records and your conference content within 90 days.

1. Parties and scope

This addendum is between the organiser who accepted the terms of service (“the controller”) and Pulse Ventures AI Ltd, company number 15797681 (“the processor”). It forms part of the terms of service and applies from the day the organiser accepts them. No separate signature is needed.

It applies to the personal data of attendees that the processor handles for the controller through the service (“the data”). It does not apply to the data that the processor controls for its own purposes, such as the details of the organiser’s team. The Privacy notice covers that.

In this addendum, “controller”, “processor”, “personal data”, “personal data breach” and “processing” have the meanings the UK GDPR gives them.

2. Details of the processing

Details of the processing
ItemDetail
Subject matter and purposeProviding the service to the controller: selling and issuing tickets, registering attendees, signing attendees in, and showing them the conference
Nature of the processingStoring, retrieving, displaying, emailing and deleting the data
DurationWhile the controller’s account is open, and then until deletion under section 10
Who the data is aboutThe controller’s attendees, ticket buyers, registrants, speakers shown in uploaded material, and people who use the controller’s contact form or chat
Types of dataNames, email addresses, order and ticket details, registration answers, pass and access records, sign-in records, chat names and messages, and messages sent through the controller’s forms
Special categoriesNone are intended. The controller must not collect special category data, such as health or religion, through the service unless it has told us and has a lawful basis

3. What the processor will do

The processor will:

  • process the data only on the controller’s written instructions, which are the terms of service, this addendum and the controller’s use of the service. The processor will tell the controller if it believes an instruction breaks the law, unless the law stops it. If the law requires processing the controller has not instructed, including a transfer outside the UK, the processor will tell the controller first, unless the law forbids that
  • process the data for no other purpose, and not sell it
  • if the police, a court or another public body asks for the data, disclose it only where the law requires it or where someone’s life or safety is at risk, disclose only what the request needs, and tell the controller first unless the law forbids it or doing so would put someone at risk (and otherwise as soon as it can)
  • make sure that everyone who can access the data is bound by a duty of confidence
  • keep the data secure with the measures in section 8
  • help the controller answer requests from people who want to use their rights, including by giving the controller an export of the data (the controller can also download registrations, orders and passes from Studio) and by correcting or deleting a named person’s data within 10 working days of the controller’s written request, and tell the controller within 5 working days if a person writes to the processor about the data
  • help the controller with its security duties, data protection impact assessments and consultations with the regulator, taking account of the nature of the processing
  • give the controller the information it needs to show that the processor follows this addendum, and allow audits as section 7 explains

4. What the controller will do

  • The controller will have a lawful basis for the data and will tell attendees how it is used.
  • The controller will give instructions that follow the law and will not ask the processor to do anything the law forbids.
  • The controller will use the service’s access controls, such as roles, to keep the data to people who need it.

5. Other companies the processor uses

The controller agrees that the processor may use the companies below to process the data. The processor has a written contract with each one that requires data protection terms at least as strong as these, and the processor remains responsible to the controller for them.

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.

The processor will tell the controller of any new company, or any replacement, by email to the workspace owner and by updating this page, at least 30 days before the company starts to process the data. The controller can object in writing within that time, on reasonable data protection grounds. If the processor cannot meet the objection, the controller may close the account and receive a refund for the unused part of what it paid.

6. Transfers outside the United Kingdom

The processor will transfer the data outside the UK only where the transfer is protected as the UK GDPR requires. That means the UK’s adequacy regulations (for the European Union), the UK Extension to the EU-US Data Privacy Framework (the UK-US data bridge) for a United States company that is certified under it, the ICO’s International Data Transfer Agreement or the UK Addendum to the standard contractual clauses, or another lawful safeguard.

7. Checking that the processor follows this addendum

The processor will answer reasonable written questions about how it protects the data, and will give the controller its relevant records. If the controller needs more, it may carry out an audit once a year, or at once after a personal data breach, on 30 days’ written notice, in working hours, and without harming other customers. The controller pays the costs. Write to hello@pulseventures.co.uk.

8. Security measures

The processor protects the data with these measures:

  • All traffic to the service is encrypted in transit.
  • The controller’s payment keys are encrypted when stored. Card details are never stored by the processor.
  • Each organiser’s data is kept apart. Every request checks which workspace it belongs to, and the service refuses to read across workspaces.
  • Access inside a workspace depends on role: owner, admin, editor or viewer. Only the owner handles money and settings.
  • Sign-in links for attendees are single use, last 15 minutes and are stored only in a scrambled form. Attendee sessions are signed.
  • Counters that limit abuse use scrambled keys.
  • The processor’s staff can open a workspace only through a controlled admin area. Each visit and search is recorded in a log that the database refuses to change or delete.
  • Each export and each deletion of attendee data is recorded in a log that the database refuses to change or delete. The log holds counts, never names or email addresses.
  • Error alerts hide email addresses.
  • The processor reviews these measures at least once a year.

9. Personal data breaches

The processor will tell the controller without undue delay, and within 48 hours, after it becomes aware of a personal data breach that affects the data. The notice will say what happened, what data is involved, what the processor is doing and who to contact. The processor will help the controller with any report to the regulator or to the people affected.

10. Returning and deleting the data

The controller can export a conference’s registrations, orders and passes at any time from Studio. For a very large conference, or for other data, the controller writes to us and we send it within 30 days. When the account closes, the controller may also ask within 30 days for a copy of the data. The processor will send it in a common format, such as CSV, within 30 days of the request.

At the controller’s choice, at the end of the service the processor will delete or return the data. The processor will delete the attendee records (registrations, attendees, check-ins, passes, orders and sign-in links) within 90 days of closure. Within the same 90 days it deletes the controller’s conference content: the conference pages, speakers, sessions and sponsors, and the uploaded images and videos together with their stored files. Copies in backups leave as the database host’s restore history rolls over, within 7 days after that, and are not restored except to recover from a fault. The processor will confirm the deletion in writing on request.

The processor keeps its own financial records (the payments ledger, the ticket fee ledger and invoices), which hold no attendee name or email address, and its audit records, for six years. These terms do not apply where the law requires the processor to keep other data.

11. General

The liability terms of the terms of service apply to this addendum. This addendum is governed by the law of England and Wales, and the courts of England and Wales have exclusive jurisdiction. If the law changes so that this addendum no longer meets the UK GDPR, we will update it, and the controller will be asked to accept the update.