Legal

Data Processing Agreement (DPA)

Contractual basis for the processing of personal data by MediSync on behalf of controllers under Art. 28 GDPR.

1. Subject

MediSync GmbH processes personal data within the MediSync product application (cloud, private cloud or on-premise) on behalf of the healthcare organisation using it. The organisation is the controller under Art. 4(7) GDPR. MediSync is the processor under Art. 28 GDPR. The basis is a data processing agreement concluded before go-live. This page summarises its main content. The signed contract version is binding.

For the public website MediSync is the controller itself. The privacy policy applies there, not this agreement.

2. Data processed and data subjects

  • Health data and other information from consultations (audio, transcripts, generated documents) under Art. 9 GDPR
  • Patient master data, where the organisation transmits it
  • User data of medical staff (name, e-mail, role, log data)
  • Information that patients submit themselves: details from online booking and answers in patient forms, including by voice
  • Appointment data that MediSync passes to the organisation's calendar provider on the organisation's instruction

Data subjects are patients and the organisation's staff.

3. Purpose and instructions

Processing serves only the delivery of the agreed services: transcription, structuring and document generation, and the handover to the organisation's practice or hospital information system. MediSync processes data only on the organisation's documented instructions.

No use for AI training: MediSync does not use the organisation's data to train, fine-tune or evaluate AI models. This commitment is part of the agreement and is passed on to all sub-processors.

The services also include online booking, sending patient forms, an AI summary of submitted forms as a draft for the treating person, filling in by voice without storing the recording, and calendar sync with the organisation's calendar. No master data is sent to the AI model for the summary; the other answers are pseudonymised first.

Calendar sync: when MediSync passes appointments to the organisation's calendar provider (Google, Microsoft) on instruction, that provider is not a sub-processor of MediSync but a processor of the organisation. Patient names go there only after the organisation confirms that it has an agreement under Art. 28 GDPR with the provider and has bound it to secrecy under Section 203(4) German Criminal Code.

4. MediSync's obligations

  • All staff are bound to confidentiality (Art. 28(3)(b) GDPR)
  • Technical and organisational measures under Art. 32 GDPR: encryption in transit and at rest, role and key separation, access control, logging
  • Support for the organisation with data subject rights (Art. 12 to 22 GDPR)
  • Support with data protection impact assessments (Art. 35 GDPR) and with personal data breaches (Art. 33 and 34 GDPR), notification to the organisation without undue delay
  • Deletion or return of all data at the end of the contract, at the organisation's choice
  • Audit and inspection rights of the organisation, including access to the security documentation

5. Sub-processors

For MediSync Cloud we use Amazon Web Services EMEA SARL as hosting provider: storage in the Frankfurt region (Germany), AI models through Amazon Bedrock in data centres in the EU, without the provider storing the inputs. E-mails to patients (booking confirmations, form links) are sent by Cloudflare, Inc. (Cloudflare Email Service); they contain name and e-mail address but no health data. For dedicated hosting or on-premise operation the providers named in the individual contract apply. We inform about planned changes in advance. The organisation may object. Contracts under Art. 28(4) GDPR are in place with all sub-processors.

6. Data location and third-country transfers

Storage takes place in data centres in Germany; AI models run in data centres in the EU. Patient data is not transferred to third countries. Exceptions: for sending e-mails, Cloudflare may also process e-mail addresses in the USA (EU-US Data Privacy Framework, with EU standard contractual clauses in addition); for calendar sync with patient names, the organisation's agreement with its calendar provider applies. Should one become necessary in an individual case, it happens only on the basis of an adequacy decision or EU standard contractual clauses (Art. 44 et seq. GDPR) and after prior information to the organisation.

7. Concluding the agreement

We provide the full contract text with the TOM annex and the sub-processor list before go-live. Requests to datenschutz@medisync.me. We review the organisation's own DPA templates and accept them where they are compatible with our technical and organisational framework.

8. Version

Version: November 2026. The signed contract version is binding.