> privacy

Error Wolf processes your traces in your browser. Stack normalization, compression, and model calls run there. We do not use accounts, product analytics, or ad trackers. We do not store your input or results on our servers.

We collect anonymous crash reports for errors thrown by Error Wolf. These reports do not include the traces or logs that you paste in.

Your input and OpenRouter key

The app stores your key in a browser cookie. The browser sends the key directly to OpenRouter and the providers that you select. Error Wolf does not proxy or store your key. The server only checks if a key exists for the hunt page. If your key does not use zero data retention (ZDR), a model provider may store your data. Configure your key with OpenRouter's ZDR guide.

Local history

The browser keeps up to 1,024 recent runs in localStorage. It removes runs after 30 days. The trash icon clears your key, consent, and history from this browser.

Our errors, not yours

The traces and logs you paste in are your data. They do not go to Error Wolf servers or Sentry. The browser sends them directly to OpenRouter. The results return to your browser.

Errors thrown by Error Wolf When the app breaks, it sends an anonymous crash report to Sentry. The report contains no user, cookie, request, or console data. We remove key-shaped strings and limit error text before the report leaves the browser.

Consent

The initialize flow stores your consent in a first-party cookie. The server uses this cookie to allow access to the hunt page. It does not store any other user data.

Open source

The full source is available on GitHub under the O'SaaSy License. You can audit, modify, and run it yourself.