Version 1.0 · in force
Privacy notice
Last updated: 16 November 2026 (added Haelyx Debrief; nothing else changed)
In force from 19 September 2026. We make no certification claims (for example ISO 27001 or SOC 2). Organisations using Haelyx for their staff can sign our data processing agreement.
What is true today (18 September 2026): Haelyx accounts are live. When you sign in with Whop we create an account record and hold the data described below, in our database in Frankfurt, Germany. DocSpeaks Web and DocSpeaks for Mac still run on your own device: your audio and transcripts never reach our servers. The Case Reflection Engine is on sale: the sections marked “signed-in app” describe what happens when you use it.
Who we are
Haelyx provides the Case Reflection Engine (a web app) and DocSpeaks for Mac (a dictation app). The controller for account data is Mohamed Shembesh, an individual based in Debrecen, Hungary. Postal address: Kardos Albert utca 28/b, 4028 Debrecen, Hajdú-Bihar, Hungary. Payments are taken and billed by Whop. Contact: mohamedshembesh0@gmail.com, or the Whop message channel that comes with your membership. EU representative under Article 27: none is required, because the controller is established in the EU (Hungary).
Never enter patient identifiers
Haelyx is built for de-identified reflections. Do not enter names, dates of birth, record or insurance numbers, addresses, phone numbers, email addresses or anything else that could identify a patient. The app checks your text before it is sent: direct identifiers block submission, and possible identifiers (for example a name with a title, an exact date or a ward and bed) must be removed or confirmed by you. The check reduces risk; it cannot catch everything, and you remain responsible for what you enter.
What we collect
- Account data: your Whop user ID and, if Whop provides it, your email address (stored encrypted). Your plan, its status and renewal date.
- Reflections (signed-in app): specialty, the three reflection questions, your answers and the extracted pattern, stored encrypted. Your case description is not stored unless you switch on “Keep case text” for that reflection.
- Text sent for processing: to generate questions and patterns, your case description and answers are sent to our server and to the language model provider listed on the subprocessors page. They are not stored by us at that step. Our requirement for this provider is no training on your text and minimal retention; we do not store this text at this step.
- Security records: a session record (we store only a keyed hash of your session token), rate-limit counters and an audit log of actions such as sign-in, export and deletion. These contain no reflection content, and IP addresses are stored only as keyed hashes.
- DocSpeaks for Mac: audio and transcripts stay on your Mac. We hold your plan status so we can offer you the download, and we log each download (time and a keyed hash of your IP address). The beta has no licence server and sends us nothing from your Mac.
- DocSpeaks Web: the browser dictation app at /docspeaks downloads a speech model to your browser and transcribes locally. Your microphone audio and transcripts never leave your device and never reach our servers.
- Haelyx Debrief: the debrief tool at /debrief is for simulated scenarios in teaching. It needs no account. Your scenario, tags, notes, the guide and the session log are kept in your browser’s local storage on your device and are built into a guide there; voice notes are transcribed inside the browser and the audio is never uploaded or kept. Nothing reaches our servers unless you press “Send to the model”. If you do, the scenario title, objectives, roles and tagged notes are sent as text to our server and to the language model provider listed on the subprocessors page, checked for identifiers first, and are not stored by us; we keep only a rate-limit counter tied to a keyed hash of your IP address. Notes about how learners performed are personal data about them even in a simulation, so use roles, not names: the tool asks for roles only and turns any initials you set into roles. Do not enter real patient data.
- Patterns saved by the earlier on-device engine: if you used the on-device version of the Case Reflection Engine, its patterns are still in your browser’s local storage on that device. Nothing from them reaches our servers unless you choose to import them into an account.
Why we use it (lawful bases)
- To provide the service you signed up for: performance of a contract (Article 6(1)(b) GDPR).
- To keep the service secure, prevent abuse and keep audit records: legitimate interests (Article 6(1)(f)).
- To meet tax, accounting and legal obligations: legal obligation (Article 6(1)(c)).
Health data: Haelyx is designed not to process health data about identifiable patients, which is why identifiers are blocked and case text is not kept by default. Our position under Article 9 is that reflections are designed to contain no identifiable patient data; we still treat all reflection content as confidential, encrypt it and never share it.
Where it is processed
Our database and server functions are set up in Frankfurt, Germany (EU). Some subprocessors are US companies; where personal data is transferred outside the EEA we rely on the safeguards named on the subprocessors page using Standard Contractual Clauses or the EU–US Data Privacy Framework where required, under each provider's data processing agreement.
How long we keep it
- Reflections: until you delete them or delete your account.
- Account data: until you delete your account. Deletion removes your account, sessions, plan records and reflections straight away.
- Audit log: metadata only, kept for 12 months.
- Rate-limit counters: 24 hours.
- Database backups: removed data may persist in backups for up to 30 days, the database provider's restore window.
- Billing records: held by Whop under its own terms.
Cookies
The signed-in app uses one strictly necessary cookie to keep you signed in. We do not use advertising or analytics cookies.
Your rights
You can access and export your data (Settings → Export data), delete your account (Settings → Delete account), and ask us to correct, restrict or stop processing it. Cancel billing in Whop. To exercise any right, message us through Whop. You can also complain to your data protection supervisory authority.
Security
Encryption in transit (TLS) and field-level encryption for reflection content and email, row-level isolation between accounts in the database, rate limits, and an append-only audit log. No system is perfectly secure; if a breach affects your data we will tell you and the relevant authority where the law requires it.
Changes
We will update this notice when the service changes, and show the date at the top.