Trust and security

Approval and audit

Patient messages require staff approval except narrowly scoped, separately enabled automation. A deterministic safety check runs before AI. Tenant permissions, encrypted provider credentials and an audit trail protect access and changes. Autonomous AI booking is planned and is not available yet.

Current launch status

OpsPilot is in pre-launch validation. Vendor BAAs and DPAs have not been signed. We have not obtained SOC 2, HITRUST or other compliance certification. Do not submit real patient information until your clinic’s contractual and technical launch checks are complete. A 99.9% uptime record has not yet been established.

Data flow and providers

Clinic staff use OpsPilot’s backend to manage records and authorize provider calls. Hosting uses Google Cloud. Depending on the clinic’s configured connections, messaging uses Twilio, Meta or an email provider; AI may use Google or OpenAI; calendar sync uses Google or Microsoft; patient payments use the clinic’s Stripe account. Not all providers are connected for every clinic.

Meta messaging is not a BAA-covered channel. Vertex AI is available as a configuration option only after the operator verifies the applicable Google agreement; selecting a setting does not execute an agreement. Ask for the current subprocessor inventory and data-flow review before onboarding.

Commercial terms

Month-to-month plans are priced per active location, with SMS and voice usage reconciled separately on your invoice. OpsPilot bills clinics directly; patient payments belong to each clinic’s connected payment account.