Skip to main content
Patient Protect circular logo mark in purple and white used for site navigationPatient Protect
Live on the Chrome Web Store

HIPAA Shield.
Catch PHI before it leaks.

A free Chromium browser extension that flags likely patient information as it is typed or pasted into a browser form — an AI chat box, a webmail composer, a vendor portal, anywhere. Detection runs on your device. Nothing is transmitted. Ever.

Free · Open Source · MIT Licensed · Works on Chrome, Edge, Brave, Arc, Opera, Vivaldi

What it looks like

A line above the box, while you are still typing.

No modal, no blocked submit, no permission to ask for. About a quarter of a second after a rule matches, a banner appears directly above the field naming what was found. You can keep typing, dismiss it, or think again.

A chat box on a site with no agreement in place

HIPAA Shield: possible PHI detected

Social Security Number, Date of birth

If you’re entering this into a tool that doesn’t have a HIPAA BAA (most consumer AI tools don’t), this may be a reportable disclosure.

Can you summarize this for a referral letter — DOB 04/12/1966, SSN 555-01-2431, presenting with…

That is the whole interaction, reproduced from the extension’s own warning text. The banner names the rules that fired and nothing else — it does not know which site you are on, whether an agreement exists with that vendor, or whether what you typed is really patient information. It reports a pattern match. You supply the judgment.

On that last point the banner is deliberately general, and so is our advice: do not assume a tool or plan is covered by a business associate agreement. Verify the vendor, the product and the plan before entering patient information.

What a detection means

A pattern match is not a breach.

Warnings like this get sold as breach detection. They are not, and a practice that treats every banner as an incident will stop reading them by Thursday. What the extension has found is a string that looks like an identifier. Everything after that is a separate question, and each one can end the inquiry:

  1. 01

    Is it protected health information?

    Nine digits in a text box might be an SSN, an account number, or a test value. PHI is individually identifiable health information held by a covered entity or business associate. The extension cannot tell which it is looking at.

  2. 02

    Would sending it be impermissible?

    Disclosure to an outside party needs the patient’s authorization, a business associate agreement, or another basis the Privacy Rule permits. If one of those is in place, there is no impermissible disclosure.

  3. 03

    Was the information unsecured?

    The Breach Notification Rule reaches unsecured PHI — information not rendered unusable, unreadable, or indecipherable by the methods HHS specifies.

  4. 04

    Does an exception apply?

    45 CFR 164.402 excludes certain events from the definition of breach outright, including some good-faith internal access and disclosures a recipient could not reasonably retain.

  5. 05

    Only then: presumption, or notification.

    An impermissible disclosure of unsecured PHI that no exception covers is presumed to be a breach unless the entity demonstrates a low probability of compromise through the four-factor risk assessment. Performing that assessment is a choice — an entity may forgo it and notify instead.

Where this leaves the tool

No HIPAA provision requires a browser extension. HIPAA Shield is a Patient Protect control, not a regulatory safeguard, and it earns its place by making the risky moment visible while it is still a choice. When an event does warrant review, the work — determining what was disclosed, to whom, whether an exception applies, and documenting the conclusion — happens after the fact, and it is work the extension has no part in.

The problem

Staff paste patient data into ChatGPT every day. The browser is where the disclosure happens.

A medical assistant pastes a chart note into ChatGPT to summarize. A biller drafts an appeal letter with claim details. A front desk coordinator cleans up a sensitive patient email. Nobody flagged any of it as a problem. It didn't feel like a breach — it felt like being resourceful.

Do not assume a consumer AI tool or plan is covered by a business associate agreement. Verify the vendor, the product and the plan before entering patient information — terms differ between a free tier, a paid seat and an enterprise agreement, and they change. A paste made without that check is a disclosure the practice cannot account for. Whether any particular one rises to an impermissible disclosure, or to a breach, is a question for afterwards. The problem is that nobody is asking it at the time.

The intervention has to happen at the moment of the choice, not in retrospect during an audit. That's the browser. That's what HIPAA Shield does.

What it detects

Eight detection rules. Five on by default.

Phone numbers, email addresses and diagnosis phrases ship off, because they fire constantly during ordinary browsing. Turn any of them on in the popup.

RuleSeverityDefaultPattern
Social Security NumberhighOnXXX-XX-XXXX, with invalid prefixes excluded
Date of birthhighOnMM/DD/YYYY, 1900–2099
Credit card numberhighOnVisa/MC/Amex/Discover, Luhn-checked
Medical Record Number (MRN)highOnMRN- or MR#-prefixed identifiers
ICD-10 diagnosis codelowOnLetter plus two digits, optional decimal
Phone numbermediumOffStandard US formats
Email addressmediumOffStandard email format
Clinical diagnosis termslowOffPhrases such as “diagnosed with” followed by a condition

Where it works

Any text input on any website.

The extension scans every text input, textarea, and editable field on every page. It's especially useful for:

  • AI chat tools where staff paste questions about real patients
  • Webmail compose windows where attachments and addresses can leak PHI
  • Customer support and CRM forms used for patient outreach
  • Vendor portals, ticketing systems, and intake forms
  • Any text input, textarea, or contenteditable field on any website

Privacy

100% client-side. Zero network requests.

