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.
ProviderRelationshipPurpose and dataAvailabilitySafeguard
Amazon Web Services (AWS)SoapBox service providerApplication hosting, RDS, S3, security, backups, monitoring, and SES emailAccount, clinical, operational, audit, and transactional-email dataCoreCore production provider; contractual safeguards are required for PHI
OpenAISoapBox service providerClinical-document generation and transcription fallback through the APIAudio, transcripts, and clinical-document content for an enabled requestCoreBAA, Modified Retention provisioning, and eligible API endpoints required
DeepgramSoapBox service providerPrimary audio transcriptionSession audio submitted for transcriptionCoreProduction PHI use requires approved contractual safeguards
AssemblyAISoapBox service providerReal-time streaming transcriptionSession audio submitted to an enabled streaming workflowFeature-gatedProduction PHI use requires approved contractual safeguards
Google CloudSoapBox service providerVertex-hosted Gemini fallback processingTranscripts or clinical-document content for an enabled fallback requestFeature-gatedDeveloper API keys are forbidden; disabled unless workload identity, BAA, and zero-retention gates are satisfied
SentrySoapBox service providerError monitoring and performance diagnosticsOperational events after application-level PHI scrubbingOptionalPHI-field scrubbing is required in addition to contractual safeguards
TwilioSoapBox service providerPractice messaging and telecommunicationsPhone numbers, message delivery data, and enabled communication contentFeature-gatedFeature and contract approval required before production PHI workflows
StediSoapBox service providerEligibility, claims, status, ERA, and insurance-discovery transactionsPatient, coverage, claim, and remittance data for enabled RCM workflowsFeature-gatedBAA, environment, and capability-verification gates apply
Claim.MDSoapBox service providerClearinghouse provisioning and healthcare transactionsPatient, coverage, claim, attachment, and remittance dataFeature-gatedProduction routing stays disabled until contractual and activation gates pass
WherebySoapBox service providerTelehealth rooms and optional recording retrievalMeeting metadata and enabled audio/video recording dataFeature-gatedProduction adapter refuses use unless its BAA gate is satisfied
Connected fax servicesCustomer-connected serviceInbound and outbound fax through SRFax, eFax, Documo, or PhaxioFax documents, routing metadata, and recipient detailsFeature-gatedAvailability and contractual responsibility depend on the configured service
Connected calendar servicesCustomer-connected serviceGoogle, Microsoft, or Apple calendar synchronizationAppointment metadata permitted by the organization configurationOptionalSync behavior is reduced unless the applicable business account is BAA-covered
RingCentral (SoapBox-managed)SoapBox service providerSoapBox-managed RingCentral calling and messaging for practices that choose itPhone numbers, call metadata, and enabled communication contentFeature-gatedProduction use requires its BAA confirmation gate and practice enablement
Connected phone servicesCustomer-connected serviceZoom Phone, RingCentral, or Dialpad screen-pop and call workflowsCall metadata and workflow context permitted by the configured integrationFeature-gatedCustomer authorization and applicable provider terms govern connected use
Customer-selected EMR destinationsCustomer-connected serviceClinician-directed note export or deep links to a selected record systemClinical note content selected by the clinician for exportOptionalThe customer controls the destination and remains responsible for its EMR relationship
StripeNon-PHI service providerSubscription and payment processingBilling and account identifiers; patient information is prohibitedCoreApplication policy prohibits patient information in Stripe metadata
ExpoNon-PHI service providerMobile push deliveryOpaque event pointers and generic notification text; PHI content is prohibitedFeature-gatedPush payload policy prohibits patient, record, message, or clinical content
CloudflareNon-PHI service providerStatic public-marketing hosting and edge deliveryPublic-site request and operational metadata; no application PHICoreThe 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