Nothing leaves your machine.

No account. No telemetry. No phone-home.

There is no sign-up, no analytics, and no crash reporting. Basanos does not open a connection to us at install, at activation, at launch, or in use. There is no setting to enable any of that, because the code to do it is not there.

Licence activation reads a signed file on disk and writes a local licence. It never contacts a licence server — before or after — so an activated seat runs the same whether the machine is online or in a sealed room.

Your data stays on disk you control.

Engagements are single project files under ~/.basanos/engagements — scope, History, findings, and captures, held locally. Nothing is uploaded, mirrored, or synced. Delete the file and the engagement is gone; there is no copy elsewhere because there is no elsewhere.

The crafted artefacts, the intercepted traffic, the client's system prompts — they exist only where you put them.

The only traffic that leaves is the traffic you aim.

Two things touch the network, both by your instruction and pointed where you choose: the requests the intercepting proxy forwards to the target endpoint you configured, and the built-in host serving an artefact to a target you are testing. The beacon that confirms a landing listens on a loopback port on your own machine. Review, crafting, and export work with the cable unplugged.

This site, too.

These pages set no cookies and send no analytics. The single request each page makes on load fetches the two typefaces from Google Fonts; nothing else is loaded, tracked, or stored. The form on the home page sends only the email address you type, and only when you submit it.

Questions about data handling for an engagement or a procurement review? Write to hello@basanos.io.