SUB-PROCESSORS

Sub-processors

Last updated: 14 May 2026

This page lists the third-party service providers ("Sub-processors") that Medq engages to process personal data on behalf of its customers, in accordance with Article 28 GDPR and the Data Processing Agreement entered into between Medq and each customer.

Customers are notified of intended changes to this list at least 30 days before they take effect.

For questions or to object to a Sub-processor on reasonable data protection grounds, contact contact@medq.be.

Current sub-processors

Hetzner Online GmbH

RoleCloud hosting and infrastructure (production servers, storage, networking)
Country of processingGermany — Nuremberg (EEA)
Transfer mechanism (if outside EEA)N/A — processing within the EEA
Personal data categoriesAll Customer Data stored on Medq infrastructure

Hetzner Online GmbH

RoleOff-server backup storage (separate from production server, same provider, same EEA region)
Country of processingGermany — Nuremberg (EEA)
Transfer mechanism (if outside EEA)N/A — processing within the EEA
Personal data categoriesEncrypted backups of all Customer Data

Resend, Inc.

RoleTransactional email delivery (appointment confirmations, reminders, system notifications)
Country of processingIreland (EEA) — Resend EU region
Transfer mechanism (if outside EEA)N/A — processing remains within the EEA. Resend's DPA is in force
Personal data categoriesRecipient email address, message subject and content, delivery metadata

BudgetSMS.net

RoleSMS reminder delivery (where enabled by the controller)
Country of processingNetherlands (EEA)
Transfer mechanism (if outside EEA)N/A — processing within the EEA
Personal data categoriesRecipient phone number, message content, delivery metadata

Functional Software, Inc. (Sentry)

RoleApplication error and performance monitoring
Country of processingEuropean Union — Sentry EU data region
Transfer mechanism (if outside EEA)N/A — processing within the EEA. Sentry's DPA is in force
Personal data categoriesDiagnostic data including request metadata, stack traces, limited user identifiers (no patient health data is intentionally included)

Mollie B.V.

RoleSubscription billing and payment processing
Country of processingNetherlands (EEA)
Transfer mechanism (if outside EEA)N/A — processing within the EEA
Personal data categoriesBilling contact details, payment metadata; full card numbers are not stored on Medq systems

Categories of data shared

Different Sub-processors receive different categories of data depending on their role. We apply the principle of data minimisation: each Sub-processor receives only the data necessary for its function. The payment processor does not receive patient data, the email provider does not receive billing data.

How transfers are protected

All Sub-processors listed above process data within the European Economic Area at the date of this page. If a future Sub-processor introduces a transfer outside the EEA, we will rely on Standard Contractual Clauses adopted by the European Commission, supplemented by additional technical and organisational measures where required following a Transfer Impact Assessment, or on EU Commission adequacy decisions where they apply. A summary of any Transfer Impact Assessment is available to controllers on request.

How to object

Customers (as controllers) may object to a Sub-processor on reasonable data protection grounds within 30 days of notification of an addition. If Medq cannot accommodate the objection, the customer may terminate the affected portion of the subscription without penalty, with pro-rata refund of pre-paid fees for the unused portion of the term.

Change log

DateChangeAffected Sub-processor
2026-05-14Initial publication(all)