On this page
Data integration tools with a BAA include Improvado, Fivetran, Hevo Data and RudderStack, which each say on their own sites that they offer or can sign one, and Twilio Segment, whose BAA is available on its Business Tier plan; for ad conversions, Curve Compliance signs a BAA on every plan and sends conversions server-side with PHI stripped before data reaches an ad platform. On Supermetrics' security page we found no BAA statement, checked November 20, 2026. Curve's Campaign Reporting puts Meta and Google Ads spend next to the conversions Curve tracked.
Book a call. Moving marketing data mainly to get conversions into Meta and Google Ads and see spend against results? Curve Compliance sends conversions server-side under the BAA it signs on every plan, and Curve's team does the setup, typically live in about a week. Book a call with Curve.
Which data integration tools sign a BAA?
Each row quotes the vendor's own page, opened November 20, 2026. A BAA usually depends on the plan and on the products it names, so confirm both before any patient data flows.
| Tool | BAA, in the vendor's words | Plan or condition | Also on that page |
|---|---|---|---|
| Improvado | “Improvado offers Business Associate Agreements to customers who require them” (Improvado Trust) | Its plan table lists HIPAA as included on Growth and Enterprise, not on MCP Only or Starter (Improvado plans) | “Improvado holds a SOC 2 Type II report, examined by BARR Advisory.” |
| Fivetran | “Meet HIPAA requirements with a business associate agreement signed by Fivetran.” (Fivetran) | None stated next to the BAA line | SOC 1 and SOC 2, ISO 27001, PCI DSS Level 1 |
| Hevo Data | “We offer Data Processing and Business Associate Agreements” (Hevo Data) | None stated on that page | SOC 2 Type II; “Sensitive fields like PII or PHI can be excluded, masked, or hashed” |
| RudderStack | “We comply with HIPAA requirements for PHI and can sign a BAA” (RudderStack) | None stated on that page | SOC 2 Type 2; “We do not store your data” |
| Twilio Segment | “Twilio BAAs are available to customers on a Business Tier plan.” (Twilio) | Business Tier plan, on a workspace that shows the HIPAA badge | “Segment is a HIPAA eligible platform” |
| Supermetrics | No BAA statement on its security page (Supermetrics) | None found | “We undergo annual SOC 2 Type II audits and are ISO 27001 certified.” Also: “We do not permanently store the data that you load using our data integrations.” |
Curve's BAA Directory tracks more vendors: see Twilio Segment and RudderStack, warehouses such as Snowflake and Google Cloud, and automation tools such as Zapier, Make and n8n in the automation and workspace category. The full list is in the BAA Directory.
What does a BAA cover in a marketing data pipeline?
HHS says a BAA must “describe the permitted and required uses and disclosures of PHI by the business associate” (HHS). It binds the vendor that signs it, for the services it names. Twilio, for example, asks customers to check that the Segment products they will use are on its list of HIPAA Eligible Products and Services before configuring a HIPAA workflow (Twilio).
A marketing pipeline has several hops: the source apps, the integration tool, the warehouse, the BI or reporting tool, and sometimes an ad platform at the end. Each vendor that handles PHI for you needs its own BAA. Further down the chain, HHS says “A business associate must establish a BAA with its subcontractor before disclosing PHI to the subcontractor,” and “A covered entity is not required to establish a BAA directly with a subcontractor of its business associate” (HHS). So your BAA with an integration tool covers that tool, and the tool's own vendors sit under its agreements with them.
Where does PHI enter a marketing data pipeline?
Through the connectors that carry people rather than ads. A connector that pulls campaign spend, clicks and impressions moves numbers about ads. Connectors that pull lead form submissions, CRM contacts, call recordings, appointment records or website events tied to a visitor move data about people, and for a clinic that is where PHI usually comes in.
Not storing data is not the same as not handling it. Some tools say they keep data only briefly, and HHS reads the conduit exception narrowly: it “is limited to entities that only provide transmission services for PHI,” 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).
Some tools let you keep health details out at the source. Hevo says “Sensitive fields like PII or PHI can be excluded, masked, or hashed” (Hevo Data), and Segment can encrypt fields you mark in its Privacy Portal before they reach cloud-mode destinations (Twilio). Excluding a field at setup is easier than cleaning it out of a warehouse later.
Do you need a BAA if the pipeline only moves ad spend data?
Campaign-level spend, clicks and impressions describe ads rather than people, so a connector limited to them carries far less risk. Few marketing pipelines stay that narrow: the next request is usually to join spend with leads, bookings or revenue by person, and that join brings PHI in. HHS is direct about the alternative to a BAA: “If a regulated entity does not want to create a business associate relationship with a vendor that meets the definition of business associate, it cannot disclose PHI to such a vendor without individuals' authorizations” (HHS). HHS notes on that page that a federal court vacated a portion of the bulletin on June 20, 2024, the part about connecting an IP address with a visit to an unauthenticated public page about specific health conditions or healthcare providers.
Whether a given pipeline needs a BAA depends on what it carries and on your role under HIPAA, so talk to your counsel before you decide one doesn't. In practice, map every connector, mark the ones that carry people, and get a BAA in place before the first of those syncs.
How do pipelines, warehouses and ad tracking fit together?
They do different jobs. A data integration tool moves data from sources into a warehouse such as Snowflake or BigQuery, and a BI tool reads it from there. Ad tracking decides what reaches Meta, Google Ads and the other ad platforms. HHS describes one way to handle a tracking vendor that won't sign: a regulated entity can “establish a BAA with another vendor, for example a Customer Data Platform vendor, that will enter into a BAA with the regulated entity to de-identify online tracking information that includes PHI” before anything goes on (HHS).
Ad tracking is the layer Curve Compliance covers. Curve replaces browser ad pixels with one script and sends conversions server-side to Meta, Google Ads, TikTok, Microsoft Advertising and LinkedIn. Each platform receives only a fixed list of fields, Curve strips PHI before data reaches an ad platform, and Event Logs show what Curve sent and what each platform accepted. Keep your pipeline for the warehouse, and let ad tracking decide what the ad platforms see. For the two side by side, see Curve Compliance vs Improvado, Curve vs RudderStack and marketing platform vs data pipeline tools.
How Curve Compliance helps
Curve Compliance signs a BAA on every plan and is SOC 2 Type II. It keeps ad attribution when a visitor leaves to book in tools such as Calendly, Acuity, Jane App or IntakeQ, receives outcomes from booking systems, CRMs and call tracking through incoming webhooks, and credits each one to the original ad click. Campaign Reporting puts Meta and Google Ads spend next to the conversions Curve tracked, per platform and campaign, with five attribution models, and HubSpot and WhatConverts outcomes show as CRM revenue and close rate.
For teams that want answers in Claude or ChatGPT, Curve MCP returns aggregate campaign and conversion results while patient-level data stays in Curve. Curve's team does the setup, typically live in about a week. Book a call to see which conversions Curve would send to Meta and Google Ads from your funnel.
Sources, checked November 20, 2026: Improvado Trust; Improvado plans; Fivetran Security; Hevo Data Security; RudderStack Security; Twilio, HIPAA Eligible Segment; Supermetrics Security; HHS, business associates; HHS, online tracking bulletin.
Frequently Asked Questions
Which data integration tools sign a BAA?
On their own sites, Improvado, Fivetran, Hevo Data and RudderStack say they offer or can sign a BAA, and Twilio offers one for Segment on its Business Tier plan. We found no BAA statement on Supermetrics' security page, checked November 20, 2026.
Does Improvado sign a BAA?
Yes. Improvado's Trust page says “Improvado offers Business Associate Agreements to customers who require them, and takes on the responsibilities of a Business Associate under that contract” (Improvado Trust). Its plan table lists HIPAA as included on the Growth and Enterprise plans and not included on MCP Only or Starter (Improvado plans); see Curve Compliance vs Improvado.
Does Fivetran sign a BAA?
Fivetran's security page lists a HIPAA BAA (Fivetran): “Meet HIPAA requirements with a business associate agreement signed by Fivetran.” Ask Fivetran which plans and products its BAA covers before any connector carries PHI.
Does Supermetrics sign a BAA?
We found no BAA statement on Supermetrics' security page on November 20, 2026. That page says “We undergo annual SOC 2 Type II audits and are ISO 27001 certified,” so ask Supermetrics directly before any connector carries PHI (Supermetrics).
Does RudderStack sign a BAA?
Yes. RudderStack's security page says “We comply with HIPAA requirements for PHI and can sign a BAA” and “we do not store your data” (RudderStack); see Curve vs RudderStack.
Which Segment plan includes a BAA?
The Business Tier. Twilio's docs say “Twilio BAAs are available to customers on a Business Tier plan,” and the workspace should show the HIPAA badge before you send PHI (Twilio); see is Twilio Segment HIPAA compliant.
What is the difference between a data pipeline and HIPAA compliant ad tracking?
A data pipeline moves data from your sources into a warehouse or reporting tool for analysis. HIPAA compliant ad tracking decides what reaches the ad platforms: Curve Compliance sends conversions server-side, gives each platform a fixed list of fields and strips PHI before data reaches an ad platform, under the BAA it signs on every plan.
Talk to Curve Compliance
Book a call. Want conversions in Meta and Google Ads and spend next to results, without PHI reaching the ad platforms? Curve Compliance signs a BAA on every plan, and Curve's team does the setup, typically live in about a week. Book a call with Curve.