Health data · read this before you send records

Privacy and data

You are being asked to describe a medical problem to a website. That deserves a specific answer rather than a policy generated from a template, so this page states what this build actually does — including the parts that are not finished yet.

What the intake assistant collects

Eight things a coordinator would ask on a first call: the treatment area and a free-text description of the problem, what you have already tried, your passport and country of residence, how soon you want to be seen, whether you are travelling alone, and a name plus one contact channel (email or WhatsApp). It also records the language you chose, the indicative cost and entry route the estimator produced, a lead score with the reasons for it, and the full transcript of the conversation.

It does not ask for your date of birth, your national ID number, imaging files, or any document. Records are requested later, by a named coordinator, on a channel you choose.

Lawful basis

Health information is special-category data. We rely on your explicit consent (GDPR Art. 6(1)(a) and Art. 9(2)(a)), collected as a separate yes/no answer at the end of the assistant, and on the contract we enter into with you to arrange the case. Consent is a hard stop in the software: if it is withheld, the case is tiered X, the score is forced to zero, and the record is marked do-not-contact and for deletion. That is not a policy statement — the intake engine refuses to produce a workable case without it.

Where it is stored on this build

This is the part most agencies would leave vague, so it is stated plainly:

  • The conversation and the case card are kept in your own browser (localStorage). Nothing is transmitted while you are answering.
  • Pressing Send to a coordinator, or submitting the contact form, attempts to POST the structured case to our server endpoint. That backend is not enabled yet. When it is absent, the page tells you so on screen rather than failing silently, and your case stays in this browser only.
  • The coordinator queue at /leads.html reads that same browser storage. It is a working copy for this device — the banner on that page says so — not a shared system of record.

Consequence for a patient today: do not rely on this test build to hold your case. Use the email or WhatsApp address on the page, or ask us to enable the secure intake endpoint, and we will confirm receipt in writing.

Who would see a submitted case

Coordinators working that case, and then only the parts a third party needs: the receiving hospital gets the clinical summary and imaging to decide suitability and price; the hotel and ground-transport providers, and the interpreters we engage, receive names and dates, never diagnoses; a consulate receives what the visa application form requires. We do not sell data, and we do not put health information into advertising audiences or analytics events.

International transfers

The case is cross-border by nature: arranging treatment in China means clinical records are read by clinicians there. If you consent, that transfer is the point of the service. Records travel as an encrypted attachment or a portal upload, and we ask your own hospital's records office for the export rather than scraping it out of you. All of this happens inside China: once you are back home we do not arrange care or act on your behalf abroad, and where you or your own doctor need a document that only a Chinese hospital or authority can issue, we make that single records request for you — charged per document, quoted before we start, and shared only with the issuer.

Retention and your rights

Ask and we delete: the case, the transcript and any documents, within the same working week, including from any coordinator's local copy. You can also ask for a copy of everything held on you, correct it, or withdraw consent for future contact. Enquiries about data go to the contact address on this page with the word data in the subject line.

Security limits we will not pretend away

  • There is no authentication on the coordinator queue in this build; anyone with the URL on a device that submitted a case can read that device's cases. Do not use it for live patient data until access control is switched on.
  • Health data on this build is not held under a data-processing agreement with a named processor, because it is not held on a server at all.
  • Session analytics are not installed. No third-party script loads on these pages except the two font files.

Who is responsible

The company behind this service is Aegis 意承咨询 — registered as 意承諮詢管理有限公司 (AEGIS CONSULTING MANAGEMENT LIMITED). It is the party that receives the case you submit here.

Still missing for a complete GDPR Art. 13 notice: the registration number, the registered address, the governing jurisdiction and a data-protection contact. They are not supplied on site-data.js → meta.legalName or legal.companyRegistration yet, so this page is a draft by design rather than a finished privacy statement.

Not medical advice

This assistant is not a doctor and does not diagnose. Suitability is decided by a licensed physician after reading your records.

If you are having symptoms that could be an emergency — chest pain, difficulty breathing, sudden weakness or severe bleeding — stop this and call your local emergency number now.

Policy as of 2026-10-12. This page changes when the intake backend goes live; the date at the top of the comparison table is refreshed with it.