Security · for reviewers
What the gate does with a document, and how to check it.
This page is for security and privacy reviewers. It says where a document goes in each part of the product, what is recorded, what is claimed and what is not, and how you can check each statement yourself.
Where a document goes
In the browser (Try it and the everyday page)
- The document is read and changed inside the browser tab. It is not uploaded.
- On /try, /simple and /start, the page's Content-Security-Policy allows network requests only to this site, so the browser itself refuses to send anything elsewhere. Forms, frames and plugins are blocked, and the address is kept out of the Referer header.
- Requests to this site, such as the page's own code, its engine files and the invented samples, are the only ones the policy allows.
- Only if you enter a seat key: the page keeps the key and a monthly release count in this browser, and after each release sends this site two things, your seat key and a random number made for that release. Nothing from the document is sent, and the server refuses any other field. If your plan has release packs, the page may show a link to buy one; it goes to Stripe only when you click it and carries your Stripe customer id. Without a seat key, nothing is sent. The page keeps one number in this browser, how many free results you have used on this device, so it can ask for a plan after the first one.
On the command line
- The command runs on your machine and reads only the files you name.
- An optional second scanner, if you turn it on, also runs on your machine.
In the self-hosted gateway
- The gateway runs on infrastructure you control and sits between your AI client and the provider.
- It accepts two routes, /v1/messages and /v1/chat/completions, and forwards only to the provider configured for each.
- Content it cannot inspect, such as PDFs, audio, files and remote image URLs, is refused, not forwarded. Images are refused too, unless the gateway was started with OCR on.
- Your API key passes through to the provider and is not stored.
What is recorded
- Each decision is written to a run log with counts and hashes, never the values.
- The log is hash-chained, so an edit, deletion or reordering breaks the chain. It is tamper-evident, not tamper-proof: someone with write access can rewrite the whole chain, so keep the latest head hash somewhere else.
- Decision records are unsigned by default. The gateway can sign its authority records with a key the customer holds. That proves the signed bytes are unchanged; it does not prove who controls the key.
What it claims
Gates the release of the document. Refuses if a declared field is still present in the extracted text. Records the decision. Does not claim that all personal information has been removed.
What it does not claim
- That all personal information has been removed.
- HIPAA de-identification, or any compliance determination.
- Signed platform evidence, single-use release, or proof of what a provider received.
- Exclusive control of network egress. The gateway sees only traffic that is routed to it.
- An accuracy rate. Detection has been measured on invented documents only.
Check it yourself
- The demo shows real engine output.
- The demo page prints the engine's package, version and build hash. Run the same command on the same file and compare.
- Recorded decisions can be checked.
- The evidence log page lets you recompute each record's hash in your browser. On your own machine, any run with --log writes the log this command checks.First
strix-release-gate tokenize --file intake.txt --log run-log.jsonlThen checkstrix-release-gate verify-log --file run-log.jsonl - A redaction receipt is the one in the log.
- A receipt is written when you redact a PDF. Redact one with a log, then check the receipt against that log.First
strix-release-gate redact --file doc.pdf --out-dir out --log run-log.jsonlThen checkstrix-release-gate verify-receipt --receipt out/doc.redaction-receipt.json --log run-log.jsonl - Signed gateway records are unchanged.
- Records are signed only when the gateway runs with a key you made. Make the key, run the gateway with it, send it a request, then check every record against the public key alone.First
mkdir keysstrix-release-gate keygen --out-dir keysstrix-release-gate gateway --log gateway-log.jsonl --sign-key keys/egress-signing.keyThen checkstrix-release-gate verify-authority --log gateway-log.jsonl --pubkey keys/egress-signing.pub.pem - The browser pages send nothing elsewhere.
- Open your browser's network panel on /try, run a document, and inspect the requests. The page's response headers show the Content-Security-Policy.
See the demo and the evidence log to try these checks now.
Report a vulnerability
Please report a suspected vulnerability privately rather than in public. Include the affected version, how it is deployed, steps to reproduce and the impact. Do not include real patient data, secrets or tokens.
Email a security report