ERRase/ docs
Privacy

Privacy Policy

Last updated: June 2026. ERRase is built with privacy as a default — not an afterthought.

What we collect

ERRase collects no personally identifiable information. The only credential that passes through the system is your Groq API key, which is transmitted directly from your browser to Groq's servers for the sole purpose of generating AI fix suggestions. It is never stored, logged, or retained by ERRase.

Your source code

Your source files are read locally by the CLI running on your own machine. Only a small snippet — ±15 lines around the error line — is sent to Groq for analysis. Your full codebase never leaves your machine and never touches ERRase servers.

Your API key

Your Groq API key is stored locally in your browser using Chrome's extension storage API. It is sent directly to Groq when you request an analysis. ERRase's backend acts as a relay only — it does not log, store, or have access to your API key beyond the duration of a single request.

Third parties

ERRase uses Groq as its AI provider. Your code snippet and error message are sent to Groq's API under their privacy policy. No other third parties receive your data. ERRase does not use analytics, tracking, or advertising of any kind.

Contact

Questions about privacy? Reach out at craig.rosario04@gmail.com