Try it — your code never leaves your browser.

Data flow

Your file is read and redacted in your browser. Only opaque tokens are POSTed to /api/v1/secured-analyze, which analyzes their structure and returns an Ed25519-signed receipt. Your source, names, values, and text never leave the tab.

file ──[redact in browser]──▶ tokens ──HTTPS──▶ server
   │                                               │
stays local                       ◀── analysis + Ed25519-signed receipt

Verify it yourself

1. Egress capture: open DevTools → Network → the secured-analyzerequest → Payload. You'll see only tokens (ID_n, NUM_n, STR_n, language keywords) — none of your names/values/strings. Those are the exact bytes that left your machine.
2. Integrity:this page computes SHA-256 of the exact bytes it sent; the server returns SHA-256 of what it received — they match (see “Show technical details” on any answer), so the server got exactly the tokens, nothing more.
3. Authenticity: the server signs that hash with Ed25519; the page verifies it against the pinned public key below. A tampered receipt is rejected.

What's guaranteed

• Your file never leaves the browser (client-side redaction).
• Sensitive content (names, values, strings, comment text) is redacted; only language keywords + structure cross.
• You see and approve the exact redacted payload before anything is sent.
• Results come back still in tokens; only your local keys file (agentyx.keys.json) can restore them — and we never receive it.

The 5 checks — run every one right now, in this browser

The proof is a demonstrable negative you produce yourself — no trust in us required.

1. ✓ in this demo1. Start egress capture — see exactly what bytes leave (DevTools → Network).
2. ✓ in this demo2. Leak-check the payload — 0 matches of your names / values / text.
3. ✓ in this demo3. Diff source ↔ payload — the Step 3 side-by-side shows only structure crosses.
4. ✓ in this demo4. Audited send — the captured payload is tokens, not the file.
5. ✓ in this demo5. Signed receipt — hash(received) == hash(tokens) ≠ hash(raw file).

Working with a real codebase? The same redaction runs on your own machines with our open-source, offline redaction tool — auditable line by line, keys stay with you. For the strongest tier (code never leaves your premises), talk to us.