Version 1.0 · Effective October 23, 2026

This Business Associate Agreement (the “BAA”) forms part of the Denzy Service Agreement (United States) between KK Technologies Inc., operating as Denzy (“Business Associate”), and the dental practice in the United States of America that has executed that agreement (“Covered Entity”). By executing the Service Agreement, the Covered Entity agrees to this BAA.

This BAA is entered into to comply with 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 CFR Parts 160 and 164 (collectively, “HIPAA”).

1. Definitions

Capitalized terms not defined in this BAA have the meanings given to them in HIPAA.

“Protected Health Information” or “PHI” means protected health information as defined at 45 CFR 160.103, limited to information Business Associate creates, receives, maintains, or transmits for or on behalf of Covered Entity.

“Electronic PHI” or “ePHI” means PHI maintained in or transmitted by electronic media.

2. Permitted Uses and Disclosures

Business Associate may use and disclose PHI only as follows:

  1. to perform the services described in the Service Agreement, including matching patients to Covered Entity, scheduling appointments, writing appointments into Covered Entity’s practice management software, and sending appointment confirmations and reminders;
  2. for the proper management and administration of Business Associate, or to carry out its legal responsibilities, provided that any disclosure to a third party is required by law or is made with reasonable assurances of confidentiality and notification of any breach;
  3. to provide data aggregation services relating to the health care operations of Covered Entity, where requested; and
  4. to create de-identified information in accordance with 45 CFR 164.514(a)–(c), which may be used by Business Associate for any lawful purpose.

Business Associate shall not use or disclose PHI other than as permitted by this BAA, the Service Agreement, or as required by law. Business Associate shall not use or disclose PHI in a manner that would violate Subpart E of 45 CFR Part 164 if done by Covered Entity.

Business Associate shall request, use, and disclose only the minimum necessary PHI to accomplish the intended purpose.

Business Associate shall not sell PHI, and shall not use or disclose PHI for marketing purposes on behalf of any third party, without a valid authorization.

3. Obligations of Business Associate

3.1 Safeguards

Business Associate shall implement and maintain administrative, physical, and technical safeguards that reasonably and appropriately protect the confidentiality, integrity, and availability of PHI, and shall comply with Subpart C of 45 CFR Part 164 with respect to ePHI. Without limiting the foregoing, Business Associate shall:

  • encrypt ePHI in transit using industry-standard transport encryption;
  • encrypt ePHI at rest using industry-standard encryption;
  • require multi-factor authentication for access to systems containing ePHI;
  • maintain role-based access controls and limit access to personnel with a legitimate need;
  • maintain audit logging of access to ePHI;
  • revoke access promptly upon personnel departure or role change; and
  • conduct periodic security risk assessments and vulnerability testing.

3.2 Reporting

Business Associate shall report to Covered Entity any use or disclosure of PHI not permitted by this BAA, any Security Incident, and any Breach of Unsecured PHI, without unreasonable delay and in no case later than thirty (30) calendar days after discovery. The report shall include, to the extent known, the individuals affected, the nature of the incident, the PHI involved, and the steps taken to mitigate and remediate.

Unsuccessful Security Incidents that do not result in unauthorized access to, or use, disclosure, modification, or destruction of ePHI — such as routine port scans, pings, or blocked login attempts — are reported in aggregate on request rather than individually.

3.3 Subcontractors

Business Associate shall ensure that any subcontractor that creates, receives, maintains, or transmits PHI on its behalf agrees in writing to restrictions and conditions at least as protective as those applying to Business Associate under this BAA, in accordance with 45 CFR 164.502(e)(1)(ii) and 164.308(b)(2).

3.4 Individual Rights

Business Associate shall, where it maintains PHI in a Designated Record Set:

  1. make PHI available to Covered Entity as necessary to satisfy Covered Entity’s obligations under 45 CFR 164.524 (access), within fifteen (15) business days of request;
  2. make PHI available for amendment and incorporate amendments as directed by Covered Entity, in accordance with 45 CFR 164.526; and
  3. maintain and make available information required to provide an accounting of disclosures, in accordance with 45 CFR 164.528.

Where an individual makes such a request directly to Business Associate, Business Associate shall forward it to Covered Entity within five (5) business days.

3.5 Access by the Secretary

Business Associate shall make its internal practices, books, and records relating to the use and disclosure of PHI available to the Secretary of the U.S. Department of Health and Human Services for purposes of determining compliance with HIPAA.

3.6 Mitigation

Business Associate shall mitigate, to the extent practicable, any harmful effect known to it of a use or disclosure of PHI in violation of this BAA.

4. Obligations of Covered Entity

Covered Entity shall:

  1. notify Business Associate of any limitation in its Notice of Privacy Practices that affects Business Associate’s use or disclosure of PHI;
  2. notify Business Associate of any changes in, or revocation of, an individual’s authorization or consent;
  3. notify Business Associate of any restriction on the use or disclosure of PHI that Covered Entity has agreed to or is required to abide by; and
  4. not request Business Associate to use or disclose PHI in a manner that would violate HIPAA if done by Covered Entity.

5. Term and Termination

This BAA takes effect on the effective date of the Service Agreement and continues until all PHI is returned or destroyed, or protections are extended in accordance with Section 5.3.

5.1 Termination for Cause

Either party may terminate this BAA and the Service Agreement if the other party materially breaches this BAA and fails to cure the breach within thirty (30) days of written notice, or immediately where cure is not possible.

5.2 Effect of Termination

On termination, Business Associate shall return or destroy all PHI it maintains, and shall ensure its subcontractors do the same. Business Associate shall retain no copies except as required by law.

5.3 Infeasibility

Where return or destruction is infeasible, Business Associate shall notify Covered Entity of the conditions making it infeasible, shall extend the protections of this BAA to that PHI, and shall limit further use and disclosure to those purposes that make return or destruction infeasible, for so long as it is retained.

6. General

6.1 Regulatory References

A reference to a section of HIPAA means the section as in effect or as amended.

6.2 Amendment

The parties shall amend this BAA as necessary for each to comply with HIPAA as amended, including any final rule amending the Security Rule. Business Associate will give Covered Entity at least thirty (30) days’ notice of any material change to this BAA. Prior versions remain available at the archive links below.

6.3 Interpretation

Any ambiguity in this BAA shall be resolved to permit compliance with HIPAA. In the event of a conflict between the Service Agreement and this BAA with respect to Protected Health Information, this BAA controls.

6.4 No Third-Party Beneficiaries

Nothing in this BAA confers any rights on any person other than the parties.

6.5 Survival

The obligations of Business Associate under Sections 3 and 5 survive termination of this BAA.

Contact

Questions about this Business Associate Agreement: support@denzy.ai

Previous versions

(No previous versions. Archived versions will be listed here as they are superseded.)