Data processing agreement
Last updated 17 November 2026
This data processing agreement (“DPA”) is part of our terms of service. It is between:
- you, the business whose workspace runs on Pistachio, the controller, and
- Pistachio (Cloakist B.V.), registered in the Netherlands under KvK number 85514411, the processor (“we”, “us”).
It applies to the personal data we process for you through your workspace. Agreeing to the terms means agreeing to it; it needs no separate signature. If you would like a signed copy for your records, email support@heypistachio.ai.
Words such as personal data, processing, controller, processor, data subject and personal data breach mean what they mean in the GDPR (Regulation (EU) 2016/679).
1. What we process, and why
We process personal data only to provide Pistachio to you, under the terms. Annex 1 sets out the details: the subject matter, nature and purpose, the types of personal data, and the categories of data subjects. The processing lasts as long as your workspace exists, and then until the data is deleted under section 9.
2. Your instructions
- We process the data only on your documented instructions. These are the terms, this DPA, and what you and your team do in Pistachio and through its settings, integrations and API.
- If the law requires us to process it otherwise, we tell you first, unless that law forbids it.
- If we believe an instruction breaks the GDPR, we tell you.
You are responsible for the lawfulness of the processing: for having a lawful basis, for what you put into Pistachio, and for informing your clients.
3. Confidentiality
Everyone at Pistachio who can reach your data is bound to keep it confidential. They reach it only when they need to, to support you or to keep Pistachio running.
4. Security
We take appropriate technical and organisational measures to protect the data, as GDPR Article 32 requires. Annex 2 lists them. We may improve them over time, but never so that the protection falls below what Annex 2 describes.
5. Sub-processors
- Your authorisation. You give us general authorisation to use sub-processors. The current list is in our privacy policy.
- Our obligations. Each sub-processor is bound by a written agreement with data protection obligations at least as protective as this DPA. We remain responsible to you for its work.
- A new one. We add a new sub-processor to that list before it starts processing your data. If you object on reasonable data protection grounds, tell us. If we can’t resolve your objection, you can close your workspace.
Services you choose to connect are not our sub-processors: they work under your own agreement with them. These include your Stripe account, a note-taker, a booking tool, an AI assistant, an API key and a webhook.
6. Transfers outside the EU
We host Pistachio in the EU. If a sub-processor processes your data outside the European Economic Area, we make sure the transfer is lawful under Chapter V of the GDPR: through an adequacy decision such as the EU–US Data Privacy Framework, or the European Commission’s Standard Contractual Clauses.
7. Helping you
Taking into account the nature of the processing, we help you to:
- Answer requests from data subjects exercising their rights. Most you can handle yourself in Pistachio. If a request reaches us, we pass it to you and don’t answer it ourselves.
- Meet your obligations under GDPR Articles 32 to 36: security, notifying breaches, data protection impact assessments and prior consultation, using the information available to us.
8. Personal data breaches
We tell you without undue delay, and within 48 hours, of becoming aware of a personal data breach affecting your data. We tell your workspace’s Owners by email, with what we know about:
- the nature of the breach and the data and people concerned
- its likely consequences
- what we are doing about it.
We add to that as we learn more, and we help you notify the supervisory authority and the people affected where you need to.
9. Return and deletion
You can export your data while your workspace exists. When your workspace closes, we delete the personal data we process for you, unless the law requires us to keep it. Copies in backups expire on the backup schedule and are never restored except to recover the service.
10. Information and audits
We make available to you the information needed to show we meet GDPR Article 28. Write to us, and we answer reasonable questions about our processing and security.
If that isn’t enough, you or an auditor bound to confidentiality may audit our compliance, with these conditions:
- at most once a year, unless a supervisory authority requires more, or after a breach
- with 30 days’ notice
- during business hours
- at your own cost
- in a way that doesn’t disturb Pistachio or other customers’ data.
11. Liability and precedence
Each side’s liability under this DPA is subject to the limits in the terms, except where the GDPR doesn’t allow them. Where this DPA and the terms conflict about personal data, this DPA prevails.
Annex 1: Details of the processing
Subject matter and purpose. Providing Pistachio to you. That means hosting and running your workspace, programmes, groups and private engagements, client portal, messages, sessions, contracts, sales, and the integrations you turn on.
Nature of the processing. Collecting, storing, organising, displaying, sending (by email and in the app), analysing (such as AI drafts, if you turn them on), and deleting.
Categories of data subjects. Your clients, participants, leads, buyers and guests. Your team members. Anyone else whose data you or they put into Pistachio.
Types of personal data:
- Identity and contact details: names, email addresses, phone numbers, profile photos.
- Programme data: enrolments, progress, worksheets, work handed in, feedback, introduction answers.
- Communication: messages, community posts, emails sent through Pistachio and the replies to them.
- Sessions: times, attendance and replies to invitations; recordings, transcripts, notes and recaps of calls.
- Contracts: signers, signatures, signed documents.
- Purchases and payments made through your own Stripe account: amounts, status, billing name, company and VAT number. Card details never reach Pistachio.
- Technical data from your clients’ visits: IP address, browser, and sign-in records.
- Special categories of data, such as health information, only if you or your clients put them in.
Duration. As long as your workspace exists, then until deletion under section 9.
Annex 2: Security measures
- Where data lives. In the EU: the database and application on Laravel Cloud (Frankfurt), files on Cloudflare R2. Our hosting and storage providers encrypt data at rest.
- In transit. Every connection to Pistachio uses TLS.
- Keeping workspaces apart. Every query is scoped to its workspace, and a request for another workspace’s records is refused.
- Access by role. Owner, Educator and Assistant each reach only what their role allows. Client portals show each client only their own work and what is shared with them.
- Sign-in. Passwords are stored as hashes. Two-factor sign-in is available to every educator and required for our own administrative access. Sign-in links expire.
- Secrets. Connector credentials and API key secrets are encrypted in the database.
- Our own access. Our staff can view a workspace as a team member only to support it. Each visit lasts fifteen minutes at a time, needs two-factor sign-in, and is logged.
- Payments. Card details are entered on Stripe’s forms and never reach Pistachio. The payment events we keep are stripped of card and bank details.
- Monitoring and upkeep. Errors and performance are monitored. Dependencies are kept up to date, and changes are tested before they ship.
- Backups. The database is backed up by our hosting provider, so the service can be recovered.