← Quarter Notes

Data Processing Agreement (Art. 28 GDPR)

Version AVV-2026-11-2 · click version for Teaching, for teachers and music schools

How this agreement is concluded

You conclude this agreement in Teaching by clicking “Conclude data processing agreement”. The GDPR expressly permits the electronic form (Art. 28(9)). We record who concluded it, when, and in which version.

  • Private teacher: you conclude the agreement for yourself before you add or invite your first student.
  • Music school: the person with the owner role concludes it once for the school and confirms that they are authorised to do so. Teachers at the school do not conclude anything.
  • If your school would like to use its own template, write to us. The agreement we then sign together applies instead of this text.
  • Municipal music schools and other bodies that need a signed version can request this agreement as a PDF for signature.

§ 1 Parties and subject matter

1.1 The controller is the teacher or music school that concludes this agreement in Teaching (“you”). The processor is Andres & Günnewig GbR, Paul-Niessenstr. 58, 50969 Köln, Germany (“we”).

1.2 We process personal data on your behalf when you use Teaching and Practice for your lessons. The basis is the Terms of Use for Teaching and Practice (“main contract”). This agreement applies for as long as the main contract runs, and thereafter for as long as we still process data for you.

1.3 We do not process on your behalf:

  • your own account;
  • your students' own accounts in Practice, insofar as they use the app for themselves (their own practice notes, their own topics);
  • the leaderboard of the reading games in Practice (voluntary, with its own pseudonym);
  • the beta measurement and the security of the apps.

We are ourselves responsible for these. Whatever a student expressly shares with you in Practice, we also process for you from the moment it is shared.

§ 2 Nature, purpose and scope

Purpose: managing and running your lessons: students, appointments, lessons and notes, learning goals and planning, material and uploads, tools (e.g. audio, sheet music, chords), communication with students and parents, invoices.

Data subjects: your students (including minors), their parents or guardians, prospective students, and for music schools also teachers and staff.

Data: master data (name, email, phone, address, date of birth, age group), parents' contact details, parental confirmation; lesson data (lessons, notes, learning goals, planning, topics, requests, appointments); progress (e.g. results of reading games, practice data that was shared); files (material, students' uploads and recordings, photos from lessons, separated stems); billing (cards, contracts, invoices, payment notes); usage and connection data insofar as needed for operation.

Special categories (Art. 9): not intended. Do not enter health data in free text that you do not need for the lessons.

Location: in the EU/EEA (Stockholm) and in Switzerland (EU adequacy decision); individual service providers based in the USA as listed in Annex 2, on the basis of the EU Standard Contractual Clauses.

Own purposes: for our own purposes we only use what operation requires: error reports (without names, email and notes), protection against misuse and, during the beta, counting days of use and device type without content. We are responsible for this ourselves; details are in the privacy policy. We do not use data from your lessons for our own purposes.

§ 3 Instructions

3.1 We process the data only on your documented instructions. Your instructions are this agreement, the main contract and your settings and actions in the app (e.g. adding, sharing, deleting, sending an invoice). You can give us further instructions by email.

3.2 If EU or German law requires us to process differently, we tell you beforehand, insofar as this is permitted.

3.3 If we consider an instruction unlawful, we tell you immediately. Until you confirm or change it, we may suspend it.

§ 4 Our obligations

4.1 Confidentiality: anyone at our end with access to the data is bound to confidentiality.

4.2 Security: we take the technical and organisational measures set out in Annex 1 (Art. 32 GDPR). We may develop them further as long as the level of protection does not decrease.

4.3 Support: with the means of the app and, where necessary, by email, we help you with:

  • requests from data subjects (access, rectification, erasure, restriction, data portability, objection);
  • notifications to the supervisory authority;
  • a data protection impact assessment.

If we receive a request that concerns you, we forward it to you.

4.4 Breaches: if we become aware of a personal data breach affecting your data, we tell you without undue delay, at the latest within 48 hours. We tell you what we know: nature, data and persons affected, consequences and measures. This lets you meet your 72-hour deadline (Art. 33).

4.5 We are not required to appoint a data protection officer. The contact person for data protection is David Andres, mail@improve-musikunterricht.de.

§ 5 Sub-processors

5.1 You give us general authorisation to engage sub-processors. The current ones are listed in Annex 2 and publicly on the “Sub-processors” page.

5.2 We announce new or replaced sub-processors to you by email at least 30 days in advance. During this time you may object for an important data protection reason. If we cannot find a solution, you may terminate the main contract without notice. In an emergency, for example if a service fails or becomes insecure, we may switch immediately. We then inform you without delay, and your right to object applies from that notice.

5.3 We contractually bind every sub-processor to the same data protection obligations. For services outside the EU without an adequacy decision, we safeguard the transfer with the EU Standard Contractual Clauses (Art. 46), and for certified US companies also via the EU-U.S. Data Privacy Framework (Art. 45).

§ 6 Your rights and audits

6.1 On request, we demonstrate that we comply with this agreement: with Annex 1, written information and, where applicable, evidence from our service providers (certificates, audit reports).

6.2 An on-site audit is possible with at least 14 days' notice, during normal business hours and at most once a year, unless there is a specific reason.

§ 7 End of the agreement: returning and deleting data

7.1 When the main contract ends, at your request we hand over a copy of your data in a common format within 30 days and then delete it, unless a legal obligation to retain it applies. If you make no request, we delete the data 30 days after the contract ends.

7.2 The data disappears from our encrypted backups after 90 days at the latest.

7.3 Invoices: the retention obligation for your invoices (up to 10 years) is yours. Before your account is deleted, you confirm that you have saved them.

7.4 Data that your students keep themselves in Practice stays with them when the agreement with you ends. It belongs to their own account (§ 1.3).

§ 8 Liability and final provisions

8.1 Liability is governed by Art. 82 GDPR. Otherwise the liability provisions of the main contract apply.

8.2 In the event of conflict, this agreement takes precedence over the main contract where the protection of personal data is concerned.

8.3 If we change this agreement, we present the new version to you in Teaching for approval. Until you approve it, the old one applies.

8.4 German law applies. If a provision is invalid, the remainder stays valid.

Annex 1: Technical and organisational measures

1. Confidentiality: physical access to data centres

  • We do not run our own servers. According to our service providers (Annex 2), their data centres are certified.

1. Confidentiality: access to systems

  • Sign-in with email and password, at least 8 characters.
  • Passwords known from data leaks are rejected.
  • The email address is verified.
  • There is no self-registration. Accounts are only created by invitation; anonymous sign-in is off.
  • Signing out clears lesson data, drafts and the page cache stored on the device. This is intended for shared devices in music schools.

1. Confidentiality: access to data

  • Every table with personal data is protected by row rules in the database (Row Level Security). A teacher only sees their own students; a student only sees their own data and what is shared with them.
  • In addition, a mandatory rule separates the data of tenants (music schools) from one another.
  • An automatic check in the code prevents new tables without these rules.
  • Connections that the teacher has not yet confirmed do not release any content.
  • Files are kept in private storage: user files in our own storage at Infomaniak (Switzerland), each account in its own area; invoices in the EU. They are only retrieved via short-lived, signed addresses after sign-in and an authorization check. The access keys for the storage are kept on the server only.
  • Files uploaded by students are checked again on every retrieval and are not copied into third-party storage.
  • Server keys with full access are kept only on the server, never in the browser.

1. Confidentiality: separation

  • Separate tenants (see above).
  • Separate environments for development and operation. Development and tests run with test accounts and test data, not with customer data.

1. Confidentiality: pseudonymisation and data minimisation

  • Error reports (Sentry) are stripped of names, email, phone, IBAN and notes before they are sent. For minors, no identifier is sent, only the role.
  • Push notifications do not contain students' names.
  • The change log stores students' free text only as “(changed)”.
  • Anonymous feedback only shows teachers results from 5 responses onwards.

2. Integrity

  • All connections are encrypted (HTTPS/TLS).
  • Changes to master and billing data are logged (who, when, which columns).
  • Sent invoices are stored as PDF; downloading again returns exactly this file.
  • Input is validated on the server. The number of requests per account is limited (e.g. downloads, invitation codes).

3. Availability and resilience

  • The database is backed up daily (changes) and weekly in full.
  • Backups are encrypted (RSA-OAEP-256 and AES-256-GCM). We keep the private key offline.
  • Files are backed up weekly in encrypted form. Backups are kept for 90 days.
  • There are tested scripts for restoring the database and files.
  • Errors in operation are reported automatically and end up with us as a task.

4. Deletion and retention

  • Photos from lessons are deleted after 7 days.
  • Cached audio of the teacher is deleted after 12 months without retrieval.
  • Incoming enquiry emails are deleted after 6 months.
  • Processed appointment emails in the appointments mailbox are deleted 30 days after receipt.
  • Earlier versions of lesson notes are deleted after 90 days.
  • Identifiers in beta feedback are removed after 90 days, beta measurement data 90 days after the end of the beta.
  • If a student deletes their account, their practice data and uploads are deleted.
  • Deletion requests are fulfilled in full. Where automatic deletion does not yet cover everything, we delete manually following a defined procedure.

