Version 1.0 · for organisations
Data processing agreement
Last updated: 19 September 2026
This agreement (the "DPA") applies when a hospital, clinic, university or other organisation (the "Customer") gives its staff access to Haelyx and determines why their data is processed. In that case the Customer is the controller and Haelyx is the processor under Article 28 of the GDPR. It forms part of the agreement between the Customer and Haelyx. To receive a countersigned copy, message us through Whop or reply to the email you received from us.
1. Parties and roles
Processor: Mohamed Shembesh trading as Haelyx, Kardos Albert utca 28/b, 4028 Debrecen, Hungary. Controller: the Customer named in the signature block. Each party complies with its own obligations under the GDPR and applicable national law.
2. Subject matter, duration, nature and purpose
- Subject matter: providing the Case Reflection Engine and DocSpeaks to the Customer's authorised users.
- Duration: for as long as the Customer's subscription runs, plus the deletion period in section 9.
- Nature and purpose: hosting user accounts; generating reflection questions and extracted patterns; storing, searching and exporting reflections for the users' own professional learning and teaching.
3. Types of personal data and data subjects
- Data subjects: the Customer's clinicians, trainees and administrators who use Haelyx.
- Personal data: user identifiers, email address, specialty, plan status, reflections and extracted patterns, security and audit logs.
- Patient data: Haelyx is designed to process de-identified reflections only. The Customer instructs its users not to enter patient identifiers; the service blocks direct identifiers before submission. Haelyx does not intend to process special category data about identifiable patients.
4. Processor obligations
Haelyx will: (a) process personal data only on the Customer's documented instructions, including this DPA and the users' use of the service; (b) ensure that anyone authorised to process the data is bound by confidentiality; (c) apply the security measures in section 6; (d) assist the Customer, taking into account the nature of the processing, in responding to data subject requests and in meeting its obligations under Articles 32 to 36 GDPR; (e) make available the information needed to demonstrate compliance with Article 28 and allow for audits as set out in section 8; and (f) tell the Customer without delay if it believes an instruction infringes data protection law.
5. Subprocessors
The Customer gives general authorisation for the subprocessors listed on the subprocessors page (Whop, Vercel, Neon and Mistral AI). Haelyx imposes data protection obligations on each subprocessor that are no less protective than this DPA, remains responsible for their performance, and will give at least 30 days' notice of any new subprocessor, during which the Customer may object on reasonable data protection grounds and, if the objection cannot be resolved, terminate the affected service.
6. Security measures
- Encryption of reflections and email addresses at rest; TLS encryption in transit.
- Database and server functions located in Frankfurt, Germany (EU).
- Case descriptions are not stored unless the user switches on "Keep case text" for that reflection.
- Automatic checks that block direct patient identifiers before text is sent.
- Session tokens and IP addresses stored only as keyed hashes; audit log of sign-in, export and deletion.
- Least-privilege access to production systems; access limited to the founder.
- Users can export and delete their data at any time; deletion removes account, sessions and reflections immediately.
7. Personal data breaches
Haelyx will notify the Customer without undue delay, and in any case within 48 hours of becoming aware of a personal data breach affecting the Customer's data, with the information the Customer needs to meet its own notification obligations.
8. Audits
Haelyx will answer the Customer's reasonable written security questionnaires once a year at no charge. Further audits or inspections, by the Customer or an auditor it appoints and who is bound by confidentiality, can take place on 30 days' written notice, during business hours and at the Customer's cost.
9. International transfers, return and deletion
Personal data is hosted in the EU. Where a subprocessor transfers data outside the EEA, the transfer relies on Standard Contractual Clauses or the EU–US Data Privacy Framework. At the end of the service Haelyx will, at the Customer's choice, return the data in a standard export format or delete it within 30 days, except where EU or member state law requires it to be kept. Backups are overwritten within the database provider's restore window (up to 30 days).
10. General
If this DPA conflicts with other terms between the parties, this DPA prevails for the processing of personal data. It is governed by Hungarian law.
Signatures
Customer: ______________________ Name and role: ______________________ Date: __________
Haelyx (Mohamed Shembesh): ______________________ Date: __________