Mindhoops

Data Processing Agreement

For schools, tutoring centres and other organisations that use Mindhoops for their pupils. It sets out how Anjuna Labs Pte. Ltd. processes personal data on your behalf, as required by GDPR Article 28, section 40 of the Thai PDPA and the Singapore PDPA.

Last updated 10 November 2026

1. 1. Parties and scope

This Data Processing Agreement ("DPA") is between the organisation that has agreed to use Mindhoops for its pupils (the "Customer") and Anjuna Labs Pte. Ltd., a company registered in Singapore (registration number [TO CONFIRM: UEN]), at 68 Circular Road, #02-01, Singapore 049422 ("we", "us" or the "Processor").

It applies when the Customer uses Mindhoops under a separate agreement with us (the "Main Agreement"). For that use, the Customer is the controller and we are the processor of the personal data described in Annex 1.

This DPA becomes part of the Main Agreement when both parties sign it or the Customer accepts it (for example, when signing or accepting the Main Agreement). To receive a signed copy, email privacy@mindhoops.com.

This DPA does not apply to parents who sign up for their own family account. For those accounts, we are the controller, as described in our Privacy Policy.

2. 2. Definitions

  • Data Protection Laws means all laws on personal data that apply to the processing under this DPA, including the Thailand Personal Data Protection Act B.E. 2562 (2019) ("Thai PDPA"), the EU General Data Protection Regulation 2016/679 and its UK version ("GDPR"), and the Singapore Personal Data Protection Act 2012 ("Singapore PDPA").
  • Personal Data means personal data that we process on the Customer's behalf under the Main Agreement.
  • Sub-processor means a third party we engage to process Personal Data.
  • Personal Data Breach means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, Personal Data.
  • Other terms such as "controller", "processor", "data subject" and "processing" have the meaning given in the Data Protection Laws.

3. 3. Details of the processing

Subject matter: providing the Mindhoops AI tutoring service to the Customer's pupils.

Duration: for the term of the Main Agreement, and afterwards until the Personal Data is deleted or returned under section 11.

Nature and purpose: hosting, storing, organising, analysing and transmitting Personal Data to run live voice lessons with an AI tutor, adapt lessons to each pupil, save pupils' work and progress, show progress to authorised adults, provide support, and keep the service secure.

The categories of data subjects and Personal Data are set out in Annex 1.

4. 4. The Customer's responsibilities

  • The Customer is responsible for having a lawful basis for the processing, including any consent from parents or guardians that the Data Protection Laws require for pupils who are children.
  • The Customer will give data subjects the information about the processing that the Data Protection Laws require.
  • The Customer's instructions to us must comply with the Data Protection Laws.
  • The Customer is responsible for keeping pupils' sign-in links and staff credentials secure within its organisation.

5. 5. Processing only on instructions

We will process Personal Data only on the Customer's documented instructions. The Main Agreement, this DPA and the Customer's use and configuration of the service are the Customer's instructions. We will not use Personal Data for our own purposes, sell it, or use it for advertising or marketing.

If the law requires us to process Personal Data in another way, we will tell the Customer first, unless the law forbids it. If we believe an instruction breaks the Data Protection Laws, we will tell the Customer promptly.

6. 6. Confidentiality

We will make sure that anyone we authorise to process Personal Data is bound by a duty of confidentiality, and has access only to the Personal Data they need for their role.

7. 7. Security

We will put in place appropriate technical and organisational measures to protect Personal Data, taking into account the risks to data subjects, especially children. These measures are described in Annex 3. We may update them over time, as long as the overall level of security is not reduced.

8. 8. Sub-processors

The Customer gives general authorisation for us to use the Sub-processors listed in Annex 2 and on our processors page.

  • We will impose on each Sub-processor, by written contract, data protection obligations that are no less protective than those in this DPA.
  • We will give the Customer notice before adding or replacing a Sub-processor, by updating our processors page and, if the Customer has asked to be notified by emailing privacy@mindhoops.com, by email. Where reasonably possible, we will give at least 30 days' notice.
  • The Customer may object to a new Sub-processor on reasonable data protection grounds within the notice period. We will then work with the Customer in good faith to find a solution. If we cannot, the Customer may end the affected part of the Main Agreement and receive a refund of any prepaid fees for the unused period.
  • We remain responsible to the Customer for the performance of our Sub-processors' obligations.

