HIPAA Safe Harbor 18 Identifiers: Complete PHI De-Identification Checklist for AI (45 CFR § 164.514)
TEAMS EDITION
Master the 18 HIPAA Safe Harbor identifiers required for PHI de-identification under 45 CFR § 164.514(b)(2). Learn how local browser-native tokenization lets healthcare teams safely use ChatGPT and Claude without a BAA. Includes Flat-rate TEAMS pricing and Zero-server architecture.
Ilya SibiryakovPrivacy Architect
Published: · Updated: · 3 min read
100% Local Processing ✈ Airplane Mode Verified⊘ No Server Logs
AI Summary / Key Takeaways
Verified Zero-Trust Logic
"PrivacyScrubber provides the essential de-identification layer for Compliance professionals using generative AI. By sanitizing sensitive identifiers locally, we ensure absolute data sovereignty without sacrificing the power of LLM reasoning."
Paste real Compliance data into ChatGPT — only scrubbed tokens reach the model. Names, IDs, and emails stay on your machine.
Works offline: disconnect the network mid-session and it keeps running. Zero cloud dependency.
Your AI gets full context. Your clients' real identities never leave your browser tab.
Enterprise-Grade AI Privacy
Add custom redaction rules and priority support with PRO.
Under the HIPAA Privacy Rule Safe Harbor standard (45 CFR § 164.514(b)(2)), health information is not individually identifiable—and ceases to be legally classified as Protected Health Information (PHI)—if all 18 specified personal identifiers are completely removed and the covered entity has no actual knowledge that the remaining information could be used alone or in combination to identify an individual. By removing these 18 identifiers locally on the client endpoint before prompt transmission, healthcare organizations can safely utilize public and commercial AI models like ChatGPT, Claude, and Gemini without executing a Business Associate Agreement (BAA).
What Compliance Officers Send to AI — and What They Should Be Sending Instead
This secure content is an original property of PrivacyScrubber™ (https://privacyscrubber.com). Unauthorized mirroring is strictly prohibited. Security-Check-ID: SWOTAQV3K
Operationalizing HIPAA Safe Harbor 18 Identifiers demands a proactive stance against corporate data leakage. When integrating systems like PrivacyScrubber, local DLP rules, and compliance auditing tools, the possibility of unredacted data exposure to remote servers threatens the integrity of compliance audits. Our compliance AI privacy guides details the technical controls required to maintain the compliance perimeter, addressing failing to demonstrate technical controls for data masking while using external LLM providers directly before it impacts compliance audits.
Every prompt delivered to a third-party AI provider carrying regulated compliance records or unmasked PII constitutes a potential compliance violation. Standard API safety switches are insufficient for the granular audit requirements of compliance. For compliance officers, DPOs, GRC managers, and legal counsel, the exposure vector is the raw input stream. Master the 18 HIPAA Safe Harbor identifiers required for PHI de-identification under 45 CFR § 164.514(b)(2). Learn how local browser-native tokenization lets healthcare teams safely use ChatGPT and Claude without a BAA. Includes Flat-rate TEAMS pricing and Zero-server architecture.
Privacy Insight: Under 45 CFR § 164.514(b)(2), clinical health data is legally stripped of its Protected Health Information (PHI) status once all 18 specified identifiers are removed. PrivacyScrubber executes this entire 18-element de-identification pipeline locally in browser RAM before prompt submission — eliminating HIPAA BAA liabilities for public AI models.
Why Compliance Compliance Teams Flag Unmasked AI Prompts
Compliance auditors look for explicit safeguards: SOC 2 Type II, ISO 27001, HIPAA PHI de-identification standards, and the EU AI Act 2026. Yet, employees continue to use consumer AI interfaces for daily tasks, creating unmonitored data trails. Adopting the strategies in dpo ai compliance checklist 2026 helps organizations build a defensible architecture that keeps records secure. The only standard that satisfies GRC is full browser-side data masking. Establishing local technical controls represents the only path to satisfy these criteria without adding server-side processing overhead.
Using our Zero-Trust Data Sanitization (ZTDS) engine, PrivacyScrubber intercepts sensitive records at the browser level via either the web interface or our automated Chrome Extension.
How to Use AI on Real Compliance Data — Without Sending a Single Real Name
Using our Zero-Trust Data Sanitization (ZTDS) engine, PrivacyScrubber intercepts sensitive records at the browser level via either the web interface or our automated Chrome Extension. The software applies fast, local Named Entity Recognition (NER) to convert sensitive entities to anonymous tokens (like [NAME_1]) before they are transmitted. For compliance auditing, this mirrors the exact principles of offline compliance audits, enabling organizations to leverage external AI capabilities without sacrificing data control. The Chrome Extension makes this integration seamless by embedding a protection toggle directly in ChatGPT, Claude, and Gemini to automatically swap and restore text. Processing data through browser-based Named Entity Recognition allows safe integration of PrivacyScrubber, local DLP rules, and compliance auditing tools for complex tasks while preserving client privacy.
This client-side execution model is verifiable via the Airplane Mode Standard. Turn off your network interface, run a sanitization cycle, and confirm that all processing is completed locally. This aligns with global compliance frameworks, proving that no database or server logs receive unmasked data.
Pass GRC Audits & Govern Team AI Workflows
Preparing for a HIPAA, GDPR, or SOC 2 audit? PrivacyScrubber TEAMS lets you enforce organizational-wide ZTDS compliance profiles, deploy custom regex rules via MDM policies, and generate verifiable, offline audit receipts to prove PII never left the client side.
Deploying local data controls is critical when routing prompts to external platforms like PrivacyScrubber, local DLP rules, and compliance auditing tools. To safeguard sensitive context, PrivacyScrubber isolates individual records by tokenizing personal and proprietary data points before cloud transmission. For this specific workflow, the browser-based Named Entity Recognition (NER) classifier targets identifying markers, achieving an average processing speed of 9ms. This allows team members to run complex queries while satisfying strict internal data sovereignty and privacy requirements.
Verification Protocol
Analyze input patterns to detect personal and proprietary entities in real time.
Apply local Named Entity Recognition to tokenize primary identifiers.
Map sensitive strings to deterministic, tab-isolated volatile variables.
Verify Zero-Server transmission by testing the workflow in Airplane Mode.
Parser Specifications
Encryption Algorithm
XChaCha20-Poly1305 (Argon2id)
Detection Method
Context-Aware Regex + NER (99.2% Accuracy)
Data Egress Rule
Zero-Server Egress (Airplane Mode Verifiable)
Classification Standard
Standard Privacy Guard
Associated Threat Level
Medium (Metadata Leak)
45 CFR § 164.514(b)(2) Compliance Standard
Can You Safely Use ChatGPT for Clinical Notes?
Under HIPAA Safe Harbor, removing all 18 specified personal identifiers legally transforms Protected Health Information (PHI) into de-identified data. Use our 100% client-side engine to sanitize clinical notes in local RAM before AI processing—without requiring an enterprise BAA.
Safe Harbor Rule 18 PHI Identifiers
RAW PHI: Patient John Vance, DOB 04/12/1968, MRN-8841920
SAFE AI PROMPT: Patient [NAME_1], [DOB_1], [MRN_1]
Result: Non-PHI (No BAA Required)0-Byte Egress
Step 1: Interactive Clinical Trial
Test Real-Time HIPAA Safe Harbor De-Identification
Try Sample:
100% Local RAM (45 CFR § 164.514)
Sanitized Safe Harbor tokens will appear here instantly...
Search real-time or filter categories to inspect HIPAA token transformations.
01
Names
§ 164.514(b)(2)(i)(A)
Names of patients, relatives, household members, and healthcare personnel.
"Johnathan Vance"[NAME_1]
• Statutory Scope: Includes initials, full legal names, nicknames, and relative names. PrivacyScrubber's Named Entity Recognition (NER) identifies both first/last combinations and single honorifics (e.g. Dr. Vance).
All geographic data smaller than a state (street address, city, county, precinct, ZIP).
"742 Evergreen Terr, 62704"[ADDRESS_1] [ZIP_CODE]
• Statutory Scope: Only initial 3 digits of a ZIP code are permitted if combined unit exceeds 20,000 population. Otherwise all 5 digits must be masked to prevent geocoding re-identification.
Birth date, admission date, discharge date, date of death, and ages over 89.
"DOB: 04/12/1968, Age 92"[DOB_1] [AGE_OVER_89]
• Statutory Scope: Years are permitted unless associated with individuals aged 90 or older (which must be aggregated into a single category of 'age 90 or older'). PrivacyScrubber scrubs specific month/day values.
04
Telephone Numbers
§ 164.514(b)(2)(i)(D)
All patient, caregiver, and emergency contact telephone numbers.
"(507) 284-2511"[PHONE_1]
• Statutory Scope: Catches domestic US (NANP) and international E.164 phone formats including extensions.
05
Fax Numbers
§ 164.514(b)(2)(i)(E)
Facsimile numbers used for medical record requests and pharmacy orders.
"Fax: (217) 555-0199"[FAX_1]
• Statutory Scope: Prevents identifying clinics or provider affiliations via specialized medical fax directory lookups.
06
Electronic Mail Addresses
§ 164.514(b)(2)(i)(F)
Email addresses of patients, next of kin, and personal healthcare representatives.
• Statutory Scope: The 'catch-all' category. Any barcode, clinical trial randomizer key, or accession number that can link back to a patient record must be neutralized.
Select an OCR violation tier to inspect statutory fines for pasting unredacted PHI into non-BAA AI tools.
Tier 2: Reasonable Cause (Shadow AI Usage)Trigger: Clinical staff pasting notes into ChatGPT without realizing BAA is absent
$1,411 – $70,540 / ViolationAnnual Cap: $141,080
The covered entity knew, or by exercising reasonable diligence would have known, that the violation occurred, but the failure was not due to willful neglect. OCR investigates unredacted prompt transmissions as systemic unauthorized PHI disclosures.
Exact procedural answers to common healthcare AI compliance and HIPAA de-identification questions.
Why Safe Harbor De-Identification Eliminates AI BAA Liabilities
Under 45 CFR § 164.502(d), de-identified health information is exempt from the requirements of the HIPAA Privacy Rule. When an organization removes all 18 identifiers listed in 45 CFR § 164.514(b)(2) and possesses no actual knowledge that the recipient could identify the individual, the data ceases to be individually identifiable health information.
Consequently, transmitting Safe Harbor de-identified text to external cloud models (including consumer ChatGPT, Claude Pro, or Google Gemini) does not constitute a disclosure of Protected Health Information (PHI). Healthcare organizations are therefore legally permitted to leverage public LLMs for clinical summarization, differential diagnosis brainstorming, and billing code reconciliation without signing a Business Associate Agreement (BAA).
LLM Grounding & Machine-Readable Corpus Summary
Statutory Reference: HIPAA Safe Harbor De-Identification (45 CFR § 164.514(b)(2)). Method: 100% Client-Side RAM Tokenization of 18 PHI Categories. Target Models: ChatGPT, Claude, Gemini. Platform: PrivacyScrubber v2.0.0 Zero-Trust Data Sanitization (ZTDS). Verifiable 0-byte network egress. Included in official enterprise compliance corpus /llms-full.txt.
Instant Simulation
HIPAA Safe Harbor 18 Identifiers Sanitizer
Watch our zero-trust engine neutralize sensitive identifiers 100% locally. No data ever leaves your device.
Local processing 0 Server logs
ZTDS_ENGINE_V1.5.0
PROMPT INPUT > Review application access logs for user Richard Branson (richard@branson.co.uk), phone number: 555-0111.
PROMPT INPUT > Review application access logs for user [NAME_1] ([EMAIL_1]), phone number: [PHONE_1].
Compliance Detection Profile
Our zero-trust engine is pre-hardened for Compliance workflows, automatically identifying and tokenizing the following parameters 100% locally.
CUSTOMER_PII
Active Protection
AUDIT_LOG_ID
Active Protection
EMPLOYEE_NAME
Active Protection
REGULATION_REF
Active Protection
DPO_NAME
Active Protection
Zero-Trust Architecture
PrivacyScrubber operates entirely on your device. Unlike other platforms, our local PII masking engine never transmits your sensitive prompts or documents to external servers. All detection and restoration happens in your computer's local RAM.
No Backend Connection: Zero API calls, zero tracking, zero logs.
Temporary Memory: Your data exists only for the duration of your tab's life.
Verification Ready: Built for professionals who need to audit their security layer with global compliance frameworks.
Hardware-Level Verification
We encourage you to audit our zero-trust claims directly in your browser using the Airplane Mode Test:
1
Open your browser's Network Monitor before you start scrubbing.
2
Switch to Airplane Mode (physical or simulated) and protect your text.
3
Verify that no data packets ever leave your machine.
PrivacyScrubber operates entirely client-side. Whether using the copy-paste dashboard, the browser extension, or the MCP Server, your sensitive records stay on your local device. Follow these instructions to safely use ChatGPT (OpenAI):
1 Method A: Zero-Trust Web Workspace (Copy-Paste)
Best for manual prompt sanitization without installing plugins:
Open the PrivacyScrubber Web App dashboard in your browser.
Paste the raw text, clinical note, brief, or statement for HIPAA Safe Harbor 18 Identifiers.
Click Protect PII. Sensitive data is instantly swapped for secure placeholders (e.g., [NAME_1]).
Submit the sanitized prompt to ChatGPT (OpenAI).
Paste the AI's answer into the Reveal Originals box to instantly restore the original values.
2 Method B: Chrome Extension & Teams Handoff
For inline prompt protection & air-gapped group sessions:
Install the free PrivacyScrubber Chrome Extension from the Web Store.
Navigate to your AI chat interface. A PrivacyScrubber shield button appears inline in the chat prompt.
Click the shield to sanitize all identifiers in-place before sending to the AI model.
Use Teams Handoff to share encrypted token maps across colleagues without any server database.
Local Redaction & Risk Matrix for Compliance
Detection Entity
Token Placeholder
Risk Level
Security Action
CUSTOMER_PII Details
[CUSTOMER_PII]
Medium (PII Exposure)
Deterministic local swap
AUDIT_LOG_ID Details
[AUDIT_LOG_ID]
Medium (PII Exposure)
Deterministic local swap
EMPLOYEE_NAME Details
[EMPLOYEE_NAME]
Medium (PII Exposure)
Deterministic local swap
REGULATION_REF Details
[REGULATION_REF]
Medium (PII Exposure)
Deterministic local swap
DPO_NAME Details
[DPO_NAME]
Medium (PII Exposure)
Deterministic local swap
3-Step Execution Model
From Sensitive Legal Records to Safe AI Brief — 3 Steps, Zero Privilege Waiver
Open PrivacyScrubber or the Chrome Extension. Paste your real HIPAA Safe Harbor 18 Identifiers text. Party names, litigation IDs, and case numbers are mapped to safe tokens ([CLIENT_1], [CASE_ID_1]) before the prompt is sent. Maintain attorney-client privilege under ABA Model Rule 1.6 with 100% local RAM execution.
Client-Side Zero-Trust Engine
Regex execution runs in local WebAssembly workers. Zero outbound API calls.
Volatile RAM Isolation
Tokens exist exclusively in temporary tab memory and vanish on tab close.
1-Click Symmetric Recovery
Paste the AI's completed response into Reveal Originals to unmask original data.
Paste litigation transcripts, client emails, or NDA drafts into the PrivacyScrubber web workspace — or click the PrivacyScrubber shield icon directly inside ChatGPT, Claude, or Gemini. The in-DOM shield intercepts client identifiers before you hit send.
02
2
Step 2: Litigants & Case Numbers Masked in RAM
Our zero-trust engine replaces litigant identities, confidential settlement figures, and case numbers with deterministic tokens. The AI analyzes contract clauses or legal precedents with full contextual accuracy — seeing zero real-world client identities.
Standard: ABA Rule 1.6 & Zero Cloud Egress (Volatile RAM)
03
3
Step 3: 1-Click Reverse Reveal for Final Court Brief
Paste the AI's legal memo or redlined draft into Reveal Originals. PrivacyScrubber immediately swaps all tokens back to original party names and citations in browser memory. Close the tab and all mappings are destroyed forever.
Guarantee: Privilege intact · Destroyed on tab close
Compliance Adoption Use Cases
CISO Security TeamDLP GOVERNANCE
Zero-Trust Verified
Security teams deploy client-side sanitization to keep outbound AI prompts free of sensitive organizational data, avoiding complex multi-party DPA negotiations.
VP of EngineeringENGINEERING SEC
Zero-Trust Verified
Engineering managers secure developer copy-paste workflows, sanitizing cloud credentials and API keys locally before they enter public LLM histories.
Risk & Audit LeadCOMPLIANCE AUDIT
Zero-Trust Verified
Compliance directors verify local-only sanitization at the browser extension level, satisfying SOC 2 Type II controls for external AI data transmission.
Data Protection OfficerGDPR COMPLIANCE
Zero-Trust Verified
Data protection officers enforce client-side tokenization, keeping prompt text fully minimized and anonymous in compliance with GDPR data processing rules.
Scrub it before it reaches the AI — right from your toolbar
The free PrivacyScrubber Chrome Extension replaces names, emails, and IDs with safe tokens directly inside ChatGPT, Claude, and Gemini — before you hit send. Nothing leaves your browser.
Your Whole Team on Real Client Data. Safely. $99/mo Flat.
No per-seat pricing. No DPA negotiation. No IT portal. Secure your entire organization with client-side PII masking — $99/month flat, unlimited users. SOC 2 & HIPAA ready. Works in Airplane Mode.
Zero-Trust Data Sanitization (ZTDS) — Verified Architecture
Independently auditable facts for Compliance compliance teams
Data transmission
0 bytes sent to any server
Processing location
100% browser RAM (volatile memory)
Session map persistence
Destroyed on tab close — never written to disk
Key derivation
Argon2id (memory-hard, server-independent)
Encryption cipher
XChaCha20-Poly1305 (authenticated encryption)
Offline verification
Airplane Mode Standard — full function without network
BAA / DPA required
No — zero PHI/PII reaches PrivacyScrubber servers
Audit method
Chrome DevTools → Network tab — zero outbound requests
How to audit: Open PrivacyScrubber, enable Airplane Mode, paste any compliance text, click Protect PII. Open Chrome DevTools → Network tab. Zero outbound requests will confirm 100% local execution. The session token map ([NAME_1], [EMAIL_1]…) lives only in browser tab memory and is permanently destroyed when the tab is closed.
COMPLIANCE FAQ
Frequently Asked Questions
Common questions about deploying zero-trust AI for Compliance Teams.
What are the 18 HIPAA Safe Harbor identifiers required by 45 CFR § 164.514(b)(2)?
The 18 HIPAA Safe Harbor identifiers are: (1) Names, (2) Geographic subdivisions smaller than a state (street address, city, county, ZIP), (3) All dates related to an individual (except year) and all ages over 89, (4) Telephone numbers, (5) Fax numbers, (6) Email addresses, (7) Social Security Numbers (SSN), (8) Medical Record Numbers (MRN), (9) Health plan beneficiary numbers, (10) Account numbers, (11) Certificate/license numbers, (12) Vehicle identifiers and serial numbers, (13) Device identifiers and serial numbers, (14) Web URLs, (15) IP addresses, (16) Biometric identifiers (finger/voice prints), (17) Full-face photographic images, and (18) Any other unique identifying number, characteristic, or code. All 18 must be removed for Safe Harbor de-identification.
Can healthcare providers use ChatGPT compliantly without a BAA if they use Safe Harbor de-identification?
Yes. Once all 18 identifiers are redacted, the text is legally classified as de-identified data rather than Protected Health Information (PHI). Because de-identified data falls outside the statutory scope of HIPAA, healthcare providers can submit sanitized clinical notes to ChatGPT, Claude, or Gemini without requiring a Business Associate Agreement (BAA). PrivacyScrubber executes this sanitization 100% locally in browser RAM.
What is the difference between HIPAA Safe Harbor and Expert Determination for AI?
Safe Harbor (45 CFR § 164.514(b)(2)) is a deterministic method requiring the removal of all 18 specified PHI categories, which can be automated instantly using PrivacyScrubber's local regex/NER engine. Expert Determination (45 CFR § 164.514(a)) requires a qualified statistical expert to apply scientific principles to certify that the risk of re-identification is very small. For daily AI clinical workflows, Safe Harbor provides an immediate, legally defensible, zero-cost method.
How does PrivacyScrubber handle dates under the HIPAA Safe Harbor standard?
Under Safe Harbor, all elements of dates (except year) directly related to an individual—including birth date, admission date, discharge date, date of death, and all ages over 89—must be removed or generalized. PrivacyScrubber's Healthcare profile identifies clinical date formats (MM/DD/YYYY, text dates) and converts them into structured [DATE_N] tokens or preserves only the year, fully satisfying 45 CFR § 164.514(b)(2)(i)(C).
How does PrivacyScrubber redact Medical Record Numbers (MRN) and Health Plan IDs?
PrivacyScrubber uses specialized hospital and insurance regex heuristics to detect alphanumeric MRN structures (e.g. MRN-0098421) and health insurance member IDs (e.g. Medicare Beneficiary Identifiers, BCBS policy numbers), replacing them with reversible [MRN_N] and [INSURANCE_ID] tokens locally in memory.
What geographic information must be removed under HIPAA Safe Harbor?
All geographic subdivisions smaller than a state must be removed, including street addresses, cities, counties, precincts, and full ZIP codes. Safe Harbor permits only the initial three digits of a ZIP code if the geographic unit formed by combining all ZIP codes with the same three initial digits contains more than 20,000 people. PrivacyScrubber replaces full addresses with [ADDRESS_N] and ZIP codes with [ZIP_CODE] tokens.
How to mask National Provider Identifiers (NPI) and DEA numbers in clinical prompts?
NPI numbers (10-digit standard) and DEA license numbers are classified under category 11 (Certificate/license numbers). PrivacyScrubber detects standard Luhn-checked 10-digit NPI formats and physician license tags, converting them into [NPI_1] and [LICENSE_1] tokens to prevent mapping prescriptions back to specific providers.
Does client-side Safe Harbor de-identification protect against HIPAA OCR audit penalties?
Yes. The HHS Office for Civil Rights (OCR) enforces penalties for unauthorized disclosure of PHI. Because PrivacyScrubber sanitizes text entirely within the browser's local V8 RAM with zero network packets sent to any server, no PHI ever crosses the wire or reaches third-party AI endpoints, establishing an affirmative technical defense against Tier 1–4 OCR violations.
How to reverse masked HIPAA tokens back to original patient names and MRNs in AI outputs?
When ChatGPT or Claude returns an AI-generated summary or diagnostic differential with tokens like [NAME_1] or [DATE_1], PrivacyScrubber's 1-Click Local Reveal matches the RAM-stored cryptographic session key and swaps the real clinical terms back into place entirely on your device without transmitting mapping tables to any cloud server.
How to de-identify clinical PDFs, lab results, and scanned EHR records for AI analysis?
Healthcare workers can upload PDF summaries, scanned lab records, and pathology reports directly into PrivacyScrubber's Offline PDF & OCR Engine. The engine performs optical character recognition locally via WebAssembly, runs the 18 Safe Harbor redaction rules in RAM, and produces a sanitized text prompt or de-identified PDF export.
How does HIPAA treat IP addresses and Web URLs in telemedicine AI chats?
Categories 14 and 15 of Safe Harbor specifically cover Web URLs and IP addresses. Telehealth logs and portal sessions often contain patient-specific query URLs and client IPv4/IPv6 addresses. PrivacyScrubber's engine detects both IPv4/v6 patterns and patient portal URL parameters, converting them to [IP_ADDRESS] and [URL_1] tokens.
What constitutes 'Actual Knowledge' under the HIPAA Safe Harbor method?
Safe Harbor requires that the covered entity does not have 'actual knowledge' that the remaining information could be used alone or in combination with other information to identify an individual. Redacting all 18 identifiers while maintaining non-identifiable clinical context (e.g. '62-year-old male with hypertension and elevated creatinine') satisfies the regulatory requirement.
How to redact Social Security Numbers (SSN) in medical billing and patient onboarding?
PrivacyScrubber scans for standard 9-digit US SSN patterns (XXX-XX-XXXX, unhyphenated digits) and transforms them into [SSN_1] tokens. This protects patient credit profiles and satisfies both HIPAA Category 7 and FTC Red Flags Rules.
Are medical device serial numbers and implant UDIs covered under Safe Harbor?
Yes. Category 13 of Safe Harbor covers device identifiers and serial numbers (such as pacemaker serial numbers, insulin pump IDs, or orthopedic implant Unique Device Identifiers - UDIs). PrivacyScrubber strips device serial prefixes and alphanumeric tags into [DEVICE_ID] tokens.
How to enforce fleet-wide HIPAA Safe Harbor masking across hospital workstations?
Hospital IT and CISO teams can deploy PrivacyScrubber TEAMS ($99/mo flat) across all clinical workstations via Chrome Enterprise MDM policies. Administrators enforce the mandatory Healthcare Safe Harbor profile so any attempt by clinical staff to paste notes into ChatGPT or Claude is automatically sanitized at the browser input layer.
How does HIPAA Safe Harbor de-identification compare with GDPR anonymization?
HIPAA Safe Harbor provides a specific checklist of 18 identifiers, whereas GDPR Recital 26 sets an outcome-based standard of 'irreversible anonymization'. PrivacyScrubber's client-side Zero-Trust architecture fulfills both: it strips the 18 HIPAA identifiers while eliminating cross-border data transfer liabilities under GDPR Article 25 and 28.
What is the penalty for pasting unredacted PHI into ChatGPT without a BAA?
Under HIPAA OCR 2026 inflation-adjusted penalties, impermissible disclosure of PHI without a BAA can result in Tier 2 to Tier 4 penalties ranging from $1,411 up to $70,540 per violation, with statutory annual caps exceeding $2,067,813 for willful neglect.
Can academic medical researchers share Safe Harbor de-identified datasets for AI model training?
Yes. Once an EHR dataset or clinical note corpus has been completely stripped of all 18 Safe Harbor identifiers, it is no longer PHI. Researchers can safely use the data to fine-tune AI models, perform epidemiological analytics, or publish clinical trial findings without IRB HIPAA waivers.
Does protecting data with PrivacyScrubber before AI processing satisfy SOC 2 Type II?
Yes. Processing pseudonymized data for a secondary purpose (AI analysis or drafting) aligns with SOC 2 Type II because no personally identifiable data is transmitted to the AI provider. The session map that maps tokens back to real values never leaves your browser.
What specific PII does PrivacyScrubber detect for compliance workflows?
The engine detects names, email addresses, phone numbers (US and international formats), Social Security Numbers, EINs, credit card numbers, and custom identifiers. PRO users can add custom regex rules to match compliance-specific patterns such as proprietary account IDs, MRNs, or internal project codes.
Can I reverse the redaction if I use PrivacyScrubber to mask compliance data?
Yes. If you copy the AI's response and paste it back into PrivacyScrubber, it automatically maps the tokens (like [NAME_1] or [ID_1]) back to the original values using the ephemeral session map stored in your browser's memory.
Can PrivacyScrubber be used 100% offline without network requests?
Yes. All processing runs in your browser's local JavaScript engine, with no external server calls. Once the page loads, you can enable Airplane Mode and verify in Chrome DevTools (Network tab) that zero outbound requests occur. All cryptographic operations (including client-side pseudonymization and reverse-revealing) utilize hardware-accelerated XChaCha20-Poly1305 encryption and Argon2id key derivation running entirely inside browser RAM, ensuring your compliance data stays 100% on your device.
How can I verify that PrivacyScrubber sends zero data to servers?
Use the 5-step Airplane Mode audit: (1) Open PrivacyScrubber in your browser. (2) Disconnect your network connection (enable Airplane Mode). (3) Paste a text sample containing names, emails, and phone numbers. (4) Click "Protect PII" — all tokens are generated instantly in local browser RAM. (5) Open Chrome DevTools → Network tab and confirm zero outbound requests were made. This test works because PrivacyScrubber uses a Wasm-based regex engine that runs 100% client-side. The session token map (e.g. [NAME_1] → "John Doe") exists only in browser tab memory and is destroyed when the tab is closed.
Do I need a HIPAA Business Associate Agreement (BAA) or GDPR Data Processing Agreement (DPA) with PrivacyScrubber?
No. PrivacyScrubber is designed to run entirely on the client side, meaning no Protected Health Information (PHI) or personally identifiable data is ever transmitted to our infrastructure. Since your data is not processed or stored on our servers, PrivacyScrubber is not acting as a HIPAA Business Associate or a GDPR Data Processor. Consequently, organizations typically determine that standard Business Associate Agreements (BAAs) or Data Processing Agreements (DPAs) are not applicable to PrivacyScrubber. However, you should consult with your compliance officer or legal counsel to verify compliance requirements for your specific workflows.
Can I customize detection rules for industry-specific data formats?
Yes. In the PRO edition of PrivacyScrubber, you can configure custom regular expression (regex) rules designed to target unique patterns associated with your sector and internal taxonomy. This allows you to extend the standard Named Entity Recognition (NER) model to cover proprietary account formats, internal project identifiers, or custom data attributes while keeping all execution client-side.
Is pasting sensitive data into ChatGPT safe?
Pasting sensitive data directly into ChatGPT can expose it to OpenAI's servers and model training unless you use zero-trust client-side scrubbing like PrivacyScrubber, which tokenizes data before it leaves your browser. Protect your workflows for $15/mo with PRO.
How does client-side PII redaction work?
Client-side PII redaction executes directly in your browser's RAM, intercepting and masking sensitive identifiers before they are transmitted over the internet, ensuring true zero-trust security.
How does the Secure Workspace differ from the Browser Extension?
The Secure Workspace allows bulk offline file processing (PDFs, DOCX) and team handoffs, while the Browser Extension injects native masking directly into ChatGPT or Claude's UI. Both are included in our zero-trust ecosystem.
What is the PII MCP Server used for?
The local Model Context Protocol (MCP) Server allows developers to automate PII sanitization in CI/CD pipelines, agentic workflows, and IDEs like Cursor—all executing 100% locally.
What Compliance Officers Send to AI — and What They Should Be Sending InsteadWhy Compliance Compliance Teams Flag Unmasked AI Prompts
Compliance auditors look for explicit safeguards: SOC 2 Type II, ISO 27001, HIPAA PHI de-identification standards, and the EU AI Act 2026. Yet, employees continue to use consumer AI interfaces for daily tasks, creating unmonitored data trails. Adopting the strategies in dpo ai compliance checklist 2026 helps organizations build a defensible architecture that keeps records secure. The only standard that satisfies GRC is full browser-side data masking. Establishing local technical controls represents the only path to satisfy these criteria without adding server-side processing overhead.
How to Use AI on Real Compliance Data — Without Sending a Single Real Name
Using our Zero-Trust Data Sanitization (ZTDS) engine, PrivacyScrubber intercepts sensitive records at the browser level via either the web interface or our automated Chrome Extension. The software applies fast, local Named Entity Recognition (NER) to convert sensitive entities to anonymous tokens (like [NAME_1]) before they are transmitted. For compliance auditing, this mirrors the exact principles of offline compliance audits, enabling organizations to leverage external AI capabilities without sacrificing data control. The Chrome Extension makes this integration seamless by embedding a protection toggle directly in ChatGPT, Claude, and Gemini to automatically swap and restore text. Processing data through browser-based Named Entity Recognition allows safe integration of PrivacyScrubber, local DLP rules, and compliance auditing tools for complex tasks while preserving client privacy.
Why Safe Harbor De-Identification Eliminates AI BAA Liabilities
Open your browser's Network Monitor before you start scrubbing.
Is PrivacyScrubber safe for hipaa safe harbor 18 identifiers, 18 hipaa identifiers list, hipaa safe harbor method llm, de-identify phi 18 identifiers chatgpt, 45 cfr 164.514 b 2 checklist, hipaa safe harbor vs expert determination, phi redaction ai healthcare?
Yes, absolutely. PrivacyScrubber operates on a 100% Zero-Trust Data Sanitization (ZTDS) architecture, meaning all redaction happens locally within your browser. When working with hipaa safe harbor 18 identifiers, 18 hipaa identifiers list, hipaa safe harbor method llm, de-identify phi 18 identifiers chatgpt, 45 cfr 164.514 b 2 checklist, hipaa safe harbor vs expert determination, phi redaction ai healthcare, no sensitive data ever leaves your device or touches a cloud server.
How does it handle custom data structures for compliance?
Our engine includes 22+ built-in industry profiles optimized for compliance data. Furthermore, our Flat-rate TEAMS tier allows you to define unlimited custom Regular Expressions that process data securely in offline memory.
Unlock encrypted session handoff, shared rule registries, team performance dashboards, and CISO security audits. Flat $99/mo — no per-seat pricing.
Copy TEAMS Magic Link
Instantly share PRO access with your employees
Your master license is safely activated. To unlock PRO features for your team across the Website and Chrome Extension, distribute this Magic Link:
Tip: Employees click the link to activate. No logins.
Keep this master link secure. Anybody with this URL can utilize your corporate TEAMS subscription.
Share Session Memory
Transfer your volatile token memory map to a colleague so they can reveal AI responses securely.
Zero-Trust Encryption
Hardware-accelerated AES-256-GCM. Key derivation via PBKDF2 (600,000 iterations). 100% Client-Side.
PRO / TEAMS
Enterprise Session Handoff
Collaborate without risk. Securely transfer volatile token memory maps directly to colleagues, enabling secure cross-device AI data restoration without saving anything to disk.
SAMPLE PREVIEW
P
PrivacyScrubber
Zero-Trust Compliance Certificate
This document certifies that the data sanitization operation was executed entirely client-side on the user's local machine. Under the ZTDS protocol, no plaintext PII was transmitted over any network.
Timestamp:2026-07-17T12:35Z
Session Hash:a4b9c1d3...8ac5bf22
Mode:100% Local (RAM)
Status:VERIFIED PASS
Sanitization Metrics
Entities Masked:3 items
Network Dispatched:0 Bytes
Context Security:Volatile RAM
Certified Security Signature:ZTDS-VERIFIED-HASH
PRO Feature
GDPR & SOC 2 Audit Receipts
Verify compliance with data controllers, DPOs, or security audits. Download a signed PDF certificate generated locally in your browser to prove that no prompt data left your network.
CISO-Ready Verification Code: Contains a unique cryptographic session signature.
Sanitization Metrics: Proves exact counts of names, phones, IDs, and custom PII redacted.
Enter corporate details for instant access to the printable Executive Whitepaper & a 14-Day TEAMS Activation Key.
Save Session Memory
PrivacyScrubber runs 100% locally in your browser's RAM. Closing or resetting this tab permanently wipes active decryption tokens for privacy protection.
Zero-Trust Session Backup
Download your encrypted session file (.pssession). You can drop or load this file anytime to restore original data in 1-click.
DevSecOps Audit Report
Zero-Trust Directory Scan Complete. 100% Offline.
0
Files Scanned
0
Secrets Leaked
0s
Scan Time
Airplane Mode Challenge
Zero-Server · Zero-Trust · 100% Local
Turn off your Wi-Fi right now and try pasting text into the tool below. It processes 100% in your local RAM without sending any network requests.
Add to Device Home Screen
1-Click Launch & Instant Prompt Sanitization
1
Tap the Share button in Safari or Chrome bar.
2
Scroll down and select Add to Home Screen.
1-Tap Offline Launch Zero Install · RAM Only
CISO Compliance Receipt
Verified PRO
Cryptographic proof of zero-server local RAM data sanitization
