simple diffusionCheck network activity
Simple Diffusion by Prosper Technologies performs local image generation. This guide helps you inspect that behavior rather than relying only on our description. It is not an independent audit, code-signing certificate or proof that every possible code path is offline.
What connections to expect
- Engine setup: downloads from the official GitHub release and its release-asset delivery hosts.
- Model setup: downloads from Hugging Face and its file-delivery services. Providers can observe normal connection records such as IP address and download requests.
- Idle use and generation after setup: the current build is designed to require no generation service or analytics endpoint. Unexpected app or worker connections deserve investigation.
- Links you choose to open: support, privacy, license and release pages open an external browser. Optional test checkout links in the direct prerelease also open external services. These are separate from local generation.
- Updates: automatic update checks are disabled in the current unsigned direct release. Microsoft Store downloads and updates, Windows reputation checks, and traffic from other apps are separate processes.
Inspect connections yourself
- Record the app version and installer SHA-256. Compare it with SHA256SUMS.txt on the same release. This detects a different file; it is not a publisher signature or a privacy audit.
- Use Microsoft Sysinternals TCPView or Windows Resource Monitor. TCPView lists network endpoints and the process that owns them. Turn off resolved address names if you want to avoid the inspection tool performing DNS lookups.
- Watch every Simple Diffusion.exe process and the local Python engine worker. Record their process IDs so browser, Windows and monitoring-tool traffic is not attributed to the app.
- Observe idle launch, setup downloads, an idle period after setup, and several local generations separately. Start observing before each phase; a snapshot may miss short-lived connections. For a deeper review, an experienced tester can record a packet capture during each phase.
- Once setup has finished, disconnect the computer from the network yourself, reopen the app and generate a harmless test image. This tests that the workflow works offline. Reconnect when you need downloads or external support pages.
What the result does and does not show
Working offline demonstrates that the tested workflow does not require a network connection. Observing no traffic for a period does not prove that no data could ever be sent, including after reconnection. Endpoint monitoring does not reveal encrypted HTTPS contents. An unsigned, privately maintained binary cannot be independently reproduced from the public repository. We do not present source inspection, a hash, or one test as a substitute for an independent audit.
Share findings safely
Use Settings → Help & diagnostics → Copy diagnostics to collect app and hardware information. Review it before posting. Network logs and captures can reveal IP addresses, device names, unrelated traffic and private paths; do not upload raw logs publicly. Report the app version, test phase, relevant process and unexpected destination through the issue tracker, with sensitive values removed.