Router.law privacy policy (draft)
Status: draft. Not in force. Router.law is in a pilot and does not yet accept real client information. Only made-up test data may be used until an independent security review is complete. This policy stays a draft until Router.law is operated by a company and the policy has been reviewed.
Last updated: 2026-10-19.
Who we are
Router.law is operated by Marty Mikhail personally ("Router.law", "we"). It will be operated by a company before this policy takes effect or any real client information is accepted; this section will then name the company. Our privacy contact is privacy@router.law. Security reports go to security@router.law.
Router.law fills official Ontario legal forms for law firms and the AI agents they use. It returns each filled form for a person to review. It never files, submits, sends or emails anything.
The short version
- We don't keep your clients' information. Client details arrive with each request, are used in memory to fill the form, and are thrown away when the request ends. There is no database of client profiles and no copy of filled forms.
- No AI model inside Router.law. We don't send client details to an AI provider or to anyone else.
- Our logs hold technical details only: which key, which form, when, how long, and whether it worked. They never hold names, addresses, amounts or any other form content.
- Router.law runs in the United States (Railway), and traffic passes through Cloudflare. See "Where information is processed".
- No tracking. No advertising, no analytics scripts and no third-party code on our pages.
Two roles
For your clients' information, we act for your firm. When your firm, or an AI agent it uses, sends us a client's details to fill a form, we handle them only to do that, on the firm's behalf. Your firm stays responsible for that information, including telling clients how it is used and getting any consent the law requires.
For account information, we are responsible. This is information about the firms and people who use Router.law: account names, keys and sign-in details.
What we handle, and for how long
| What | Why | Where it is | How long |
|---|---|---|---|
| Client details sent to fill or check a form (names, addresses, dates, amounts; health details on accident benefits forms) | To fill and check the form you asked for | Server memory, during that one request | Deleted when the request ends |
| The filled PDF | To give it back to you | Returned in the response. With a chat app (MCP), held encrypted in memory for a one-time download | Deleted after the download, or after 10 minutes at most |
| Router.law Files: your firm's file number with the stage, work done, outstanding items, key dates and a list of documents (type and date received only) | So your firm's agent can pick up where the work left off | Our database, kept apart from sign-in and usage data, with every field encrypted | While the file is open, then 2 years after it is closed; then deleted automatically. If your firm leaves Router.law: exported on request, then deleted within 30 days, including from backups as they rotate, with written confirmation |
| Account details: account name, key labels and key IDs | To run your account | Our hosting provider's secret store | While the account is open |
| API keys and console passwords | To sign you in | Only as one-way scrambled versions (hashes); we can't read the original | Until revoked or changed |
| Authenticator app setup key (console password sign-in) | To check your sign-in codes | Our hosting provider's secret store | Until it is replaced |
| Chat app connections (for example Claude): the app's name and its return address, and sign-in tokens | To keep the app signed in | Our database. Tokens only as hashes | App records: 180 days after last use. Tokens: 1 hour (access) or 30 days (refresh) |
| Usage totals: per day, account, tool and result, counts only | To show each account its own use, and for future billing | Our database | 2 years, then deleted |
| Technical logs: time, request ID, key ID, account name, form ID, tool, result, timing and error codes | To run, secure and fix the service | Our hosting provider's log system | 30 days |
| Internet (IP) addresses | To limit repeated sign-in attempts | Server memory only. Not in our logs | 2 minutes at most |
| Console sign-in cookie | To keep you signed in to the console | Your browser, plus a hashed copy in server memory | 30 minutes idle, 8 hours at most |
| Emails you send us | To answer you | The operator's personal inbox (forwarded by Cloudflare) | As long as needed to deal with your message |
What Router.law Files never holds: names, addresses, notes or any other free text about a client. It accepts only a file number, codes from fixed lists, form IDs and dates, and refuses anything else, including folder paths (a folder name can carry a client's name or health details). Please never use a client's name as a file number.
What we don't do
- We don't sell or rent personal information, or share it for advertising.
- We don't use client details to train any AI model, or for anything except the form you asked for.
- We don't send client details to any AI provider or other third party.
- We don't file, submit, send or email anything for you.
- We don't use advertising or analytics cookies.
Your AI agent
If you use Router.law through an AI agent or chat app (for example Claude or ChatGPT), the information you type into that app is handled by its provider under its own terms. That happens outside Router.law. Router.law sends its results only back to the agent that asked.
Where information is processed
Router.law runs on Railway, in the United States, and its database is with Railway in the same region. Requests reach Router.law through Cloudflare, which provides our web address, encryption in transit and protection against attacks. Cloudflare decrypts and re-encrypts traffic on its way through and may handle it at a location near you, which may be outside Canada.
Information processed outside Canada is subject to the laws of that country, and its courts, law enforcement and national security authorities may be able to access it. Because Router.law keeps no client details after a request ends, there is very little to access. Client details are still processed in the United States during each request.
Who we share information with
Only the service providers that run Router.law, and only to run it:
| Provider | What it does | What it can see |
|---|---|---|
| Railway (United States) | Hosting, database and logs | Everything Router.law processes, while it runs there |
| Cloudflare | Web address, encryption in transit, attack protection | Traffic passing through it, including requests |
| Cloudflare Email Routing | Forwards email sent to router.law addresses to the operator's personal inbox | Emails you send us |
GitHub holds our source code and never receives client information. We may also disclose information where the law requires it. If that happens, we'll tell the affected firm unless the law forbids it.
How we protect information
- Encryption in transit (HTTPS only) and strict security settings on every page.
- Keys, passwords and sign-in tokens are stored only as hashes.
- A code from an authenticator app for console password sign-in, and two-step sign-in on our administrator accounts.
- Logs are filtered in code, so client details can't be written to them.
- Router.law Files is encrypted field by field, append-only and shown only to your own firm's team keys.
- Filled forms carry no scripts, links or attachments.
- An independent security review and penetration test before any real client information is accepted.
Cookies
The console uses one cookie to keep you signed in. It is needed to sign in, can't be read by scripts, and is sent only to router.law. Our public pages set no cookies. Cloudflare may set a security cookie to tell people from automated attacks.
Your choices and rights
- Your clients: we don't keep client details, so we have none to give, correct or delete after a request ends. Clients should contact the firm that holds their file.
- Your account: you can ask us what account information we hold about you, ask us to correct it, or ask us to close your account. Write to privacy@router.law. We'll answer within 30 days.
- Router.law Files: your firm can see everything it has recorded, with its full history, in the console.
If something goes wrong
If a security breach affects information we handle for your firm, we'll tell your firm promptly, with what we know. Where there is a real risk of significant harm, we'll report it to the Privacy Commissioner of Canada and notify the people affected, or help your firm to do so. We keep a record of every breach for at least 24 months.
Questions and complaints
Write to privacy@router.law. If we can't resolve your concern, you can contact the Office of the Privacy Commissioner of Canada.
Changes
We'll post changes here with a new date. If a change would affect client information, we'll tell account holders before it takes effect.