Trust and security

Pilot: Router.law does not yet accept real client information. It will only after an independent security review.

What Router.law keeps

No client data. Each request carries the client profile; Router.law uses it in memory to fill the form and discards it. There is no database of profiles and no copy of filled forms.
Over MCP, a filled PDF waits at most 10 minutes for its one-time download, encrypted, in memory only.
Logs hold metadata only: request ID, key ID, form ID, timing and error codes.

HTTPS only, with HSTS and strict security headers. The public pages run no scripts and no third-party code or tracking.
API keys are random, stored only as salted scrypt hashes, scoped and revocable. MCP apps sign in with OAuth 2.1 and get short-lived tokens.
No AI model inside Router.law. Filling and checking are deterministic code, and client details are never sent to an AI provider or any other third party by Router.law.
Only official form files whose SHA-256 matches the recorded value are filled. Output PDFs carry no scripts, links or attachments.
Router.law never files, submits, sends or emails anything.