Your data, plainly
What runlaw collects, why, and who else is involved in delivering it. No analytics, no advertising, no training on your traffic.
What we collect
- Access requests: the email you enter and the country of the request, as reported by our network provider.
- Accounts: your name, email, a password hash, your API key hashes, credit balance and usage counts.
- Gateway traffic: traces of the calls you send through the gateway, as described on the security page.
How it is used
We use this data to run the service: to sign you in, enforce your policies, bill usage against your credits, and show you your traces. We don't sell it, and we don't use your traffic to train models.
Cookies and third parties
runlaw sets one cookie, rl_session, to keep you signed in. There are no analytics or advertising cookies.
- Pages load a typeface from Google Fonts, which receives your IP address when you visit.
- Gateway calls are forwarded to the model provider (OpenAI today), whose API data policy applies to those requests.
- The service runs on Cloudflare, which processes traffic to deliver it.
Your control
You can revoke API keys and change your password from the console at any time. Traces older than the most recent 5,000 in your workspace are deleted automatically. To have an account and its workspace deleted, contact the workspace owner who granted your access.
