KLYR Media Logo
HomeBlogMedical Website Privacy Policy: What It Must Cover
Healthcare Marketing
November 19, 2026
13 min read

Medical Website Privacy Policy: What It Must Cover

What a medical website privacy policy must say, how it differs from your HIPAA Notice of Privacy Practices, and how to audit your site so the two match.

Medical Website Privacy Policy: What It Must Cover

Medical Website Privacy Policy: What It Must Cover

Clinic administrator comparing two privacy documents

A medical website privacy policy is a plain-language page that tells visitors what your site collects, who gets it, how long you keep it and what choices they have. It is not the same thing as your HIPAA Notice of Privacy Practices, and you need to know the difference. The policy only protects you if it matches what your site actually does. That means what your forms, pixels, chatbots and analytics tools do after a patient clicks.

Most trouble starts there. The policy says one thing, the tracking tags say another. Here is how to get both right.

Klyrmedia
Build a Website Around Real Practices
Klyrmedia creates HIPAA-compliant healthcare websites, helping providers align their online presence with the way their sites work.
Visit

TL;DR

  • Your site needs two documents: a HIPAA Notice of Privacy Practices (NPP) for protected health information, and a website privacy policy for everything the site collects.
  • If you are a covered entity, the NPP must be posted prominently on your website under 45 CFR 164.520.
  • The biggest risk is third-party tracking. Sharing PHI with a tracking vendor without a business associate agreement (BAA) or another permission can count as a breach.
  • State laws can cover health data that HIPAA does not, so a policy copied from another state’s clinic may not fit you.
  • Audit what the site really does first, then write the policy to match it.

Table of Contents

Two documents, not one

Owners often ask for “a HIPAA privacy policy for the website” and get one page that tries to do both jobs. It rarely works.

The Notice of Privacy Practices is a HIPAA document. HHS explains that a covered entity must post it prominently on any website that gives information about its services or benefits. It has to be in plain language. It must describe how PHI may be used and disclosed, the individual’s rights, your legal duties and a contact person. It also needs an effective date, and you must revise it promptly when practices change materially (HHS guidance).

If a patient first gets service electronically, HHS says you must send an electronic NPP automatically in response to the first request for service. You also need a good-faith effort to get an acknowledgment. Patients always keep the right to a paper copy (HHS FAQ).

The website privacy policy covers the visitor experience: contact forms, newsletter signups, cookies, analytics, ad tags, chatbots. Much of that data is not PHI, such as someone who reads a blog post and leaves. Some of it may be, such as an appointment request.

A well-built hospital example shows how the two fit together. Summa Health’s website privacy policy says it applies to both PHI and non-PHI. For PHI, the HIPAA Notice controls if the two conflict. It separates data people give you directly (contact details, insurance, payment, survey answers) from data collected automatically (IP address, device identifiers, referral URLs, ad data, web logs, email open data).

That split is worth copying. Link the two documents to each other, and make the NPP win any conflict.

Two documents, not one

What a medical website privacy policy should explain

The Association of National Advertisers publishes 11 key elements of a privacy policy. Translated for a practice, here is what your page should cover:

  1. Who you are and how to reach you. Name a real contact, such as your privacy officer or office manager, and an email or phone number that someone answers.
  2. What you collect. List what visitors type in (name, phone, insurance, symptoms in a message box) and what the site picks up on its own (IP address, device, pages viewed).
  3. How you use it. Scheduling, billing, reminders, marketing, site improvement. Say marketing if you do marketing.
  4. Cookies and tracking tools. Name the categories you use and explain how a visitor can turn them off.
  5. Who you share it with. Name the categories of recipients and, where you can, the actual companies. Include opt-out options.
  6. Marketing choices. How to unsubscribe from email and text messages.
  7. Security. What you do to protect data, in general terms. Do not promise “100% secure.”
  8. Retention. How long you keep what you collect. Many policies skip this one.
  9. Children and special populations. Say how you handle data from minors.
  10. Changes. How you notify people when the policy changes.
  11. An effective date. Update it every time you edit the page.

Write it so a patient can read it

