ChoirZone Open the app →

Data Processing Agreement

The GDPR Article 28 terms on which ChoirZone processes personal data for your choir. They apply to every choir automatically — you do not have to ask for them.

Last updated: 22 November 2026

In plain words. Your choir decides what goes into ChoirZone and why; we only hold it and serve it back, on your instructions. We do not use it for anything of our own, we do not train AI on it, and when you leave you get it back or we delete it. The rest of this page is the same thing said the way the GDPR requires.

Need it signed on paper? Email support@choirzone.com with your choir’s legal name and address and we will send a countersigned copy, at no charge.

1. Parties and standing

These terms are between Trädtopp BV ("ChoirZone", "we"), a company established in Belgium, as processor, and the choir using ChoirZone ("the choir", "you") as controller. They form part of the Terms of Service and take effect when the choir begins using the service.

They cover only the personal data the choir puts into ChoirZone. For an individual’s own account data we are the controller, and the Privacy Policy governs that instead.

2. What we process, and why

  • Subject matter — providing ChoirZone: a rehearsal and administration tool for a choir and its singers.
  • Duration — for as long as the choir uses ChoirZone, plus the deletion period in section 9.
  • Nature and purpose — storing, organising, displaying and transmitting the choir’s content to its members; sending the notifications the choir chooses to send; producing the statistics the choir sees in its own console.
  • Categories of data subject — the choir’s members and administrators, and anyone who applies to the choir through a "Singers wanted" advertisement.
  • Types of personal data — name, email address, voice part, role in the choir; attendance, RSVPs and participation in events; practice activity and leaderboard standing where the choir enables it; score annotations; voice recordings a singer chooses to save; travel and car-sharing arrangements; fees recorded as owed or paid; and, for applicants, what they chose to send with their application.
  • Special categories — ChoirZone does not ask for and is not designed to hold special-category data. A voice recording is a recording of a person’s voice; we do not perform biometric identification on it and nor may anyone else through ChoirZone.

3. Our instructions

We process the choir’s personal data only on the choir’s documented instructions, which are: these terms, the Terms of Service, and whatever the choir does through the app and the management console. We will also process where EU or Member State law requires it, and in that case we will tell the choir first unless the law forbids it.

We will tell the choir if, in our opinion, an instruction infringes the GDPR.

We do not use the choir’s data for our own purposes. We do not sell it, do not advertise against it, and do not use it — or allow anyone else to use it — to train artificial intelligence models.

4. Confidentiality

Everyone we allow to access the choir’s data is bound to confidentiality and only has the access their work requires. In practice that is a very small number of people, and access to live systems is used to run the service, fix faults and answer support requests — not otherwise.

5. Security

We maintain appropriate technical and organisational measures under Article 32, including:

  • encryption of all traffic in transit (HTTPS);
  • passwords stored only as salted hashes;
  • uploaded scores and recordings held in private storage with no public address, reachable only through signed links that expire after an hour;
  • content scoped so that a choir’s material is reachable only by that choir’s members;
  • restricted, authenticated access to production systems;
  • managed hosting with the providers listed in section 6, and regular backups of the database.

The current measures are described in the Privacy Policy, which we keep up to date. We may change them, but not in a way that materially lowers security.

6. Sub-processors

The choir gives general authorisation for us to engage the sub-processors below. Each is bound by terms no less protective than these.

  • Render — application and database hosting (United States).
  • Cloudflare — storage for uploaded scores and recordings (R2), and video for live streams where a choir uses them.
  • Resend — sending transactional email.
  • Google Firebase Cloud Messaging — delivering push notifications.
  • Stripe — processing subscription payments.
  • Apple and Google — only where a user chooses to sign in with them.

We will give notice before adding or replacing a sub-processor that handles choir content. Email us to be put on the list for that notice. If the choir reasonably objects to a new sub-processor on data-protection grounds, it may tell us within 30 days, and if we cannot resolve it the choir may terminate and receive a pro-rata refund of any period paid for and not used.

7. International transfers

ChoirZone’s servers and database run in the United States (Oregon), and some sub-processors process data in the United States and elsewhere. Transfers out of the EEA are made under the European Commission’s Standard Contractual Clauses, together with the supplementary measures described in section 5. The GDPR applies to this processing in full, wherever the data physically sits.

8. Helping you meet your own duties

  • Data subject rights. Most requests the choir can satisfy itself from the console — members, their details and their records are all visible and editable there, and a member can export or delete their own account from the app. Where that is not enough, we will help, free of charge, taking the nature of the processing into account.
  • Requests that reach us. If a data subject contacts us directly about choir data, we will not answer for the choir; we will tell them to approach the choir, and tell the choir.
  • Breaches. We will notify the choir without undue delay after becoming aware of a personal data breach affecting its data, with what we know and what we are doing. Where we are the controller, we will notify the supervisory authority within 72 hours as required.
  • Impact assessments. We will give the choir the information it reasonably needs for a DPIA or a prior consultation.

9. Deletion and return

The choir can export and delete its own content at any time while the service is running. When the choir stops using ChoirZone, we will, at the choir’s choice, return its data or delete it. If the choir tells us nothing, we delete it within 90 days of the account closing, other than what we must keep by law — payment records for accounting, for example — which stay only as long as the law requires.

Backups age out on their own cycle; data in a backup is not restored into live use after deletion.

10. Audit

We will make available the information needed to show we are meeting Article 28, and will allow and contribute to an audit by the choir or an auditor it appoints. Audits are on reasonable notice, no more than once a year unless a breach or a regulator’s instruction makes another necessary, and conducted so as not to disrupt the service or expose another choir’s data. In the first instance we will answer a written questionnaire, which for a service of this size is normally enough.

11. Liability and law

These terms are governed by Belgian law, and the liability provisions of the Terms of Service apply to them. Nothing here limits a data subject’s rights or the liability either party has directly under the GDPR.

Contact

Questions about these terms, or a request for a signed copy: support@choirzone.com.

See also: Privacy Policy · How ChoirZone handles sheet music · Terms of Service