Do not put health information in an enquiry or live chat
At the planning stage, tell us only the functional accommodation you want—for example, step-free access or a meal without a named ingredient. If more sensitive detail is genuinely needed, we will request it later through a secured task with a just-in-time notice and any consent required for your location.
Scope and relationship to the general policy
This Consumer Health Data Privacy Policy applies where a U.S. state law treats travel-related accessibility, dietary, medical, location or purchasing information as “consumer health data,” including Washington’s My Health My Data Act and applicable Connecticut requirements. It supplements the Privacy Policy; if this notice gives a more protective rule for covered health data, this notice controls.
It applies to health data we control through the ChinaHue website, invited account, traveller portal and direct support. A hospital, insurer, government authority or travel supplier acting independently applies its own notice and duties. We do not provide health care and this policy is not a HIPAA notice.
Health data categories, sources and purposes
| Category | Source | Why it may be collected |
|---|---|---|
| Accessibility and mobility | The traveller, parent/guardian or authorized booking contact. | Evaluate step-free routes, vehicle access, room features, walking distance, pacing or other requested accommodations. |
| Allergy and dietary information | The traveller or authorized contact. | Communicate a requested meal restriction to the selected restaurant, hotel, guide or food provider. |
| Limited medical or safety information | The traveller, guardian or—during an incident—an emergency contact or responder. | Assess a requested travel arrangement, prepare a proportionate safety plan or respond to an emergency. |
| Inferences about health | Only when unavoidable from the details you provide or the accommodation you request. | Understand and deliver the requested accommodation; never advertising, unrelated profiling or eligibility scoring. |
| Location or booking information linked to health needs | The itinerary, account or device information you choose to provide. | Coordinate the requested service at the relevant place and time. We do not use precise location to infer unrelated health characteristics. |
We do not collect reproductive or sexual-health information, biometric identifiers, genetic information, prescriptions, diagnoses or medical records as part of an ordinary booking. Do not upload them unless a specific secured request explains why the item is necessary.
How we use covered health data
We use covered health data only to provide the accommodation or travel service you request, communicate with you, protect traveller safety, secure the service, comply with law and maintain the minimum evidence needed for an incident or privacy request. We do not use it for advertising, data brokerage, unrelated research, automated eligibility decisions or to infer characteristics beyond the request.
Where consent is required, the secured collection step will identify the data, purpose and recipient categories before collection. Refusing optional health data will not prevent an unrelated service. If a detail is necessary to provide a requested accommodation safely, we will explain the practical consequence and look for a less intrusive alternative.
Who may receive covered health data
We may disclose only the portion needed to:
- Google Cloud Platform, which hosts the secured application and private storage as a processor;
- the specifically selected travel supplier, such as a hotel, vehicle operator, guide, restaurant or activity provider that must provide the requested accommodation;
- an emergency responder, insurer, professional adviser, regulator or authority, when reasonably necessary and lawful; or
- another person you direct us to contact.
We currently have no affiliate that receives consumer health data for its own purposes. We do not sell consumer health data. We do not disclose it for advertising or permit a processor to use it for an unrelated purpose. The secured task must identify the actual supplier recipient or supplier category before submission; we keep that disclosure with the trip record.
Consent, authorization and collection controls
A general acceptance of Account Terms, Booking Terms or the Privacy Policy is not consent to collect or share covered health data. Where applicable law requires consent, we request it separately and retain the notice version, stated purpose, recipient categories and time of the choice. A sale would require a separate signed authorization, but we do not sell this data.
For Washington or Connecticut residents, a traveller-data task that may collect covered health data must remain unavailable until the required state-specific consent, privacy assessment and processor controls are active. If the secured task does not show this notice and the required choice, do not submit health data; ask us for a non-sensitive planning alternative.
A parent or legal guardian must authorize covered health-data processing for a child when required. We do not invite a child to open an account or submit a traveller form directly.
Retention and deletion
A trip task will state its deletion date or objective deletion trigger before submission. The default target is deletion from the active traveller record no later than 30 days after the relevant trip ends or the requested arrangement is abandoned, unless a shorter period is practical. A narrowly separated incident, consent or legal record may be kept for the applicable claim or recordkeeping period without keeping the underlying passport or medical document.
When deletion is required, we send the request to processors and other entities holding data at our direction, subject only to a documented legal exception. Protected backups age out under the applicable backup cycle and are not restored for ordinary business use.
Your health-data rights
Subject to applicable law, you may request access to covered health data and a list of recipients; withdraw consent for future collection or sharing; request deletion, including from processors and recipients; correct related account information; and appeal a refusal. Email the Privacy Officer with the subject “Consumer health data request.” We will verify identity proportionately, respond within the required time and explain any lawful exception.
If we deny a request, reply with “Health data appeal.” We will provide a written decision and the regulator contact available for your location. Washington residents may also contact the Washington State Attorney General; Connecticut residents may contact the Connecticut Attorney General.
Changes and contact
The version and effective date appear above. We will not use previously collected health data for a materially new purpose without the notice and consent required by law. Questions, complaints, requests and appeals may be sent to: