Detector · geo

IP addresses tokenization

IP addresses are PII under GDPR, leak geographic info, and are a common pivot point for de-anonymization. Cypherz detects IPv4 and IPv6 and tokenizes them at the boundary — especially valuable for SOC analyst AI tools.

  • 01

    IPv4 + IPv6

    Octet-validated IPv4 and standard IPv6 formats.

  • 02

    Distinct token prefixes

    IPv4 tokens use `<IP_…>`, IPv6 uses `<IP6_…>`. Easy to spot when reviewing logs.

Same input, with and without Cypherz

// Without Cypherz — the model sees real data:
Request from 192.168.1.42 and 2001:db8::1.

// With Cypherz — the model sees surrogates:
Request from <IP_a1b2c3d4e5f6> and <IP6_d4e5f6a1b2c3>.

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

Common questions

Frequently asked.

Are ip 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 ip addresses protection to your AI features.

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