Sploitly

Privacy

Privacy, in plain words

We need very little to do this job, so we keep very little.

What we store

  • Your package list, if you save one: package names, exact versions and ecosystem, taken from your lockfile.
  • A project label that you choose.
  • Your webhook address, if you set one, and the status code each delivery got back. Not the response body.
  • Your alerts, so your agent can show them and close them when fixed.
  • Your account: your plan, a fingerprint of each key (never the key itself), and how many calls each key makes per day.

What we never store

  • Your code, secrets, file contents or file paths.

Who can read it

Your package list is encrypted in transit (HTTPS) and on disk. It is not hidden from us: we have to read it to match new threats against it. If you prefer not to save a list, your agent can call check_packages whenever you like instead.

To find known flaws, we send package names, versions and ecosystem (never your project label or account) to OSV.dev, the public open source vulnerability database.

Your key

The setup tool, coming at launch, will write your key into your coding agent's own user-level settings file, never into your project, and never print it, so it does not land in the chat or in git. That file is not your operating system's password store. Connections that sign in through the browser, so your agent never needs to see a key, are also coming at launch.

Deleting your data

You can delete a project's list at any time through the API. Deleting it also closes its alerts. There is deliberately no agent tool for this, so a web page that tricks your agent cannot delete your projects.

Questions

Email [email protected].