> privacy

error-wolf runs entirely in your browser. Stack normalization, compression, and model calls happen client-side. No accounts. No server-side storage of your input or results. We collect anonymous telemetry to help improve the code: Vercel Web Analytics for site-wide aggregated page views (see Web analytics) and Sentry in privacy mode for errors, performance, and product usage after you initialize from the home page (see Consent and telemetry).

Your Data & OpenRouter key are private

Stored in a same-site cookie. Sent directly from your browser to OpenRouter (and the selected providers). We never proxy your key or see it. If your OpenRouter key allows storage of data (i.e. not ZDR), model providers may store your data. Configure your key with OpenRouter’s ZDR guide.

Local history

Up to 1024 recent runs are kept in localStorage. They are pruned automatically after 30 days. The trash icon in the header clears your key, consent, and all history in one step.

Web analytics (Vercel)

We use Vercel Web Analytics for site-wide aggregated page views and traffic. It is not tied to the initialize consent cookie on the home page. Error and usage telemetry uses Sentry as described below. Before analytics events are sent, we strip query strings from the reported URL in your browser so tokens and other sensitive query data are not included.

Consent and telemetry

We use Sentry in privacy mode for basic error, performance, and usage data only. No personal data or stack traces are sent. When you use the initialize flow on the home page, consent is stored as a first-party cookie for that experience. That cookie does not disable Vercel Web Analytics (traffic still uses the section above). Optional feedback you submit with a screenshot is visible to us in Sentry.

Open source

The full source is available on GitHub with an O'SaaSy license. You can contribute, audit, or fork and run it yourself.