Privacy Policy

Signal Visor · effective 14 November 2026

The short version: Signal Visor does not collect, transmit or look at anything you do with it. There is no server behind it, no account and no analytics, and the author has no visibility into what you record or what it decodes.

What the program stores

Settings, the crash-recovery checkpoint and the local log are written only on your own computer, under %LocalAppData%\SignalVisor. Sessions, exports and pictures go wherever you save them. Recordings are read in place and are never copied anywhere. The version from the Microsoft Store keeps the same files inside its own package folder, which Windows removes when the program is uninstalled.

Recordings

A capture is read from disk and analysed on your machine. Nothing about it is uploaded, and the program makes no connection to the internet of its own – no update check, no licence phone-home, no crash or usage reporting. The Help button and F1 open this website in your own browser; that is the browser's connection, not the program's.

Radios on your network

When you ask it to, Signal Visor looks for an ADALM-Pluto on your local network and connects to the address you give it. That traffic stays inside your own network. The USB scan lists radios the computer can already see through Windows Plug and Play; it reads identifiers, nothing more. A HackRF is read over USB directly. For an RTL-SDR, Signal Visor connects to rtl_tcp at the address you give (normally this computer) and, if you give its path, starts that program and stops it again.

Logs and diagnostics

A rotating technical log is kept under %LocalAppData%\SignalVisor\logs: the time, the program version, the radio and its settings, errors, and how long a receive run lasted. The contents of decoded messages are deliberately never written to it – a log from a tool that runs for days should not end up holding your sensors' readings.

Settings → Collect diagnostics packs that log together with your settings, the list of radios the machine can see, the native runtime inventory and what the protocol library loaded into a single ZIP. It is created only when you ask for it, saved where you choose, and sent nowhere. It contains no capture data and no decoded values.

No tracking

No cookies, no analytics, no third parties – neither in the program nor on this website.

Questions

If anything here is unclear, write to petr@fotoventus.cz. Since no usage data ever reaches the author, there is nothing to look up on request beyond answering your question.

Changes

Any future change to this policy will be published on this page with an updated date.