On this page

HIPAA compliance for CRM comes down to checks you run before any patient data goes in: a business associate agreement (BAA) for your plan and features, the vendor's HIPAA settings on, access controls and audit logs in use, a BAA for every tool that moves PHI in or out, and ad reporting that sends conversions instead of patient details. For which vendors sign a BAA and on which plans, see HIPAA-compliant CRM: which CRMs sign a BAA. Curve Compliance handles the last check: it credits the outcomes your CRM records to the original ad click and sends conversions server-side, under the BAA Curve signs on every plan and with PHI stripped before data reaches an ad platform.

Book a call. Want to see which CRM stages your ads produce without sending patient details to Meta or Google? Curve Compliance credits CRM outcomes to the original ad click and sends conversions server-side. Curve's team does the setup, typically live in about a week. Book a call with Curve.

When does CRM data count as PHI?

Most clinic CRMs hold it. Health information is individually identifiable when it “relates to the past, present, or future physical or mental health or condition of an individual; the provision of health care to an individual; or the past, present, or future payment for the provision of health care to an individual” and identifies the person or could reasonably be used to (45 CFR 160.103). A lead record with a name and phone number next to the service someone asked about, a consult date or a stage such as consult booked meets that test once your practice holds it.

That makes the CRM vendor your business associate: a person who, on behalf of a covered entity, “creates, receives, maintains, or transmits protected health information” (45 CFR 160.103). HHS lists a “Cloud service provider engaged to create, receive, maintain, or transmit electronic PHI (ePHI) (such as to process and/or store ePHI) on behalf of the covered entity” among its examples (HHS).

What should the BAA cover?

A covered entity may let a business associate hold PHI only with “satisfactory assurance that the business associate will appropriately safeguard the information” (45 CFR 164.502). The contract must “Establish the permitted and required uses and disclosures of protected health information by the business associate,” and require the vendor to “Report to the covered entity any use or disclosure of the information not provided for by its contract of which it becomes aware, including breaches of unsecured protected health information” and to pass the same terms down to its subcontractors (45 CFR 164.504).

For a CRM, the plan and product named in the BAA matter as much as the signature. HubSpot's Sensitive Data feature, which carries its BAA, is listed for Enterprise subscriptions (HubSpot). At Salesforce, “Customer and Salesforce must sign a BAA that includes the HIPAA Covered Service” you use (Salesforce). For agencies on HighLevel, “HIPAA must be enabled individually for each sub-account that requires it” (HighLevel). Confirm that the account your clinic's data sits in is the one the BAA names, then keep the signed copy with your compliance records.

What should you check before patient data goes into a CRM?

CheckWhat the rule or vendor saysHow to verify
BAA for your plan and product“satisfactory assurance that the business associate will appropriately safeguard the information” (45 CFR 164.502)A signed BAA on file that names the product, plan or account you use
Vendor HIPAA settings onHubSpot: “To store HIPAA-covered data, you must select both the Health/Medical Data checkbox and the We are a HIPAA-covered entity or business associate checkbox.” (HubSpot)A screenshot of the setting, plus which fields are marked as PHI
CRM in your risk analysis“Conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability of electronic protected health information” (45 CFR 164.308)The CRM and each integration listed in your current risk analysis
Unique logins and limited access“Assign a unique name and/or number for identifying and tracking user identity.” (45 CFR 164.312)No shared logins; roles that hide PHI fields from staff who don't need them
Audit logs reviewed“regularly review records of information system activity, such as audit logs, access reports, and security incident tracking reports” (45 CFR 164.308)Where the CRM's audit log lives, who reviews it and how often
Inbound tools under a BAAData transmission services that need routine access to PHI are business associates; the conduit exception is narrow (HHS)Each form, webhook and integration tool that sends leads in, with its BAA
Nothing with PHI goes to ad platformsMarketing uses or disclosures of PHI need an authorization (45 CFR 164.508)No lead lists, contact uploads or treatment-named stages sent to Meta or Google

Which CRM settings and access controls should be on?

The Security Rule asks for person or entity authentication, “procedures to verify that a person or entity seeking access to electronic protected health information is the one claimed,” and audit controls: “Implement hardware, software, and/or procedural mechanisms that record and examine activity in information systems that contain or use electronic protected health information” (45 CFR 164.312). In a CRM that means one login per person, roles that limit who sees health fields, and an audit trail someone reviews.

Vendors put the HIPAA switches in different places, and switching them on changes what the CRM can do. HubSpot says “Sensitive Data properties are unavailable in certain tools, including personalization tokens, sandboxes, chatbots and playbooks” (HubSpot). Zoho lets admins mark PHI fields and choose to “Restrict data transfer to third party apps” (Zoho). Keap is plain about the limit of any switch: “Enabling HIPAA Security Controls in Keap does not make your business HIPAA compliant” (Keap). Before you rely on them, talk to your counsel about how the settings fit your own policies.

What flows into the CRM from ad forms and webhooks?

Leads reach a CRM from website forms, ad platform lead forms, booking tools, call tracking and chat, often through webhooks or an integration tool in the middle. Each step that handles PHI for you needs its own check. HHS counts a “person that provides data transmission services with respect to PHI to a covered entity and that requires access on a routine basis to such PHI” as a business associate, and says “The conduit exception is limited to entities that only provide transmission services for PHI” (HHS). A tool that reads or maps the data to do its job is doing more than passing it along.