5. Regular review

  • The host's database advisories (security, performance) are reviewed and addressed regularly.
  • Every code change is reviewed by a second instance and by automated tests before release, including security checks of the row rules and function permissions.
  • This annex is updated in the event of material changes, at least once a year.

6. Organisation

  • The operator is a civil-law partnership (GbR) with two partners.
  • Only David Andres has administrative access to the production systems.
  • Anyone with access is bound to confidentiality.
  • Production data is only read in individual cases when needed for support or troubleshooting.
  • Development tools, including AI assistants, work with test data. They only get access to production data with express approval in the individual case.
  • We report data protection breaches to controllers within 48 hours at the latest (DPA § 4.4).

Annex 2: Sub-processors

Annex 2 to the data processing agreement. We announce every change by email 30 days in advance (DPA § 5.2).

Database, sign-in, file storage

Provider: Supabase Pte. Ltd., Singapore

Purpose: storing all app data, sign-in, storage for invoices

Data: all data under DPA § 2

Place of processing: EU (Stockholm)

Basis for third-country transfer: Standard Contractual Clauses in case of access from outside the EU

File storage

Provider: Infomaniak Network SA, Rue Eugène-Marziano 25, 1227 Les Acacias (Geneva), Switzerland

Purpose: material, uploads, recordings, stems

Data: files as described in DPA § 2

Place of processing: Switzerland

Basis for third-country transfer: EU adequacy decision (2000/518/EC, confirmed 2024)

App hosting

Provider: Vercel Inc., USA

Purpose: delivering the apps, server functions

Data: all data a page or request needs (in transit)

Place of processing: EU (server functions in Stockholm); delivered via Vercel's global network

Basis for third-country transfer: Standard Contractual Clauses

Email delivery

Provider: Plus Five Five, Inc. (Resend), USA

Purpose: invitations, sign-in emails, reminders, invoices to students and parents

Data: email address, name, content of the email, invoice PDF

Place of processing: USA (delivery and logs)

Basis for third-country transfer: EU-U.S. Data Privacy Framework, in addition Standard Contractual Clauses

Error reports

Provider: Functional Software Inc. (Sentry), USA

Purpose: detecting technical errors

Data: error type and location; for adults an account identifier; names, contact details and notes are removed beforehand

Place of processing: EU (organisation in the Europe region)

Basis for third-country transfer: EU-U.S. Data Privacy Framework, in addition Standard Contractual Clauses for support access

Separation into instrument stems (beta only, on request only)

Provider: Modal Labs, Inc., USA

Purpose: separating an uploaded recording into stems

Data: the audio file

Place of processing: USA

Basis for third-country transfer: Standard Contractual Clauses (in Modal’s data processing agreement)

Backups (encrypted, GitHub)

Provider: GitHub, Inc., USA

Purpose: encrypted backups of database and files, 90 days

Data: all data, encrypted only; the key is not held by GitHub

Place of processing: USA

Basis for third-country transfer: EU-U.S. Data Privacy Framework, in addition Standard Contractual Clauses

Backups (encrypted, Dropbox)

Provider: Dropbox International Unlimited Company, Ireland

Purpose: storing the daily mail backup, 8 weeks

Data: as above, encrypted only

Place of processing: EU/USA

Basis for third-country transfer: Standard Contractual Clauses

Mailboxes for appointments and the mail backup

Provider: RockingHoster Deutschland GmbH, An der Strusbek 21, 22926 Ahrensburg, Germany

Purpose: the mailbox from which Teaching retrieves appointments, and the mailbox that receives the daily mail backup

Data: appointments with students' names; the backup encrypted only

Place of processing: Germany (EU)

Not sub-processors, but recipients

You use these services yourself, or they only receive data when you call them up. We list them so that you know where data goes:

  • Dropbox and Google Drive: only if you connect your own account. The files are then in your account, and your contract with Dropbox or Google applies.
  • YouTube (Google Ireland Limited): when a page shows an embedded video or a thumbnail of one, the IP address and device information may be sent to YouTube, even before anyone starts the video. We use privacy-enhanced mode. To search for a video, we only send the title and artist to YouTube, no data about people.
  • Browser vendors' push services (Apple, Google, Mozilla): notifications are transmitted encrypted and do not contain students' names.
  • lrclib: only title and artist, no personal data.
Sub-processors as a separate page