JEVX

Privacy Policy

Last updated: October 1, 2026 · applies to JevX for GitHub (Chrome extension), the jevx CLI and the JevX MCP server.

In short

  • JevX has no servers that receive your code or keys. We don't collect, sell or share personal data.
  • Your code goes only to the AI provider you choose, with your API key, and only when you start a scan.
  • Your API keys stay on your device.
  • No analytics, no tracking, no ads.

JevX for GitHub (Chrome extension)

What it stores, on your computer only

  • The API keys you enter (Gemini, xAI or OpenRouter; optional TypeSafe and GitHub tokens), in Chrome's local extension storage. They are never synced to your Google account and never sent to JevX.
  • The results of each scan (scorecards and the few lines of code they point to), so you can see them again. "Remove keys" in settings clears the keys; removing the extension clears everything.

What it sends, and to whom

  • GitHub (api.github.com, raw.githubusercontent.com): reads the file list and source files of the repository you are viewing. Your GitHub token, if you add one, is sent only to GitHub.
  • The AI provider you pick (Google Gemini, xAI or OpenRouter): the selected source files, with anything that looks like a secret removed first. Sent only after you click "Find where Jev fits". That provider's own privacy policy applies.
  • TypeSafe (api.typesafe.ai), only if you add a TypeSafe key: the few lines of each suggested spot and the proposed question.

It does not read pages other than GitHub repositories, does not read your browsing history, and does not run in the background on other sites. It never changes anything on GitHub.

Permissions and why

  • sidePanel: show the results next to the page.
  • tabs: read the address of the current tab, to know which GitHub repository you are viewing.
  • storage: keep your keys and saved results on your computer.
  • Host access to GitHub and to the AI providers listed above: only to make the requests described here.

CLI and MCP server

The jevx command runs on your computer. It sends source files (secrets removed) to the AI provider whose key you set, after asking you once, and optionally to TypeSafe. Keys come from your environment and are never written to disk by JevX. In the MCP server, your own AI app (e.g. Claude) does the reading; JevX sends nothing itself, except the optional TypeSafe score.

Opt-in sharing (--share)

Only if you turn it on, the CLI shares anonymous outcomes to improve JevX: the kind of code (e.g. "keyword list on user text"), the scores and whether a change was kept. Never code, file or function names, paths, string literals or keys, and only a random id per repository. The Chrome extension never shares anything.

Contact

Questions or requests: open an issue, or report privately via GitHub security advisories.