Medical & Health Disclaimer

Last reviewed: July 15, 2026

PeachBot health, telemedicine, and clinical workflow features are intended to support communication, data organization, monitoring workflows, and professional review. They do not replace licensed healthcare professionals, emergency services, clinical judgment, patient examination, or jurisdiction-specific medical regulation.

1. No Medical Advice or Doctor-Patient Relationship

PeachBot does not provide medical advice, diagnosis, treatment, prescription, therapy, emergency triage, or clinical decision-making. Use of the website or software does not create a doctor-patient relationship with PeachBot, its operators, developers, authors, contributors, partners, or affiliates.

Any health-related output must be reviewed by a qualified and licensed healthcare professional who is responsible for the patient, the clinical context, the jurisdiction, professional duties, consent, documentation, and follow-up.

2. Emergency and Critical Care Exclusion

PeachBot is not designed for medical emergencies, urgent triage, critical care alarms, ambulance dispatch, life-support control, or public emergency response. If symptoms are urgent, severe, worsening, or life-threatening, users must contact local emergency services or a qualified healthcare provider immediately.

3. Telemedicine Use

Telemedicine features, where provided, are communication and workflow tools. They must be used only by appropriately qualified professionals and organizations that satisfy local licensing, consent, record-keeping, privacy, cross-border practice, prescribing, patient identity, and standard-of-care requirements.

• India: Users should consider Indian medical ethics, telemedicine guidance, professional registration, the DPDP Act and Rules, ABDM-related obligations when integrated, and CDSCO requirements if a regulated medical-device purpose exists.
• Singapore: Users should consider professional duties under Singapore Medical Council guidance, healthcare licensing requirements, the PDPA, and PDPC AI/data guidance.
• UAE: Users should consider UAE health authority rules, professional licensing, health data requirements, Federal Decree-Law No. 45 of 2021 on personal data protection, and applicable free-zone rules.
• EU/EEA: Users should consider GDPR, the EU AI Act, MDR/IVDR, professional licensing, telemedicine laws, and member-state health rules.

4. Medical Device and SaMD Boundary

A software feature may become regulated as a medical device or software as a medical device when its intended purpose includes diagnosis, prevention, monitoring, prediction, prognosis, treatment, alleviation of disease, clinical decision-making, or similar medical use. PeachBot features must not be used for those purposes unless the exact product version and deployment have been assessed and authorized where required.

Relevant frameworks may include India CDSCO rules, EU MDR/IVDR, Singapore Health Sciences Authority requirements, UAE health authority rules, ISO 13485, ISO 14971, IEC 62304, IEC 62366-1, IEC 82304-1, clinical evaluation, cybersecurity controls, traceability, validation, and post-market monitoring.

5. AI Limits, Bias and Validation

AI outputs may be incomplete, biased, stale, incorrectly interpreted, or unsuitable for a particular patient, device, population, environment, language, or workflow. Deploying organizations must perform local validation, clinical risk management, dataset review, model monitoring, human oversight, audit logging, incident response, and change control.

6. User Responsibility

Users are responsible for ensuring lawful use, consent, privacy notices, professional supervision, security, record retention, regulatory filings, patient communication, and escalation to in-person care whenever appropriate. For medical or telemedicine compliance questions, contact [email protected].