Resources
Is WordPress HIPAA Compliant? Hosts, Plugins and the Places Patient Data Hides
WordPress can't sign a BAA; your host and plugins decide. Where patient data hides in a practice site, and what GoDaddy and HostGator say. Checked Nov 2026.
By ClinicSite Editorial Team, Healthcare Practice Web Architecture · Published August 13, 2026
General information, not legal advice. Vendor terms were verified in 2026 and change without notice.
The short answer: the question moves to your host, your plugins and you
HIPAA requires a covered entity, such as a practice that bills insurance electronically, to have a business associate agreement (BAA) with each vendor that creates, receives, maintains or transmits protected health information (PHI) on its behalf. The BAA is signed between your practice and that vendor. HHS also requires business associates to bind their own subcontractors to the same terms.
WordPress, the free software from WordPress.org, is not a vendor in that sense. Nobody signs a BAA "for WordPress." Instead, every company whose servers or services handle data from your WordPress site is a candidate: the host, the form plugin's cloud service if it has one, the email provider that sends notifications, the backup destination, and any analytics or chat service a plugin connects to.
Two practical consequences follow. A WordPress site that never receives patient information may not need any of this. A WordPress site that does collect it needs a BAA at every hop, not just with the host.
Where patient data can hide in a WordPress site
Vendor-written guides tend to cover only their own layer, so it is worth doing this inventory yourself.
| Place | How PHI gets there | Who would need a BAA |
|---|---|---|
| Form plugin entries in the database | Many form plugins can save each submission to the WordPress database as well as emailing it | Your host |
| Form notification emails | The plugin emails the full submission to the practice inbox | Your email provider, and any relay service |
| SMTP and email-log plugins | Some plugins that improve email delivery can keep a copy of each sent message | Your host, plus the email-delivery service |
| Backups | Host snapshots and backup plugins copy the whole database, including form entries | The host, and any cloud storage the backups go to |
| Security and firewall plugin logs | Logs can record IP addresses alongside the pages visited, such as a booking page | Your host, and the security vendor if logs leave your server |
| Analytics and pixel plugins | Tags send page addresses and events to third parties | Google states it offers no BAA for Analytics |
| Chat and callback widgets | Visitors type symptoms into a chat box | The chat vendor |
| Anti-spam services | Some anti-spam tools send form content to an outside service for checking | The anti-spam vendor |
| Staging sites and downloaded copies | Developers clone the live database to test changes | Whoever hosts the copy, and the developer if they access it |
Two of these routinely surprise practice owners. The first is backups: deleting form entries from the dashboard does not remove them from last month's backup. The second is the staging copy a web developer made two years ago, which may still contain every submission up to that date.
Hosts: what they say about BAAs
Host terms are explicit enough that you can usually answer this in five minutes by reading them.
HostGator. Its Terms of Service, verified in 2026, disclaim "any representation or warranty that the Services, as offered, comply with" HIPAA. They say customers needing secure storage of protected health information "are expressly prohibited from using the Services for such purposes," that storing PHI is "a material violation of this Agreement, and grounds for immediate account termination," and: "We do not sign 'Business Associate Agreements.'" That is a clear answer, and typical of budget shared hosting.
GoDaddy. GoDaddy does publish a HIPAA Business Associate Agreement. Its scope section says it applies to "the Microsoft® 365 email services sold and supported by GoDaddy," and that GoDaddy "may expand the scope." GoDaddy's help center describes HIPAA-compliant email as an add-on requiring at least one Business Professional or Premium Security email account, and says the BAA alone "doesn't achieve compliance." We found no GoDaddy page offering a BAA for web hosting or Managed WordPress. If your practice site runs on GoDaddy hosting, ask GoDaddy in writing before putting PHI on it.
WordPress.com. The hosted service run by Automattic is different from WordPress.org software. Its Terms of Service, read on the same date, do not mention HIPAA, and we found no WordPress.com or Automattic page offering a BAA. Ask them directly before relying on either answer.
HIPAA-focused WordPress hosts. Several hosts advertise WordPress hosting with a signed BAA. Treat that as the start of the check, not the end. Get the BAA document itself, confirm it names the hosting plan you will buy, and remember it covers the host's infrastructure, not third-party services your plugins send data to.
Forms, email and backups: practical fixes
Decide whether you need a form at all. Tap-to-call and email links collect nothing on the site. Our website forms guide walks through that decision field by field.
If you keep a form, stop the database copy if your plugin allows it, or set entries to delete automatically after a short period.
Cut notification emails down to "new submission received," with details only in a system covered by a BAA.
Check email delivery. If notifications travel through a delivery service or are logged by a plugin, that is another vendor and another copy.
Find every backup destination, including old cloud folders, and set retention limits.
Delete stale staging sites and downloaded database files.
The maintenance burden
WordPress sites need core, theme and plugin updates, and someone has to apply them, test them, and notice when a plugin is abandoned by its developer. For a practice handling PHI on the site, that maintenance becomes part of your HIPAA security work. HHS's tracking bulletin, for example, tells regulated entities to address tracking technologies in their risk analysis and risk management processes, and the same thinking applies to any plugin that touches patient data.
If your practice depends on one developer or agency for all of this, that is workable when the arrangement is written down: who updates what, how often, who can see form entries, and whether that person needs a BAA because they can access PHI.
Alternatives: a PHI-free site, or a different platform
Keep WordPress, collect nothing. Remove forms and tracking plugins, link out to your EHR's booking and intake tools (which come under that vendor's BAA), and keep the site informational. This is often the simplest fix, and it shrinks the inventory above to almost nothing.
Keep WordPress, move to a host that signs a BAA, and then work through every plugin and email hop. This suits practices that genuinely need web intake on their own site.
Move off WordPress. ClinicSite is one option built around the first approach. Published ClinicSite sites run on Microsoft Azure under a content security policy that blocks form submission and third-party scripts, so there are no plugins to update and no form database. Online booking is the exception; it is off by default, and when a practice turns it on, it stores each patient's name, contact details and notes and emails them to the practice. ClinicSite publishes no HIPAA certification or SOC 2 report, and the hosting page states its business associate agreement position as "Partial."
If you like your current WordPress design, ClinicSite can capture your existing pages instead of generating new ones. Your WordPress site stays live until you point your domain elsewhere. Before any move, read our guide to switching your practice website without losing rankings. And if you want to look first, start a free preview; it needs no account or card and is deleted after seven days.
Related Practitioner Guides
Measure how heavy page builders slow mobile LCP and hurt conversions in our WordPress plugin speed audit for clinics.
Check 2026 seat pricing, redirect tiers, and BAA limits in our Webflow vs. Framer medical website comparison.
Sources
GoDaddy HIPAA Business Associate Agreement (scope: Microsoft 365 email services sold by GoDaddy)
WordPress.com Terms of Service (no mention of HIPAA or BAAs as of access date)
HHS OCR tracking bulletin (risk analysis; BAA with tracking vendors; partly vacated June 20, 2024)
ClinicSite FAQ (no plugins to update; old site stays live until domain is pointed)
Frequently asked questions
- Can WordPress be HIPAA compliant?
- A WordPress site can be part of a HIPAA-compliant setup if every vendor that handles PHI from it has signed a BAA with your practice, and your own safeguards are in place. That usually means a host that signs a BAA, a form service or email provider covered by its own BAA, controlled backups, and no analytics or pixels on patient-facing pages.
- Is GoDaddy HIPAA compliant?
- GoDaddy's published BAA, verified in 2026, covers the Microsoft 365 email services it sells, as an add-on to qualifying email plans. We found no GoDaddy page offering a BAA for web hosting or Managed WordPress. So GoDaddy email can be set up under a BAA, while putting PHI on a GoDaddy-hosted website needs written confirmation from GoDaddy first.
- Does WordPress.com sign a BAA?
- We found no WordPress.com or Automattic page offering one, and the WordPress.com Terms of Service verified in 2026 do not mention HIPAA. That does not prove a negative, so contact Automattic in writing if this matters to your decision. Until you have a signed agreement, keep patient information off a WordPress.com site.
- Do I need HIPAA-compliant hosting for a WordPress brochure site?
- If the site has no forms, no chat, no patient portal and no tracking on care-related pages, it may hold no PHI, and specialist hosting adds little. The moment it collects patient information, the host is a business associate and needs a BAA. Our [HIPAA website requirements guide](/guides/hipaa-website-requirements) covers how to tell which side of that line you are on.
- Are WordPress form plugins HIPAA compliant?
- A plugin is code running on your server, so the question becomes where its data goes. Entries saved in the database sit with your host. Notifications go through your email provider. Some form products also run a cloud service of their own, which would need its own BAA. Check each path, and check whether the plugin vendor offers a BAA for any service it operates.
- Does my web developer need to sign a BAA?
- If your developer or agency can log in and see form entries, database backups or email logs containing PHI, they are likely handling PHI on your behalf and may be a business associate. If they never see patient data, they probably are not. Ask your compliance reviewer, and limit developer access to what the work actually requires.
Related
- Webflow vs Framer for Medical Practice Websites: 2026 Costs, Redirects and HIPAA LimitsWebflow Premium is $25/mo, Framer Pro $30/mo plus $40 per editor, and Framer Basic has no 301 redirects. A 2026 cost, SEO and HIPAA breakdown for clinics.
- Psychiatric and Ketamine Clinic Website Examples: 6 Blueprints That Book Safely6 annotated psychiatry, TMS, Spravato and IV ketamine website blueprints: REMS 2-hour monitoring copy, off-label wording, 988 placement and LCP under 2.5s.
- New Medical Practice Website Launch Checklist (2026)A 30-day website launch checklist for new medical practices: domain, core pages, online booking, local SEO, accessibility, and QA before opening day.
- How Much Does a Medical Practice Website Cost in 2026? Three-Year Totals by ApproachWhat a U.S. medical, dental or therapy practice website costs over three years by approach, with dated vendor prices, hidden costs and a staff-time worksheet.
- All resourcesEvery ClinicSite guide in one place.
See what your clinic site could look like
Paste your current website address. You get a full generated replacement to look at, free, with no account and no card.
Free preview with no card. Previews are deleted after 7 days.