Detect and redact phone numbers in formats from 150+ countries. Mobile, landline, toll-free, and international formats with 99.8% accuracy.
Comprehensive detection across all formats and regions
Recognize phone formats from every country including country codes, area codes, and local number patterns.
Mobile, landline, toll-free, premium rate, VoIP, and emergency numbers detected and classified.
Handles all formatting variations: parentheses, dashes, spaces, dots, and international prefixes (+, 00).
Contextual analysis distinguishes phone numbers from dates, IDs, and other numeric sequences.
Full redaction, last 4 digits, area code preservation, or custom masking patterns.
Support compliance with telephone privacy regulations including TCPA and international equivalents.
Simple integration, powerful results
Send your documents, text, or files through our secure API endpoint or web interface.
Our AI analyzes content to identify all sensitive information types with 99.7% accuracy.
Sensitive data is automatically redacted based on your configured compliance rules.
Receive your redacted content with full audit trail and compliance documentation.
Get started with just a few lines of code
import requests
api_key = "your_api_key"
url = "https://api.redactionapi.net/v1/redact"
data = {
"text": "John Smith's SSN is 123-45-6789",
"redaction_types": ["ssn", "person_name"],
"output_format": "redacted"
}
response = requests.post(url,
headers={"Authorization": f"Bearer {api_key}"},
json=data
)
print(response.json())
# Output: {"redacted_text": "[PERSON_NAME]'s SSN is [SSN_REDACTED]"}
const axios = require('axios');
const apiKey = 'your_api_key';
const url = 'https://api.redactionapi.net/v1/redact';
const data = {
text: "John Smith's SSN is 123-45-6789",
redaction_types: ["ssn", "person_name"],
output_format: "redacted"
};
axios.post(url, data, {
headers: { 'Authorization': `Bearer ${apiKey}` }
})
.then(response => {
console.log(response.data);
// Output: {"redacted_text": "[PERSON_NAME]'s SSN is [SSN_REDACTED]"}
});
curl -X POST https://api.redactionapi.net/v1/redact \
-H "Authorization: Bearer your_api_key" \
-H "Content-Type: application/json" \
-d '{
"text": "John Smith's SSN is 123-45-6789",
"redaction_types": ["ssn", "person_name"],
"output_format": "redacted"
}'
# Response:
# {"redacted_text": "[PERSON_NAME]'s SSN is [SSN_REDACTED]"}
Phone numbers represent direct communication channels to individuals, making them highly sensitive personal data requiring protection. Unlike static identifiers, phone numbers enable immediate, real-time contact, creating unique privacy and security concerns. From telemarketing abuse to social engineering attacks, exposed phone numbers create tangible risks for individuals.
The challenge of phone number detection lies in the extraordinary diversity of formats used globally. Each country has its own numbering plan, format conventions, and display preferences. A single phone number might be written dozens of different ways depending on context and author preference. Effective phone number redaction must recognize all these variations while avoiding false positives from other numeric sequences.
Phone number formats vary dramatically across countries and regions. Understanding these variations is essential for comprehensive detection:
North America (NANP): 10-digit numbers following the pattern NPA-NXX-XXXX. Common formats include (555) 123-4567, 555-123-4567, 555.123.4567, and +1 555 123 4567.
United Kingdom: Variable length numbers with area codes. London numbers like 020 7123 4567, mobile numbers like 07700 900123, and national rate numbers follow different patterns.
European Union: Each member state has unique formats. German numbers like +49 30 12345678, French numbers like +33 1 23 45 67 89, and Italian numbers follow distinct national patterns.
Asia-Pacific: Diverse formats including Japanese numbers (+81 3-1234-5678), Chinese numbers (+86 10 1234 5678), and Indian numbers (+91 98765 43210).
Beyond format detection, our system classifies phone numbers by type, enabling nuanced redaction policies:
Mobile Numbers: Personal mobile numbers typically require the highest protection as they're most directly tied to individuals.
Landline Numbers: May be personal home lines or business numbers. Context helps determine appropriate handling.
Toll-Free Numbers: Business contact numbers (800, 888, etc. in US) may not require redaction in business contexts.
Premium Rate: Numbers with special billing that may require different handling.
Emergency Numbers: 911, 999, 112, etc. are generally excluded from redaction.
Many numeric sequences resemble phone numbers but aren't—dates, identification numbers, account numbers, and reference codes can trigger false matches. Our multi-layer validation eliminates these false positives through pattern validation, contextual analysis, and semantic understanding of surrounding text.
Phone numbers are protected under major privacy regulations and telecommunications laws. GDPR classifies phone numbers as personal data. HIPAA includes phone numbers among the 18 protected identifiers. The Telephone Consumer Protection Act (TCPA) in the US restricts how phone numbers can be used for marketing. Similar regulations exist in many jurisdictions worldwide.
RedactionAPI has transformed our document processing workflow. We've reduced manual redaction time by 95% while achieving better accuracy than our previous manual process.
The API integration was seamless. Within a week, we had automated redaction running across all our customer support channels, ensuring GDPR compliance effortlessly.
We process over 50,000 legal documents monthly. RedactionAPI handles it all with incredible accuracy and speed. It's become an essential part of our legal tech stack.
The multi-language support is outstanding. We operate in 30 countries and RedactionAPI handles all our documents regardless of language with consistent accuracy.
Trusted by 500+ enterprises worldwide





We support phone formats from 150+ countries including US/Canada (NANP), UK, EU member states, China, Japan, India, Australia, Brazil, and more. We handle international format (+1-555-123-4567), national format ((555) 123-4567), and local variations with any separator (dashes, spaces, dots, parentheses).
We use multiple validation layers: format pattern matching, country code verification, area code validation where applicable, length checking, and contextual analysis of surrounding text. This eliminates false positives from dates, account numbers, and other numeric sequences.
Yes, we detect local format phone numbers based on document context and configured default country. When processing documents, you can specify expected countries to improve detection of local formats without international prefixes.
Options include: full redaction ([PHONE_REDACTED]), last 4 digits visible ((XXX) XXX-1234), area code preservation ((555) XXX-XXXX), country code only (+1 XXXXXXXXXX), and custom patterns. Tokenization is available for referential integrity.
Yes, we handle extensions (x123, ext. 123, extension 123), vanity numbers (1-800-FLOWERS), and additional context like "mobile:", "cell:", "fax:", "tel:", etc. Extensions are included in redaction to fully protect the contact information.
The Telephone Consumer Protection Act restricts how phone numbers can be used for marketing. Redacting phone numbers from shared data, analytics exports, and archived records helps prevent unauthorized use and demonstrates privacy controls for compliance.