BUSINESS ASSOCIATE AGREEMENT

Affective Software, Inc. d/b/a Gottman Inc.

Effective Date: The date of the Covered Entity's electronic acceptance. Gottman will capture and store the acceptance date and applicable Agreement version in the Covered Entity's user record.

Recitals

This Business Associate Agreement ("BAA" or "Agreement") is entered into between Affective Software, Inc. d/b/a Gottman Inc., a Washington corporation ("Business Associate" or "Gottman"), and the licensed mental health professional or group practice identified below ("Covered Entity" or "Provider") (each a "Party" and collectively the "Parties").

WHEREAS, Business Associate provides certain services to Covered Entity through the Gottman Connect clinical platform (the "Platform") pursuant to the Gottman Terms of Use (the "Underlying Agreement");

WHEREAS, in connection with those services, Business Associate may create, receive, maintain, or transmit Protected Health Information ("PHI") on behalf of Covered Entity;

WHEREAS, the Health Insurance Portability and Accountability Act of 1996 ("HIPAA"), the Health Information Technology for Economic and Clinical Health Act ("HITECH Act"), and implementing regulations at 45 C.F.R. Parts 160 and 164 (collectively, "HIPAA Rules") require that Covered Entity and Business Associate enter into this Agreement;

NOW, THEREFORE, in consideration of the mutual promises set forth herein and in the Underlying Agreement, the Parties agree as follows:

1. Definitions

Capitalized terms used but not defined in this Agreement have the meanings set forth in the HIPAA Rules. Key definitions include:

1.1 Breach

"Breach" means the acquisition, access, use, or disclosure of PHI in a manner not permitted under the HIPAA Privacy Rule that compromises the security or privacy of the PHI, as defined at 45 C.F.R. § 164.402.

1.2 Business Associate

"Business Associate" has the meaning given at 45 C.F.R. § 160.103 and, for purposes of this Agreement, refers to Affective Software, Inc. d/b/a Gottman Inc.

1.3 Covered Entity

"Covered Entity" has the meaning given at 45 C.F.R. § 160.103 and, for purposes of this Agreement, refers to the Provider who has agreed to the Gottman Terms of Use and activated Gottman Connect for clinical use with clients.

1.4 Data Aggregation

"Data Aggregation" means the combining of PHI created or received by Business Associate on behalf of Covered Entity with PHI received by Business Associate in its capacity as a business associate of another covered entity, to permit data analyses that relate to the health care operations of the respective covered entities.

1.5 Designated Record Set

"Designated Record Set" has the meaning given at 45 C.F.R. § 164.501.

1.6 Electronic Protected Health Information (ePHI)

"ePHI" means PHI that is transmitted or maintained in electronic media, as defined at 45 C.F.R. § 160.103.

1.7 Protected Health Information (PHI)

"PHI" means individually identifiable health information created, received, maintained, or transmitted by Business Associate on behalf of Covered Entity, as defined at 45 C.F.R. § 160.103, subject to the exclusions set forth therein.

1.8 Required by Law

"Required by Law" has the meaning given at 45 C.F.R. § 164.103.

1.9 Security Incident

"Security Incident" means the attempted or successful unauthorized access, use, disclosure, modification, or destruction of information or interference with system operations in an information system, as defined at 45 C.F.R. § 164.304.

1.10 Subcontractor

"Subcontractor" means a person or entity to whom Business Associate delegates a function, activity, or service, other than in the capacity of a member of the Business Associate's workforce, involving the use or disclosure of PHI.

2. Obligations of Business Associate

2.1 Permitted Uses and Disclosures

Business Associate may use or disclose PHI only as follows:

  • To perform functions, activities, or services for or on behalf of Covered Entity as specified in the Underlying Agreement, provided such use or disclosure would not violate the HIPAA Rules if done by Covered Entity;
  • As required by law;
  • For Business Associate's proper management and administration, provided that disclosures are required by law or Business Associate obtains reasonable assurances from the recipient that the PHI will be kept confidential and used only for the purpose for which it was disclosed;
  • To report violations of law to appropriate authorities, as permitted under 45 C.F.R. § 164.502(j)(1); and
  • For Data Aggregation services to Covered Entity, if applicable under the Underlying Agreement.

