Under UK GDPR you are the data controller for your customers' personal data, and Session is your processor.

Get a Data Processing Agreement
Article 28 requires a written contract with any processor. Ours is at bookasession.org/dpa, covering sub-processors, security, breach notification, data-subject requests and what happens to your data if you leave. Email us for a countersigned copy, or to use your insurer's or council's template.
Where your data is hosted
- Your data (bookings, customers, waivers, consent) is stored in the Republic of Ireland (EEA), and the app runs in Dublin.
- Payments - handled by Stripe Payments Europe, an Irish entity. Card numbers never reach Session.
- Email - marketing email is sent through AWS in London. Transactional email (confirmations, reminders) goes through Resend in the US.
A few sub-processors are US-based - Clerk for logins, Resend for transactional email, Vercel for hosting, and Better Stack for uptime monitoring and logs. Those transfers are covered by the UK International Data Transfer Agreement. Annex 3 of the DPA lists every sub-processor with its location, and we'll give you 30 days' notice before that list changes.
Answer a subject access request
A request for a copy of someone's data is an Article 15 request; you have one month to respond.
- 1
Find and export them
In Customers, search for their name or email, then use Export with the search still applied. You get one row for that person - contact details, visit and spend history, membership, marketing consent, and any survey answers.
- 2
Add their bookings if they've asked for detail
Reports → Export gives you the bookings ledger for a date range. See CSV exports.
The CSV is machine-readable, as the law requires.
Handle a deletion request
A request to be deleted is an Article 17 request. Open the customer in Customers and choose Erase personal data.
- They've never booked, bought or signed anything (no bookings, memberships, vouchers or waivers). The record is removed entirely.
- They've booked before. Their name, email, phone and any survey answers are removed, their sign-in is closed, and they come off every mailing list. The booking and payment rows stay as anonymous entries, and their signed waiver keeps the fact and version they agreed to without the signature or name.
- They sent a request. Their contact details and message go; the dates stay.
- They're named in your log. Accident, injury and near-miss entries are kept, unlinked, until a claim could no longer be brought (3 years, or until they could be 21 if they may have been under 18), then deleted. Maintenance and feedback entries naming them are deleted at once.
HMRC requires you to keep transaction records for six years, and a signed waiver defends a liability claim; Article 17(3) allows retaining data on those grounds. Erasure doesn't change your reports.
Erasure can't be undone, so check the request.
Marketing consent
Consent is recorded per organisation with an audit trail: the wording shown, where and when. Customers can withdraw it from their account page or any marketing email's unsubscribe link, and you can change it on their record in Customers. Booking emails (confirmations, reminders) are sent regardless. See grow your subscriber list.
Special category data
The optional community survey asks for demographic details including ethnicity, which is special category data under Article 9. It's off unless you switch it on. If you turn it on, you're responsible for identifying an Article 9 condition and telling your customers what you're collecting and why. The log's accident and injury entries hold health information, which is also special category data: only Admins can read them, and the alert emails never include it. Only the venue whose survey collected the answers sees them, even when the customer books elsewhere on Session. If a customer answers the survey again at another venue, the new answers replace the old ones and belong to that venue.
What the help assistant can see
Ask AI (in Help & support and the help center search) is given your venue's settings so it can answer questions about your setup: the facts already on your public FAQs page, plus details like whether Stripe is connected and your region.
It is not given your customers, bookings, payments, vouchers or emails, and can't look one up.
Those settings are sent to Anthropic to generate the answer. They contain no customer personal data, so Anthropic isn't on the sub-processor list in Annex 3.
Your question and the answer are recorded against your organisation to improve the articles. If you'd rather not use it, use Chat with support instead.
Importing a checklist
Import your checklist sends your photo, PDF or text to Anthropic to read; Session doesn't keep it. Cover staff names and signatures.
AI apps you connect
An AI app an admin connects reads your reports and customer records under your own account with its provider, so it isn't a Session sub-processor (DPA section 6.5).
Common questions
-
Do I need to register with the ICO? Almost certainly: most UK businesses holding customer data pay a fee. Check at ico.org.uk.
-
Do I need my own privacy policy? Yes. Session's privacy policy covers us as your processor; your customers need a notice from you about what you collect and why. Host it anywhere, such as a Google Doc, and link it under Privacy policy in Booking page → Links.
-
Can I get my data out if I leave? Yes. See exporting all your data. The DPA keeps your data available for export for 30 days after you leave, with 90 days' notice if Session ever winds down.
-
What happens if there's a data breach? We'll tell you without undue delay and within 48 hours, with what happened and what's affected. Reporting to the ICO is your call as controller - we won't do it unless you ask.
-
A customer says delete everything, but they owe me money. Erasure doesn't cancel a debt or an unfinished dispute. Article 17(3) lets you retain what you need to establish or defend a legal claim. Settle the matter first, then erase.