9. 9. Helping the Customer

  • Data subject requests. Taking into account the nature of the processing, we will help the Customer respond to requests from data subjects to exercise their rights (such as access, correction, deletion, restriction, objection and portability). If we receive a request directly, we will pass it to the Customer without undue delay and will not respond ourselves unless the Customer tells us to or the law requires it.
  • Impact assessments and consultations. We will give the Customer reasonable help with data protection impact assessments and any prior consultation with a regulator, using the information available to us.
  • Security and breaches. We will help the Customer meet its own security and breach notification obligations.

10. 10. Personal Data Breaches

We will notify the Customer without undue delay, and in any case within 48 hours, after becoming aware of a Personal Data Breach. This allows the Customer to meet its own deadlines, such as notifying the regulator within 72 hours under the Thai PDPA and the GDPR where required.

Our notice will include, as far as we know at the time: what happened, the categories and approximate number of data subjects and records affected, the likely consequences, and the steps we have taken or propose to take. We will provide more information as it becomes available.

We will take reasonable steps to contain the breach and reduce its effects. Notifying the Customer of a breach is not an admission of fault.

11. 11. Deletion or return at the end

When the Main Agreement ends, the Customer may ask us to return the Personal Data in a common, machine-readable format, if it asks within 30 days. After that, we will delete the Personal Data within 30 days, and copies in backups will be removed within a further 30 days, unless the law requires us to keep it.

During the Main Agreement, the Customer can ask us to delete Personal Data at any time.

12. 12. Information and audits

We will make available to the Customer the information reasonably needed to show that we comply with this DPA and GDPR Article 28, such as answers to security questionnaires and our Sub-processors' certifications or reports where we can share them.

If this information is not enough, or a regulator requires it, the Customer (or an independent auditor bound by confidentiality) may carry out an audit, with at least 30 days' written notice, no more than once a year (unless there has been a Personal Data Breach), during normal business hours, and in a way that does not disrupt our business or put other customers' data at risk. The Customer bears its own audit costs.

13. 13. International transfers

We are based in Singapore, and our Sub-processors process Personal Data in the United States. We will transfer Personal Data outside the country where it was collected only in line with the Data Protection Laws:

  • EU/EEA: the Standard Contractual Clauses adopted by the European Commission (Decision 2021/914) are incorporated into this DPA by reference: Module 2 (controller to processor) where the Customer is a controller, and Module 3 (processor to processor) where the Customer is itself a processor. Clause 7 (docking clause) applies; for Clause 9, option 2 (general authorisation) applies with the notice period in section 8; the optional wording in Clause 11 does not apply; for Clauses 17 and 18, the law and courts of Ireland apply. Annexes I to III of the Clauses are completed by the Annexes to this DPA.
  • UK: the International Data Transfer Addendum to the EU Standard Contractual Clauses issued by the UK Information Commissioner applies, completed with the information in this DPA.
  • Switzerland: the Standard Contractual Clauses apply with the changes needed for the Swiss Federal Act on Data Protection.
  • Thailand: we will transfer Personal Data abroad only as permitted by sections 28 and 29 of the Thai PDPA and its subordinate rules, relying on the destination having adequate protection standards, appropriate safeguards (such as binding contracts with Sub-processors), or, where required, consent obtained by the Customer.
  • Singapore: we will comply with the transfer limitation obligation of the Singapore PDPA by making sure recipients are bound by legally enforceable obligations that give a comparable standard of protection.

If there is a conflict between this DPA and the Standard Contractual Clauses, the Standard Contractual Clauses prevail.

14. 14. Liability

Each party's liability under or in connection with this DPA is subject to the limitations and exclusions of liability in the Main Agreement, except where the Data Protection Laws do not allow this.

15. 15. Order of precedence and general terms

If there is a conflict, the following order applies: (1) the Standard Contractual Clauses, where they apply; (2) this DPA; (3) the Main Agreement.

This DPA lasts as long as we process Personal Data for the Customer. The governing law and jurisdiction of the Main Agreement apply to this DPA, except where the Standard Contractual Clauses or the Data Protection Laws require otherwise.

We may update this DPA to reflect changes in the law or in our service, as long as the update does not reduce the protection of Personal Data. We will give the Customer notice of material changes.

16. Annex 1: Description of the processing