The CRM's BAA does not stretch to those tools. Keap says “the Keap BAA does not cover your use of third party products or services” (Keap), and Salesforce says the customer “is responsible for ensuring that its use of any third-party telephony service in conjunction with Agentforce Contact Center meets HIPAA requirements” (Salesforce). List every inbound connection, the fields each payload carries and the BAA that covers it. For safe routes, see connect lead forms to your CRM without PHI, lead routing from ad click to CRM and Facebook lead ads to a patient CRM.

What should never flow from the CRM to ad platforms?

Patient details. HIPAA requires that “a covered entity must obtain an authorization for any use or disclosure of protected health information for marketing,” with narrow exceptions (45 CFR 164.508). HHS applies the same logic to ad technology: “Regulated entities must ensure that all tracking technology vendors have signed a BAA and that there is an applicable permission prior to a disclosure of PHI,” and disclosures “to tracking technology vendors for marketing purposes, without individuals’ HIPAA-compliant authorizations, would constitute impermissible disclosures” (HHS tracking bulletin). A June 2024 court order vacated only the bulletin's part on IP addresses and unauthenticated public pages about health conditions or providers, not these lines.

In CRM terms, that rules out uploading lead or patient lists to build audiences, syncing lifecycle stages named after treatments, and sending contact details tied to a service. A CRM's own BAA doesn't change this, because the ad platform is a separate recipient. What Meta and Google need is narrower: that a conversion happened, and which click produced it.

How do you keep ad attribution without sending PHI?

Send the outcome, not the record. Curve Compliance receives outcomes from CRMs, booking systems and call tracking through incoming webhooks, and from offline conversion uploads out of a CRM or EHR, then credits each one to the original ad click. Conversions go server-side to Meta Conversions API, Google Ads, TikTok, Microsoft Advertising and LinkedIn and can use neutral event names; each platform receives only a fixed list of fields, and contact identifiers are off by default. Event Logs show what Curve sent to each platform and what the platform accepted.

Campaign Reporting then puts Meta and Google Ads spend next to Curve-tracked conversions per platform and campaign. HubSpot and WhatConverts outcomes show as CRM revenue and close rate. For GoHighLevel bookings, Curve's team sets up the handoff so bookings made days later are still credited to the original ad; see GoHighLevel bookings in Meta and Google Ads. To choose which stages count, see CRM lifecycle stages as conversions.

How Curve Compliance helps

Curve Compliance connects your CRM to your ad results without putting patient details in the ad platforms. Curve signs a BAA on every plan, is SOC 2 Type II, strips PHI before data reaches an ad platform, and checks every event for PHI-like patterns such as condition names, form answers or emails in URLs. It keeps ad attribution when a visitor leaves to book in IntakeQ, Calendly, Acuity, Jane App and other booking tools.

If your leads start on a form, Curve Forms host them under Curve's BAA with the ad and campaign attached to every lead. An export API lets a scheduled job on your side keep your CRM current. Curve's team does the setup, typically live in about a week. Book a call to see which CRM stages your ads produce, campaign by campaign.

Sources, checked November 20, 2026: 45 CFR 160.103; 45 CFR 164.308; 45 CFR 164.312; 45 CFR 164.502; 45 CFR 164.504; 45 CFR 164.508; HHS, business associates guidance; HHS OCR, online tracking technologies bulletin; HubSpot, Store Sensitive Data in HubSpot; Salesforce, Business Associate Addendum Restrictions; Zoho, HIPAA compliance with Zoho CRM; HighLevel, HIPAA compliance with HighLevel; Keap, HIPAA Security Controls; Pipedrive Terms of Service.

Frequently Asked Questions

What does HIPAA compliance for a CRM require?

A signed BAA that covers the CRM plan and features you use, the vendor's HIPAA settings switched on, and your own safeguards around it: unique logins, limited access, audit log review and a risk analysis that includes the CRM. Every tool that moves PHI into or out of the CRM needs the same review, and ad platforms should receive conversions, not patient details.

Does a BAA make my CRM HIPAA compliant?

No. The BAA is the contract; the settings, access rules and reviews are yours. Keap puts it plainly: “Enabling HIPAA Security Controls in Keap does not make your business HIPAA compliant” (Keap).

Do I need a BAA with the tool that sends form leads to my CRM?

Usually, if it handles PHI as part of its service. HHS says the conduit exception is limited to entities that only provide transmission services, and “Entities that access PHI on a regular or frequent basis to perform a service on behalf of a covered entity are not conduits” (HHS).

Can I sync CRM leads to Meta or Google Ads?

Not with PHI unless each person has signed a HIPAA authorization for that marketing use (45 CFR 164.508). Send conversions instead: Curve Compliance credits CRM outcomes to the original ad click and sends each platform only a fixed list of fields.

Which CRMs sign a BAA?

HubSpot, Salesforce, Zoho CRM, HighLevel and Keap offer one on named plans, products or add-ons, while Pipedrive's terms say its services “are not designed to comply with industry-specific regulations such as the Health Insurance Portability and Accountability Act (HIPAA)” (Pipedrive terms). See which CRMs sign a BAA for plans and conditions.

Do CRM audit logs matter for HIPAA?

Yes. The Security Rule requires audit controls that record activity in systems holding ePHI (45 CFR 164.312) and procedures to regularly review records such as audit logs and access reports (45 CFR 164.308).

Talk to Curve Compliance

Book a call. Want CRM outcomes counted as conversions in Meta and Google Ads, without patient details going to the ad platforms? Curve Compliance signs a BAA on every plan, and its team does the setup, typically live in about a week. Book a call with Curve.