Cypherz.
Start free

Detector · identity

US Social Security Numbers tokenization

SSNs are the highest-stakes PII in US contexts. Sending one to an LLM provider — even accidentally in a support transcript — can be a HIPAA violation, a CCPA disclosure trigger, or a reportable security event. Cypherz tokenizes them at the boundary.

Start freeTry the free PII detector

  • 01

    Standard format detection

    Detects `XXX-XX-XXXX` format reliably. Add a custom regex for unformatted 9-digit strings if needed.

  • 02

    Audit-logged

    Every SSN tokenization is recorded for compliance assessors.

Same input, with and without Cypherz

// Without Cypherz — the model sees real data:
Patient SSN 555-12-1234 on file.

// With Cypherz — the model sees surrogates:
Patient SSN <SSN_a1b2c3d4e5f6> on file.

// The application gets the original back inside its trust boundary.

Common questions

Frequently asked.

Are us social security numbers tokens deterministic?

Yes — within a project, the same input always maps to the same surrogate token. This makes joins, dedupe, and analytics keep working on tokenized data without ever decrypting.

Can I disable this detector for a specific project?

Yes — every detector is toggleable per project at creation time and editable from the dashboard.

What if I have a custom format Cypherz doesn't recognize?

Add a custom regex or literal list per project. Cypherz applies your rules after the built-in detectors run.

Are tokenization mappings encrypted at rest?

Yes — AES-256-GCM with envelope encryption. Each project has its own data-encryption key wrapped under the master key.

Get started

Add us social security numbers protection to your AI features.

Sign up, create a project, copy your API key. The first request is tokenized in under sixty seconds.

Start freeTry the free PII detector

Other detectors