Somewhere on your clinic’s website there is probably a form that asks a parent for their child’s name, age, diagnosis and insurance. And somewhere in that website’s code there may be a small script, installed years ago by a web designer or an ads consultant, quietly reporting that form submission to Meta or Google.
Nobody meant for it to happen. But intent does not change what HIPAA says about it.
What HHS says about tracking technology
The HHS Office for Civil Rights (OCR) published guidance on online tracking technologies in December 2022 and updated it in March 2024. The core message has not changed: HIPAA-covered providers may not use tracking tools in a way that discloses PHI to the tracking vendor without a HIPAA permission.
A few points matter most for ABA clinics:
- Forms and scheduling pages are the hot zone. OCR’s example is a public page where someone books an appointment or types in symptoms. If a tracker captures their email or reason for care, that is a disclosure of PHI.
- Portal logins count too. If a tracker captures what a parent types on your portal login or registration page, HIPAA applies.
- A cookie banner is not consent. OCR says accept/reject banners are not a valid HIPAA authorization.
- Your privacy policy is not a permission. Telling visitors you use tracking does not make sharing PHI with the vendor allowed.
- “We’ll strip it out later” doesn’t work. A vendor promising to remove PHI after receiving it still needs a BAA, plus a HIPAA permission for the disclosure.
What the 2024 court ruling changed, and what it didn’t
In June 2024, a federal court in Texas (American Hospital Association v. Becerra) vacated one part of that guidance: the idea that an IP address plus a visit to a public page about a health condition is automatically PHI. HHS dropped its appeal that August.
That ruling helps if you run basic analytics on your blog or “About ABA” pages. It does not touch forms, scheduling tools, portals or anything where a parent types information about their child. Those remain squarely under HIPAA. State privacy laws and class-action lawsuits over pixels are also separate from the ruling.
Where ABA websites usually leak
Â
- The intake or contact form. A Meta or Google tag fires on submit, or on the thank-you page, and sends along form fields, the page URL, or the visitor’s IP and browser IDs.
- “Is ABA right for my child?” quizzes and checklists. These work like the symptom checkers OCR warns about. Answers about a child’s behavior plus an identifier is health information.
- Session recording and heatmap tools. Tools that replay a visitor’s clicks and typing can capture form fields unless masking is configured correctly.
- Chat widgets. A parent will type their child’s diagnosis into a chat box within the first two messages. Where does that transcript go?
- Embedded scheduling and insurance verification tools. Third-party widgets often bring their own trackers.
- URLs that carry data. A thank-you page like /thank-you?name=jamie&dx=autism puts PHI into every analytics tool on the page.
A 30-minute self-audit
Â
You can get a first read on your risk without a developer:
- List every page where a parent can type information: forms, chat, booking, portal login, quizzes.
- Install a free tag-inspection browser extension and visit each of those pages. Note every tracker that loads (Meta, Google, TikTok, LinkedIn, Hotjar, Microsoft Clarity and similar).
- Submit a test form with fake details. Check whether the thank-you URL contains any of what you typed.
- Ask your web developer or agency for the list of tools that receive form submissions, and which of them have signed a BAA with you.
- Check your Meta Events Manager. If Meta has labeled your account as health and wellness and restricted events, that is a sign its systems have already noticed health data.
If any tracker without a BAA loads on a page where parents type information, treat it as a priority fix.
How to fix it without losing your marketing data
Â
The goal is not to go blind. It is to measure results without handing PHI to ad platforms.
- Use a form and intake tool that signs a BAA. Send submissions straight to a HIPAA-compliant CRM, not to email inboxes or ad platforms.
- Remove third-party pixels from forms, booking, chat and portal pages. Keep them, if at all, on general content pages only, and review them with your compliance lead.
- Measure conversions without identifiers. Count “form submitted” as an anonymous event, or route data through a server-side or customer data platform vendor that signs a BAA and strips identifiers before anything reaches an ad platform. OCR’s own guidance points to this approach.
- Mask or remove session recording on any page with form fields.
- Keep data out of URLs. Use a plain, static thank-you page.
- Add tracking to your HIPAA risk analysis. OCR has said its investigations focus on whether you identified and managed these risks.
The bottom line
Â
Most ABA clinics with a leaky website didn’t choose to share PHI. They inherited a setup built for e-commerce. The fix is usually a few focused changes, and it protects the families who trusted you with their child’s information before they ever walked through your door.
Not sure what’s running on your site? Book a free HIPAA marketing audit with Tailwinds AI. We’ll scan your forms, booking pages and trackers and show you exactly what’s being sent, and to whom.
This article is for general information and is not legal advice. Talk to a healthcare attorney or your compliance officer about your clinic’s specific situation.


