Skip to content

Data Processing Agreement

Version 1.3 · in force since December 6, 2026 · forms part of the Service Terms for Clients

Translation. In case of doubt, the Spanish version prevails.

When an ensemble manages the data of its members in Melodistic, the ensemble decides why and how, and Melodistic processes the data on its behalf. This agreement complies with Article 28 of the General Data Protection Regulation (GDPR).

1. Parties and standard clauses

  • Controller: the Client that contracts Melodistic (Annex I).
  • Processor: Villadiego OÜ (Annex I).

The parties adopt the standard contractual clauses between controllers and processors of Commission Implementing Decision (EU) 2021/915 of 4 June 2021 (hereinafter, ‘the Clauses’), which are incorporated into this agreement by reference. Annexes I to IV of the Clauses are Annexes I to IV of this document. For Clause 7.7, the parties choose option 2 (general written authorisation), with 30 days' prior notice. If anything in this agreement contradicts the Clauses, the Clauses prevail.

What follows summarises how they apply in Melodistic.

2. Instructions

Melodistic processes the data only on the Client's documented instructions. The Client's instructions are these terms, the configuration of its Ensemble, what its Users with permission to do so do in the app and the features the Client switches on, such as Cecilia, the connection with other apps or the API keys. If Melodistic believes that an instruction infringes the law, it says so immediately and does not carry it out.

3. Confidentiality and security

Only those people at Melodistic for whom it is strictly necessary in order to provide the service or assist the Client have access to the data, and they are bound to secrecy. Melodistic applies the measures in Annex III and may improve them, but never reduce them.

4. Sub-processors

The Client authorises Melodistic to use the sub-processors in Annex IV. Melodistic will notify the Main Admin by email of any addition or change at least 30 days in advance. If the Client objects on reasonable data protection grounds and no solution is found, it may cancel with a refund of the part not used. Melodistic imposes on each sub-processor, in substance, the same obligations as this agreement and is responsible for their compliance.

