Trust & data processing
Know where each part of the work goes.
SoapBox separates service providers that may support our platform from services your practice chooses to connect. The exact providers involved depend on the workflow and configuration you use.
Reviewed inventoryInventory 2026-11-04
SoapBox service providerSelected and managed by SoapBox for an enabled product workflow.
Non-PHI service providerReceives limited account or operational data; patient information is prohibited.
Customer-connected serviceConnected by your practice; availability and contract responsibility depend on that configuration.
| Provider | Relationship | Purpose and data | Availability | Safeguard |
|---|---|---|---|---|
| Amazon Web Services (AWS) | SoapBox service provider | Application hosting, RDS, S3, security, backups, monitoring, and SES emailAccount, clinical, operational, audit, and transactional-email data | Core | Core production provider; contractual safeguards are required for PHI |
| OpenAI | SoapBox service provider | Clinical-document generation and transcription fallback through the APIAudio, transcripts, and clinical-document content for an enabled request | Core | BAA, Modified Retention provisioning, and eligible API endpoints required |
| Deepgram | SoapBox service provider | Primary audio transcriptionSession audio submitted for transcription | Core | Production PHI use requires approved contractual safeguards |
| AssemblyAI | SoapBox service provider | Real-time streaming transcriptionSession audio submitted to an enabled streaming workflow | Feature-gated | Production PHI use requires approved contractual safeguards |
| Google Cloud | SoapBox service provider | Vertex-hosted Gemini fallback processingTranscripts or clinical-document content for an enabled fallback request | Feature-gated | Developer API keys are forbidden; disabled unless workload identity, BAA, and zero-retention gates are satisfied |
| Sentry | SoapBox service provider | Error monitoring and performance diagnosticsOperational events after application-level PHI scrubbing | Optional | PHI-field scrubbing is required in addition to contractual safeguards |
| Twilio | SoapBox service provider | Practice messaging and telecommunicationsPhone numbers, message delivery data, and enabled communication content | Feature-gated | Feature and contract approval required before production PHI workflows |
| Stedi | SoapBox service provider | Eligibility, claims, status, ERA, and insurance-discovery transactionsPatient, coverage, claim, and remittance data for enabled RCM workflows | Feature-gated | BAA, environment, and capability-verification gates apply |
| Claim.MD | SoapBox service provider | Clearinghouse provisioning and healthcare transactionsPatient, coverage, claim, attachment, and remittance data | Feature-gated | Production routing stays disabled until contractual and activation gates pass |
| Whereby | SoapBox service provider | Telehealth rooms and optional recording retrievalMeeting metadata and enabled audio/video recording data | Feature-gated | Production adapter refuses use unless its BAA gate is satisfied |
| Connected fax services | Customer-connected service | Inbound and outbound fax through SRFax, eFax, Documo, or PhaxioFax documents, routing metadata, and recipient details | Feature-gated | Availability and contractual responsibility depend on the configured service |
| Connected calendar services | Customer-connected service | Google, Microsoft, or Apple calendar synchronizationAppointment metadata permitted by the organization configuration | Optional | Sync behavior is reduced unless the applicable business account is BAA-covered |
| RingCentral (SoapBox-managed) | SoapBox service provider | SoapBox-managed RingCentral calling and messaging for practices that choose itPhone numbers, call metadata, and enabled communication content | Feature-gated | Production use requires its BAA confirmation gate and practice enablement |
| Connected phone services | Customer-connected service | Zoom Phone, RingCentral, or Dialpad screen-pop and call workflowsCall metadata and workflow context permitted by the configured integration | Feature-gated | Customer authorization and applicable provider terms govern connected use |
| Customer-selected EMR destinations | Customer-connected service | Clinician-directed note export or deep links to a selected record systemClinical note content selected by the clinician for export | Optional | The customer controls the destination and remains responsible for its EMR relationship |
| Stripe | Non-PHI service provider | Subscription and payment processingBilling and account identifiers; patient information is prohibited | Core | Application policy prohibits patient information in Stripe metadata |
| Expo | Non-PHI service provider | Mobile push deliveryOpaque event pointers and generic notification text; PHI content is prohibited | Feature-gated | Push payload policy prohibits patient, record, message, or clinical content |
| Cloudflare | Non-PHI service provider | Static public-marketing hosting and edge deliveryPublic-site request and operational metadata; no application PHI | Core | The marketing deployment is separate from the authenticated clinical service |
Inclusion does not mean every provider receives your data. Feature availability and the provider selected for a request depend on your organization’s configuration and approved workflow.
Agreements
Your BAA is part of signup.
An authorized representative accepts our Business Associate Agreement on the organization’s behalf when creating the account. Contact us if your organization also needs a data processing agreement.
Read the BAARequest a DPA