
Trust center
Answers for the state CIO,before the questionnaire.
Security posture,item by item
ZunovaMD is in build, and no clinic or patient uses it yet. Built means built and tested on synthetic data. Phases are our build order: Phase 1 is the core record and the partner demo, Phase 2 adds prescribing, dispensing, state connections and backups, and Phase 3 brings the first clinics live.
HIPAA and business associate agreements
BAAs plannedNo patient data reaches ZunovaMD today, and this website holds none. No vendor BAA is signed yet (each vendor is listed below), and each clinic signs a BAA with us before any patient data moves.
Tenant isolation
Built, synthetic dataPostgres row-level security keeps each clinic's records apart, and cross-tenant tests check it on synthetic data.
Encryption
Planned, Phase 1Not built yet: the platform runs on synthetic data only, with no hosted database and no key management. Planned: TLS 1.3 in transit, AES-256 at rest and keys in a managed KMS, with per-clinic keys for the most sensitive fields.
Zero-trust access
Partly builtBuilt on synthetic data: staff sign in through a demo identity provider, ten roles are checked on the actions that sign, review, book, bill and export, and break-glass asks for a reason and goes on the audit trail. Not built yet: single sign-on, mandatory multi-factor for staff and passkeys for patients, which wait on a real identity provider.
Audit ledger
Built, synthetic dataAppend-only and hash-chained for each clinic, with a viewer that checks the chain, running on synthetic data. A daily job that verifies every chain is built and starts once the job runner is chosen.
Backups
Planned, Phase 2Not built yet: there is no hosted platform database to back up. Planned: encrypted, cross-region, object-locked snapshots and a monthly restore drill, with a fifteen-minute recovery point and a four-hour recovery time as the targets.
Endpoint and exfiltration defense
Planned, Phase 2Not built yet. Planned: alerts on bulk or off-hours reads, export controls with a second approver and download watermarking, then managed endpoint detection for clinic devices in Phase 3.
AI governance
Partly builtNo model-backed agent runs yet, and we decided that no model is trained on patient data, de-identified data included. Built on synthetic data with a mock model: each agent statement is checked against the record before it shows, question sets are versioned and evaluated, and each agent has a kill switch per clinic. A real model waits on a BAA with zero retention.
Certifications
PlannedThe audits, self-assessments and training we have planned or started are listed below, with register IDs and status. We show a badge only when we hold the report or certificate, not before.
Certificationsand status
Earned means we hold the report or certificate. Planned items carry a target quarter. Each line names its ID in our certification register. There is no federal HIPAA certification, so we do not show one. ONC health IT certification is not part of the first release (CERT-016); we decide on it in 2027.
| Item | Kind | Register ID | Status |
|---|---|---|---|
| SOC 2 Type I reportA CPA firm examines how our controls are designed, as of one date.Planned, target 2027 Q3Audit, CERT-001 | Audit | CERT-001 | Planned, target 2027 Q3 |
| SOC 2 Type II reportA CPA firm tests whether those controls worked across an observation period.Planned, target 2028 Q1Audit, CERT-002 | Audit | CERT-002 | Planned, target 2028 Q1 |
| HITRUST e1 certificationA validated assessment of 43 foundational cybersecurity controls, renewed each year.Planned, target 2028 Q1Audit, CERT-004 | Audit | CERT-004 | Planned, target 2028 Q1 |
| Third-party penetration testAn outside firm tests the web app, APIs and mobile apps. We fix critical findings before go-live.Planned, target 2027 Q1Audit, CERT-014 | Audit | CERT-014 | Planned, target 2027 Q1 |
| HIPAA Security Rule risk analysisRequired before go-live. Repeated each year and after major changes.Planned, target 2026 Q4Self-assessment, CERT-029 | Self-assessment | CERT-029 | Planned, target 2026 Q4 |
| NIST Cybersecurity Framework 2.0 self-assessmentWhere we stand and where we aim, across the framework's six functions.Planned, target 2026 Q4Self-assessment, CERT-030 | Self-assessment | CERT-030 | Planned, target 2026 Q4 |
| HHS health sector cybersecurity performance goalsThe voluntary practices HHS ranks highest for health care.Planned, target 2026 Q4Self-assessment, CERT-031 | Self-assessment | CERT-031 | Planned, target 2026 Q4 |
| CSA STAR Level 1 questionnaireOur answers to the Cloud Security Alliance questionnaire, published in its STAR Registry.Planned, target 2027 Q1Self-assessment, CERT-033 | Self-assessment | CERT-033 | Planned, target 2027 Q1 |
| PCI DSS self-assessment questionnaire ACard numbers are typed into Stripe-hosted fields and never reach our systems.Planned, target 2027 Q1Self-assessment, CERT-035 | Self-assessment | CERT-035 | Planned, target 2027 Q1 |
| WCAG 2.2 AA conformance report, this websiteAutomated checks plus manual keyboard, screen reader and zoom tests.Planned, target 2026 Q4Self-assessment, CERT-036 | Self-assessment | CERT-036 | Planned, target 2026 Q4 |
| WCAG 2.2 AA conformance report, platform and patient appThe same report for the cockpit, the patient wallet and the clinician app.Planned, target 2027 Q1Self-assessment, CERT-037 | Self-assessment | CERT-037 | Planned, target 2027 Q1 |
| Vulnerability disclosure policy and security.txtA reporting channel and good-faith terms for security researchers, per RFC 9116.Planned, target 2026 Q4Self-assessment, CERT-038 | Self-assessment | CERT-038 | Planned, target 2026 Q4 |
| NIST AI Risk Management Framework self-assessmentThe risks of each agent mapped, measured and managed.Planned, target 2027 Q1AI governance, CERT-032 | AI governance | CERT-032 | Planned, target 2027 Q1 |
| CSA STAR for AI Level 1 questionnaireOur answers to the Cloud Security Alliance AI controls questionnaire.Planned, target 2027 Q2AI governance, CERT-034 | AI governance | CERT-034 | Planned, target 2027 Q2 |
| CHAI Applied Model Card for each agentWhat each agent was built for, how it was tested and where it stops.Planned, target 2027 Q1AI governance, CERT-040 | AI governance | CERT-040 | Planned, target 2027 Q1 |
| HIPAA workforce security trainingEveryone who can reach patient data is trained first, and we keep the records.Planned, target 2026 Q4Training, CERT-050 | Training | CERT-050 | Planned, target 2026 Q4 |
| Texas HB 300 privacy trainingTexas law training within 90 days of hire, with signed statements kept six years.Planned, target 2027 Q1Training, CERT-051 | Training | CERT-051 | Planned, target 2027 Q1 |
Subprocessors,named
One list, used here, in the privacy notice and in the app privacy labels.
| Vendor | Purpose | Patient data | Agreement |
|---|---|---|---|
| Anthropic | Language models behind the agents | Yes | BAA planned |
| Twilio | Phone, SMS, WhatsApp, fax | Yes | BAA planned |
| Deepgram | Medical speech to text | Yes | BAA planned |
| LiveKit | Video visits | Yes | BAA planned |
| Stripe | Payments; card data never touches ZunovaMD systems | No | No BAA needed |
| Amazon Web Services | Clinical record store (Postgres), files, audio, audit logs, staff and patient sign-in (Cognito), secrets, monitoring, and backup copies in a second US region; BAA signed before the first pilot clinic (D2) | Yes | BAA planned |
| Resend | Transactional email with no patient data in any message. Resend's security page says it cannot sign a BAA | No | No BAA needed |
| Netlify | Hosts this marketing site only; no PHI | No | No BAA needed |
| Sentry | Error monitoring with PHI scrubbing | No | No BAA needed |
| Composio | Links staff email, drive and calendar accounts to the work board. Demo links only today; no real account links until its BAA is signed | Yes | BAA planned |
| TypeSafe | Typed yes-or-no, label and score decisions (Jev). Runs on a mock today; no clinic text is sent until a BAA with zero retention is signed | Yes | BAA planned |
| Microsoft (Microsoft 365, Graph) | Transactional email from the app (invites, digests); no patient data in any message | No | No BAA needed |
| Stedi | Claims, eligibility checks, claim status and payer remittance files (clearinghouse) | Yes | BAA planned |
| Health Gorilla | Lab orders, results and result PDFs | Yes | BAA planned |
| DoseSpot | Electronic prescribing, including controlled substances (EPCS) | Yes | BAA planned |
| Bamboo Health (PMP Gateway) | State prescription monitoring (PDMP) checks before a controlled-substance prescription | Yes | BAA planned |
| Health information exchanges (SHARE in Arkansas, KONZA in Kansas, a Texas regional exchange, eHealth Exchange) | Clinical documents and demographics exchanged for treatment | Yes | BAA planned |
| Tenovi | Cellular hubs that relay readings from home monitoring devices | Yes | BAA planned |
| Terra | Readings from patients' wearables and health apps | Yes | BAA planned |
| Intuit (QuickBooks) | Accounting journals; no patient text in any entry | No | No BAA needed |
| Xero | Accounting journals; no patient text in any entry | No | No BAA needed |
| GoHighLevel (LeadConnector) | Sales leads from the site's demo form and partner sign-ups; no patient data | No | No BAA needed |
| Withings | A patient's connected scale and blood pressure cuff readings | Yes | BAA planned |
| Expo (push service) | Push notices to the patient and clinician phone apps | Yes | BAA planned |
| Kisi | Door access: release a lock for a checked-in visitor | Yes | BAA planned |
Report a vulnerability
Email security@zunovamd.com. We acknowledge within two business days and do not pursue researchers who act in good faith. Machine-readable details are at /.well-known/security.txt.
Send us your questionnaire
This website holds no patient data and requires no login. For the platform, we answer security questionnaires line by line.
Contact security