A sub-processor that is only used in a feature that the Client activates separately (for example, Cecilia's provider) is authorised by the Client when activating it, and the authorisation is only valid for its Ensemble.

5. Transfers outside the European Economic Area

Melodistic keeps the data in the European Union. If a sub-processor processes it outside, there must be a safeguard under Chapter V of the GDPR: an adequacy decision (such as the EU-US Data Privacy Framework) or the standard contractual clauses for transfers. Annex IV states which is used in each case.

6. Data subjects' rights

If a member asks Melodistic to access, rectify or erase their data in an Ensemble, Melodistic passes the request to the Client without replying on the substance. The Client can deal with most requests from the app (editing or removing a member, exporting their data) and Melodistic assists it with the rest.

7. Security breaches

Melodistic notifies the Client without undue delay and, at the latest, within 48 hours of becoming aware of a breach affecting its data. The notification includes what happened, the data and persons affected, the likely consequences and the measures taken, and is supplemented as more becomes known. Notifying the authority and the data subjects is the Client's responsibility, with Melodistic's assistance.

8. Assistance to the Client

Melodistic gives the Client the information it needs to carry out a data protection impact assessment or a prior consultation with the authority, where applicable.

9. End of the service

When the contract ends, the Client may ask in writing for a copy of its data. Melodistic erases the data 12 months after the end if there has been no activity in the Ensemble in that time, or earlier if the Client asks in writing, including the copies held by sub-processors, unless the law requires it to be kept. What remains in periodic backups disappears when those backups are no longer retained. If the Client asks in writing, Melodistic certifies the erasure.

10. Audit

Melodistic makes available to the Client the information necessary to demonstrate that it complies with this agreement and replies to its questionnaires. The Client may request an audit, once a year except in the event of a breach or indications of non-compliance, with 30 days' notice and without access to the data of other Clients. Each party bears its own cost, unless the audit uncovers a serious breach by Melodistic.

11. Obligations of the Client

As controller, the Client undertakes to:

  1. Have a legal basis for each item of data it records (normally, the person's relationship with the Ensemble) and inform its members that it uses Melodistic.
  2. Collect and keep the authorisation of the mother, father or guardian before registering a minor under 14.
  3. Not ask for the national identity document (DNI) unless it needs it for a specific purpose (insurance, federation, grant), and not require it from minors under 14.
  4. Not record health data or other special categories of data, nor create reasons for absence of its own that reveal them. The only exception is the reason ‘Illness’, which only the musician may choose, with their explicit consent. Only people with attendance permission can see it, and after 12 months it becomes ‘Personal reason’. Free fields must not contain diagnoses or illnesses.
  5. Activate location check-in only if it needs it, and inform its musicians.
  6. Keep Users and permissions up to date, and withdraw access from anyone who leaves the Ensemble.
  7. Before switching on the connection with other apps or creating API keys, assess whether it suits it and inform its members; and, if it gives keys to a third party that processes its data, have with it the contract the law requires.

12. Liability

Each party is liable to data subjects and to the authorities in accordance with Article 82 of the GDPR. As between the parties, the limitation of liability in the Service Terms applies, except where the law does not allow liability to be limited.

13. Connections requested by the Client: MCP and API

The Client may switch on in its Ensemble the connection with artificial intelligence assistants (MCP) and create API keys. Doing so is a documented instruction of the Client (section 2):

  • With the MCP, the Client instructs Melodistic to deliver to the app that each authorised User connects the data that User can see, except the excluded data: health, treasury, contact details and identity documents, the location of check-ins and the names of minors.
  • With the API, to deliver it to the software that uses the keys the Client creates, with the scope the Client gives them.

Those apps and that software are not sub-processors of Melodistic: the Client or its Users choose them, and Melodistic has no contract with them. What they do with the data, including processing it outside the European Economic Area, falls outside this agreement and is the Client's responsibility.

For its part, Melodistic applies the exclusions on the server, logs each use without its content for 90 days and allows the Client to switch off the connection, disconnect everyone and revoke keys, with effect from the next call.

Annex I · List of parties

RoleWhoContact
ControllerThe Client, with the details of its billing account in MelodisticThe Main Admin of each Ensemble
ProcessorVilladiego OÜ, registration number 16440563, Sepapaja tn 6, 15551 Tallinn, Harju maakond, Estoniasoporte@melodistic.com

Signing this annex is the acceptance of the Service Terms, recorded with date and version.

Annex II · Description of the processing

Data subjects: members of the Ensemble (musicians, conductors, admins, staff), applicants, deputising musicians, mothers, fathers or guardians of minor members, and third parties who appear in the treasury (suppliers, organisations that book performances).

Purpose: managing the Ensemble and its musicians: calling and organising events, monitoring attendance, distributing sheet music, seating the musicians, communicating with them and keeping the Ensemble's accounts and equipment; and, with the data from the conversations with Cecilia anonymised, reviewing how the chat works in order to correct and improve it.

Nature: hosting, recording, consultation, organisation, communication to the Ensemble's Users according to their permissions, sending of notifications, delivery to the apps and software that the Client or its Users connect (section 13) and erasure.

Category of dataExamplesHow long it is kept
Identification and contactName, surnames, email, telephone, photo, date of birthWhile the person is in the Ensemble or the Client decides
Identity documentDNI or other document, only if the Client requests itThe same; not required below the age of 14 if the date of birth is on record
Musical dataInstrument, voice, section, seat, sheet music assignedFor the duration of the contract
Attendance and forecastReplies to invitations, attendance, absences with their reason or textFor the duration of the contract; the reason ‘Illness’, 12 months
Location check-inCoordinates at the moment of checking in30 days from the event; afterwards only the check-in time remains
Treasury and equipmentMembership subscriptions, payments and their receipts, uniforms and instruments on loanFor the duration of the contract
CommunicationsNotifications, messages, surveys and their repliesFor the duration of the contract
Conversations with CeciliaWhat Users write and the replies, only if the Client activates CeciliaThe period the Client chooses: 30, 90 or 365 days from the last message
Acceptance of the rulesDate, version and PNG image of the signature, which only the person who configures the rules and its author can seeFor the duration of the contract
Technical dataDevice identifier for notifications, access and sending logs, log of MCP and API uses (who, when and which function, without the content), Ensemble activityWhile the person uses the app; access and sending logs, 12 months; log of uses, 90 days; Ensemble activity, for the duration of the contract

Special categories of data: Melodistic does not ask for any, and the Client undertakes not to enter them (section 11). The only exception is the reason for absence ‘Illness’, a health data item. Only the musician chooses it, with their explicit consent as the legal basis; people with attendance permission can see it, after 12 months it becomes ‘Personal reason’ and it never goes out through the MCP.

Duration: that of the service contract, plus the erasure periods in section 9.

Annex III · Technical and organisational measures

  • Encrypted connections with HTTPS on the website and the app.
  • Passwords stored using hash functions, never in plain text.
  • Separation of the data of each Ensemble: queries are filtered by the Ensemble and the User's permissions.
  • Role-based permissions within each Ensemble, set by the Main Admin.
  • Sheet music, profile photos and documents in private storage, served through signed links that expire. Band logos, event covers and uniform photos may be in public storage, accessible with their link.
  • Private calendar links for each person and Ensemble, which do not give access to the account.
  • MCP connection with each User's sign-in. It is revoked when the password is changed or reset, when the User disconnects it and when the Client switches it off or disconnects everyone, with effect from the next call. Excluded data is filtered on the server.
  • API keys that are shown only once, stored as a hash and can be revoked at any time; two-factor authentication to give read access to the treasury.
  • Per-minute usage limits on the MCP and the API.
  • Periodic backups of the database, kept in the EU.
  • Logging of access and sending for 12 months, and of MCP and API uses, without their content, for 90 days.
  • Access by Melodistic staff limited to those who need it, with individual accounts. When staff enter as a User to provide support, this is logged. The reading of a conversation with Cecilia by Melodistic staff, and each anonymised export, are also logged.
  • Automatic deletion of check-in coordinates 30 days after the event.
  • Testing in pre-production before each change to production.
  • Commitment to notify breaches within 48 hours.

Annex IV · Sub-processors

Sub-processorPurposeWhereSafeguard
Hosting providerHosting of the website, the app and the database; emailEU—
Google Cloud EMEA Ltd (Ireland)Storage of sheet music, photos and documents; generation of exportsEU—
Google Ireland Ltd · Firebase Cloud MessagingSending of phone notificationsEU and USEU-US Data Privacy Framework or standard clauses
Apple Distribution International Ltd (Ireland)Delivery of notifications on iPhone (APNs)EU and USEU-US Data Privacy Framework or standard clauses
Artificial intelligence providersAssisted score upload and assisted rules import, on documents, without the profiles or the contact details of membersDepending on the providerThose of Chapter V of the GDPR if they leave the EU
Google Cloud EMEA Ltd (Ireland)Only if the Client activates Cecilia: see the Cecilia termsEU—
Amazon (Kindle)Only if a musician asks to send sheet music to their Kindle: their Kindle email address, the title and the fileUSEU-US Data Privacy Framework or standard clauses
Cloudflare, Inc.Protection of the registration and sign-up forms against automated submissions: IP addressEU and USEU-US Data Privacy Framework or standard clauses
Google Fonts, jsDelivr, cdnjs and unpkgDelivery of fonts and libraries to the browser: IP addressEU and outside the EUThose of Chapter V of the GDPR
OpenStreetMap (Nominatim)Placing on the map the address of an event and the area for car sharingUnited KingdomAdequacy decision

The apps and software that the Client or its Users connect through the MCP or the API are not sub-processors (section 13).

Country and language