Cypherz.
Start free

Detector · geo

Street addresses tokenization

Street addresses leak through email signatures, shipping confirmations, and CRM exports constantly. Cypherz detects standard US-format addresses and the most common UK variants, then tokenizes them.

Start freeTry the free PII detector

  • 01

    US street format support

    Number + name + Street/St/Avenue/Ave/Road/Rd/Boulevard/Blvd/Lane/Drive/Court/Way/etc.

  • 02

    Combine with postal code detector

    Together with the postal code detector, removes the geocoding signal almost entirely.

Same input, with and without Cypherz

// Without Cypherz — the model sees real data:
Ship to 1521 Mission Street, San Francisco, CA 94103.

// With Cypherz — the model sees surrogates:
Ship to <ADDR_a1b2c3d4e5f6>, San Francisco, CA <ZIP_d4e5f6a1b2c3>.

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

Common questions

Frequently asked.

Are street addresses 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 street addresses 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