On this page

A website contact form is HIPAA compliant when the company that hosts and stores the submissions signs a business associate agreement (BAA) with your practice, the system behind the form meets the HIPAA Security Rule, and what a person types stays away from ad tags and from any analytics vendor without a BAA. That holds even for a short contact form: HHS gives the example of tracking code that collects an email address or the “reason for seeking health care typed or selected by an individual” on a provider's web page, and says the HIPAA Rules then apply (HHS tracking bulletin). Curve Forms from Curve Compliance are HIPAA-compliant contact, lead and intake forms hosted by Curve under the BAA it signs on every plan, with the ad and campaign that brought each person attached to the lead and form answers never sent to ad platforms.

Book a call. Want a contact form that keeps answers under a BAA and still shows which ad brought each lead? Curve Forms are hosted by Curve 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.

When does a website contact form collect PHI?

Protected health information (PHI) is individually identifiable health information held or sent electronically or in any other form (45 CFR 160.103). The definition reaches information that “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 that identifies the person, or could reasonably be used to identify them. A clinic's contact form usually asks for a name, an email address or phone number, and a message. Once a person names a symptom, a treatment they want or an appointment, the submission ties health information to someone you can identify.

HHS makes the same point about public web pages. Tracking on a page that lets people “schedule appointments or use a symptom-checker tool without entering credentials may have access to PHI in certain circumstances,” and when that code collects an email address or the reason someone is seeking care, “the regulated entity is disclosing PHI to the tracking technology vendor, and thus the HIPAA Rules apply” (HHS tracking bulletin). In June 2024 a federal court vacated one portion of that bulletin: the part about connecting an IP address with a visit to a public page about health conditions or providers. The appointment example above turns on details a person types in, not on the page visit alone.

A question about parking or opening hours, with no health detail, is a different case. You can't control what people type into a free-text box, though, so set up any contact form on a clinic site as one that may receive PHI. If you're unsure whether a particular form is in scope, talk to your counsel.

Which website form tools sign a BAA?

A company that stores form submissions for a clinic is a business associate. 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), and a covered entity may let a business associate hold PHI only “if the covered entity obtains satisfactory assurance that the business associate will appropriately safeguard the information” (45 CFR 164.502). What the common tools say on their own pages today:

Form toolBAA for form submissions?What the vendor says
Squarespace form blockNo“Other parts of the Squarespace platform, including contact form features like the form block, can't be used as part of a HIPAA compliant solution.” Acuity Scheduling is the HIPAA-enabled exception (Squarespace)
Webflow formsNo“Please do not collect Protected Health Information using the Platform as Webflow does not offer HIPAA compliant services at the present time.” (Webflow terms)
Wix (site-level PHI protection)Yes, for the site, once you activate PHI protection and sign the BAA“HIPAA compliance is available with Business, Plus, Elite, Business Elite and Enterprise plans.” Wix says data in forms built with old Wix Forms may not be handled as securely, and to recreate them with the new version (Wix)
JotformYes, in its dedicated HIPAA environment“The dedicated HIPAA environment is available as an upgrade for eligible customers on the Gold subscription and on Jotform Enterprise.” (Jotform)
Cognito FormsYes, on its Enterprise plan“Your organization must be on the Cognito Forms Enterprise plan (and not a trial) in order to enter into a BAA.” (Cognito Forms)

A BAA covers only what the vendor names in it. Squarespace says your BAA “doesn't cover other Squarespace features” (Squarespace), and Wix says “HIPAA compliance depends on your own setup, chosen apps, and how you manage sensitive health data” (Wix). Check each tool in the BAA Directory, for example Jotform, Cognito Forms and Squarespace, and compare more builders in HIPAA compliant forms: form builders that sign a BAA.

What must the form itself do?

The BAA is the contract. The Security Rule sets the technical floor for the system behind the form (45 CFR 164.312), and the Privacy Rule's minimum necessary standard limits how PHI is used and shared (45 CFR 164.502):

  • Protect the submission in transit. The rule: “Implement technical security measures to guard against unauthorized access to electronic protected health information that is being transmitted over an electronic communications network.” Serve the form page and its submission over HTTPS.
  • Limit who can see submissions. Use “technical policies and procedures for electronic information systems that maintain electronic protected health information to allow access only to those persons or software programs that have been granted access rights.” Give inbox access only to the staff who answer leads.
  • Keep a record of access. The audit controls standard asks for mechanisms “that record and examine activity in information systems that contain or use electronic protected health information.”
  • Ask for less. When it uses or discloses PHI, a covered entity must “make reasonable efforts to limit protected health information to the minimum necessary to accomplish the intended purpose of the use, disclosure, or request.” Collecting less leaves less to protect. A contact form needs a way to reach the person and enough context to route the request. A dropdown for the service or location keeps answers short, while a large free-text box invites detail.
  • Keep ad tags off the form. Browser pixels and session replay scripts on the form page can read what people type, which the next section covers.

