Subprocessors
Vendors that handle practice or patient data to run DARO. Version 2026-10-22.
How this list works
DARO's production service at daroclinical.com now runs on AWS. The AWS BAA has been executed. The list below distinguishes current production services from services still awaiting activation. Each vendor processes data only to provide its contracted service. Customers receive at least 30 days' notice before a new subprocessor that will handle protected health information is added, as required by DARO's BAA.
A vendor agreement alone does not establish HIPAA compliance. Services that handle protected health information must be eligible under the applicable agreement and securely configured. Each external practice must also have an executed BAA with DARO before entering real patient information.
Production and demonstration environments
The former managed hosting, AI gateway and email sender are not part of the AWS production patient-data path. Development previews and sample or test practices are separate demonstration environments and must contain fabricated data only; never enter real patient information there.
Optional practice integrations
Twilio SMS remains pending activation. Fax, electronic prescribing, clearinghouse, lab and other optional integrations are not included in the active AWS services above. Before an integration is enabled for a practice, its actual provider, data use and required agreements must be disclosed and reviewed. A practice's own vendor agreement does not make that vendor covered by DARO's AWS BAA.
| Vendor | Purpose | Data | Location | BAA |
|---|---|---|---|---|
| Amazon Web Services (AWS) | Production application hosting, self-hosted PostgreSQL database, authentication, private file storage and encrypted backups | Practice records, patient records, account information, uploaded files and backups | United States — Ohio (us-east-2) | AWS BAA executed; PHI use is limited to HIPAA-eligible services configured under that agreement |
| Amazon Web Services (AWS) — Bedrock and Transcribe | AI-assisted note drafting and clinical organization through Amazon Bedrock; audio transcription through Amazon Transcribe | Submitted visit audio, transcripts, draft notes and clinical context | United States — Ohio service endpoints; Bedrock US inference profiles may process in other US regions | Under the AWS BAA for eligible services; AI requests use AWS, not the former managed AI gateway |
| Amazon Web Services (AWS) — Simple Email Service (SES) | Production email delivery, including invitations, reminders and practice messages | Recipient email addresses and message content, including any practice information included in a message | United States — Ohio (us-east-2) | Under the AWS BAA for eligible services; production email uses SES, not the former email sender |
| Stripe | DARO subscriptions and practice-owned patient card payments | Billing contacts, payment details, transaction amounts and payment identifiers; not clinical notes or visit audio | United States | Payment processing is limited to the financial transaction function; the HIPAA payment-processing exception is not a blanket exemption for other data uses |
| Twilio — pending activation | Optional SMS reminders; not yet activated for production patient messaging | When enabled: recipient phone number and reminder message with a secure link; no patient name, condition or clinical details in reminder text | Service region and retention settings must be confirmed before activation | Execute the qualifying Twilio BAA and complete delivery setup before patient use; recorded SMS consent is required |