Data Processing Agreement
Verwerkersovereenkomst pursuant to Article 28 of the General Data Protection Regulation (GDPR).
Effective date: 2026-03-20
Last updated: 2026-11-16 (optional export to Google Sheets)
Processor: Didenco
Contact: jan@didenco.be
1) Parties and Roles
- Controller — the user, healthcare professional, or practice that uses the Service and determines the purposes and means of processing patient data ("you").
- Processor — Didenco, which processes personal data on behalf of and on the documented instructions of the Controller.
Where several healthcare professionals use the Service as one practice, patient records are held at the level of that practice and the practice acts as Controller towards Didenco. The practice admin designated in the Service exercises the Controller's decisions on who may access the practice's patient records.
By accepting the Terms & Conditions and using the Service, the Controller instructs Didenco to process personal data as set out in this Agreement. This Agreement forms part of, and is subject to, those Terms.
2) Subject Matter, Nature and Purpose
- Subject matter: processing of personal data — including special-category medical data — that the Controller submits to, or generates through, the Service.
- Nature and purpose: to provide the administrative and AI-assisted physiotherapy workflow features of the Service, including transcription-based note generation, session records, medical report drafting, and secure storage.
- Duration: for the term of the Controller's use of the Service, and until data is deleted or returned in accordance with Section 9.
3) Categories of Data and Data Subjects
| Data subjects | Categories of personal data |
| Patients of the Controller |
Patient names, transcripts, conversation summaries, medical/session notes, medical reports, example medical reports, and uploaded files. This includes special-category health data (Art. 9 GDPR). Audio recordings are not stored in the database. |
| Controller's users and staff |
Name, email, role, authentication metadata, and practice membership and role. |
4) Obligations of the Processor
Didenco shall:
- Process personal data only on the Controller's documented instructions, including regarding international transfers, unless required to act by EU or Member State law (in which case Didenco will inform the Controller, unless legally prohibited).
- Ensure that persons authorized to process the data are bound by an appropriate duty of confidentiality.
- Implement the technical and organizational security measures described in Annex A (Art. 32 GDPR).
- Respect the conditions in Section 6 for engaging sub-processors.
- Assist the Controller, taking into account the nature of the processing, in responding to data subject requests (access, rectification, erasure, restriction, portability, objection).
- Assist the Controller in ensuring compliance with its obligations under Articles 32–36 GDPR (security, breach notification, data protection impact assessments, and prior consultation), taking into account the information available to Didenco.
- Notify the Controller without undue delay after becoming aware of a personal data breach, and provide the information needed for the Controller to meet its notification obligations.
- Make available to the Controller the information necessary to demonstrate compliance with Art. 28 GDPR, and allow for and contribute to audits, including inspections, conducted by the Controller or a mandated auditor, subject to reasonable notice and confidentiality.
- Immediately inform the Controller if, in its opinion, an instruction infringes the GDPR or other data protection law.
5) Obligations of the Controller
- Ensure a valid legal basis exists for the processing, including obtaining explicit patient consent where required (Art. 9(2)(a)).
- Provide instructions that comply with applicable data protection law.
- Ensure the accuracy and lawfulness of the personal data submitted to the Service.
- Decide which healthcare professionals belong to the practice, and approve only those who need access to its patient records for the care they provide.
- Keep the practice code confidential, replace it when it may have been shared beyond the practice, and remove users who leave the practice without delay.
- Inform patients, where required, that their record is accessible to the treating professionals of the practice, in line with applicable professional and patient-rights rules.
- Where its users export data to a third-party service of their own (see Section 6a), ensure a legal basis and an appropriate agreement with that service, and manage the retention, access and deletion of the exported copy.
6) Sub-processors
- The Controller grants general authorization for Didenco to engage sub-processors to deliver the Service. Didenco's current sub-processors are:
- Amazon Web Services (AWS) — hosting, database, storage, audit logging, and LLM processing (AWS Bedrock), in the EU regions
eu-north-1 and eu-central-1.
- Speechmatics (Cantab Research Ltd, United Kingdom) — audio transcription. Engaged under a signed Data Processing Agreement incorporating the EU Standard Contractual Clauses and the UK Addendum; audio is retained for no longer than 7 days and is not used for model training. Speechmatics' own sub-processors are listed at speechmatics.com/legal/privacy-policy.
- Google (Google Workspace / Gmail) — support-email delivery, under the Google Workspace Cloud Data Processing Addendum (which incorporates the EU Standard Contractual Clauses).
- Didenco imposes data protection obligations on each sub-processor equivalent to those in this Agreement, and remains fully liable for the performance of its sub-processors.
- Didenco will inform the Controller of any intended changes concerning the addition or replacement of sub-processors, giving the Controller the opportunity to object.
6a) Exports Directed by the Controller
- The optional Open in Google Sheets action is an instruction of the Controller, given per session by a user's click. The user's browser downloads the filled Excel intake form from the Service and uploads it directly to the user's own Google Drive (Google Drive API,
drive.file scope: access only to files the app creates), converted to a Google Sheet.
- The Google access token stays in the browser memory and is never sent to or stored on Didenco's servers. Didenco's servers send no data to Google for this feature.
- Google is a destination chosen by the Controller and is not a Didenco sub-processor for this export (Didenco's own use of Google for support email, listed in Section 6, is separate). The Controller is responsible for an appropriate agreement with Google (e.g. Google Workspace with Google's Cloud Data Processing Addendum) and a legal basis; a personal/consumer Google account is not suitable for patient health data. Data may be processed outside the EEA under Google's terms.
- Once exported, the copy is outside the Processor's scope: Didenco cannot see, delete or manage it, and Sections 7 and 9 do not apply to it. Its retention, access and deletion are the Controller's responsibility.
7) International Transfers
- Personal data is processed and stored within the EEA by default.
- Any transfer to a third country takes place only under an appropriate transfer mechanism (e.g., Standard Contractual Clauses) together with supplementary safeguards where necessary.
8) Security
Didenco maintains appropriate technical and organizational measures to protect personal data against unauthorized or unlawful processing and against accidental loss, destruction, or damage, as set out in Annex A and in the Privacy & Security Policy.
9) Return and Deletion of Data
- On termination of the Service, or on the Controller's request, Didenco will delete or return all personal data and delete existing copies, unless retention is required by law.
- Deletion follows the retention schedule in the Data Retention Policy (medical records typically 10 years, or as required by local law).
10) Liability and Governing Law
Liability under this Agreement is governed by the liability provisions of the Terms & Conditions. This Agreement is governed by applicable Belgian law and the GDPR.
Annex A — Technical and Organizational Measures
- Encryption of data at rest (AWS KMS) and in transit (TLS).
- Role-based access control and least-privilege access.
- Practice isolation: patient records are accessible only to the approved users of the practice they belong to. Joining a practice requires the practice code and the practice admin's approval; attempts to use a code are rate-limited.
- Unique accounts, strong authentication, and quarterly access reviews.
- Audit logging and monitoring of security-relevant events.
- Backups with restore testing and controlled key management.
- Documented data breach procedure with 72-hour supervisory-authority notification where required.
- Segregation of environments and restricted administrative access.
For full details, see the Privacy & Security Policy.
Contact
For questions about this Agreement or data processing: jan@didenco.be