Know what we keep.And what we never do.
RouterLane sits between your agents and the models, so it sees your prompts and your code. This page says what is stored, for how long, and how it is protected.
What is stored
| Data | When | Kept for |
|---|---|---|
| Request metadata: time, account, key, tier, model, effort, the routing decision, token counts, timing, status and cost | Every request | As long as needed for billing and support |
| Transcripts: prompts, responses, reasoning, tool calls and tool results | When transcript logging is on | 30 days by default, then the bodies are deleted and the metadata stays |
| Raw parameters: what the router sent to the model | When raw logging is on | With the transcript |
| Response cache: an identical request and its answer | Every answered request | 10 minutes, in memory only |
| Decision cache: how a task was classified | New tasks | 24 hours |
| Smart+ workspace: the repository copy, its installs and the patch | Smart+ jobs | Deleted after 48 hours |
| Contact form messages | When you write to us | As long as needed to answer and keep a record |
Enterprise deployments set their own logging: transcripts on or off, raw parameters on or off, and the retention window.
What is never stored
- Your raw API key. Only its SHA-256 hash is kept.
- Credentials in request headers:
Authorization,x-api-key, cookies and proxy credentials are stripped before anything is logged. - Your git history. Smart+ uploads files, not commits.
- Files git ignores, and
node_modules.
Keys
- Generated randomly, with the
rl_prefix. - Shown once, when issued. RouterLane keeps a SHA-256 hash and the first characters for display.
- Revocable at any time; a revoked key is refused on its next request.
- Unknown keys get a 401 and nothing else.
Smart+ isolation.Model-written commands, fenced.
Smart+ agents run shell commands that a model wrote, against a copy of your repository. They run behind these boundaries.
Upload
Over HTTPS, with a token good for one job. It never passes through a model. Symlinks and paths that would climb out of the copy are dropped on unpack.
Separate account
Jobs run as a unix account that owns nothing and cannot read the service's code, database or credentials.
Bounded
Every command has a timeout and takes its process group down with it. Output is capped. Commands that reach outside the workspace are refused.
Fenced files
File tools refuse paths that resolve outside the repository copy.
Your tree untouched
The patch is applied with git apply. Nothing is committed on your machine, and a patch that does not apply is saved beside your code instead.
Deleted
Workspaces are deleted after 48 hours.
In transit
The API, the website and Smart+ transfers are HTTPS only, with HSTS.
Model providers
To answer a request, RouterLane forwards it to the infrastructure provider that runs the chosen model. Requests a content filter blocks on the way in are never forwarded.
This website
No analytics, no tracking cookies, no third-party requests: fonts and scripts are served from routerlane.com. The only cookie RouterLane sets is the console session.
Reporting a vulnerability
Email security@routerlane.com. Include what you found, the endpoint or page it affects, the steps to reproduce it, and the impact you expect. We read every report and reply to the address you write from.
While you research:
- Use only your own account and keys. Do not access, change or delete anyone else's data.
- Do not degrade the service for others: no load tests, no denial of service, no spam through the contact form.
- Give us reasonable time to fix the issue before you disclose it publicly.
We will not pursue legal action against research done in good faith within these rules.
Privacy questions go to privacy@routerlane.com. See also the privacy policy.