Can the thank-you page fire Meta or Google tags?

Not with PHI in what they send. HHS says “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 that disclosures “to tracking technology vendors for marketing purposes, without individuals’ HIPAA-compliant authorizations, would constitute impermissible disclosures” (HHS tracking bulletin).

On a contact form the risk is specific. A pixel on the thank-you page receives that page's URL, so a form that passes the chosen service or answers in the redirect URL hands them to the pixel. A tag on the form page itself runs alongside the fields, and session replay scripts record “mouse movements, clicks, and typing” (HHS tracking bulletin).

The safer pattern is to send the conversion, not the content. With Curve Compliance, one script replaces browser ad pixels, and conversions go server-side from Curve's servers to the Meta Conversions API and Google Ads, with each platform receiving only a fixed list of fields. Curve strips PHI before data reaches an ad platform. To see which tags fire on your contact page today, run Curve's free website scan, which lists the pixels and trackers on a page.

What should the notification email contain?

As little as your team can work with. Many form tools email each submission to the practice, which puts the patient's message in a mailbox and on every device that syncs it. HHS's answer on email with patients says providers may use it if they “apply reasonable safeguards when doing so,” such as “limiting the amount or type of information disclosed through the unencrypted e-mail” (HHS FAQ). Squarespace says that for HIPAA-enabled Acuity accounts, “Email notifications we send you won’t include client form answers” (Squarespace). Cognito Forms says “PHI should be marked as protected to prevent transmission via email” unless patients have signed a waiver (Cognito Forms).

A practical setup is a notification that says a new submission is waiting and links to a secure inbox, where staff read the details. If the full message does go by email, use an email service that signs a BAA; see HIPAA compliant email providers.

How Curve Compliance helps

Curve Forms are contact, lead and intake forms built and hosted by Curve under the BAA Curve signs on every plan, so a submission never passes through a third-party form tool. Build a stacked form or a guided flow with one step per card. Add logic that shows or hides fields based on earlier answers, keep privacy consent and marketing consent as separate checkboxes, and set screening outcomes by age, service area or insurance, each with its own end screen.

Every lead lands in the Leads inbox with its answers, UTMs and ad click ID, attribution and staff notes. Notification emails go to your team with Reply-to set to the respondent, or Curve can send a detail-free notification that links to the inbox. Form events reach Meta, Google Ads and your other destinations server-side through your event mappings; form answers, page titles and free text are never sent to ad platforms. Curve is SOC 2 Type II, and its team does the setup, typically live in about a week. Book a call to see a contact form that ties each lead to the ad that brought it.

Sources, checked November 20, 2026: HHS OCR, online tracking technologies bulletin; HHS, business associates guidance; HHS FAQ, email with patients; 45 CFR 160.103; 45 CFR 164.312; 45 CFR 164.502; Squarespace, Acuity Scheduling and HIPAA; Webflow Terms of Service, section 3.6; Wix, HIPAA compliance for your Wix site; Jotform, how to enable the HIPAA environment; Cognito Forms, HIPAA compliance.

Frequently Asked Questions

What is a HIPAA compliant contact form?

A HIPAA compliant contact form is a website form whose host signs a BAA with your practice and protects submissions under the HIPAA Security Rule, and that keeps what people type away from ad tags and from any analytics vendor without a BAA.

Is a Squarespace contact form HIPAA compliant?

No. Squarespace says contact form features like the form block “can't be used as part of a HIPAA compliant solution,” and that Acuity is its only feature designed for HIPAA (Squarespace). See Squarespace in the BAA Directory.

Is a Webflow form HIPAA compliant?

No. Webflow's terms ask customers not to collect protected health information on the platform, because “Webflow does not offer HIPAA compliant services at the present time” (Webflow terms). More in is Webflow HIPAA compliant.

Are Wix forms HIPAA compliant?

They can be. Wix offers site-wide PHI protection and a BAA on its Business, Plus, Elite, Business Elite and Enterprise plans, and says forms built with old Wix Forms should be rebuilt with the new version (Wix).

Does a contact form need a BAA?

Yes, when the form collects PHI for a covered entity. The company that hosts and stores the submissions is a business associate under 45 CFR 160.103, so you need a BAA with it before it holds that data.

Can I put a Meta pixel on a contact form thank-you page?

Not if it can send PHI to Meta. HHS says tracking vendors must have signed a BAA and a permission must apply before PHI is disclosed (HHS tracking bulletin); sending the conversion server-side with a fixed list of fields, as Curve Compliance does, keeps form answers away from Meta.

Should the notification email include the patient's message?

Only if your email service signs a BAA and your team needs the details there. A notification that says a submission is waiting and links to a secure inbox keeps the message out of email.

Talk to Curve Compliance

Book a call. Want a contact form that keeps answers under a BAA and still shows which ad brought each lead? Curve Forms are hosted by Curve under the BAA it signs on every plan. Curve's team does the setup, typically live in about a week. Book a call with Curve.