Data Processing Agreement

Updated 13 November 2026Version 1What changed

In short

  • When you enter your members' data, you decide (controller) and we process it for you (processor).
  • This agreement is part of the Terms of Service. It applies automatically, with nothing to sign.
  • We use only the listed services, and tell you 30 days before adding one.
  • If something goes wrong, we tell you within 48 hours of knowing.

This summary helps you read. The full text below is what applies.

This Data Processing Agreement ("DPA") is part of the Terms of Service between the studio using MoveMembers (the "Customer") and NOPA STUDIO ("we"). It applies whenever we process personal data on the Customer's behalf. It is written to meet Article 28 of the EU General Data Protection Regulation (GDPR), Thailand's Personal Data Protection Act and Singapore's Personal Data Protection Act. If you need a signed copy, write to hello@movemembers.com.

1. Roles

The Customer is the controller of the personal data it enters into the Service about its members, leads, customers and their guardians. We are its processor. We process that data only to provide the Service, on the Customer's documented instructions. The Terms, this DPA and the Customer's use of the Service's features are those instructions. If we think an instruction breaks the law, we tell the Customer.

2. What we process

  • People concerned: the Customer's members, leads, customers, guardians of minors, and its staff.
  • Data: identity and contact details, memberships and bookings, attendance, payments and receipts, messages, notes, documents and signed waivers, and, where the Customer chooses to record them, health-related data such as body measurements or medical forms.
  • Purpose: running the Customer's bookings, memberships, payments, check-in and communication.
  • Duration: for as long as the Customer's account exists, then until deletion under section 9.

3. Our team

Only people who need it to run or support the Service can access Customer data, and they are bound by confidentiality. Support staff open a studio's data only to answer that studio's request or to fix a fault.

4. Security

We apply the measures described in the annex below and on our Security page, and we keep them up to date.

5. Sub-processors

The Customer authorises the sub-processors listed on our Sub-processors page. We bind each of them to data protection terms at least as protective as this DPA. We email the Customer at least 30 days before adding or replacing one. The Customer may object for a reasonable data protection reason. If we cannot address it, the Customer may end the affected service and get a refund for the unused prepaid period.

6. Transfers

Customer data is hosted in Europe. Where a sub-processor processes it outside the European Economic Area, the transfer relies on the European Commission's standard contractual clauses or another lawful safeguard.

7. Helping the Customer

We help the Customer, through the Service's features and on request, to answer people who use their rights, to carry out impact assessments, and to meet its security obligations. If a member writes to us directly, we pass the request to the Customer within 5 working days and do not answer it ourselves unless the Customer asks.

8. Personal data breaches

If we become aware of a breach affecting Customer data, we tell the Customer without undue delay and within 48 hours. We give what we know: what happened, the data and people concerned, the likely consequences and what we are doing. We update the Customer as we learn more.

9. End of the service

The Customer can export its data at any time, and the deletion link sent to the owner also returns the full export. When the owner confirms the deletion in Settings, the data is deleted from our systems straight away. If the Customer asks us by email instead, we delete it within 30 days. Backups are overwritten on their normal cycle. We keep only what the law requires, such as invoices.

10. Audits

We make available the information needed to show we meet this DPA: this document, our Security page and answers to reasonable written questions. Where the law requires more, the Customer may ask for an audit with 30 days' notice, once a year, at its own cost, by an auditor bound by confidentiality.

11. Liability and order of documents

Liability under this DPA follows the Terms of Service. If this DPA and the Terms conflict on personal data, this DPA applies.

12. Annex: security measures

  • Each studio can reach only its own records, checked by the server on every request.
  • Passwords stored as one-way scrypt hashes. Sign-in attempts limited. Optional two-step sign-in for owners.
  • Sessions signed by the server, HTTPS-only cookies, HTTPS everywhere.
  • Roles and rights checked on the server. Optional staff PIN for sensitive actions.
  • Card numbers never stored: they are typed on Stripe's pages.
  • Database backups every 4 hours, checked and copied away from the server.
  • Keys and secrets kept outside the code. App secrets hashed, webhook secrets encrypted.
  • The AI model receives members as anonymous references; email addresses, phone numbers and member names are removed by the server before a request leaves.

A question about this page? Write to hello@movemembers.com. A person answers, in your language.

Write to us
Version history
  1. 13 November 2026first version.

This document is written in English. If a translation and the English version differ, the English version applies.