Khnum Forge ram sigil KHNUM FORGE
From the forge to the modern regulated workplace — Khnum Forge
Business Associate Agreement

Business Associate Agreement for Tyr

Version 1.0 · Effective on acceptance

This Agreement is between Khnum Forge, Inc., a Texas corporation ("Khnum"), and the business named on the Order Form that subscribes to Tyr, Khnum's hosted legal software ("Customer").

1. What this Agreement covers

1.1 Customer subscribes to Tyr under the Khnum Forge Terms and Conditions for Tyr (the "Terms") and the order it placed (the "Order Form"). This Agreement sets the rules for Protected Health Information that Customer places in Tyr, and is separate from the Terms. Capitalized words are explained in Section 2; de-identification is explained in Section 4.4.

1.2 This Agreement applies to information to the extent it is Protected Health Information in Customer's hands under the HIPAA Rules, that is, to the extent Customer places it in Tyr as a Covered Entity or as a Business Associate of its clients. In either case Khnum is a Business Associate of Customer. Records Customer holds in another capacity, such as its own client's medical records obtained with that client's authorization, are protected by the Terms and by Texas law (Section 9), and Khnum applies the safeguards in Section 3 to them in any event.

1.3 If Customer is itself a Business Associate of its own clients (for example, a law firm that handles Protected Health Information for a hospital client), Khnum is Customer's Subcontractor. The HIPAA Rules then require Customer to pass its restrictions down to Khnum, and this Agreement does that: Khnum accepts the same restrictions and conditions on Protected Health Information that bind Customer. Customer's clients do not sign a separate agreement with Khnum; the chain of agreements, from the client to Customer to Khnum, is what the HIPAA Rules require. A stricter term in Customer's own agreements binds Khnum only under Section 1.4.

1.4 Customer will tell Khnum in writing of any stricter restriction in its own agreements that affects Khnum's permitted uses, including any limit on de-identification. Khnum will follow it from the tenth business day after that notice unless, within those 10 business days, Khnum tells Customer in writing that it cannot. If Khnum cannot, Customer may end this Agreement by written notice without a cure period, and Section 11.4 applies.

1.5 Customer confirms that it may place Protected Health Information in Tyr and have Khnum perform the uses in Section 4, including de-identification. This Agreement covers all Protected Health Information Khnum creates, receives, maintains, or transmits for Customer through Tyr, including any placed there before the Effective Date. Customer will not place Protected Health Information in Tyr before accepting this Agreement.

2. Words with special meanings

2.1 These words have the meanings the HIPAA Rules give them, explained here in ordinary words. If an explanation and the regulation differ, the regulation controls. A section of the HIPAA Rules means that section as in effect or as amended.

2.2 HIPAA Rules means the federal privacy, security, breach-notification, and enforcement regulations at 45 CFR Parts 160 and 164. The Privacy Rule, Security Rule, and Breach Notification Rule are Subparts E, C, and D of Part 164.

2.3 Protected Health Information or PHI means information, including demographic details, created or received by a health care provider, health plan, employer, or health care clearinghouse, that identifies a person or gives a reasonable basis to identify one, and that relates to the person's past, present, or future physical or mental health or condition, the health care the person receives, or past, present, or future payment for that care. It excludes education records, a Covered Entity's own employment records, and information about a person dead more than 50 years. All PHI under this Agreement is electronic, and the Security Rule applies to all of it. Here, PHI means only the PHI Khnum handles for Customer.

2.4 Covered Entity means a health plan, a health care clearinghouse, or a health care provider that transmits health information electronically in one of the standard transactions HIPAA regulates, such as a claim or an eligibility inquiry. A law firm rarely is one.

2.5 Business Associate means a person or company, outside a Covered Entity's workforce, that creates, receives, maintains, or transmits PHI on the Covered Entity's behalf, or that provides legal, accounting, consulting, or similar services to the Covered Entity where the service involves the disclosure of PHI to it from the Covered Entity or from another Business Associate. A law firm that receives PHI from a Covered Entity client, or from that client's Business Associate, while providing it legal services is one. So is a Subcontractor.

2.6 Subcontractor means a person or company to which a Business Associate delegates part of its work with PHI, other than its own employees.

2.7 Security Incident means an attempted or successful unauthorized access to, use of, disclosure of, change to, or destruction of information in an information system, or interference with how that system operates.