The extension does not collect, transmit, store on any server, or share any data. Every check happens inside your browser, on your device. No telemetry, no analytics, no error reporting, no usage tracking. The source contains no fetch, XMLHttpRequest or sendBeacon calls at all, in any state. You can check that yourself in a minute.

What it does need is broad access, and that deserves saying out loud rather than leaving for the install prompt. The content script matches <all_urls>, so Chrome will tell you the extension can read and change your data on all websites. It has to run on every page, because the paste you want caught is on a page nobody predicted. What it does with that access is read field contents locally and compare them against the rules you have enabled. That reading never leaves the device.

Fields inspected
Text, search, URL, telephone, email and password inputs; every textarea; any editable region. Password fields are included on purpose — an identifier pasted into the wrong box is exactly the case worth catching.
What is stored
One key, enabledRules, in chrome.storage.local. It holds your rule toggles and nothing else. It persists until you uninstall, and it is not synced.
Detection history
None. There is no log, no counter, and no record of what was found or where. Dismiss a banner and it is gone.
Network activity
None, under any state — no beacons, no update pings, no remote code, no error reporting.

FAQ

Frequently asked questions

Are Chrome extensions HIPAA compliant?

No extension is HIPAA compliant or non-compliant as an intrinsic property — HIPAA regulates entities and their uses of protected health information, not software categories. What matters is what the extension can access, what it stores, what it transmits, who receives it, and how the practice uses it. An extension that sends form contents to a vendor's servers is handling PHI on the practice's behalf, which makes that vendor a business associate and requires an agreement under 45 CFR 164.502(e) and 164.308(b). An extension that processes text on the device and transmits nothing creates no such relationship. Judge each one on its permissions, its data flows, and its vendor terms.

Do we need a BAA with Patient Protect to use HIPAA Shield?

No. A business associate relationship arises when a vendor creates, receives, maintains, or transmits protected health information on a covered entity's behalf. Patient Protect does not receive or access PHI through HIPAA Shield — the extension transmits nothing, so no page content, field contents, or detection results ever reach us. Distributing the extension does not by itself create a business associate relationship with Patient Protect, and no BAA is required for use of Shield itself. HHS draws the same distinction: supplying software to a covered entity does not make the supplier a business associate where it has no access to the covered entity's PHI. This answer is scoped to the extension. Other Patient Protect services may involve their own contractual and business associate arrangements, which are handled separately.

Does installing HIPAA Shield make my practice HIPAA compliant?

No. It addresses one specific risky behavior: entering patient information into a browser form that should not receive it. It is not a risk analysis, a policy set, workforce training, a business associate program, or data loss prevention, and no HIPAA provision requires a browser extension.

Is HIPAA Shield really free?

Yes. The extension is open source under the MIT license. There is no premium tier, no paid plan, and no upsell.

Does the extension send my data anywhere?

No. The extension makes zero network requests and never transmits page content, form contents, detection results, or any other data. All detection runs in your browser. The full source is on GitHub — verify it yourself at github.com/patient-protect/hipaa-shield.

What does it detect, and what is on by default?

Eight rules. Social Security Numbers, dates of birth, credit card numbers (Luhn-checked), Medical Record Numbers and ICD-10 codes are on by default. Phone numbers, email addresses and clinical diagnosis terms are off by default, because they fire too often during ordinary browsing. Every rule is toggleable in the popup.

Which fields does it read?

Text, search, URL, telephone, email and password inputs, every textarea, and any editable region on the page. Password fields are included so that patient identifiers pasted into the wrong box are still caught. Nothing read from any field is transmitted, stored, or logged.

Will it work on Firefox or Edge?

It works on any Chromium-based browser: Chrome, Edge, Brave, Arc, Opera, Vivaldi. A Firefox port is in progress and will ship when Manifest V3 compatibility is finalized.

Can I customize what it detects?

Yes. Click the extension icon to open the settings popup, then toggle individual rules. Settings are stored locally via chrome.storage.local and never transmitted.

Release notes

Hear when Shield changes.

New detection rules, the Firefox port, and changes to what is on by default. Patient Protect product updates and new free tools go out on the same list. Nothing about your browsing, and nothing the extension detects — it has no way to tell us either.

What comes after

Shield covers one doorway. There are others.

The browser is one place patient data leaves a practice. Once it is watched, the useful next question is where else the data goes — and then whether the rest of the program holds up.

HIPAA Shield is one of 19 free resources Patient Protect publishes. See the full collection.

Part of the HIPAA Foundation · Free tools & resources

See the full collection
PreventMIT

Prevent disclosure

Shield catches the casual disclosure at the keystroke. The platform prevents the cascade of policy, training, and BAA gaps that made the disclosure possible in the first place.

Next in the sequence

ePHI Data Flow Mapper

Protection at the moment of the decision — not another document explaining what should have happened afterward.

The extension and the platform are separate. Shield detections do not sync to Patient Protect, the platform receives no telemetry from it, and nothing about your browsing is monitored. There is no integration between them — the extension makes no network requests at all.

From free tools to a running program

Ready to start the real work?

The extension addresses one risky moment in a browser. The Patient Protect platform manages the ongoing work around it — continuous monitoring, BAA tracking, audit-log review, workforce training, and incident response.

Free tools stay free — no account needed. The 14-day platform trial asks for a card for identity verification; no charge before day 14, cancel any time.