Rechtliches
Auftragsverarbeitungsvertrag
Dieses Dokument gibt es nur auf Englisch. Die englische Fassung ist verbindlich.
Last updated: 4 November 2026
This Data Processing Agreement ("DPA") is between the studio that accepts the Kilndar Terms of Service (the "Studio", the controller) and Kilndar Ltd, a company registered in England and Wales with company number 17557766 and registered office at 73 Kentish Town Road, London NW1 8NY, United Kingdom ("Kilndar", the processor). It forms part of the Terms and is made to meet Article 28 of the UK GDPR. Where the two disagree on data protection, this DPA wins.
1. Definitions
Words such as "personal data", "processing", "controller", "processor", "data subject" and "personal data breach" have the meaning they have in the UK GDPR and the Data Protection Act 2018. Where the EU GDPR applies to the Studio, they also have the meaning they have there.
2. Roles
- The Studio is the controller of the personal data of its customers, attendees, members and staff that is held in Kilndar.
- Kilndar is the processor. It processes that data only to provide the service and on the Studio's instructions.
- The Studio takes payments through its own Stripe account. Card numbers are typed into Stripe's own fields and never reach Kilndar.
3. About the processing
- Subject matter: providing the Kilndar platform to the Studio.
- Duration: while the Agreement runs, and until the data is deleted or returned under section 11.
- Nature and purpose: hosting and running bookings, schedules, payment records, piece and kiln tracking, courses, memberships, gift cards, customer emails, marketing the customer agreed to, reviews, team tools and reports, as the Studio sets them up.
- Data and data subjects: see Annex 1.
4. What Kilndar commits to
Kilndar will:
- process the data only on the Studio's documented instructions, which include the Terms, this DPA and the way the Studio sets up and uses the platform, unless the law requires otherwise, in which case it tells the Studio first unless the law forbids it;
- make sure everyone allowed to process the data is bound by confidentiality;
- keep the security measures in Annex 2;
- use sub-processors only as section 7 allows;
- help the Studio, as far as the platform reasonably allows, to answer data subject requests and to meet its duties on security, breach notices, impact assessments and consulting the regulator;
- tell the Studio without undue delay after becoming aware of a personal data breach affecting its data, with the information the Studio reasonably needs;
- give the Studio the information it needs to show compliance with Article 28, and allow audits by the Studio or an auditor it appoints, on reasonable notice, at most once a year unless after a breach, and under confidentiality;
- delete or return the data at the end, under section 11.
5. What the Studio commits to
The Studio will:
- have a lawful basis for the processing and explain it to its customers and staff in its own privacy notice;
- give only lawful instructions;
- keep the data it enters accurate; and
- send marketing only to people who agreed to receive it. Marketing consent is off by default in Kilndar.
6. Requests from data subjects
If someone contacts Kilndar directly about their data, Kilndar passes the request to the Studio, unless the law requires Kilndar to act. The Studio can answer most requests itself in the admin: download a customer's profile and booking history, correct their details, anonymise them, and manage their marketing consent.
7. Sub-processors
- The Studio gives Kilndar general authorisation to use sub-processors. The current list, with what each one does and where, is on our Sub-processors page.
- Kilndar tells the Studio, by email or in the admin, before it adds or replaces a sub-processor. The Studio may object on reasonable data protection grounds, and if we cannot resolve it, the Studio may end the Agreement.
- Kilndar binds each sub-processor to data protection terms that protect the data as this DPA does, and stays responsible for them.
- Tracking and ad accounts the Studio connects itself, such as Meta, TikTok or Google, are the Studio's own providers, not Kilndar's sub-processors.
8. Transfers outside the UK
Some sub-processors process data outside the UK. Where they do, Kilndar relies on UK adequacy regulations, the ICO's International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses.
9. Liability
Liability under this DPA is subject to the limits in the Terms, except where the law does not allow it to be limited.
10. Term
This DPA applies from the moment the Studio accepts the Terms, and for as long as Kilndar processes personal data for the Studio.
11. Deletion or return
When the Agreement ends, the Studio can export its data for 30 days. Kilndar then deletes the Studio's personal data within 90 days, or returns it if the Studio asks, unless the law requires Kilndar to keep it. Copies held in backups are deleted as those backups expire.
12. Law
This DPA is governed by the law of England and Wales.
Annex 1: Data and data subjects
Data subjects: the Studio's customers and people interested in its services, attendees named on bookings, gift buyers and recipients, members, and the Studio's staff.
Personal data:
- Contact details: name, email, and phone when given.
- Bookings and purchases: what was booked or bought, dates, party size, amounts paid and refunded, answers to booking questions, waiver acceptance, notes and occasion messages.
- Pieces: photos of pottery pieces and where they are in the studio.
- Memberships, gift cards, vouchers and loyalty stamps.
- Feedback: reviews, ratings, survey scores and complaints.
- Marketing consent and the emails sent to each person.
- Staff: name, email, role, branch, shifts, hours, time off and sign-in details.
- Not processed: card numbers, which stay with Stripe.
Special category data: none intended. Customers may write health or access needs in free-text answers, and the Studio handles those as controller.
Frequency: continuous, while the Agreement runs.
Annex 2: Security measures
- Data sits in a Postgres database in Ireland, hosted on Supabase, encrypted at rest. Every connection to Kilndar is encrypted over HTTPS.
- Every record carries the studio it belongs to, and row-level security in the database lets only that studio's own staff read or change it.
- Staff sign in with their own accounts and a role (owner, manager or host), can be limited to their own branch, and switch on shared counter tablets with a personal PIN. Passwords are stored hashed.
- Customers have no accounts: each booking link is signed and opens that booking only.
- Changes to bookings, sessions and activities are written to an audit log with who made them.
- Card payments run on Stripe. Card numbers never touch Kilndar's servers.
A studio that wants a signed copy of this DPA can ask at hello@kilndar.com.