On this page
A HIPAA compliant website builder is one that signs a business associate agreement (BAA) for the site features that handle patient information. Among the big builders, Wix offers PHI protection and a BAA on its Business, Plus, Elite, Business Elite and Enterprise plans (Wix), Squarespace says Acuity Scheduling is its only feature designed for HIPAA (Squarespace), and Webflow's terms ask you not to collect protected health information on the platform (Webflow terms). Whichever builder you use, Curve Compliance handles the ad tracking on those pages: one script replaces browser ad pixels, conversions go server-side with a fixed list of fields, and Curve strips PHI before data reaches an ad platform, under the BAA Curve signs on every plan.
Book a call. Running ads to a Wix, Squarespace, Webflow or WordPress site? Curve Compliance replaces the browser pixels with server-side conversions and checks every event for PHI-like patterns. Curve's team does the setup, typically live in about a week. Book a call with Curve.
What makes a website builder HIPAA compliant?
A builder becomes your business associate when it handles PHI for you. HIPAA defines a business associate as a person who, on behalf of a covered entity, “creates, receives, maintains, or transmits protected health information” (45 CFR 160.103), and 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). Before a business associate holds PHI, the covered entity needs “satisfactory assurance that the business associate will appropriately safeguard the information” (45 CFR 164.502). That assurance is the BAA.
Whether your builder needs one depends on what the site does. HHS says “Tracking technologies on many unauthenticated webpages do not have access to individuals’ PHI,” and a page listing your services, location and hours collects nothing about a patient (HHS tracking bulletin). Add a contact form, a booking widget, a chat box, a patient login or file uploads, and the platform that stores those submissions is handling PHI for you. A builder's BAA also has limits of its own. Wix says “While Wix provides tools and HIPAA-compliant hosting to help you comply with HIPAA, you are responsible for how you use and configure your site” (Wix). If you're unsure whether your site handles PHI, talk to your counsel.
Which website builders sign a BAA?
Each row comes from the builder's own page, opened today. Plan names are the vendor's; check the plan you are on before you collect patient information.
| Builder | BAA? | What the vendor says | Directory |
|---|---|---|---|
| Wix | Yes, on named plans | “HIPAA compliance is available with Business, Plus, Elite, Business Elite and Enterprise plans.” You activate PHI protection, then sign the BAA (Wix) | Wix |
| Squarespace | Only for Acuity Scheduling | “Acuity is the only Squarespace feature currently designed to offer services consistent with HIPAA obligations. Your Business Associate Addendum (BAA) doesn't cover other Squarespace features.” (Squarespace) | Squarespace, Acuity |
| Webflow | No | “Please do not collect Protected Health Information using the Platform as Webflow does not offer HIPAA compliant services at the present time.” (Webflow terms) | Webflow |
| Shopify | No | Shopify says “certain business activities are not supported by our platform, such as uploading Protected Health Information subject to HIPAA.” (Shopify AUP) | Shopify |
| WordPress.com | No public statement | Automattic's terms of service for WordPress.com, checked today, don't mention HIPAA (Automattic terms) | WordPress.com |
Self-hosted WordPress is software, not a vendor that signs anything, so the BAA question goes to the company that hosts the site and to each plugin vendor that stores form entries. For hosts, see HIPAA compliant website hosting; for Webflow in depth, see is Webflow HIPAA compliant.
Is the builder or the form the bigger risk?
Usually the form, and the apps around it. Builders keep pages, but patient details arrive through forms, booking tools, chat and inbox features, and each one is either inside the builder's BAA or outside it. Squarespace is direct about this: its contact form features, “like the form block, can't be used as part of a HIPAA compliant solution,” and “To collect secure patient information online for areas outside of Acuity, we recommend linking to an external, compliant service” (Squarespace).
Wix draws the line inside its own platform. Once PHI protection is on, “non-compliant Wix apps are automatically hidden from your App Market searches,” you're prompted to disconnect non-compliant Wix Inbox channels such as Facebook and Instagram, and forms built with old Wix Forms should be recreated with the new version (Wix). The practical test for any builder is the same: list every feature that receives patient input, and confirm each one is covered by a BAA, whether the builder's or another vendor's.
Do pixels on a builder site send PHI?
They can, and no builder's BAA covers Meta or Google. HHS says “Websites commonly use tracking technologies such as cookies, web beacons or tracking pixels, session replay scripts, and fingerprinting scripts,” and that disclosures “to tracking technology vendors for marketing purposes, without individuals’ HIPAA-compliant authorizations, would constitute impermissible disclosures” (HHS tracking bulletin). A pixel added site-wide fires on every page, including the form and the thank-you page. In June 2024 a federal court vacated the bulletin's guidance on connecting an IP address with a visit to a public page about health conditions or providers. HHS notes that the order covers a portion of the guidance; its example about details people type into an appointment page is a separate part.
Even Wix's own analytics change once PHI protection is on: Wix says “you lose analytic data that might previously have been available to you” (Wix). Clinics still need to know which ads produce bookings. The answer is to send conversions without PHI. Curve Compliance replaces browser ad pixels with one script, sends conversions server-side from Curve's servers to Meta, Google Ads, TikTok, Microsoft Advertising and LinkedIn, gives each platform only a fixed list of fields, and flags PHI-like patterns such as condition names, form answers or emails in URLs so they can be stopped at the source. To see what your builder site sends today, run the free website scan; it lists the pixels and trackers on a page. More on the setup at HIPAA-compliant conversion tracking.
How do you add HIPAA compliant forms to any builder?
You have three routes. Use the builder's own HIPAA forms where it offers them under its BAA, as Wix does with PHI protection on. Embed a form from a host that signs a BAA. Or link out to a hosted form page on a host that signs a BAA; Squarespace itself recommends “linking to an external, compliant service” for patient information outside Acuity. On a builder that doesn't sign a BAA, the condition is that patient information never reaches the builder, so read its terms before you embed anything that collects it. Compare form hosts in HIPAA compliant forms: form builders that sign a BAA.
Curve Forms are hosted by Curve under the BAA Curve signs on every plan. You can add one with a script that resizes itself, an iframe for locked-down CMS areas, a hosted link, a QR code or a custom domain. A built-in check shows when Curve has seen traffic from the published form, so you can confirm the install before sending visitors.
How Curve Compliance helps
Curve Compliance sits on top of whatever builder you use. One script replaces browser ad pixels; conversions go server-side to Meta Conversions API, Google Ads, TikTok, Microsoft Advertising and LinkedIn with a fixed list of fields; contact identifiers are off by default; and Event Logs show what Curve sent to each platform and what the platform accepted. When a visitor leaves to book in IntakeQ, Calendly, Acuity, Jane App or another booking tool, Curve keeps the ad attribution, and bookings made days later still match.
Curve Forms add HIPAA-hosted lead and intake forms with the ad and campaign attached to every lead, and form answers never sent to ad platforms. Curve is SOC 2 Type II, signs a BAA on every plan, and its team does the setup, typically live in about a week. Book a call to see what your builder site sends to ad platforms today and how Curve replaces it.
Sources, checked November 20, 2026: Wix, HIPAA compliance for your Wix site; Squarespace, Acuity Scheduling and HIPAA; Webflow Terms of Service, section 3.6; Shopify Acceptable Use Policy; Automattic Terms of Service (WordPress.com); HHS OCR, online tracking technologies bulletin; HHS, business associates guidance; 45 CFR 160.103; 45 CFR 164.502.
Frequently Asked Questions
What is a HIPAA compliant website builder?
A HIPAA compliant website builder is one that signs a BAA covering the site features that store or send patient information, such as forms and booking. Wix offers one on named plans, Squarespace only for Acuity, and Webflow and Shopify say their platforms are not for PHI.
Is Wix HIPAA compliant?
Wix can be, on its Business, Plus, Elite, Business Elite and Enterprise plans, once you activate PHI protection and sign its BAA (Wix). Wix says you remain responsible for how you configure the site and which apps you connect; see Wix in the BAA Directory.
Is Squarespace HIPAA compliant?
Only Acuity Scheduling is. Squarespace says Acuity “is the only Squarespace feature currently designed to offer services consistent with HIPAA obligations,” and its form block can't be part of a HIPAA compliant solution (Squarespace).
Is Webflow HIPAA compliant?
No. Webflow's terms say “Please do not collect Protected Health Information using the Platform as Webflow does not offer HIPAA compliant services at the present time” (Webflow terms). A practice can still keep a Webflow site for marketing pages if patient information never reaches Webflow and ad tracking runs outside it.
Is WordPress HIPAA compliant?
WordPress is software, so it depends on who hosts the site and which plugins store form entries. For WordPress.com, Automattic's terms checked today don't mention HIPAA (Automattic terms), and the BAA Directory lists no public statement.
Do I need a BAA with my website builder if my forms go elsewhere?
If no patient information is entered, stored or sent through the builder itself, the BAA question moves to the form host, booking tool and any other vendor that receives that information. Ad pixels on the builder still need to be kept away from PHI.
Does a HIPAA compliant builder make my ad pixels safe?
No. A builder's BAA covers the builder, and HHS says tracking vendors must have signed a BAA and a permission must apply before PHI is disclosed to them (HHS tracking bulletin). Server-side conversions with a fixed list of fields, as Curve Compliance sends them, keep PHI out of what Meta and Google receive.
Talk to Curve Compliance
Book a call. Want ad tracking and lead forms that hold up on any website builder? Curve Compliance replaces browser pixels with server-side conversions, and Curve Forms are hosted under the BAA Curve signs on every plan. Curve's team does the setup, typically live in about a week. Book a call with Curve.