2.8 Breach means acquiring, accessing, using, or disclosing PHI in a way the Privacy Rule does not permit, where that compromises the security or privacy of the PHI. Any such act is presumed to be a Breach unless Khnum (or Customer, for its own act) shows, by a documented risk assessment of the four factors in 45 CFR 164.402, a low probability that the PHI was compromised. Breach excludes: a workforce member's unintentional, good-faith access within their authority that goes no further; an inadvertent disclosure between two people authorized to handle PHI at the same organization that goes no further; and a disclosure to someone who could not reasonably have kept the information.

2.9 Unsecured PHI means PHI that has not been made unusable, unreadable, or indecipherable to unauthorized persons by a method the Secretary has specified, such as approved encryption.

2.10 Required by Law means a mandate contained in law, enforceable in a court, that compels Khnum to make a use or disclosure of PHI, including a statute, a regulation, a court order, a court-ordered warrant, and a subpoena or summons issued by a court or grand jury. A demand that is not enforceable in that way is not Required by Law; Khnum will tell Customer of any such demand under Section 5.7 and respond only as Customer directs or as this Agreement otherwise permits.

2.11 Secretary means the Secretary of the United States Department of Health and Human Services, or the Office for Civil Rights acting for the Secretary.

3. How Khnum protects Customer's data

3.1 Khnum will use appropriate administrative, physical, and technical safeguards, and will comply with the Security Rule, to protect the confidentiality, integrity, and availability of electronic PHI and to prevent any use or disclosure this Agreement does not allow.

3.2 Khnum will keep Customer's data in storage dedicated to Customer, encrypted under Customer's own encryption key, on Google Cloud. Khnum holds one business associate agreement with Google Cloud, and it covers every Google service Khnum uses for Customer's data; Customer does not need its own agreement with Google. Khnum will store Customer's data, backups included, only in the United States, except that Khnum's de-identification service may run in Google's global location.

3.3 Khnum will apply three controls to text that could leave the Google Cloud environment covered by Khnum's business associate agreement with Google Cloud. Prevention. Khnum will pass the documents Customer places in Tyr through its de-identification gate before any model call leaves that environment. The gate removes or masks the identifier classes listed in Khnum's written documentation of the gate. It fails closed: if it cannot verify that de-identification was applied, Khnum will block the call. The gate does not de-identify images, so Khnum will refuse them on that path. Detection. Khnum will screen every call to a provider outside that environment, before and after it is sent. If the text looks like PHI, or if the call is made for a firm on Khnum's PHI-bearing register, Khnum will page its founder and its privacy mailbox immediately. The alert will carry metadata only, never PHI. Containment. For a firm on that register, Khnum's gateway will block, before sending, any provider that has not agreed to zero data retention. Accepting this Agreement places Customer on Khnum's PHI-bearing register. These controls are safeguards. They do not release information from PHI status; Section 4.4 says when that happens.

3.4 Khnum will not train any model on Customer's data, PHI or not, and will not allow any vendor to do so.

3.5 Khnum will record every change to PHI in Tyr, and every transmission of PHI to a vendor, in audit logs kept in write-once storage that cannot be altered or deleted.

3.6 Khnum maintains a written risk analysis and risk management plan, security policies, and a contingency plan for restoring service and data, and reviews them at least once a year and after any material change to Tyr. These are Khnum's standing HIPAA program; nothing is prepared separately for each customer. Khnum's staff will access PHI only when needed to provide, support, or secure Tyr.

3.7 Khnum will not block Customer's access to its own PHI except as Required by Law. During any suspension under the Terms, Customer may still export its data. On request Khnum will give Customer, in confidence, a written summary of its safeguards; Khnum does not provide on-site audits.

4. What Khnum may and must do with PHI

4.1 Khnum will not use or disclose PHI except as this Agreement permits or requires, or as Required by Law, and never in a way that would violate the Privacy Rule if done by Customer or, where Customer is a Business Associate, by Customer's Covered Entity client, except as Section 4.5 allows.

4.2 Khnum may use and disclose PHI to provide Tyr to Customer: to store, search, analyze, and draft over Customer's matter files at Customer's direction, to support its users, and to operate, maintain, and secure the service. Khnum may disclose PHI to its Subcontractors under Section 6.

4.3 Khnum will disclose PHI when Required by Law, and to the Secretary when the Secretary requires it to investigate or determine compliance with the HIPAA Rules. Khnum will give Customer any electronic copy of PHI Customer needs to answer a person's request for an electronic copy of that person's records.

4.4 De-identification. Customer permits Khnum, under 45 CFR 164.502(d)(1), to use PHI to create de-identified information. Khnum's gate, which Section 3.3 describes, removes or masks the identifier classes listed in Khnum's written documentation of the gate. Information is treated as PHI unless an expert determination under 45 CFR 164.514(b)(1), or the safe-harbor removal of every identifier listed in 45 CFR 164.514(b)(2)(i)(A) through (R), has been completed and documented. Until then the gate is a safeguard, not a release from PHI status, and Khnum treats the gate's output as PHI. In plain words: information counts as de-identified only when the law's test is met and documented. Khnum uses the gate's output, and any de-identified information, only to process Customer's request, never to train a model. Khnum will not re-identify it, attempt to re-identify it, or disclose any key, code, or map that could re-identify it. Any such key is PHI, stays in Customer's encrypted storage, and never travels with the text the gate sends.

4.5 Khnum's own management and administration. Khnum may use PHI when necessary for its proper management and administration or to carry out its legal responsibilities, such as security monitoring, incident response, audit logging, legal process, and defending a claim. Khnum may disclose PHI for those purposes only if Required by Law, or if the recipient first assures Khnum in writing that it will hold the PHI in confidence, use or disclose it only as Required by Law or for the purpose given, and report any breach of that confidence to Khnum.

4.6 Data aggregation. Data aggregation means combining PHI from several covered entities to analyze their health care operations together. This Agreement does not permit Khnum to provide it.

4.7 Minimum necessary; no sale; no marketing. Khnum will use, disclose, and request only the minimum PHI needed for the purpose. Khnum will not sell PHI, disclose PHI for direct or indirect payment, or use PHI for advertising, marketing, or any similar purpose.

4.8 Customer's own duties. Khnum takes on none of Customer's Privacy Rule obligations. If Khnum later agrees in writing to carry one out, it will meet the Privacy Rule requirements that apply to Customer in doing so.

5. Reporting incidents and breaches

5.1 Khnum will report to Customer any use or disclosure of PHI that this Agreement does not permit, any Security Incident, and any Breach of Unsecured PHI, of which Khnum becomes aware.

5.2 Timing. Khnum will notify Customer immediately after it discovers a Breach, any successful Security Incident involving Customer's PHI, or an unauthorized acquisition of Customer's data that is a breach of system security under Tex. Bus. & Com. Code 521.053(a), and in every case without unreasonable delay. Khnum will then send a written report within 48 hours after it confirms the event. Khnum confirms an event when it has established what happened and, for a Breach, when it completes the risk assessment under Section 5.3, which it will complete without unreasonable delay. For a Breach, Khnum will never send the written report later than 60 calendar days after discovery. Khnum will report any other use or disclosure this Agreement does not permit within 10 business days after discovering it, with the risk assessment that supports treating it as other than a Breach. Khnum discovers an event on the first day any Khnum employee, officer, or agent, other than one who caused it, knows of it or with reasonable diligence would know of it. Khnum may delay a notice only at a law enforcement agency's written request, and only for as long as the law allows.

5.3 Content. Each report will state, as far as Khnum then knows: what happened and when; when Khnum discovered it; the kinds of PHI involved; each person whose Unsecured PHI was, or Khnum reasonably believes was, acquired, accessed, used, or disclosed; what Khnum has done and will do to investigate, contain, and prevent a repeat; and anything else Customer needs for its own notices. Khnum will update it as it learns more, and will carry out, document, and share with Customer the risk assessment the Breach Notification Rule calls for.

5.4 Who sends notices. Customer decides on and sends any notice to individuals, the Secretary, the media, state regulators, and its own clients. Khnum will supply what those notices need in time for Customer's deadlines, including the content Texas law requires in a notice to the Texas Attorney General. If Khnum must file a notice with a regulator itself, it will tell Customer first and coordinate the content.

5.5 Unsuccessful attempts. Khnum will report routine unsuccessful Security Incidents, such as blocked log-ins and port scans that do not reach PHI, in summary form on request.

5.6 Contingency plan. Khnum will tell Customer within 24 hours after it activates its contingency plan for an event that affects Customer's data.

5.7 Legal demands. Where the law allows, Khnum will tell Customer before it responds to a subpoena, court order, or other legal demand for Customer's PHI.

6. Subcontractors

6.1 Khnum will not let any Subcontractor create, receive, maintain, or transmit PHI for Khnum until that Subcontractor has signed a written contract accepting the same restrictions and conditions that apply to Khnum under this Agreement and agreeing to comply with the Security Rule. Khnum's hosting provider, Google Cloud, is under such a contract, and Khnum will keep it so. Khnum applies the controls in Section 3.3 to any model or vendor that is not under such a contract, and treats information the gate has handled as PHI unless Section 4.4 says it is not.

6.2 Khnum remains responsible for its Subcontractors' handling of PHI. If Khnum learns of a pattern of activity by a Subcontractor that materially violates its contract, Khnum will take reasonable steps to cure it and, if those fail, end the contract where feasible.

7. Access, amendment, and accounting

7.1 Khnum will make PHI available to Customer, within 10 business days of Customer's request, so Customer can act on a person's request for access under 45 CFR 164.524 or for amendment under 45 CFR 164.526, and will incorporate any amendment Customer directs. Only Customer makes amendments; Customer may retrieve and edit its own files at any time. Khnum does not decide which of Customer's records form part of a designated record set, the records the Privacy Rule gives a person the right to see and amend.

7.2 Khnum will record every disclosure of PHI it makes, except disclosures the Privacy Rule excludes from an accounting: the date, the recipient's name and address if known, a brief description of the PHI, and the purpose, together with any other information 45 CFR 164.528 requires for an accounting. Khnum will give Customer that record, for the six years before the request, within 10 business days of a request for an accounting of disclosures.

7.3 If a person asks Khnum directly for access, amendment, or an accounting, Khnum will forward the request to Customer within 5 business days and will not answer the person directly.

8. Books, records, and regulators

8.1 Khnum will make its internal practices, books, and records about the use and disclosure of PHI received from, or created or received for, Customer available to the Secretary to determine compliance with the HIPAA Rules, and will cooperate with Customer in any investigation by the Secretary, the Texas Health and Human Services Commission, or the Texas Attorney General concerning Customer's PHI.

8.2 Khnum will keep its HIPAA policies, incident files, risk assessments, and training records in electronic form for at least six years from the date each was created or last in effect, whichever is later.

9. Texas law

9.1 Under Chapter 181 of the Texas Health and Safety Code, Khnum is a "covered entity" - a term that chapter defines more broadly than HIPAA does - and Khnum will comply with the provisions of that chapter and of Chapter 183 that apply to Khnum.

9.2 Training. Khnum will train each employee whose duties involve PHI on state and federal PHI law, as Tex. Health & Safety Code 181.101 requires, within 90 days of hire and again within one year after a material change in that law, and will have each sign a statement of completion that Khnum keeps for six years.

9.3 No sale. Khnum will not disclose PHI to anyone for direct or indirect payment. The subscription fee pays for software and hosting, never for a disclosure of PHI.

9.4 Electronic disclosure. Khnum will disclose PHI electronically only: to Customer; to its Subcontractors under Section 6; to the Secretary under Section 4.3; under Section 4.5; as Required by Law; and as Customer directs in writing. For a disclosure Customer directs, Customer will obtain any authorization from the individual that Texas law requires. Khnum will post, and keep posted, a notice on its website that PHI it holds is subject to electronic disclosure.

9.5 Texas breach law. Khnum's notices under Section 5 are also its notices to Customer under Chapter 521 of the Texas Business and Commerce Code. Customer, as owner or licensee of the data, will send the notices to individuals, consumer reporting agencies, and the Texas Attorney General that chapter requires, with Khnum's help under Section 5.4.

10. Customer's responsibilities

10.1 Customer will not ask Khnum to use or disclose PHI in any way the Privacy Rule would not permit if done by Customer or by Customer's Covered Entity client.

10.2 Customer manages its own users, credentials, and access rights in Tyr and decides what it uploads.

10.3 Customer will not put PHI in a support request, an email, or any other channel outside Tyr unless Khnum has designated that channel for PHI. The safeguards in Section 3 apply only to Tyr. If Customer sends PHI through another channel, Customer is responsible for that disclosure, and Khnum will tell Customer and will delete the PHI or return it to Customer.

