Charm ABA
TermsPrivacyBAASign In

Effective July 6, 2026

PHI Business Associate Addendum

This earlier addendum applies to accounts created before October 2, 2026 that have not signed the current Business Associate Agreement, which replaces it for every account that signs. The current agreement is at charmaba.com/baa. These terms apply only to approved customers and users.

1. Limited Scope

These PHI Business Associate Addendum terms apply only when Charm ABA has expressly approved a customer or user for PHI workflow use and the customer is a HIPAA covered entity, business associate, or authorized provider organization using Charm ABA for the approved treatment-plan workflow.

If a separately signed Business Associate Agreement exists between the parties, that signed agreement controls over this page to the extent of a direct conflict. If no separately signed agreement exists, these PHI BAA terms are intended to provide conservative PHI-use restrictions for approved client access.

2. Definitions

Capitalized HIPAA terms not defined here, including Protected Health Information, Electronic Protected Health Information, Covered Entity, Business Associate, Security Incident, and Breach, have the meanings given to them under HIPAA.

"Customer" means the approved provider organization or other approved entity using Charm ABA for the approved PHI workflow. "Company" means Indy Toy Lab LLC d/b/a Charm ABA.

3. Permitted Uses And Disclosures

  • Company may use and disclose PHI only to provide, operate, secure, monitor, audit, support, and improve the approved Charm ABA treatment-plan workflow.
  • Company may use and disclose PHI as required by law.
  • Company may use PHI for internal management, administration, data aggregation, security, and legal responsibilities only to the extent permitted by HIPAA and the applicable agreement.
  • Company will not sell PHI or use PHI for marketing without the authorization required by HIPAA.
  • Company will not use PHI to train public or general-purpose AI models.

4. Customer Responsibilities

  • Customer must upload only PHI it is legally authorized to use and disclose for the approved treatment-plan workflow.
  • Customer must apply the minimum necessary standard and avoid uploading irrelevant or excessive records.
  • Customer must ensure each user has an individual authorized account and appropriate role authority.
  • Customer must review all generated output through qualified clinical personnel before use or payer submission.
  • Customer must not send PHI through email, chat, screenshots, SMS, social messages, or other channels not approved by Company as covered for PHI.
  • Customer must notify Company promptly of unauthorized access, misdirected PHI, workforce changes affecting access, or suspected incidents involving the Service.

5. Safeguards

Company will implement administrative, physical, and technical safeguards designed to protect electronic PHI in the approved workflow and to help protect against uses or disclosures not permitted by this Addendum.

  • Private PHI artifact storage in the approved storage path.
  • Access controls for approved users and operators.
  • Audit events and operational monitoring.
  • Support procedures designed to keep PHI out of uncovered support channels.
  • Vendor and subprocessor controls intended to keep PHI within approved HIPAA/BAA-covered or out-of-boundary paths.

6. Subcontractors

Company may use subcontractors and vendors to provide the Service. Company will require subcontractors that create, receive, maintain, or transmit PHI for the approved workflow to agree to restrictions and safeguards at least as protective as those required by HIPAA and the applicable agreement.

7. Reporting

Company will report to Customer without unreasonable delay any use or disclosure of PHI not permitted by this Addendum that Company discovers, including a Breach of unsecured PHI. Company will report Security Incidents as required by HIPAA and the applicable agreement. Routine unsuccessful security events may be reported in aggregate or through operational documentation unless a specific agreement requires otherwise.

8. Access, Amendment, Accounting, And Restrictions

To the extent Company holds PHI needed for Customer to meet HIPAA obligations, Company will provide reasonable assistance for access, amendment, accounting of disclosures, restriction, and confidential communication requests as required by HIPAA and the applicable agreement. Customer remains responsible for receiving, validating, and responding to individual requests unless a signed agreement says otherwise.

9. HHS Access

Company will make its internal practices, books, and records relating to the use and disclosure of PHI received from, created by, or received by Company on behalf of Customer available to the Secretary of HHS for purposes of determining Customer's HIPAA compliance, as required by law.

10. Return Or Destruction

At termination of the applicable approved PHI relationship, Company will return or destroy PHI if feasible and required by the applicable agreement. If return or destruction is infeasible, Company may retain PHI only for limited legal, security, backup, audit, dispute, or compliance purposes and will continue to protect it under these restrictions.

11. Termination And Suspension

Company may suspend PHI workflow access immediately if it determines that continued access may create legal, security, privacy, clinical, operational, vendor, or patient-safety risk. Customer may terminate PHI workflow use by requesting access removal and following any applicable offboarding procedure.

12. Order Of Precedence

For approved PHI use, the most specific written agreement signed or accepted by Company governs. If the Terms of Service conflict with this Addendum regarding PHI handling, this Addendum controls for PHI handling. The Terms of Service continue to govern payment, account, product, limitation-of-liability, indemnity, and non-PHI matters unless a signed agreement says otherwise.

13. Conservative Interpretation

If a workflow, user, data type, support channel, vendor, or disclosure is not clearly approved for PHI use, it is not permitted. Company may require additional written approval, scope limits, technical controls, or legal terms before enabling or continuing PHI processing.

These terms are intended to protect Charm ABA, its customers, and individuals whose information may be processed through approved client workflows. They are not a substitute for legal advice.