Business Associate Addendum ("BAA")
Business Associate Addendum
Peaberry Software Inc. d.b.a. Customer.io
This Business Associate Addendum (this “BAA”) dated ___________________(the “Effective Date”), is entered into between Peaberry Software Inc. d.b.a. Customer.io (“Customer.io”) and the customer agreeing to the terms below (“Company,” “you” and “your”), and supplements, amends and is incorporated into, as applicable, the Customer.io Cloud Services Agreement Terms of Service between Customer.io and Company (as at any time amended, restated, supplemented or otherwise modified, the “Services Agreement”). You and Customer.io shall be referred to collectively as the “Parties” and individually as a “Party”.
This BAA defines the rights and responsibilities of each Party with respect to PHI, as defined below, under the Administrative Simplification Section of the Health Insurance Portability and Accountability Act of 1996 and the regulations promulgated thereunder, as each may be amended from time to time, including by the Health Information Technology for Economic and Clinical Health Act (“HITECH Act”) and the Modifications to the HIPAA Privacy, Security, Enforcement, and Breach Notification Rules Under the Health Information Technology for Economic and Clinical Health Act and the Genetic Information Nondiscrimination Act; Other Modifications to the HIPAA Rules; Final Rule (collectively, “HIPAA”).
This BAA shall be applicable only in the event and to the extent Customer.io meets, with respect to you and as to your use of the Services (as defined in the Services Agreement), the definition of a Business Associate set forth at 45 CFR §160.103.
1. Defined Terms.
Capitalized terms used but not otherwise defined shall have the same meaning as in either (a) HIPAA, or (b) the Services Agreement. For the purposes of this BAA, capitalized terms shall have the following meanings:
“Breach Notification Rule” shall mean the Standards for Notification in the Case of Breach of Unsecured Protected Health Information at 45 CFR part 160 and part 164, subparts A and D.
“CFR” shall mean the Code of Federal Regulations.
“Individual” shall have the same meaning as the term “individual” in 45 CFR § 160.103 and shall include a person who qualifies as a personal representative in accordance with 45 CFR § 164.502(g).
“PHI” shall have the same meaning as the term “protected health information” in 45 CFR § 160.103, limited to the information created, received, maintained, or transmitted by Customer.io, in its capacity as a Business Associate, from you or on your behalf.
“Privacy Rule” shall mean the Standards for Privacy of Individually Identifiable Health Information at 45 CFR part 160 and part 164, subparts A and E.
“Security Rule” shall mean the Health Insurance Reform: Security Standards at 45 CFR part 160 and part 164 subparts A and C.
“Secretary” shall mean the Secretary of the Department of Health and Human Services or the Secretary’s designee.
“Unsecured Communications” shall mean the transmission of plain text email, SMS, Push, webhooks, communications using the public Internet or open networks or similar unsecured communications.
2. Obligations and Activities of Customer.io.
- Customer.io agrees not to use or disclose PHI other than as permitted or required by the Services Agreement, this BAA or as Required by Law, or if such use or disclosure does not otherwise cause a Breach of Unsecured PHI.
- Customer.io agrees to comply with the applicable provisions of the Security Rule and to provide physical, technical and administrative safeguards designed to prevent impermissible uses and disclosures of PHI, including any applicable safeguards required by the Services Agreement.
- If Customer.io agrees as part of this BAA to carry out a Covered Entity obligation of yours under the Privacy Rule, then Customer.io will comply with the requirements of the Privacy Rule applicable to the Covered Entity.
- Customer.io agrees to mitigate, to the extent commercially reasonable and reasonably practicable, any harmful effect that is known to Customer.io of a use or disclosure of PHI by Customer.io or its Subcontractors in breach of the requirements of this BAA.
- Without unreasonable delay, Customer.io agrees to report to you any Breach of Unsecured PHI as and to the extent required under the Breach Notification Rule. Notwithstanding the generality of the foregoing, the Parties acknowledge that there may be minor or unsuccessful attempts to access Unsecured PHI, which make a real-time reporting requirement impractical for both Parties. Therefore, the Parties agree that (i) notification under this Section is not required for any such unsuccessful attempts when they do not result in a Breach of Unsecured PHI, including, for example, pings against network devices; port scans; attempts to log on to a system or database with an invalid password or username; and detection of malware, (ii) Customer.io’s ability to report on system activity is limited by, and to, the Services that you have purchased (and does not extend to networks or systems operated by third parties as part of general Internet connectivity). Customer.io undertakes no obligation to report network security related incidents or events that occur on the Customer.io managed network, but do not directly involve your PHI, and (iii) if your use of the Services includes the transmission of Unsecured Communications, Customer.io shall have no obligation to monitor or attempt to monitor the access to the Unsecured Communications, including whether they are stored by or potentially accessed by third parties during ordinary transmission activities.
- Customer.io agrees to obtain from any Subcontractor that it permits to create, receive, maintain or transmit PHI, reasonable assurances that it will adhere to substantially similar restrictions and conditions that apply to Customer.io under this BAA or applicable law with respect to the PHI. For the avoidance of doubt, this does not apply to third party conduits and providers who are involved in the transmission, routing, storage or receipt of communications that is inherent in the delivery of the Services.
- All PHI maintained by Customer.io on your behalf will be available to you through the Services in a time and manner that reasonably allows you to comply with the requirements under 45 CFR § 164.524 of the Privacy Rule. Customer.io shall not be obligated to provide any PHI directly to any Individual or person other than you.
- You may use the Services to make any amendments to PHI maintained by Customer.io on your behalf in a time and manner that reasonably allows you to comply with the requirements under 45 CFR § 164.526 of the Privacy Rule.
- You acknowledge that Customer.io is not required by this BAA to make disclosures of PHI to Individuals or any person other than you and that Customer.io, therefore, does not expect to maintain documentation of disclosure as described in 45 CFR § 164.528 of the Privacy Rule. In the event that Customer.io does make such disclosure, Customer.io shall provide to you, promptly on your request, documentation of disclosures as would be required for you to respond to a request by an Individual for an accounting of disclosures in accordance with 45 CFR §164.504(e)(2)(ii)(G) and §164.528 of the Privacy Rule.
- In the event that a request for access, amendment or an accounting is made directly to Customer.io, Customer.io shall forward the request to you without undue delay.
- Customer.io agrees to make internal practices, books and records relating to the use and disclosure of PHI received from Company available to the Secretary for purposes of the Secretary determining compliance with the Privacy Rule; provided, however, that time incurred by Customer.io in complying with any such request that exceeds its normal customer service parameters or any other extraordinary compliance requirements under this BAA shall be charged to you at Customer.io’s then-current standard hourly rate for professional services. Nothing in this section waives any legal privilege or discovery protection, including the trade secrets or confidential commercial information.
3. Permitted Uses and Disclosures by Customer.io.
Except as otherwise limited in this BAA or the Services Agreement, Customer.io may use or disclose PHI:
- in connection with the Services for you or on your behalf as specified in the Services Agreement, as long as the use or disclosure would not violate the Privacy Rule if done by you (except pursuant to Sections 3(b) and (c);
- as Required by Law;
- for the proper management and administration of Customer.io or to carry out its legal, regulatory or contractual responsibilities, as long as, with respect to any disclosure, Customer.io obtains reasonable assurances from the person or entity to whom the PHI is disclosed that it will remain confidential and used or further disclosed only as Required By Law or for the purpose for which it was disclosed to such person or entity, and that such person or entity will notify Customer.io of any Breaches of Unsecured PHI;
- to create de-identified information or Limited Data Sets;
- to provide Data Aggregation Services; and
- to report violations of law to appropriate Federal and State authorities, consistent with 45 CFR §164.502(j)(1).
4. Your Obligations.
- You shall not include any limitations in your Notice of Privacy Practices that would limit or prohibit Customer.io’s provision of the Services or its use or disclosure of PHI. You shall obtain all necessary authorizations, consents and permission by Individuals to permit Customer.io to provide its Services and use or disclose PHI as permitted or required under this BAA or the Services Agreement.
- You shall notify Customer.io of any restriction to the use or disclosure of PHI that you have agreed to or is required to comply with 45 CFR §164.522 to the extent that the restriction may affect Customer.io’s use or disclosure of PHI. In the event of such restriction, Company (i) acknowledges that such restrictions may impact Customer.io’s ability to provide Services or to otherwise provide support for Company’s account in a timely manner; (ii) waives any claim of breach of Customer.io’s Services or such support obligations (including response times under the Services Agreement) arising from such restrictions; and (iii) agrees that Customer.io has the right to change the pricing or other terms relating to the Services that may be affected by the restrictions.
- You agree that you will not request Customer.io to create, receive, maintain, transmit, use or disclose PHI in any manner that would not be permissible under the Privacy Rule, Security Rule or Breach Notification Rule if done by you or by Customer.io.
- You agree, as part of your security and other obligations to implement and maintain appropriate safeguards as required for you to comply with the Security Rule, Privacy Rule and Breach Notification Rule as applicable to you and your use of the Services. This includes, without limitation, (i) implementing reasonable safeguards required by 45 CFR §164.530(c) of the Privacy Rule; (ii) performing a risk analysis and implementing a risk management plan with respect to PHI; (iii) reasonably limiting the amount or type of information used and disclosed through the Services; (iv) notifying Individuals of the unsecure nature of Unsecured Communications and obtaining permission or instructions from the Individual to communicate through these Unsecured Communications channels; (v) permitting Individuals to utilize alternative secure electronic methods to receive confidential communications from you; (vi) verifying the recipient’s address and that it is correctly entered into the Services prior to using the Services to transmit PHI; (vii) including a privacy statement and providing a contact to whom a recipient can report a misdirected message; and (viii) encrypting PHI transmitted through the Services where appropriate or required by the Security Rule (such as through the use of encrypted attachments). The Parties agree and acknowledge that implementing the safeguards described in this Section do not guarantee that you are in compliance with all legal requirements, including HIPAA.
- You acknowledge and agree that the Services include the transmission of Unsecured Communications. Although Customer.io encrypts information at rest, you should encrypt, or take other appropriate actions with respect to, any sensitive data, including PHI, you use or disclose in conjunction with the Services. You understand, acknowledge and agree that Unsecured Communications sent using the Services may be unsecured, may be intercepted by unauthorized third parties and may be maintained, used and disclosed by third parties (such as a recipient’s email service provider) who have no obligations to you or Customer.io with regards to the treatment of the communications. Although Services include support for TLS, content will be transmitted even if the recipient does not also support TLS, resulting in an unencrypted transmission. You agree to inform, and it is your sole responsibility to inform, your customers and end users of these aspects of the Services.
5. Term and Termination.
- The term of this BAA shall continue for the term of your use of the Services that would require you to enter into a business associate agreement.
- If either Party materially breaches this BAA, then the non-breaching Party may terminate this BAA, as well as those provisions of the Services Agreement that would require you to enter into a business associate agreement, on 30 days’ written notice to the breaching Party unless the breach is cured within the 30-day period.
- Upon your reasonable request, Customer.io shall destroy all PHI that is in Customer.io’s possession. Customer.io shall retain no copies of the PHI. In the event that Customer.io determines that destroying the PHI is infeasible, Customer.io shall extend the protections of this BAA to PHI and limit further uses and disclosures of PHI to those purposes that make the destruction infeasible, for as long as Customer.io maintains PHI. This section does not require Customer.io to segregate any PHI from other information maintained on Customer.io’s servers.
6. Miscellaneous.
- Each Party agrees to take reasonable actions to amend this BAA as is necessary for each Party to comply with the requirements of HIPAA as they may be amended from time to time; provided, however, that if an amendment would materially increase the cost of Customer.io in providing Customer.io Service, then Customer.io shall have the option to terminate the BAA and those provisions of the Services Agreement that would require you to enter into a business associate agreement on thirty (30) days advance notice.
- Nothing express or implied in this BAA is intended to confer, nor shall anything in this BAA confer, upon any person or entity other than the Parties and their respective successors or assigns, any rights, remedies, obligations or liabilities whatsoever.
- Any ambiguity in this BAA shall be resolved to permit each of the Parties to comply with HIPAA.
7. Execution.
The Parties, intending to be duly bound, hereby execute this BAA:
Peaberry Software, Inc. d/b/a Customer.io
Full Name:
Brad Harrison
Position:
General Counsel
Address:
Customer.io, 9450 SW Gemini Dr.,
Suite 43920, Beaverton, Oregon 97008-7105
Other information necessary for the contract to be binding (if any):
Signature:
Company:
Full Name:
Position:
Address:
Other information necessary for the contract to be binding (if any):
Signature: