DemandView
TermsPrivacyBAA

Business Associate Agreement

Last updated November 17, 2026

This Business Associate Agreement ("BAA") is between the med spa that accepts it in the DemandView app ("Covered Entity") and DemandView, a sole proprietorship owned by Megan Mahoney ("Business Associate"). It applies whenever Business Associate creates, receives, maintains or transmits Protected Health Information on Covered Entity's behalf in providing the DemandView service under the Terms of Service. It takes effect when an authorized person accepts it in the app.

Contents
  1. Definitions
  2. Permitted uses and disclosures
  3. Safeguards
  4. Reporting
  5. Subcontractors
  6. Individuals' rights
  7. Covered Entity's obligations
  8. Government access
  9. Term and termination
  10. Miscellaneous
  11. Acceptance

1. Definitions

Capitalized terms not defined here (including "Protected Health Information" or "PHI", "Breach", "Security Incident", "Subcontractor" and "Unsecured PHI") have the meanings given in HIPAA, the HITECH Act and their regulations at 45 C.F.R. Parts 160 and 164 (together, "HIPAA").

2. Permitted uses and disclosures

  • Business Associate may use and disclose PHI only to provide the DemandView services to Covered Entity (for example building retention, membership and survey lists and metrics), as this BAA permits, or as required by law.
  • Business Associate may use PHI for its own proper management and administration and to meet its legal responsibilities, as 45 C.F.R. 164.504(e)(4) allows.
  • Business Associate may de-identify PHI under 45 C.F.R. 164.514 and use de-identified data only to provide and improve the service.
  • Business Associate will request, use and disclose only the minimum necessary PHI, and will not use or disclose PHI in a way that would violate HIPAA if done by Covered Entity.
  • Business Associate will not sell PHI or use it for marketing on its own behalf.

3. Safeguards

Business Associate will use appropriate administrative, physical and technical safeguards, and comply with Subpart C of 45 C.F.R. Part 164 (the Security Rule) for electronic PHI, to prevent uses or disclosures not permitted by this BAA. These include encryption in transit, access limited to the owner of Business Associate, one-way hashing of patient identifiers in stored datasets, and prompt deletion of files containing names or contact details once they've served their purpose.

4. Reporting

Business Associate will 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 no later than 10 business days after discovery (and in any case within the 60 days HIPAA requires), with the information required by 45 C.F.R. 164.410 as it becomes available. Unsuccessful attempts that don't result in unauthorized access (such as pings, port scans or blocked log-in attempts) are reported here in aggregate and need no further notice.

5. Subcontractors

Business Associate will ensure that any Subcontractor that creates, receives, maintains or transmits PHI on its behalf agrees in writing to the same restrictions and conditions that apply to Business Associate, as 45 C.F.R. 164.502(e)(1)(ii) and 164.308(b)(2) require.

6. Individuals' rights

Within 15 business days of a request from Covered Entity, Business Associate will make PHI it holds in a Designated Record Set (if any) available for access or amendment, and provide the information needed for an accounting of disclosures, so Covered Entity can meet 45 C.F.R. 164.524, 164.526 and 164.528. Business Associate will forward to Covered Entity any such request it receives directly from an individual.

7. Covered Entity's obligations

  • Send Business Associate only the minimum PHI needed for the features it uses.
  • Obtain any consents or authorizations HIPAA and other laws require for the uses it asks Business Associate to support (including patient consent for marketing texts or emails).
  • Tell Business Associate about any restriction or revoked authorization that affects its use of PHI.

8. Government access

Business Associate will make its internal practices, books and records relating to PHI available to the Secretary of Health and Human Services to determine compliance with HIPAA.

9. Term and termination

This BAA lasts as long as Business Associate holds PHI for Covered Entity. If either party materially breaches it and doesn't cure the breach within 30 days of written notice, the other party may terminate this BAA and the services. When the services end, Business Associate will return or destroy all PHI it holds (including hashed datasets derived from it), keeping no copies, or, if that isn't feasible, extend this BAA's protections to the PHI and limit further use to the purposes that make return or destruction infeasible.

10. Miscellaneous

  • This BAA is interpreted to comply with HIPAA, and will be amended as needed to keep up with changes to it.
  • If this BAA conflicts with the Terms of Service, this BAA controls as to PHI.
  • Nothing in this BAA creates rights for anyone other than the parties.
  • Notices go to the email addresses on the account and to megan@demandviewmedia.com.

11. Acceptance

An authorized person at Covered Entity accepts this BAA in the DemandView app (Plan, credits and add-ons → Business Associate Agreement), recording their name, title, email and the date. Business Associate is bound when Covered Entity accepts it. Covered Entity may request a countersigned copy at any time.

Questions: megan@demandviewmedia.com · DemandView, owned and operated by Megan Mahoney, Arizona.