Skip to main content
This metric is particularly valuable for identifying sensitive personal data that may require special handling or protection. Detecting PII is essential for compliance with privacy regulations and protecting user information.

Calculation method

PII detection is computed through a specialized process:
1

Model Foundation

A specialized Small Language Model (SLM) trained on proprietary datasets forms the core of the detection system, enabling accurate identification of various PII types.
2

Content Analysis

The system performs comprehensive scanning of both input and output text, utilizing pattern recognition and contextual analysis to identify potential PII occurrences.
3

Classification Process

Each detected PII instance is systematically categorized by its specific type (e.g., SSN, email, address).

PII Categories Detected

The current model detects the following precisely defined categories:
Account Information: Bank account numbers, Bank Identification Code (BIC) and International Bank Account Number (IBAN).
Address: A physical address. Must contain at least a street name and number, and may contain extra elements such as city, zip code, state, etc.
Credit Card: Credit card number (can be full or last 4 digits), Card Verification Value (CVV) and expiration date.
Date of Birth: This represents the day, month and year a person was born. The context should make it clear that it’s someone’s birthdate.
Email: An email address.
Name: A person’s full name. It must consist of at least a first and last name to be considered PII.
Network Information: IPv4, IPv6 and MAC addresses.
Password: A password.
Phone Number: A phone number.
Social Security Number (SSN): A US Social Security Number.
Username: A username.

Optimizing your AI system

Addressing PII in Your System

When PII is detected in your system, consider these approaches:
Implement data redaction: Automatically mask or remove PII before processing or storing data.
Create PII handling policies: Develop clear guidelines for how different types of PII should be processed.
Set up user consent flows: Ensure users understand when and how their PII might be used.
Establish data retention policies: Define how long different types of PII should be stored.

Performance Benchmarks

We evaluated PII Detection against gold labels on the “test” split of rungalileo/pii dataset using top frontier models. This dataset was created from the open-source gretelai/synthetic_pii_finance_multilingual dataset by remapping its labels.

Classification Report

Benchmarks based on the rungalileo/pii evaluation dataset. Performance may vary by use case.

Best practices

Real-time PII Detection

Implement PII detection as part of your input validation pipeline to catch sensitive information before processing.

Data Minimization

Only collect and process the minimum amount of PII necessary for your application’s functionality.

Secure Storage

When PII must be stored, ensure it’s properly encrypted and access is strictly controlled.

Regular Audits

Periodically review your system for unintended PII exposure or collection.
Automatically identify PII occurrences in any part of the workflow (user input, chains, model output, etc), and respond accordingly by implementing guardrails or other preventative measures. This helps ensure compliance with privacy regulations like GDPR, CCPA, and others.