Now live · See DIAL3D on a live treatment center site — chat, call, and verify insurance. No demo call required.

Business Associate Agreement.

Last reviewed · November 2, 2026

Summary

Our standard process is to sign a Business Associate Agreement (BAA) with each customer that processes Protected Health Information (PHI) through our platform. This includes the Trial plan — our standard process doesn't ask you to process PHI without a BAA at any plan tier.

Our standard process is a signed BAA during onboarding. A standard template is available; customer-provided BAA templates are also acceptable as long as the substantive HIPAA-required terms are present.

Standard BAA scope

The BAA covers the standard HIPAA-required terms: (a) permitted uses and disclosures of PHI, (b) administrative, physical, and technical safeguards consistent with the HIPAA Security Rule, (c) reporting of security incidents and breaches, (d) subcontractor flow-down requirements, (e) compliance with applicable provisions of HIPAA's Privacy Rule, (f) availability of PHI to the customer on request, and (g) return or destruction of PHI at contract termination.

Specific terms — including breach notification timeframes, audit rights, and indemnification language — are negotiable within reasonable bounds.

42 CFR Part 2 QSOA

For customers operating federally-assisted treatment programs subject to 42 CFR Part 2, we'll work with your counsel on a Qualified Service Organization Agreement (QSOA) under 42 CFR § 2.11 during onboarding, in addition to the standard BAA. Once signed, the QSOA permits DIAL3D to receive Part 2 information in the course of providing the service and binds us to maintain its confidentiality consistent with the rule.

If your program is subject to Part 2, tell us during onboarding so the QSOA can be handled alongside the BAA.

Subcontractor flow-down

DIAL3D uses a limited set of subprocessors that may handle PHI in the course of operating the service. All subprocessors that handle PHI have executed BAAs with DIAL3D and are bound by terms substantially similar to those in the customer-facing BAA.

The current subprocessor list is available on request and is updated when material changes occur. Customers may request to be notified of new subprocessors before they handle PHI; opt-out is available within a reasonable transition period.

How to execute

Standard process: during onboarding, we send the BAA for signature.

If your organization requires a custom BAA template, send it to [email protected] with your legal contact. Our compliance team will review it.

After execution

Once executed, the BAA remains in effect for the duration of the customer's use of DIAL3D plus the retention period for PHI specified in the BAA. Termination of the underlying service contract terminates the BAA's forward-looking obligations, but does not terminate the retention, return, and destruction obligations.

Need this document, a security questionnaire, or a deeper conversation?

Need to execute a BAA, request a copy of the standard template, or have legal questions about scope? Contact our compliance team.

Contact our compliance team

Other trust + compliance pages

See how DIAL3D handles compliance in production.

Thirty minutes. We screen-share the agent through a real call, then show you the audit trail, the consent record, and the encryption posture.

Chat with Avery