HIPAA Compliant

Keep PHI Out of
Your AI Stack

De-identify clinical notes without breaking analytics. Joinable tokens + round-trip re-ID + cryptographic audit trails.

Input (PHI)
Output (De-identified)
Click "De-identify" to see the result...
PHI Found: -
Processing: -
Tokens: -

What Makes Redact Different

Three core differentiators that no competitor offers at our price point.

🔗

Joinable Tokenization

Same patient across 1000 documents = same token. Enable longitudinal analysis without exposing PHI.

🔄

Round-Trip Re-ID

De-ID → Send to LLM → Get response → Re-ID. Critical for AI scribes and clinical documentation AI.

📜

Cryptographic Receipts

Every operation produces a signed receipt proving what went in, what came out, and what was found.

🏥

HIPAA Safe Harbor

Detects all 18 HIPAA identifiers plus clinical extensions. Ages >89 automatically generalized.

📄

FHIR & HL7v2 Support

Native parsing of healthcare data formats. Process structured and narrative text together.

Fast & Scalable

Process 100+ documents per second. Pattern engine runs on CPU, no GPU required.

Simple, Transparent Pricing

Start free, scale as you grow. No hidden fees.

Developer

For testing and development

$0
1,000 docs/month free
  • Pattern-based detection
  • All transform policies
  • API access
  • Community support
Get API Key
Enterprise

For healthcare organizations

Custom
Volume discounts available
  • Everything in Pro
  • Dedicated infrastructure
  • Custom integrations
  • BAA included
  • SLA guarantee
  • 24/7 support
Contact Sales

Built for Healthcare

Security and compliance are foundational, not afterthoughts.

🔒

SOC 2 Type II

In progress. Expected Q2 2025.

🏥

HIPAA Compliant

BAA available for all paid plans.

🗑️

Zero Retention

PHI never stored. Memory only.

🔐

Encryption

TLS 1.3 + AES-256-GCM.

Simple API, Powerful Results

One endpoint. JSON in, JSON out. Start in minutes.

POST /api/v1/deidentify
# De-identify clinical text
curl -X POST https://api.redact.health/api/v1/deidentify \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d '{
    "text": "Patient John Smith, DOB 01/15/1980",
    "policy": "safe_harbor"
  }'

# Response
{
  "text": "Patient [NAM_abc123], DOB 02/02/1980",
  "document_id": "doc-xyz789",
  "phi_found": 2,
  "phi_types": {"PATIENT_NAME": 1, "DOB": 1}
}