Why I built a Post-Quantum PII anonymization API (and how it works)

The problem with most data anonymization tools is that they solve today's threat model, not tomorrow's.
RSA-2048 and ECDSA — the algorithms behind most audit log signatures today — are vulnerable to Shor's algorithm running on a sufficiently large quantum computer. Security researchers estimate we have 8–15 years before that becomes a real attack vector. That sounds like a long time until you realize compliance audit logs need to remain verifiable for decades.
So I built Vortex DFS.
It's a REST API with two core capabilities:

1. PII Anonymization

Send any text payload. Get back sanitized content with an AES-256-GCM encrypted token map for reversibility if needed. Detects names, emails, CPF, SSN, credentials, and more.

1. Post-Quantum Cryptographic Audit

Audit events are signed using a lattice-based scheme (LWE — Learning With Errors), which is resistant to quantum attacks. NIST has already standardized this family of algorithms in FIPS 203/204.
The stack:

Rust + Actix-web (sub-15ms p99 latency)
Supabase PostgreSQL for customer management
Stripe for instant key provisioning
Keys delivered by email in under 60 seconds after payment

**One call to anonymize:**
bashcurl -X POST https://okamotosecurytlabs.com.br/v1/shield/anonymize \
  -H "Authorization: Bearer YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"content": "John Smith, card 4111-1111-1111-1111, SSN 123-45-6789"}'

**Response**:
json{
  "sanitized": "[NAME] [CARD] [SSN]",
  "risk_score": 0.94,
  "detections": [...],
  "latency_ms": 12.3
}

Who is this for:

Fintech and healthtech handling sensitive user data
Companies under GDPR/LGPD compliance requirements
Developers building audit pipelines that need to survive quantum

Starts at $9/week with instant API key delivery.
Try it: