Skip to contentpistachio
Why Pistachio
Claude & ChatGPT
Compare
FAQ
Sign in
Privacy policyTermsData processing agreement

Privacy policy

Last updated 17 November 2026

This policy explains what personal data Pistachio collects, why, who helps us handle it, and what you can ask of us. It covers heypistachio.ai, the Pistachio app, and the client portals educators run on it.

Who we are

Pistachio is run by Pistachio (Cloakist B.V.), a private limited company registered in the Netherlands under KvK number 85514411, at P. C. Hooftstraat, 2026 XS Haarlem, the Netherlands. In this policy “Pistachio”, “we” and “us” mean Pistachio (Cloakist B.V.).

For a question about privacy, or a request about your data, email support@heypistachio.ai.

Our two roles

Educators use Pistachio to run programmes, groups and one-to-one work with their clients. Educators here means coaches, trainers, mentors, consultants and the teams who work with them. That gives us two roles:

  • We are the controller for educators’ accounts, for applications to the founding pilot, and for visitors to heypistachio.ai. We decide what that data is used for, and this policy explains it.
  • We are a processor for what an educator’s workspace holds about their clients. That covers contacts, participants, messages, work handed in, recordings, transcripts, contracts and payments. The educator is the controller of that data and decides what happens to it. We handle it only on their instructions, under our data processing agreement.

If you are the client of an educator who uses Pistachio, the educator’s own privacy notice applies to you. Ask them first. If you write to us, we pass your request on to them.

What we collect as controller

Educator accounts

  • Your name, email address and password (stored only as a hash). Also your language, a profile photo if you add one, and your two-factor settings if you turn them on.
  • Your workspace: its name, team members and their roles, branding and custom domain. Also its settings, and the connectors and apps you connect.
  • When you agreed to our terms, and which version you agreed to.
  • How you use the app: the pages you open, the actions you take, any errors, and the IP address and browser each request came from.
  • What you send us: messages to support, feedback, and our replies.

We use this to provide the service you signed up for, which is performance of a contract (GDPR Art. 6(1)(b)). We also use it to keep Pistachio secure, prevent abuse and fix problems, which are our legitimate interests (Art. 6(1)(f)). And we keep the records the law requires, such as financial records (legal obligation, Art. 6(1)(c)).

We email you what the service needs: sign-in links, invitations, notifications you can switch off in Settings, and news of important changes to Pistachio. We don’t send you marketing unless you have asked for it.

Founding pilot applications

When you apply on heypistachio.ai, we receive:

  • your name and email address
  • how you coach and roughly how many clients you have
  • the tools you use, and what you tell us about what’s next.

We email your answers to our support inbox and send you a confirmation. Your answers are not stored in the app. We use them to reply to you and arrange a call, which are steps you asked for before any contract (Art. 6(1)(b)). Choosing who joins the pilot is our legitimate interest (Art. 6(1)(f)). The form uses Cloudflare Turnstile to keep bots out.

Visitors to heypistachio.ai

Our servers and monitoring record the IP address, browser and page of each request. We use these to deliver the site, keep it secure and find errors, which are our legitimate interests. We run no analytics and no advertising trackers. The cookies we use are listed below.

What we process for educators

For an educator, we hold the data they and their clients put into their workspace. It’s up to the educator what a workspace holds. It may include:

  • names, email addresses and phone numbers
  • progress through a programme, worksheets and work handed in
  • messages and community posts
  • session times and attendance
  • recordings, transcripts and notes from calls
  • contracts and signatures
  • purchases and payments made through the educator’s own Stripe account.

We use it only to provide Pistachio to that educator, as our data processing agreement sets out, never for our own purposes. We don’t sell it, build profiles from it or use it to train AI models.

AI drafts

AI drafts stay off until an Owner of a workspace turns them on. Once they are on, Pistachio sends Anthropic what a draft needs, which writes the draft and sends it back. That can be a call’s transcript and the session’s context, work a participant handed in, or documents an educator imports. An educator reviews every draft before anything reaches a client. Anthropic works as our sub-processor and, under its commercial terms, does not use this data to train its models. We record how much each draft cost, never what it says.

Who helps us

These companies help us run Pistachio. Each handles personal data only for the purpose given here, under a written agreement with us. They are our sub-processors.

  • Laravel Cloud (Laravel Holdings Inc.) for hosting, the database, background work and live chat connections, in the EU (Frankfurt).

  • Cloudflare (Cloudflare, Inc.), which does five things for us:

    • DNS
    • file and image storage (R2)
    • video hosting and playback (Stream)
    • the bot check on the pilot application form (Turnstile)
    • receiving and handling email sent to our support inbox.

    Laravel Cloud’s network edge also runs on Cloudflare.

  • Resend (Resend, Inc.) for sending email and receiving replies to it. Our own email goes out from the EU (Ireland). Email from a workspace’s own domain goes out from the region the workspace chooses when it sets the domain up. Resend tells us whether an email was delivered and whether a link in it was clicked.

  • SignWell for contract signing, when a workspace asks its clients to sign a contract.

  • Anthropic (Anthropic, PBC) for AI drafts and content import, only in workspaces that turn AI drafts on.

  • Laravel Nightwatch (Laravel Holdings Inc.) for monitoring errors and performance, including which signed-in account made a request, in the EU.

A workspace can also connect services of its own choosing. They receive data at the educator’s direction, under the educator’s own agreement with them:

  • Stripe, to sell and take payments through the educator’s own Stripe account.
  • Granola, Fireflies and Wispr Flow, to bring in transcripts of calls.
  • Calendly and Cal.com, for bookings. Pistachio adds the client’s name and email address to the booking link so the booking can be matched back.
  • AI assistants an educator connects (such as Claude or ChatGPT), and the API keys and webhooks they set up. These receive what the educator asks them for.

We update this list before we start using a new sub-processor.

Transfers outside the EU

We host Pistachio in the EU. Some of the companies above are based in the United States or handle data there. Each such transfer is protected by one of two safeguards:

  • the EU–US Data Privacy Framework, where the company is certified under it, or
  • otherwise, the European Commission’s Standard Contractual Clauses.

How long we keep it

  • Account data: as long as your account exists. Deleting a workspace deletes its data. When you close your account, we delete your personal data, except what the law requires us to keep, such as financial records.
  • Pilot applications: while we are in touch about the pilot, then deleted.
  • Server logs and monitoring: only as long as we need them to keep Pistachio secure and fix errors.
  • Data held for an educator: as long as the educator keeps it. Deleting it in Pistachio deletes it from our systems. Copies in backups expire on the backup schedule.

Cookies and storage

We use only functional cookies: the ones the site needs to work, or to remember a choice you made. We use no analytics, advertising or tracking cookies, so we don’t ask for consent.

  • pistachio-session keeps you signed in and the site secure. It lasts up to 7 days, or 3 days for an educator.
  • XSRF-TOKEN protects forms against cross-site request forgery. It lasts up to 7 days.
  • remember_web_… and remember_contact_… keep you signed in when you ask to be remembered, or after you sign in with a link we emailed you. They last up to 400 days, or until you sign out.
  • locale remembers your language, for a year.
  • appearance remembers light, dark or system, for a year.
  • sidebar_state remembers whether the app’s sidebar is open, for 7 days.

Your browser’s local storage also keeps a few small preferences that never leave it: your appearance, list or grid views, the last tab or stage you opened, which new features you have seen, and the progress of a video upload so it can resume.

Two services may set cookies of their own: Stripe on a payment step, to prevent fraud, and Cloudflare for the bot check on the pilot application form. Content an educator embeds from another service, such as a video, loads from that service under its own terms.

You can delete cookies in your browser at any time; you will be signed out.

Your rights

Under the GDPR you can ask us to:

  • give you a copy of your personal data
  • correct it
  • delete it
  • restrict how we use it
  • send it to you in a portable format.

You can also object to how we use it: where we rely on our legitimate interests, you can object at any time.

Email support@heypistachio.ai. We answer within one month. If your data is in an educator’s workspace, the request goes to the educator, and we help them answer it.

You can also complain to a data protection authority. In the Netherlands that is the Autoriteit Persoonsgegevens (autoriteitpersoonsgegevens.nl). You can also go to the authority where you live or work.

Security

  • All traffic is encrypted.
  • Each workspace’s data is kept apart from every other workspace’s.
  • What each team member can reach depends on their role.
  • Two-factor sign-in is available to every educator.
  • Connector credentials are encrypted.
  • Our own access to a workspace is limited, logged and time-limited.

The data processing agreement lists our security measures in full.

Children

Educator accounts are for adults. An educator who works with children is responsible for having a lawful basis for their data, including a parent’s consent where that is needed.

Changes to this policy

When what we do changes, we update this page and the date at the top. If a change matters to you, we tell educators by email before it takes effect.

Product

  • Why Pistachio
  • Claude & ChatGPT

Weighing it up

  • Compare
  • FAQ

Join or sign in

  • Join the founding pilot
  • Sign in
  • Participant sign-in
  • Create your account
heypistachio.ai · Built by coaches, for coaches© 2026 PistachioPrivacy policyTermsPhoto credits

pistachio