This is where most policies fail. A 2024 study of 100 US hospital websites (McCoy et al., 2024) found policies averaged 2,527 words at a college reading level (Flesch-Kincaid grade 13.7). The authors note the average US patient reads at about an 8th-grade level.

So aim for short sentences, headings that match patient questions, and a summary at the top. A long policy nobody can read is not a defense. It is a liability sitting on your site.

Where policies break: third-party tools

The same study found that 96.0% of hospital websites sent user information to third parties. The median was 9 third-party domains. Only 71.0% had a publicly accessible privacy policy, and just 56.3% of those named specific third-party companies (McCoy et al., 2024).

Study findings on hospital website tracking

The gap between what sites do and what policies say is the problem. Patients may assume they are only tracked by familiar names. In fact, data can go to brokers and ad companies they have never heard of.

What HHS says about tracking technologies

HHS’s Office for Civil Rights (OCR) published guidance on online tracking technologies. The points that matter for your policy:

  • Tracking tools can touch PHI on logged-in pages, such as a patient portal. In some cases they can touch PHI on public pages too, such as appointment booking or symptom checkers.
  • Data from a public page is PHI only when it relates to a person’s health, health care or payment for care.
  • To send PHI to a tracking vendor, you need a signed BAA and a Privacy Rule permission, or the patient’s authorization.
  • A cookie banner is not a HIPAA authorization.
  • A vendor promising to de-identify the data after it receives it is not enough.

A federal court changed part of the picture. On June 20, 2024, the Northern District of Texas (American Hospital Association v. Becerra) vacated the portion of the guidance that treated an IP address plus a visit to a public condition-specific page as triggering HIPAA. HHS notes that not all tracking data is PHI (HHS guidance).

Don’t read that as a green light. Law firms point out that whether data is PHI can hinge on a visitor’s intent, which you can’t see. A student reading an oncology page is not PHI. A person seeking a second opinion on a diagnosis may be (Morrison Foerster, 2024). The safest policy and the safest site treat appointment and symptom pages carefully.

We go deeper on this in HIPAA tracking technologies: what providers must know and in Facebook Pixel and HIPAA.

HIPAA is not the only law

HIPAA covers covered entities and their business associates. Health data collected outside that relationship may fall under state law. EPIC’s January 2026 report summarizes several:

  • Washington’s My Health My Data Act requires readable privacy policies, consent before collecting or selling consumer health data, and deletion rights. It also bans geofencing around health facilities.
  • Nevada’s SB 370 took effect in January 2026 with similar consent requirements.
  • Minnesota’s HF 1 (effective July 2025) covers “consumer health data” beyond PHI.
  • California’s CMIA and CCPA/CPRA can reach website analytics, marketing data and non-PHI app data that fall outside the HIPAA exemption.

If you serve patients in more than one state, or run ads that reach them, check which of these touch you. A policy copied from a clinic in another state may promise rights you don’t honor, or miss ones you owe. Talk to a healthcare attorney for your state before you finalize wording.

What changed recently

Three updates affect what your pages should say today.

  • NPP changes. Under the 2024 Privacy Rule update on reproductive health care, covered entities had to comply with the modified NPP requirements of 45 CFR 164.520 by February 16, 2026 (Federal Register copy). If your NPP is older than that, review it. EPIC notes that the rule’s ban on sharing PHI tied to lawful reproductive care with law enforcement has since been vacated, while state laws fill some gaps (EPIC, 2026).
  • Access requests. On November 16, 2026, HHS announced a final rule modernizing the HIPAA Privacy Rule. It shortens response times for PHI access requests, provides for electronic access through a personal health app where available, changes fee rules (including free copies and advance notice of fees), and lets patients direct an EHR copy to someone they designate. It takes effect 60 days after publication. Once you see the final text, update the rights section of your NPP and the request instructions on your site.
  • Penalties. After the January 28, 2026 inflation adjustment, civil penalties under 45 CFR 102.3 reach up to $2,190,294 per violation and per identical provision per year (EPIC, 2026).

How to audit your site and make the policy match

