SOC 2, BAAs and Badges: How to Read an AI Vendor's Security Claims Before Your ABA Clinic Signs
Informational only; not legal, compliance or security advice. Details come from the sources listed below as of Nov. 19, 2026. Talk with your own compliance lead or attorney before you sign.
Most AI tools pitched to ABA clinics show a "HIPAA compliant" badge, a SOC 2 logo, maybe "BAA available." They sound alike, but they are very different, and only one is something you sign.
Here is what each one actually means.
The badge: "HIPAA compliant"
There is no official HIPAA certification. In an FAQ on the Security Rule, HHS says it does not endorse or otherwise recognize private organizations' "certifications," and that those certifications don't take away a covered entity's legal obligations. HHS can still find a violation later.
So treat a badge as marketing until it is backed by something you can read.
The contract: the business associate agreement
This is the one that matters most legally. HHS's cloud computing guidance says that when a clinic uses a cloud service to create, receive, maintain or transmit electronic PHI on its behalf, that service is a business associate, and the two must sign a HIPAA-compliant business associate agreement (BAA). HHS says this applies even if the vendor only stores encrypted data and doesn't hold the key.
For an AI tool that touches session notes, recordings or intake calls, that means:
- Ask for the BAA before anyone on your team enters client data, including during a free trial.
- Check which plan it covers. Some vendors offer a BAA only on certain tiers.
- Read what it allows the vendor to do with your data, including whether data can be used to train models.
The same guidance also says HHS's rules apply to subcontractors. If a vendor sends your data on to another cloud or AI service, that subcontractor is a business associate too. Ask who is in that chain.
The audit: a SOC 2 report
SOC 2 comes from the AICPA, the accounting profession's standards body. A CPA firm examines a vendor's controls against trust services criteria covering security, availability, processing integrity, confidentiality and privacy. It is not a HIPAA review, and it doesn't replace a BAA.
Two details help you read one:
- Type 1 or Type 2. According to AICPA's SOC 2 guide, a Type 1 report looks at whether controls were suitably designed as of a point in time. A Type 2 report also tests whether those controls actually operated effectively over a period of time, and it includes the auditor's tests and results. If a vendor says "SOC 2," ask which type and what dates it covers.
- What is left out. The guide explains that a report can "carve out" a subservice organization, meaning that vendor's controls aren't covered. For an AI product, the outside model provider or hosting company may sit in that carve-out. The guide also describes "complementary user entity controls," which are things you, the customer, are expected to do. Those are your homework: user access, passwords, who gets an account and turning off former staff.
One more caution. On its SOC page, the AICPA has posted a notice saying it is looking into anonymous allegations about the business practices of a compliance vendor offering SOC services. A logo on a website isn't the report. Ask to see the report itself, usually under an NDA, and check the name of the CPA firm that signed it.
Your part: the risk analysis
HHS's cloud guidance says a clinic using a cloud service should understand that service well enough to do its own risk analysis. A vendor's paperwork feeds into that. It doesn't replace it.
The same guidance lists issues a service level agreement can cover. These make a good question list:
- How available and reliable is the system?
- How are backups and data recovery handled, including after ransomware?
- How do we get our data back if we leave?
- Who is responsible for which security tasks?
- What limits apply to use, retention and disclosure?
A short checklist before you sign
- Get the signed BAA, and confirm it covers the plan you're buying.
- Ask for the current SOC 2 report. Note the type, the dates, any carve-outs and your listed customer duties.
- Ask where the AI processing happens and which subcontractors see client data.
- Ask whether your data trains models, and get the answer in writing.
- Add the tool to your clinic's risk analysis and AI use policy.
AI can save a BCBA real hours. But families trust us with their child's information, not the vendor. Before a tool sees one session note, know in writing what protects that data.
Sources
- https://www.hhs.gov/hipaa/for-professionals/special-topics/health-information-technology/cloud-computing/index.html
- https://www.hhs.gov/hipaa/for-professionals/faq/2003/are-we-required-to-certify-our-organizations-compliance-with-the-standards/index.html
- https://www.aicpa-cima.com/topic/audit-assurance/audit-and-assurance-greater-than-soc-2
- https://catalogimages.wiley.com/images/db/pdf/9781945498602.excerpt.pdf
More from the blog
- An Autism Center Replaced Its Supervisor With AI. Here Is What AI Can't Take Over in RBT Supervision
- AI Translation for ABA Families: What Still Needs a Qualified Human Translator
- AI Trend Readings on ABA Graphs: What the Math Sees and What Visual Analysis Still Catches
- AI Claim Scrubbing for ABA Billing: What It Catches and What It Can't Fix
Informational only; not legal, clinical or compliance advice. Vendor HIPAA/BAA statements are as published by the vendors and are not verified by us. Sponsorship never changes our rankings. Corrections: admin@gtbehaviorbolts.com.