Local files and network traffic

Status on 2026-10-18, for version 0.2.4 of the desktop app on Windows.

Each destination below is a host found by static analysis of 105 Python modules. The list is regenerated from the package, so a newly referenced host changes the published result.

No outbound request reads a result file or a bar file in order to send it, and a run emits no telemetry unless you tick one of the two optional data-sharing boxes on the sign-in screen; both start unticked, neither sends a bar file, and the privacy page lists their exact fields. What travels from a result is what the assistant quotes when you ask it to read one, described in the next section.

The assistant shipped with the app answers through a relay (https://stochastly.com/api/assistant): the text you type leaves the machine. When you ask it to read a run, what it quotes from that run — figures from your results, node names from your graph — travels in the next request of that same conversation. Your bar files and your result files are not uploaded; what the assistant reads out of them, in the turn where you ask, is.

There is one assistant, and it is hosted. The setting that governs it is a single checkbox — the assistant is shown or it is not — and the label beside it in the app states that the conversation leaves the machine. No screen in the interface selects a model that runs on your own hardware.

An assistant endpoint supplied by a caller is validated before the engine fetches it: the scheme has to be http(s) and the host has to be loopback (http://127.0.0.1:11434 by default). A host outside that set is refused by name unless you allow it yourself. A local binary that fetches any URL a caller hands it is a fetch service running under your account, which is the failure this check exists for.

Static analysis reads hosts declared in the package. 7 call sites build their URL while running and are counted without a name; the last row of the list above gives each one by file and line. The licence client is among them, and its host is declared in the package and listed above.

No import reaches a host through a third-party library: no download library ships with the engine, so no destination is decided outside this code.

The desktop front reaches the engine over loopback, and is out of this count. Every destination listed above is an ordinary HTTPS request from a process running under your account: a network monitor records it, so the count above is checkable on your own machine.