2.2 Prohibited Uses and Disclosures

Business Associate shall not:

  • Use or disclose PHI in a manner that would violate the HIPAA Rules if done by Covered Entity, except as permitted by this Agreement;
  • Use or disclose PHI for marketing purposes without valid authorization from the individual, except for communications that fall within the exceptions set forth in the definition of "marketing" at 45 C.F.R. § 164.501;
  • Sell PHI; or
  • Use or disclose PHI in a manner that violates applicable law.

2.3 Minimum Necessary

Business Associate shall use, disclose, or request only the minimum necessary PHI to accomplish the intended purpose, consistent with 45 C.F.R. § 502(b).

2.4 Safeguards

Business Associate shall implement appropriate administrative, physical, and technical safeguards that reasonably and appropriately protect the confidentiality, integrity, and availability of ePHI as required by the HIPAA Security Rule (45 C.F.R. Part 164, Subpart C). These safeguards shall include, at a minimum:

  • Encryption of ePHI in transit and at rest;
  • Role-based access controls;
  • Multi-factor authentication for administrative access;
  • Regular risk assessments and security reviews;
  • Workforce training on HIPAA requirements; and
  • Documented security incident response procedures.

2.5 Subcontractors

Business Associate shall ensure that any Subcontractor that creates, receives, maintains, or transmits PHI on behalf of Business Associate agrees to the same restrictions, conditions, and requirements that apply to Business Associate under this Agreement by entering into a written subcontractor business associate agreement. Business Associate shall use reasonable efforts to oversee its Subcontractors' compliance with such agreements but shall not be liable for acts or omissions of Subcontractors except to the extent caused by Business Associate's failure to comply with this Section 2.5.

2.6 Reporting Obligations

Business Associate shall:

  • Report to Covered Entity any use or disclosure of PHI not permitted by this Agreement of which Business Associate becomes aware, including Breaches of Unsecured PHI as required by 45 C.F.R. § 164.410, without unreasonable delay and in no event later than thirty (30) calendar days after discovery;
  • Report to Covered Entity any Security Incident of which Business Associate becomes aware. The Parties acknowledge that routine unsuccessful attempts to penetrate or access systems (e.g., pings, port scans) occur regularly and that Business Associate need not provide individual notice of each such unsuccessful attempt, but shall report patterns of unsuccessful attempts;
  • Provide Covered Entity with the information required under 45 C.F.R. § 164.410(c) (identity of individuals affected, description of the Breach, types of PHI involved, steps affected individuals should take, steps Business Associate is taking to mitigate harm, and contact information) as soon as reasonably practicable following discovery of a Breach.

2.7 Individual Rights

To the extent Business Associate maintains a Designated Record Set on behalf of Covered Entity, Business Associate shall:

  • Make PHI available to Covered Entity or individuals as necessary to enable Covered Entity to comply with individuals' rights of access under 45 C.F.R. § 164.524, within 30 days of a request;
  • Make PHI available for amendment and incorporate any amendments requested by Covered Entity pursuant to 45 C.F.R. § 164.526;
  • Provide an accounting of disclosures of PHI as required by 45 C.F.R. § 164.528 within 60 days of a request; and
  • Implement restrictions on the use or disclosure of PHI agreed to by Covered Entity pursuant to 45 C.F.R. § 164.522.

2.8 HHS Access

Business Associate shall make its internal practices, books, and records relating to the use and disclosure of PHI received from, or created or received on behalf of, Covered Entity available to the Secretary of the U.S. Department of Health and Human Services (HHS) for the purposes of determining Covered Entity's compliance with the HIPAA Rules.

2.9 De-Identification

Business Associate may de-identify PHI in accordance with 45 C.F.R. Section 164.514(a)-(c) only as reasonably necessary to provide, maintain, secure, debug, troubleshoot, and improve the Platform and the user experience. De-identified data is no longer PHI, but Business Associate will not publish it, use it for independent research or marketing, disclose it to third parties for their own purposes, or use it to train third-party models. Any de-identification and subsequent internal use must remain consistent with this Agreement, the underlying services agreement, and applicable law.

3. Obligations of Covered Entity

