HIPAA Compliant Website: Forms, Trackers and Hosting After the 2024 Ruling
· · Updated

A HIPAA compliant website doesn’t exist as a product you can buy or a badge you can display. HIPAA governs how covered entities and their vendors handle protected health information, and most of its website duties start when a site collects, stores or passes along that information for a covered entity. So ask where on the site that information appears and which vendors can see it. On the evidence below, the answer sits in the forms, the tracking scripts and the hosting.
Short answer: no website is HIPAA compliant by default. Check what your forms send to vendors and which scripts run on booking and symptom pages, then get a signed BAA from every host or tool that handles PHI.
This is the guide we’d give an executive before a redesign or a vendor review. It draws on the text of the rules and HHS guidance, plus the federal court decision that changed how the tracking rules read.
This isn’t legal advice. Your privacy officer and healthcare counsel decide what applies to your organization.
Does HIPAA apply to your website at all?
It depends on who runs the site and what the site touches. The regulation defines a covered entity as a health plan, a health care clearinghouse, or a health care provider who transmits health information electronically in connection with certain transactions (45 CFR 160.103). A business associate is a person who creates, receives, maintains or transmits protected health information on a covered entity’s behalf. Your web agency, your hosting company and your form tool can all land in that second group.
Protected health information is individually identifiable health information, meaning details that relate to a person’s health or payment for care and either identify them or could reasonably be used to identify them. A page describing your cardiology services doesn’t hold PHI on its own. A form where a person types their name, email address and the reason for the visit joins identity and health in one submission.
Your Notice of Privacy Practices has to be on the site even if no PHI ever touches it. A covered entity whose website “provides information about the covered entity’s customer services or benefits must prominently post its notice on the web site and make the notice available electronically through the web site” (45 CFR 164.520(c)(3)(i)).
Where the tracking-technology rule stands
In December 2022 HHS’s Office for Civil Rights published a bulletin on online tracking technologies, revised in 2024. The part that drew attention said a regulated entity’s website could disclose protected health information to a tracking vendor even on a public page. The American Hospital Association and others sued.
On June 20, 2024, in American Hospital Association v. Becerra (N.D. Tex.), the court vacated one piece of that guidance. It called that piece the “Proscribed Combination,” where a technology “connects (1) an individual’s IP address with (2) a visit to a UPW addressing specific health conditions or healthcare providers,” with UPW meaning an unauthenticated public webpage. The judge was careful about scope. A footnote says the bulletin “contains an array of guidance for covered entities, much of which is both legally and pragmatically sound,” and that the court’s analysis “concerns only the Proscribed Combination and the Revised Bulletin’s attempt to apply HIPAA obligations to this ostensibly new IIHI context.” According to a law firm’s summary, OCR withdrew its appeal on August 29, 2024.
The bulletin on hhs.gov still carries a note saying HHS “is evaluating its next steps in light of that order,” and the page was last reviewed June 26, 2024. As of October 2026 OCR has issued no newer tracker guidance that we located. Its list of resolution agreements, with the latest entry dated September 17, 2026, includes no web-tracker case. We wouldn’t read that as permission, since OCR has put its position in writing and the FTC has acted on similar facts.
The bulletin still says tracking technologies on a regulated entity’s user-authenticated pages “generally have access to PHI.” It also keeps this language for public pages that take input:
Tracking technologies on a regulated entity’s unauthenticated webpage that permits individuals to schedule appointments or use a symptom-checker tool without entering credentials may have access to PHI in certain circumstances.
In the bulletin’s example, where a tracker collects an email address or the reason for the visit typed into such a page, the entity is disclosing PHI to the vendor, “and thus the HIPAA Rules apply.” The bulletin says a tracking vendor is a business associate if it meets the definition, “regardless of whether the required BAA is in place.” A BAA doesn’t cover ad targeting either. The bulletin says disclosures of PHI to tracking vendors “for marketing purposes, without individuals’ HIPAA-compliant authorizations, would constitute impermissible disclosures,” and that consent banners for cookies “do not constitute a valid HIPAA authorization.”
A Health Affairs study published in April 2023 looked at the homepages of 3,747 US nonfederal acute care hospitals and found at least one third-party data transfer on 98.6% of them. A JAMA Network Open study published in April 2024 found that 96 of 100 hospital websites in a nationally representative sample sent user information to third parties. Both looked at hospitals, so the numbers don’t automatically describe a dental group or a behavioral health operator.
What a web form does to your HIPAA scope
A form raises two questions. Where does the submitted data go, and what else is running on the page while someone types?
A contact or appointment form that emails its contents to a staff inbox through an ordinary mail service has sent identifiable health information through that service. If the form saves entries in the WordPress database, the database lives on a server with a hosting company. If it hands the entry to a CRM, the CRM now holds it. Each of those is a business associate relationship when the data is PHI, and each needs a signed agreement. A form plugin that stores entries on a vendor’s servers needs one too. Apply the same test to chat widgets, booking embeds and the email or text services that send confirmations.
The second question matters just as much. A form that asks for a reason for the visit, on a page carrying an advertising pixel, can send that text to the ad platform along with the visitor’s identifiers.
You can collect only what you need to book a call and keep the clinical detail for a secured portal after login, or host the forms on a vendor that signs a BAA and run no third-party marketing scripts on those pages. If neither fits, build the intake inside your own application on infrastructure you’ve covered with agreements, the kind of custom web application our software development team scopes and builds. Which one fits depends on your volume, your EHR and how much your intake team wants upfront.
Analytics, pixels and ad platforms
Is Google Analytics HIPAA compliant? Google’s help page says Google “makes no representations that Google Analytics satisfies HIPAA requirements and does not offer Business Associate Agreements in connection with this service.” It says customers “may only use Google Analytics on pages that are not HIPAA-covered.” Authenticated pages are likely to be covered, and public pages related to providing care are more likely to be, so “customers should not set Google Analytics tags on HIPAA-covered pages.” Google tells customers to work with their legal team to decide which pages those are.
Meta’s position is similar. Under its Business Tools Terms, effective November 3, 2025, advertisers promise not to share business tool data that “includes or is based on, directly or otherwise, health information, financial information, consumer report information, or other categories of sensitive information.” We read those terms as a sign that Meta won’t sign as a business associate. Google Ads treats personal health content, such as health conditions and treatments for chronic conditions, as a sensitive category, and its policy bars advertiser-curated audiences when promoting in that category, which includes customer match, your data segments, audience expansion and lookalike segments.
The exposure also reaches past HIPAA. The FTC enforces a separate Health Breach Notification Rule against vendors of personal health records, such as many health apps, and related companies that HIPAA doesn’t cover. Its 2024 amendments clarify that the rule applies to health apps and similar technologies, and that a breach includes “an unauthorized disclosure.” The FTC has treated sharing health data with ad platforms without permission that way, as in the GoodRx case.
GoodRx agreed in 2023 to a $1.5 million civil penalty in the FTC’s first case under that rule, after the agency said it shared users’ prescription medications and health conditions with advertising platforms including Facebook, Google and Criteo. BetterHelp agreed to pay consumers $7.8 million to settle FTC charges that it shared email addresses, IP addresses and health questionnaire information with Facebook, Snapchat, Criteo and Pinterest.
In July 2023 the FTC and OCR sent a joint letter naming “the Meta/Facebook pixel and Google Analytics” and warning that “even if you are not covered by HIPAA, you still have an obligation to protect against impermissible disclosures of personal health information under the FTC Act and the FTC Health Breach Notification Rule.” In July 2026 the FTC, joined by Utah and California, sued Hims & Hers, alleging it shared health information “via third-party tracking technologies that automatically shared certain ‘Events'” from visitors to its website. That case is pending.
Washington’s My Health My Data Act, which its Attorney General describes as protecting “personal health data that falls outside the ambit” of HIPAA, requires a separate consumer health data privacy policy linked from the homepage. The Attorney General’s office says violating the Act is a per se violation of the state Consumer Protection Act, enforced by the Attorney General “as well as through private action.” If you serve Washington residents, ask counsel whether the Act reaches your public pages.
Hosting and other vendors
We found no federal agency that certifies hosting as HIPAA compliant. The rules ask for a written agreement and your own safeguards. Under 45 CFR 164.502(e) a covered entity may let a business associate handle PHI if it gets satisfactory assurance the information will be safeguarded, and the assurance must be documented in a written contract or other written arrangement. Section 164.308(b) says the same for electronic PHI.
HHS’s cloud computing guidance addresses encrypted data. It says a cloud provider that stores ePHI for a covered entity is a business associate “even if the CSP processes or stores only encrypted ePHI and lacks an encryption key for the data.” The conduit exception, which covers pure transmission services like a postal carrier, is “limited to transmission-only services.” A web host that stores your forms or your patient portal doesn’t qualify. A BAA doesn’t replace the customer’s own risk analysis, which the guidance says is still required.
The Security Rule’s section 164.312 covers access control, audit controls, integrity, authentication and transmission security. Encryption is listed there as addressable, which means you must assess whether it is reasonable and appropriate and implement it if so. If not, you document why and put an equivalent measure in place where one is reasonable and appropriate (45 CFR 164.306(d)(3)). A proposed rule published January 6, 2025 would “require regulated entities to encrypt all ePHI at rest and in transit, with limited exceptions.” In the 2026 Unified Agenda it is listed as a long-term action with a final action date of July 2027, so it is still a proposal.
Choose a host that will sign a BAA and tell you in writing which services it covers, since a BAA may cover only some of a vendor’s services. Changing hosts can also affect search, so plan it with the same care as a redesign that affects search.
Marketing content and patient stories
As a general rule, a covered entity “may not use or disclose protected health information without an authorization that is valid under this section,” unless another provision permits it (45 CFR 164.508(a)(1)). For marketing it adds that a covered entity “must obtain an authorization for any use or disclosure of protected health information for marketing,” with narrow exceptions. The definition of marketing in 45 CFR 164.501 leaves out a provider’s communications about its own health-related services unless a third party pays the provider to make them. That doesn’t free a clinic to publish a patient’s details. We found no provision that permits putting them on a public site, so the general rule’s authorization requirement applies.
We found no HHS rule on testimonials, so what follows is our reading of the general rule. A patient story with a name, a photo or enough detail to identify the person discloses protected health information, and the safe route is a signed authorization before it goes on the site. The same applies to before-and-after images and video. Keep a log of who approved what and when.
What a mistake costs
Civil penalties come in four tiers and are adjusted for inflation each year. The Federal Register notice of January 28, 2026 sets the lowest tier, where the entity didn’t know, at $145 up to $73,011 per violation. The top tier, uncorrected willful neglect, starts at $73,011. The regulation’s calendar-year cap is $2,190,294. HHS applies lower annual caps under a 2019 notice of enforcement discretion, which it said applies “until further notice” and which we found no notice withdrawing. The table shows the caps as that notice states them, before the yearly inflation adjustments.
| Tier | Annual cap as stated in the 2019 notice |
|---|---|
| No knowledge | $25,000 |
| Reasonable cause | $100,000 |
| Corrected willful neglect | $250,000 |
| Uncorrected willful neglect | $1,500,000 |
A checklist for the next vendor review
- List every form, chat widget and booking embed on the site, what each one asks, and where each entry goes (inbox, database, CRM, scheduling tool). Cut free-text clinical fields from public pages, and confirm a signed BAA for each recipient that handles PHI.
- Run a scan, including tags loaded through a tag manager, for every third-party script on form pages, appointment pages, symptom checkers and portal login pages. Remove advertising pixels from those pages.
- Keep Google Analytics off HIPAA-covered pages, and decide with counsel, in writing, which pages those are.
- Check that your Notice of Privacy Practices is posted prominently on the site.
- Add the website, its forms and its tags to your risk analysis.
- Get a BAA from your host and agency, with a written list of the services each covers.
- Confirm access controls, audit logging and encryption in transit, and document your decision on encryption at rest.
- Get authorizations on file before any patient story, photo or video goes live.
- Review accessibility on the same pages. Our accessibility guide covers that review.
- Write down who owns this review and when it repeats, because plugins and marketing tags change after launch.
If you’d like someone to look at a specific form or tag setup before you commit to a rebuild, book a call.
Sources
- Use of Online Tracking Technologies by HIPAA Covered Entities and Business Associates, HHS Office for Civil Rights, December 2022, revised March 2024, last reviewed June 2024. Supports the authenticated-page, appointment-page, business associate, marketing and consent-banner statements.
- American Hospital Association v. Becerra, No. 4:23-cv-01110-P, US District Court, N.D. Texas, 2024.
- OCR withdraws appeal in AHA v. Becerra, McDermott Will & Schulte, 2024. Supports the appeal withdrawal date.
- 45 CFR 160.103, Legal Information Institute, current.
- 45 CFR 164.312, 164.306, 164.501, 164.502, 164.508, 164.520 and 164.308, Legal Information Institute, current. Support the technical safeguards, business associate assurances, authorization rules, the marketing definition and the notice posting rule.
- Guidance on HIPAA and Cloud Computing, HHS, current. Supports the cloud provider and conduit statements.
- HIPAA and Google Analytics, Google Analytics Help, current.
- Health in personalized advertising, Google Ads policy, current.
- Meta Business Tools Terms, Meta, effective November 3, 2025.
- GoodRx enforcement action, Federal Trade Commission, February 2023.
- BetterHelp action, Federal Trade Commission, March 2023.
- FTC, States Act Against Hims & Hers, Federal Trade Commission, July 2026. Supports the tracking allegation; the case is pending.
- FTC finalizes changes to the Health Breach Notification Rule, Federal Trade Commission, April 2024.
- FTC and OCR joint letter on third-party trackers, Federal Trade Commission and HHS OCR, July 2023.
- Protecting Washingtonians’ Personal Health Data and Privacy, Washington State Office of the Attorney General, current. Supports the My Health My Data Act statements.
- Resolution Agreements, HHS Office for Civil Rights, checked October 2026. Supports the enforcement statement.
- Notification of Enforcement Discretion Regarding HIPAA Civil Money Penalties, HHS, Federal Register, April 2019. Supports the annual caps HHS applies.
- Annual Civil Monetary Penalties Inflation Adjustment, HHS, Federal Register, January 2026.
- HIPAA Security Rule to Strengthen the Cybersecurity of Electronic Protected Health Information, Federal Register document 2024-30983, January 2025, and the 2026 Unified Agenda entry, RIN 0945-AA22, reginfo.gov. Support the proposed encryption requirement and the agenda listing.
- Widespread Third-Party Tracking On Hospital Websites Poses Privacy Risks For Patients And Legal Liability For Hospitals, Friedman et al., Health Affairs, April 2023.
- User Information Sharing and Hospital Website Privacy Policies, McCoy et al., JAMA Network Open, April 2024.
Want more of our writing in your Google results? Add Innovara as a preferred source.