10.4 Customer will obtain any consent or authorization that HIPAA or Texas law requires before it places PHI in Tyr or directs a disclosure. Customer will tell Khnum in writing of any limit in an authorization, any restriction it or its client has agreed to under 45 CFR 164.522, and any change in its privacy practices that affects what Khnum may do with PHI.

10.5 Customer will keep its notice contact in its Tyr account current, and will handle individuals' requests for access, amendment, and accounting with Khnum's help under Section 7.

11. Term, termination, and what happens to PHI

11.1 This Agreement starts on the Effective Date and continues until Customer's subscription ends or a party ends it under Section 1.4, 11.2, or 11.3. Section 11.8 says what continues after that.

11.2 Termination by Customer. If Customer determines that Khnum has violated a material term of this Agreement, it may give Khnum written notice. Khnum has 30 days to cure a curable violation. If Khnum does not, or the violation cannot be cured, Customer may end this Agreement and the subscription at once by written notice. Customer may also end this Agreement under Section 1.4.

11.3 Termination by Khnum. If Khnum learns of a pattern of activity by Customer that materially violates this Agreement, Khnum will take reasonable steps to cure it with Customer and, if those fail within 30 days, may end this Agreement and the subscription by written notice.

11.4 Effect of ending. Ending this Agreement for any reason ends Customer's subscription to Tyr and its right to place PHI in Tyr, and Sections 11.5 through 11.7 then apply. Customer may not place PHI in Tyr again without a new business associate agreement.

11.5 Export period. When this Agreement ends for any reason, Customer may export its data for 30 days, or for any longer period the Terms allow.

11.6 Destruction. After the export period, Khnum will destroy all PHI it still holds for Customer by cryptographic erasure: Khnum destroys Customer's encryption key, not merely disabling it, so that every copy under that key, including backups and copies held by Khnum's hosting provider, is permanently unreadable and no one, including Khnum, can recover it. The parties treat this as destruction under this Agreement and under Tex. Bus. & Com. Code 521.052(b)(3); if any law treats that PHI as not destroyed, Section 11.7 applies to it. Khnum keeps no readable copy and will confirm the erasure in writing on request.

11.7 Where destruction is not feasible. The law may require Khnum to keep certain records. For any PHI Khnum cannot destroy, Khnum will extend this Agreement's protections to it for as long as Khnum holds it, limit its use and disclosure to the purposes that make destruction infeasible, and destroy it when that purpose ends.

11.8 Survival. Sections 3 through 9 and 11.5 through 12 continue after this Agreement ends for as long as Khnum holds any PHI or records about it.

12. General terms

12.1 Acceptance. Customer accepts this Agreement by checking its own read-and-agree box on Khnum's purchase page, or later through a link Khnum sends. The person who checks the box represents that they may bind Customer. That act is Customer's electronic signature, and its date is the Effective Date.

12.2 Electronic agreement. Both parties agree to enter into this Agreement electronically and intend it as a written agreement under the federal Electronic Signatures in Global and National Commerce Act and the Texas Uniform Electronic Transactions Act.

12.3 Record of acceptance. Khnum will keep the exact text, version, and publication date accepted, the name and title of the person who accepted it, Customer's account, and the date and time, with the Order Form, in write-once storage for at least six years after this Agreement ends. Customer may download the accepted Agreement at any time.

12.4 Order of precedence. For anything concerning PHI, this Agreement controls over the Terms and the Order Form. For everything else, the Terms control.

12.5 Governing law and venue. Texas law governs this Agreement. Any dispute under it will be brought in the state or federal courts sitting in Bexar County, Texas, as the Terms provide.

12.6 Independent contractor. Khnum performs under its own policies and controls as an independent contractor, not as Customer's agent.

12.7 Changes. Khnum may change this Agreement when a change in the HIPAA Rules or Texas law requires it, on at least 30 days' written notice. The change takes effect when the notice period ends, or on the compliance date of the change in law if that is earlier. Any other change requires both parties' written agreement.

12.8 Interpretation. Any ambiguity in this Agreement is to be read to permit compliance with the HIPAA Rules and Texas law. If a court holds any part unenforceable, the rest remains in effect. This Agreement creates rights only for Khnum and Customer.

12.9 Notices. Written notices to Khnum go to legal@khnumforge.com. Written notices to Customer go to the notice contact in Customer's Tyr account. Email is sufficient for any notice under Section 5.