Covered Entity shall, and shall be solely responsible for any liability arising from its failure to:

  • Notify Business Associate promptly, and in any event within ten (10) business days, of any limitation in its Notice of Privacy Practices that affects Business Associate's use or disclosure of PHI;
  • Notify Business Associate promptly, and in any event within ten (10) business days, of any changes in, or revocation of, authorization by an individual that affects Business Associate's use or disclosure of PHI;
  • Notify Business Associate of any restriction on the use or disclosure of PHI that Covered Entity has agreed to under 45 C.F.R. § 164.522;
  • Not request Business Associate to use or disclose PHI in any manner that would not be permissible under the HIPAA Rules if done by Covered Entity;
  • Obtain all authorizations or consents required by applicable law before directing Business Associate to use or disclose PHI for any purpose that requires such authorization; and
  • Implement appropriate safeguards to protect PHI, including secure practices for accessing the Platform.

4. Term and Termination

4.1 Term

This Agreement shall become effective on the date Covered Entity affirmatively accepts it electronically within the Gottman Connect platform, as captured in the Covered Entity's user record, or on the date of a separately executed signature below, as applicable. The electronic acceptance date will ordinarily coincide with platform activation. This Agreement shall remain in effect until terminated as set forth herein or upon expiration or termination of the Underlying Agreement.

4.2 Termination for Cause

Either Party may terminate this Agreement immediately upon written notice if the other Party materially breaches any provision of this Agreement and: (a) the breaching Party fails to cure the breach within 30 days of receiving written notice; or (b) the breach is incurable. Termination of this Agreement by Business Associate for Covered Entity's breach shall also entitle Business Associate to terminate or suspend the Underlying Agreement.

4.3 Effect of Termination

Upon termination of this Agreement for any reason, Business Associate shall, at the election of Covered Entity and subject to technical feasibility:

  • Return to Covered Entity all PHI received from, or created on behalf of, Covered Entity, if feasible; or
  • Destroy all PHI received from, or created on behalf of, Covered Entity and retain no copies; or
  • If return or destruction is infeasible (e.g., due to legal retention requirements), extend the protections of this Agreement to such PHI and limit further use or disclosure to those purposes that make return or destruction infeasible for so long as Business Associate maintains such PHI. Without limiting the foregoing, Sections 2.1 through 2.4, 2.6, and 5 shall survive termination or expiration of this Agreement for so long as Business Associate retains any PHI.

5. General Provisions

5.1 Regulatory References

Any reference in this Agreement to a section of the HIPAA Rules means the section as in effect or as amended from time to time.

5.2 Amendment

The Parties agree to amend this Agreement as necessary to comply with changes in applicable law, including changes to the HIPAA Rules. Gottman may make non-material amendments by providing 30 days' written notice to Covered Entity; continued use of the Platform following such notice constitutes acceptance of a non-material amendment. For a material amendment, Gottman will provide notice and require renewed affirmative acceptance before the amendment becomes effective, except where applicable law permits another process. Covered Entity may terminate this Agreement by discontinuing use of the Platform before the effective date of an amendment if it does not agree to the revised terms.

5.3 Interpretation

This Agreement shall be interpreted as broadly as necessary to implement and comply with the HIPAA Rules. Any ambiguity shall be resolved in favor of a meaning that complies with the HIPAA Rules.

5.4 No Third-Party Beneficiaries

Nothing in this Agreement shall confer upon any person other than the Parties any rights, remedies, obligations, or liabilities.

5.5 Relationship to Underlying Agreement

This Agreement is incorporated into and forms part of the Underlying Agreement. In the event of a conflict between this Agreement and the Underlying Agreement regarding PHI, this Agreement controls.

5.6 Governing Law

This Agreement shall be governed by the HIPAA Rules and, to the extent not preempted, the laws of the State of Washington.

5.7 Entire Agreement

This Agreement, together with the Underlying Agreement, constitutes the entire agreement between the Parties with respect to the subject matter hereof.

Signatures

By signing below or, where applicable, by affirmatively checking the acceptance box presented within the Gottman Connect platform, each Party represents that it has authority to enter into this Agreement and agrees to be bound by its terms. Gottman will capture and store the acceptance date and applicable Agreement version in the Covered Entity's user record.