Public website
Marketing, education, trust content, and B2B inquiries. No PHI should be intentionally submitted. Work contact details only.
Plane A — marketing surface
Trust & Security
Data handling
Clear plane boundaries for what may be submitted where — aligned to the public website, product demo, and future secure application model.
MedicalBot communicates security and governance capabilities based on documented architecture, implementation scope, and verified agreements. Certification or regulatory status is presented only when formally established.
Boundaries
Three processing planes
This public site is not a regulated clinical system. Sensitive-data processing is not an intentional function of the public site or public demos.
Public product demo
Labeled architecture and workflow previews with illustrative data. No PHI. Do not enter real patient identifiers or credentials.
Plane B — demo / sandbox
Secure product environment
Sensitive-data processing only under configured contractual, technical, consent, and governance controls. Separate threat model from this website.
Plane C — secured application
Practice
What evaluators should do
- Use Book a Demo and Contact forms for business discussions — never for clinical records.
- Treat public chat, voice, or console demos as education unless a customer-controlled secure environment is explicitly in use.
- Expect customer-configurable residency, retention, and subprocessors when sensitive processing is contracted.
- Do not interpret architecture language on this site as a live control attestation for a production tenant.
See MedicalBot in a guided demo
Book a product walkthrough with our team. We discuss architecture, governance patterns, and fit for your organization — without collecting PHI.
Do not submit protected health information (PHI) on this website.