Detector · contact

Phone numbers tokenization

Phone numbers are a high-value lookup key for identity theft. They also appear constantly in CRM data, support transcripts, and SMS logs that you might want to summarize with an AI. Cypherz detects standard US, E.164, and common European formats.

  • 01

    E.164 and local format support

    Handles +1, (415) 555-0142, 415.555.0142, and international variants.

  • 02

    Resistant to false positives

    Detection rules biased against grabbing random number sequences.

Same input, with and without Cypherz

// Without Cypherz — the model sees real data:
Call +1 415 555 0142 or (408) 555-0199.

// With Cypherz — the model sees surrogates:
Call <PHONE_a1b2c3d4e5f6> or <PHONE_d4e5f6a1b2c3>.

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

Common questions

Frequently asked.

Are phone 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 phone numbers protection to your AI features.

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