Trust & Security
Subprocessors
Vendor and service categories that may process data for MedicalBot. Status labels are intentional: nothing is marked Active until selected.
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.
Registry
Publication policy
This page is backed by a structured registry in product code. Active status requires an actual selection — evaluation lists are not live subprocessorship claims.
Statuses in use: Under evaluation, Planned, Contract dependent, and Active.
There are currently no Active subprocessors listed. Entries below describe categories under consideration or future dependency — not confirmed production vendors.
Current registry entries
| Name | Category | Status | Purpose |
|---|---|---|---|
Cloud hosting provider (to be selected) No named cloud vendor is listed as Active until selected. | Infrastructure & hosting | Planned | Application hosting, compute, storage, and related infrastructure services for marketing and future secured product planes. Residency and region options to be defined per customer deployment. |
Edge / CDN / static hosting (to be selected) | Infrastructure & hosting | Under evaluation | Delivery of the public website and static assets. |
Transactional email provider (to be selected) | Communications | Planned | Demo booking confirmations and B2B transactional messages — non-PHI business contact only on the public plane. |
CRM / lead intake (to be selected) | Customer support | Planned | Storage of B2B inquiry and demo request details submitted on the public website. |
Web analytics provider (to be selected) | Analytics & measurement | Under evaluation | Aggregate traffic and conversion measurement for the marketing website, subject to cookie and consent configuration. |
AI inference / model API providers (to be selected) Customer-configurable option Not Active. Named model vendors will be published only when selected for a given environment. | AI model services | Contract dependent | Model inference for assistive workflows when a customer configures governed AI features. Provider choice, residency, and data-processing terms are deployment- and contract-dependent. |
Telephony / voice infrastructure (to be selected) Customer-configurable option | Communications | Contract dependent | Voice channel connectivity for configured organisational voice workflows when enabled. |
Identity / SSO provider (to be selected) | Security operations | Planned | Staff and administrator authentication for product consoles — designed to support MFA and organisational identity federation. |
Secrets management service (to be selected) | Security operations | Planned | Storage of API keys and credentials outside application source — not for PHI storage. |
Payment processor (to be selected) Customer-configurable option | Payments | Contract dependent | Administrative payment workflows when a customer enables billing integrations. Not used for clinical data. |
Named subprocessors are published here once selected and documented. Customers are notified through contractual channels whenever a subprocessor's status changes to Active. Contact us for current information.
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.