Skip to main content
BAA Directory

Does Webflow sign a BAA?

The answer

Does not sign a BAA

No. Webflow's terms say it does not offer HIPAA compliant services and ask you not to collect Protected Health Information on the platform.

Site builders. Checked on the vendor's own pages on .

On this page

What Webflow says

“Please do not collect Protected Health Information using the Platform as Webflow does not offer HIPAA compliant services at the present time.”

Source: Webflow Terms of Service, section 3.6, HIPAA Non-Compliance, checked .

“You acknowledge that the Platform may not be compliant with the Health Insurance Portability and Accountability Act and amendments thereto (“HIPAA”) and you agree not to provide or enable End Users to provide Protected Health Information, as defined in HIPAA, in the Website Content or otherwise in connection with your use of the Platform.”

Source: Webflow Terms of Service, section 3.6, HIPAA Non-Compliance, checked .

What this means for ad tracking

The site builder is where your pixels live. Built-in marketing integrations and tag settings load ad pixels on every page, including service pages, forms and checkout.

Without a BAA, patient data should not be collected through Webflow itself, and browser pixels on service, booking and checkout pages tell ad platforms which page a visitor was on.

Curve Compliance closes that gap: it sends the conversion itself server-side, under a BAA it signs on every plan, so your campaigns keep a conversion signal without a pixel carrying patient data. Book a call to see it on your own funnel.

How Curve helps

  • Curve gives you a conversion signal that does not depend on Webflow or a browser pixel carrying patient details.
  • Server-side conversion tracking in place of pixels: conversions reach your ad platforms from Curve's server, not from the patient's browser.
  • PHI-like pattern detection checks every event before it goes out, and neutral event names keep conditions and treatments out of what the platforms see.
  • Identifiers are hashed with SHA-256 to each platform's requirements.
  • Attribution is kept through booking tools, so a booked appointment is credited to the ad that brought the patient in.
  • Consent management for your site, alongside the tracking.
  • A HIPAA-compliant setup done by Curve's team, in about a week, with a BAA signed on every plan.

Book a call with Curve and Curve's team will walk through your tracking setup with you.

Read the full guide

For the full picture on Webflow and patient data, read Is Webflow HIPAA Compliant? Website Builder Tracking Risks for Medical Practice Sites.

Frequently asked questions

Does Webflow sign a BAA?

No. Webflow's terms say it does not offer HIPAA compliant services and ask you not to collect Protected Health Information on the platform. In Webflow's words: “Please do not collect Protected Health Information using the Platform as Webflow does not offer HIPAA compliant services at the present time.” We checked Webflow's own pages on September 29, 2026.

Can I use Webflow with patient data?

Not under a BAA from Webflow, based on its own pages. Keep Protected Health Information out of Webflow, and check what it sends to other services.

Can I still track ad conversions that come through Webflow?

Yes, when the conversion reaches your ad platforms without health information. Curve sends conversions server-side under a BAA it signs on every plan, with neutral event names and SHA-256 hashed identifiers.

Does Curve Compliance sign a BAA?

Yes. Curve Compliance signs a BAA on every plan, and Curve's team does the HIPAA-compliant setup in about a week. Book a call to get started.

Sources

Last checked . Vendors change their plans and terms, so confirm the current terms with Webflow before you send it patient data.

See every tool in the BAA Directory.

Track ad conversions under a BAA

Curve signs a BAA on every plan. Curve's team sets up HIPAA-compliant conversion tracking for you in about a week, sending conversions server-side in place of pixels.

Book a call