ItemDescription
Controller (data exporter)The Customer: the school, tutoring centre or other organisation named in the Main Agreement
Processor (data importer)Anjuna Labs Pte. Ltd., 68 Circular Road, #02-01, Singapore 049422. Contact: privacy@mindhoops.com
Categories of data subjectsPupils (children aged about 5 to 14); the Customer's staff, such as teachers and administrators; parents and guardians of pupils
Pupil dataFirst name, age, school and school year, optional name pronunciation, tutor voice and language settings; the child's voice, streamed live during lessons and turned into a text transcript (audio is not recorded or stored); session transcripts (up to the last 600 lines per session) and AI-written session notes and summaries; images of the on-screen board and saved pen strokes; lesson progress, mastery per objective and time spent learning; goals and rewards; pseudonymous analytics and error data (internal ID and age only, no name and no lesson content)
Staff and parent dataName, email address, hashed password or Google sign-in profile (name, email, photo), language setting, notifications; IP address, browser and device details, and usage and error data
Sensitive dataNone is intended. The Customer should not give us sensitive data. Pupils are children, so the processing needs extra care, which is reflected in Annex 3.
FrequencyContinuous, whenever the service is used
Nature and purposeProviding the AI tutoring service: running live voice lessons, adapting lessons, saving work and progress, reporting progress to authorised adults, support, security and fixing errors
RetentionFor the term of the Main Agreement, then deleted as set out in section 11. OpenAI may keep API data for up to 30 days for abuse monitoring. Analytics events are kept no longer than 24 months
Sub-processorsAs listed in Annex 2

17. Annex 2: Sub-processors

The Customer authorises the following Sub-processors. The current list is always available on our processors page.

ProviderWhat forDataLocation
Convex (Convex, Inc.)Database, backend and sign-in: stores accounts, child profiles, lessons, progress, saved pages, session transcripts and notesAll account and learning data described in our Privacy PolicyUnited States
OpenAI (OpenAI, L.L.C.)The live voice tutor (speech recognition, reasoning and speech), images of the child's page, session notes for parents and voice previewsThe child's voice, first name, age, year group, lesson and progress, images of their handwritten work, and the transcript. Not used to train OpenAI's modelsUnited States
Vercel (Vercel Inc.)Hosting and delivering the websiteIP address, browser details and request logsUnited States (global edge network)
PostHog (PostHog, Inc.)Product analytics and error tracking, so we can see which features are used and fix problemsPseudonymous account IDs, pages and actions, device and browser details, approximate location from IP, parent email and name. Not what children say to the tutorUnited States
Google Analytics (Google LLC)Website analytics for our public and parent pages: how visitors find us and which pages they usePseudonymous cookie IDs, pages visited, referrer, device and browser details, approximate location from IP. Never used on children's pagesUnited States
Stripe (Stripe Payments Singapore Pte. Ltd. and Stripe, Inc.)Taking payments: saving cards, subscriptions, invoices and receiptsParent name, email address, card details, billing country, subscription and payment historySingapore and United States
Resend (Plus Five Five, Inc. (Resend))Sending account emails, such as password reset codesParent email address and the email contentUnited States
Google (Google LLC)Signing in with Google, only if a parent chooses itParent name, email address and profile pictureUnited States

18. Annex 3: Technical and organisational measures

  • Encryption in transit: all traffic between browsers, our servers and Sub-processors uses HTTPS/TLS. Live voice is streamed over encrypted WebRTC.
  • Encryption at rest: data is encrypted at rest by our hosting and database providers.
  • Least-privilege access: access to Personal Data is limited to the people and systems that need it for their role.
  • Separate environments: development and production environments are kept separate.
  • Pupil sign-in: pupils sign in with private links rather than passwords or email addresses. A link can be reset at any time, which signs the pupil out on every device.
  • Passwords: adult passwords are stored only in hashed form. Password reset codes expire after 15 minutes.
  • No audio storage: pupils' voices are streamed in real time and are not recorded or stored.
  • Data minimisation: each Sub-processor receives only the data it needs. Lesson content is never sent to our analytics provider, and pupils are identified there only by an internal ID and age.
  • Logging: we keep logs of system activity and errors to detect and investigate problems.
  • Sub-processor due diligence: we review each Sub-processor's security and data protection terms before using it, and use its data processing terms.
  • Deletion on request: Personal Data can be deleted on request, and deleting a pupil profile removes that pupil's learning data immediately.