Map-free reversible redaction
Most reversible tokenization keeps a vault of originals. Some enterprise vendors offer vaultless FF1 tokenization behind a sales process. Obscate makes it a self-serve API call: strategy: "fpe" returns an empty token_map, and restore needs only the key.
- Nothing to store or ship around — no map in your database, your logs, or your queue.
- Deterministic — the same value encrypts to the same token under the same key, so joins and analytics still work on redacted data.
- Standards-based — NIST SP 800-38G FF1 with AES-256, verified against all nine official NIST FF1 sample vectors.
Why FF1 and not FF3-1: NIST’s February 2025 draft revision (SP 800-38G Rev. 1, 2nd public draft) drops FF3 after a published attack that also affects FF3-1.
// request
{ "text": "Refund card 4242 4242 4242 4242", "strategy": "fpe" }
// response
{ "redacted": "Refund card 7695 1067 6534 8610",
"reversible": true,
"token_map": {} }
// later — key only, no map
POST /v1/restore-fpe { "text": "…7695 1067 6534 8610" }
→ { "text": "Refund card 4242 4242 4242 4242" }