Write the policy last. Start with what the site does.

  1. Inventory every tag. Use your browser’s developer tools or a tag-scanning tool to list analytics, ad pixels, chat widgets, heatmaps, scheduling embeds and fonts or maps loaded from other domains. Ask your web developer for the list. If nobody can produce it, that is your first finding.
  2. Map each tag to a page. Note where it fires. Pixels on the home page are one thing. Pixels on booking, symptom-checker, refill and portal-login pages are another, because those are where PHI can appear.
  3. Check every form. For each form, list the fields, where the submission goes (email, CRM, scheduling vendor) and who can see it. Free-text boxes are the riskiest, since patients type symptoms into them.
  4. Sort vendors. For each vendor receiving data from health-related pages, ask: do we have a signed BAA? Is there a Privacy Rule permission or patient authorization? If the answer is no, remove the tool from those pages. HHS says a banner won’t fix it.
  5. Decide what stays. Keep only the tools you can document. Move marketing tags off sensitive pages.
  6. Write the policy from the inventory. Each tool, data type and recipient category on your list belongs in the policy. Anything in the policy that you don’t do comes out.
  7. Link and date it. Put the privacy policy and NPP in the footer of every page and near every form. Add an effective date.
  8. Repeat. Re-run the audit whenever you add a plugin, change an ad platform or redesign. Calendar it twice a year at a minimum.

This is the kind of work our HIPAA-compliant web design process is built around, and we lay out the flow in our HIPAA compliant website workflow guide. For the technical side, see medical website security.

What happens when policy and practice don’t match

HHS is direct about it. If PHI goes to a tracking vendor without a Privacy Rule permission and without a BAA, and security or privacy of that PHI is compromised, it is presumed a breach of unsecured PHI. The only way out is to demonstrate a low probability of compromise. A breach means notifying affected individuals and the HHS Secretary, and the media when applicable (HHS guidance). OCR also says it prioritizes Security Rule compliance in its investigations.

A missing or inaccurate policy won’t cause that by itself. But a policy that says “we never share your information” while a pixel fires on your booking page turns a technical gap into a documented one. For the broader picture, read the role of data privacy in healthcare.

Getting a site that matches its policy

If you run an independent pharmacy or practice, you probably don’t have an IT department. You have a website someone built three years ago and a stack of plugins nobody has reviewed.

KLYR Media works only with healthcare providers, mostly independent pharmacies, clinics and practices in the United States. We build HIPAA-compliant websites with compliance in from day one, and we also run healthcare SEO, PPC and automation. That means your site, your ads and your patient follow-up are planned together instead of by three vendors who never talk.

Klyrmedia

If you want your site and your privacy documents to say the same thing, start with our HIPAA Web Design Service.

Our view: the policy is the last step, not the first

We talk to pharmacy and clinic owners who tell us the same thing: “We have a privacy policy.” Then we look at the site, and the policy describes a website that doesn’t exist.

Here is what we think. A policy is a description. If the site underneath is a pile of tags added by whoever built it, then the policy is a guess. Fixing the words doesn’t fix the leak.

That’s why we start with the build. Independent providers are competing with chains and online giants that have legal teams. You don’t need a legal team’s budget. You need a site built for healthcare, where compliance is a design decision and marketing tools are chosen with PHI in mind, not bolted on later.

The good news: this is fixable, and once it is fixed, it stays easy. Know your tags, know your vendors, keep the page honest. Then you can market with confidence instead of crossing your fingers every time you add a plugin.

Opinly

FAQ

Does my medical website need both a privacy policy and a HIPAA Notice of Privacy Practices?

If you are a HIPAA covered entity, yes. The NPP is required and must be posted prominently on your site. A website privacy policy covers data collected through the site, including cookies and analytics. Link them to each other and state that the NPP controls for PHI.

No. HHS says a cookie banner is not a HIPAA authorization. If a tracking vendor receives PHI, you need a BAA and a Privacy Rule permission, or a valid authorization. Removing the tool from sensitive pages is the cleanest fix.

Can I copy another practice’s privacy policy?

It’s risky. A copied policy describes someone else’s tools, vendors and state. Yours has to match what your site does and the state laws that apply to your patients. Build the policy from your own tag and form inventory.

How often should I update it?

Update it whenever your tools, vendors or the law change, and put a new effective date on it. Review it at least twice a year. The HHS final rule on access requests announced November 16, 2026 is a reason to review now.

Sources

Share this article: