Version 2026-10-01
Business Associate Agreement
This is the agreement Charm ABA signs with each customer. New accounts sign it electronically when they first sign in, and receive a countersigned copy by email and in their account.
Business Associate Agreement
Indy Toy Lab LLC, d/b/a Charm ABA
Version 2026-10-01. Effective on the date the Customer signs it ("Effective Date").
This Business Associate Agreement ("BAA") is entered into between Indy Toy Lab LLC, an Indiana limited liability company doing business as Charm ABA ("Company" or "Business Associate"), and the organization named in the signature block below, on whose behalf the signer executes this BAA ("Customer" or "Covered Entity"). Together, the "Parties."
By signing this BAA electronically, the individual signing represents and warrants that they are authorized to bind the Customer to this BAA, and the Customer agrees to be bound by it. The Customer may not use the Service until this BAA has been signed.
1. Purpose and Scope
1.1 Company provides a software service that drafts applied behavior analysis treatment-plan documents from records the Customer uploads (the "Service"). In providing the Service, Company may create, receive, maintain, or transmit Protected Health Information on behalf of the Customer, which makes Company a business associate of the Customer under HIPAA.
1.2 This BAA governs PHI only when it is submitted through the features of the Service that Company designates as approved for PHI (the "Approved PHI Workflow"). PHI sent to Company through any other channel, including email, chat, support tickets, screenshots, text messages, or social media, is outside this BAA. Company will make reasonable efforts to delete such PHI on discovery, but Customer bears responsibility for any such disclosure.
1.3 Company is an independent contractor. Nothing in this BAA makes Company the agent of the Customer within the meaning of the federal common law of agency, and Company has no authority to act on the Customer's behalf beyond providing the Service.
2. Definitions
2.1 "HIPAA" means the Health Insurance Portability and Accountability Act of 1996, the Health Information Technology for Economic and Clinical Health Act, and their implementing regulations at 45 C.F.R. Parts 160 and 164, each as amended.
2.2 Capitalized terms not defined in this BAA, including "Breach," "Business Associate," "Covered Entity," "Data Aggregation," "Designated Record Set," "Electronic Protected Health Information," "Protected Health Information" or "PHI," "Required by Law," "Secretary," "Security Incident," "Subcontractor," and "Unsecured PHI," have the meanings given in HIPAA. "PHI" in this BAA refers only to PHI Company creates, receives, maintains, or transmits on behalf of the Customer through the Approved PHI Workflow.
2.3 "Terms" means Company's Terms of Service, as updated from time to time, which the Customer has accepted separately.
3. Permitted Uses and Disclosures by Company
3.1 To provide the Service. Company may use and disclose PHI to provide, operate, maintain, secure, monitor, support, troubleshoot, and improve the Service, and as otherwise permitted or required by this BAA or the Terms.
3.2 Management and administration. Company may use PHI for its proper management and administration and to carry out its legal responsibilities. Company may disclose PHI for those purposes if the disclosure is Required by Law, or if Company obtains reasonable assurances from the recipient that the PHI will be held confidentially, used or further disclosed only as Required by Law or for the purpose for which it was disclosed, and that the recipient will notify Company of any instance of which it is aware in which confidentiality has been breached.
3.3 Data Aggregation. Company may use PHI to provide Data Aggregation services relating to the health care operations of the Customer.
3.4 De-identification. Company may de-identify PHI in accordance with 45 C.F.R. § 164.514(a)–(c). De-identified information is not PHI, and Company may use and disclose it for any lawful purpose, including improving the Service, benchmarking, research, and product development, during and after the term of this BAA.
3.5 Required by Law. Company may use and disclose PHI as Required by Law.
3.6 Artificial intelligence. The Service uses third-party artificial-intelligence models to draft documents. PHI submitted to those models is processed under terms that prohibit the model provider from using it to train or improve general-purpose models and that limit retention to what is needed to return the result. Company will not itself use PHI to train models that are made available to anyone other than the Customer.
3.7 Limits. Company will not use or disclose PHI in a manner that would violate Subpart E of 45 C.F.R. Part 164 if done by the Customer, except as permitted by Sections 3.2 through 3.4. Company will not sell PHI or use or disclose PHI for marketing without the authorization required by HIPAA.
3.8 Minimum necessary. Company will make reasonable efforts to limit its uses, disclosures, and requests of PHI to the minimum necessary to accomplish the intended purpose, consistent with HIPAA. Company may rely on the Customer's determination of minimum necessary for PHI the Customer submits.
4. Company's Obligations
4.1 Safeguards. Company will implement administrative, physical, and technical safeguards that reasonably and appropriately protect the confidentiality, integrity, and availability of Electronic PHI, and will comply with Subpart C of 45 C.F.R. Part 164 to the extent it applies to business associates.
4.2 Reporting. Company will report to the Customer, without unreasonable delay and in no event later than thirty (30) days after Discovery, any use or disclosure of PHI not permitted by this BAA of which Company becomes aware, any Security Incident, and any Breach of Unsecured PHI. "Discovery" occurs on the first day a Breach is known to Company's designated privacy or security personnel, or by exercising reasonable diligence would have been known to them. Company's report will include the information reasonably available to Company at the time and will be supplemented as Company learns more.
4.3 Unsuccessful Security Incidents. The Parties acknowledge that the Service is subject to continuous unsuccessful attempts at unauthorized access, such as pings, port scans, denial-of-service attempts, log-in attempts with invalid credentials, and malware that is blocked before it executes, none of which result in unauthorized access, use, disclosure, modification, or destruction of PHI. This Section constitutes notice of all such Unsuccessful Security Incidents, and no further reporting of them is required.
4.4 Mitigation. Company will mitigate, to the extent practicable, any harmful effect known to Company of a use or disclosure of PHI by Company in violation of this BAA.
4.5 Subcontractors. Company may engage Subcontractors to create, receive, maintain, or transmit PHI on its behalf, including cloud infrastructure, storage, database, email delivery, and artificial-intelligence providers. Company will enter into a written agreement with each such Subcontractor that requires the Subcontractor to comply with restrictions and conditions at least as restrictive as those that apply to Company under this BAA. Company maintains a current list of Subcontractors and will make it available on request or by posting it on its website. Company may add or replace Subcontractors without the Customer's consent, and posting the updated list constitutes notice.
4.6 Access. To the extent Company maintains PHI in a Designated Record Set, Company will, within fifteen (15) business days of a written request from the Customer, make that PHI available to the Customer so that the Customer can meet its obligations under 45 C.F.R. § 164.524. Company does not respond directly to individuals; an individual's request received by Company will be forwarded to the Customer.
4.7 Amendment. To the extent Company maintains PHI in a Designated Record Set, Company will, within fifteen (15) business days of a written request from the Customer, make the amendments to PHI that the Customer directs under 45 C.F.R. § 164.526.
4.8 Accounting of disclosures. Company will document the disclosures of PHI that would be required to be included in an accounting under 45 C.F.R. § 164.528 and, within fifteen (15) business days of a written request from the Customer, provide the information needed for the Customer to respond to an individual's request for an accounting. Disclosures for treatment, payment, and health care operations, and disclosures to the Customer itself, are excluded as HIPAA permits.
4.9 Customer's obligations under Subpart E. To the extent Company is to carry out one or more of the Customer's obligations under Subpart E of 45 C.F.R. Part 164, Company will comply with the requirements of Subpart E that apply to the Customer in the performance of those obligations. No such delegation exists unless stated in a written amendment signed by both Parties.
4.10 Books and records. Company will make its internal practices, books, and records relating to the use and disclosure of PHI available to the Secretary for the purpose of determining the Customer's compliance with HIPAA, to the extent Required by Law. Company will notify the Customer of any such request unless prohibited by law, and nothing in this Section waives any privilege or requires disclosure to the Customer or any other third party.
4.11 Cost of assistance. Assistance under Sections 4.6 through 4.8 that requires more than reasonable effort, that arises from the Customer's own act or omission, or that is requested more than four (4) times in any twelve-month period, may be charged at Company's then-current professional-services rates.
5. Customer's Obligations
5.1 Authority. The Customer represents that it is a Covered Entity or a Business Associate acting on behalf of a Covered Entity, and that it has all rights, consents, and authorizations required to disclose to Company the PHI it submits and to permit the uses and disclosures described in this BAA.
5.2 Approved workflow only. The Customer will submit PHI only through the Approved PHI Workflow and will not submit PHI through any other channel.
5.3 Minimum necessary. The Customer will submit only the PHI reasonably needed for the Service to produce the requested document and will not submit records irrelevant to that purpose.
5.4 Notice of Privacy Practices and restrictions. The Customer will notify Company in writing of any limitation in its notice of privacy practices, any change in or revocation of an individual's permission to use or disclose PHI, and any restriction on the use or disclosure of PHI the Customer has agreed to or is required to abide by under 45 C.F.R. § 164.522, in each case to the extent the limitation, change, or restriction may affect Company's use or disclosure of PHI. Company is not bound by any such limitation until it has received written notice and had a reasonable time to implement it, and Company may terminate this BAA if a restriction is one it cannot reasonably accommodate.
5.5 No impermissible requests. The Customer will not request Company to use or disclose PHI in any manner that would not be permissible under HIPAA if done by the Customer, except as permitted by Sections 3.2 through 3.4.
5.6 Accounts and workforce. The Customer is responsible for every account it creates or authorizes, for the acts and omissions of its workforce members and agents using the Service, for maintaining the confidentiality of credentials, and for promptly removing access for individuals who no longer require it.
5.7 Clinical responsibility. The Service produces drafts. The Customer is solely responsible for reviewing, editing, verifying, and approving every document before clinical use, submission to a payer, or inclusion in a medical record, and for all clinical and billing decisions. Company does not practice medicine, behavior analysis, or any other licensed profession, and does not provide legal advice.
5.8 Breach and incident notification duties. As between the Parties, the Customer is solely responsible for determining whether an incident is a Breach requiring notification, and for all notifications to individuals, the Secretary, the media, state regulators, and any other party under HIPAA or state law. Company will provide the information reasonably available to it to support those notifications. If a notification is required because of Company's violation of this BAA, Company will reimburse the Customer's reasonable, documented, out-of-pocket costs of the notifications that HIPAA requires, subject to Section 8.
6. Term and Termination
6.1 Term. This BAA takes effect on the Effective Date and continues until the later of the termination of the Customer's account and the return or destruction of all PHI under Section 6.4.
6.2 Termination by the Customer for cause. If the Customer determines that Company has violated a material term of this BAA, the Customer will notify Company in writing with reasonable detail, and Company will have thirty (30) days to cure. If Company does not cure within that period, the Customer may terminate this BAA and the Customer's use of the Approved PHI Workflow.
6.3 Termination and suspension by Company. Company may suspend the Customer's access to the Approved PHI Workflow immediately, and may terminate this BAA on written notice, if Company reasonably determines that (a) the Customer has violated this BAA or the Terms, (b) continued access presents a legal, security, privacy, clinical, or patient-safety risk, (c) a change in law, regulation, or Subcontractor terms makes continued performance impracticable, or (d) the Customer's account is closed for any reason. Company may also terminate this BAA for convenience on thirty (30) days' written notice, in which case the Customer will stop submitting PHI on receipt of the notice.
6.4 Return or destruction. Within ninety (90) days after termination, Company will destroy the PHI it maintains in the Approved PHI Workflow, and will make PHI available for the Customer to export during the first thirty (30) of those days, using the export features of the Service. The Parties agree that return or destruction is infeasible for PHI held in encrypted backups, system and audit logs, records needed to demonstrate compliance, and records subject to legal hold, and Company will continue to extend the protections of this BAA to that PHI and limit its use and disclosure to the purposes that make return or destruction infeasible, for as long as Company retains it. Company will confirm destruction in writing on request.
6.5 Survival. Sections 3.4, 4.10, 5.7, 5.8, 6.4, 6.5, 7, 8, and 9 survive termination.
7. Amendments and Changes in Law
7.1 Company may amend this BAA by posting a revised version and notifying the Customer through the Service or by email at least thirty (30) days before the revision takes effect, except that an amendment required to comply with a change in law may take effect immediately on posting. Company may require the Customer to sign the revised version before continuing to use the Service, and the Customer's continued submission of PHI after the effective date of a revision constitutes acceptance in any event. If the Customer does not accept a revision, its sole remedy is to stop submitting PHI and terminate its account before the revision takes effect.
7.2 The Parties will negotiate in good faith any further amendment necessary for either Party to comply with HIPAA. If the Parties cannot agree within thirty (30) days, either Party may terminate this BAA on written notice.
8. Liability and Indemnification
8.1 Limitation. The limitations and exclusions of liability in the Terms apply to this BAA. Without limiting them, Company's total aggregate liability arising out of or relating to this BAA, whether in contract, tort, or otherwise, will not exceed the fees the Customer paid to Company for the Service in the twelve (12) months immediately preceding the event giving rise to the claim. Company will not be liable for indirect, incidental, special, consequential, or punitive damages, or for loss of business, revenue, or goodwill, even if advised of their possibility. This Section does not limit Company's obligations under Section 5.8, which are subject to the aggregate cap.
8.2 Indemnification by the Customer. The Customer will defend, indemnify, and hold harmless Company and its members, managers, employees, and contractors from and against all claims, losses, fines, penalties, costs, and expenses, including reasonable attorneys' fees, arising out of or relating to (a) the Customer's or its workforce's violation of this BAA or HIPAA, (b) PHI the Customer submitted without the required authority or outside the Approved PHI Workflow, (c) the Customer's clinical, billing, or payer-submission decisions, or (d) any claim by an individual whose PHI the Customer submitted, except to the extent the claim results from Company's violation of this BAA.
8.3 No indemnification by Company. Except for the reimbursement obligation in Section 5.8, Company has no obligation to indemnify or defend the Customer under this BAA.
9. General
9.1 No third-party beneficiaries. Nothing in this BAA confers any right, remedy, or benefit on any person other than the Parties, including any individual whose PHI is submitted to the Service.
9.2 Interpretation. Any ambiguity in this BAA will be resolved to permit the Parties to comply with HIPAA. A reference to a section of HIPAA means the section as in effect or as amended.
9.3 Order of precedence. This BAA controls over the Terms and any other agreement between the Parties with respect to PHI. The Terms control with respect to everything else, including payment, account terms, intellectual property, disclaimers, dispute resolution, and limitation of liability, except as Section 8 expressly provides.
9.4 Governing law and venue. This BAA is governed by the laws of the State of Indiana, without regard to its conflict-of-laws rules, and by HIPAA where it applies. Any dispute not subject to the dispute-resolution provisions of the Terms will be brought exclusively in the state or federal courts located in Marion County, Indiana, and each Party consents to their jurisdiction.
9.5 Notices. Notices to Company under this BAA must be sent by email to jordan@indytoylab.com or by mail to Indy Toy Lab LLC, Attention: Privacy Officer, PO Box 102, Westfield, IN 46074. Notices to the Customer may be sent to the email address on the Customer's account. A notice sent by email is received on the next business day after it is sent, and a notice sent by mail is received when it is delivered. Notice under Section 4.2 may be given by email.
9.6 Entire agreement; severability; waiver. This BAA, together with the Terms, is the entire agreement of the Parties regarding PHI and supersedes the "PHI Business Associate Addendum" previously posted by Company and any prior agreement on the subject. If any provision is held unenforceable, the remainder continues in effect. A waiver is effective only in writing and only for the instance given.
9.7 Electronic signature. The Parties consent to do business electronically and agree that this BAA may be signed electronically. A signer's typed name, entered in the signature field of the Service and submitted with the signer's confirmation, is that signer's signature and has the same force as a handwritten one. Company's record of the signing user, the account, the organization, the version signed, the cryptographic hash of the signed text, and the time, network address, and device of signing is conclusive evidence of the Customer's signature and agreement.
9.8 Countersignature and copies. Company's signature is applied electronically at the time the Customer signs. Company will deliver a fully signed copy of this BAA to the email address on the Customer's account and will make it available for download in the Service. Each fully signed copy is an original.