Skip to main content
Get your sensitive information detection running in minutes with Fiddler Guardrails for PII/PHI. This guide walks you through detecting PII, PHI, and custom entities to protect sensitive data across your applications.

What You’ll Build

In this quick start, you’ll implement a sensitive information detection system that:
  • Detects a comprehensive set of personally identifiable information (PII) entity types
  • Identifies protected health information (PHI) entity types for healthcare compliance
  • Configures custom entity detection for organization-specific data
  • Provides real-time detection with sub-second latency
Interactive TutorialFor more advanced examples, including batch processing, performance optimization, and production deployment patterns:Open the Complete Sensitive Information Guardrail Notebook in Google Colab →Or download the notebook from GitHub →

Prerequisites

  • Fiddler account with access token
  • Python 3.10+ environment
  • Basic understanding of data privacy concepts

Overview

Fiddler’s PII and PHI detection, powered by the Centor Model for PII/PHI, provides enterprise-grade protection against data leakage by automatically detecting sensitive information across multiple categories. These guardrails integrate seamlessly with Fiddler’s AI Observability platform, enabling continuous monitoring and automated compliance reporting.

Key Capabilities

  • PII Detection: a comprehensive set of entity types, including names, addresses, SSN, credit cards, emails, and phone numbers
  • PHI Detection: healthcare-specific entity types for HIPAA compliance
  • Custom Entities: Define organization-specific sensitive data patterns
  • Real-time Processing: Sub-second latency for production applications
1

Set Up Your Environment

Connect to Fiddler and configure the Sensitive Information Guardrail API:
2

Define Helper Functions

Create reusable functions for interacting with the API:
3

Example 1: PII Detection

Detect common personally identifiable information:
Expected Output:
4

Example 2: PHI Detection for Healthcare

Detect protected health information in medical contexts:
Expected Output:
5

Example 4: Custom Entity Detection

Define and detect organization-specific sensitive data:
Expected Output:

API Reference

Endpoint

Request Format

Request Parameters

Response Format

Response Fields

Supported Entity Types

PII Entities

The Centor Model for PII/PHI returns labels as lowercase strings — use these exact values when filtering responses.
  • Personal: person, date of birth
  • Contact: email, email address, phone number, mobile phone number, landline phone number, fax number, address, postal code
  • Financial: credit card number, credit card expiration date, cvv, cvc, bank account number, account number, iban
  • Government IDs: social security number, passport number, driver’s license number, tax identification number, license plate number, cpf, cnpj
  • Digital: ip address, digital signature, website

PHI Entities

  • Medical: medication, medical condition
  • Insurance: health insurance number, health insurance id number, national health insurance number
  • Identifiers: birth certificate number, serial number

Code Examples

Next Steps

After completing this quick start:

Summary

You’ve learned how to:
  • ✅ Detect a comprehensive set of PII entity types in text data
  • ✅ Identify PHI for healthcare compliance
  • ✅ Configure custom entities for your organization
  • ✅ Integrate the Fiddler Guardrails for PII/PHI API into your applications.
Fiddler Guardrails for PII/PHI offer enterprise-grade protection for sensitive information with sub-second latency, making them ideal for real-time applications while ensuring compliance with privacy regulations such as GDPR, HIPAA, and CCPA.