Check a program

Desktop programs carry third-party code too: usage statistics, crash reports, analytics, remote experiments. Here you can check any program the way we do: see which of these libraries are built in and whose servers the addresses in its code point to.

Your files are not uploaded. The check runs right in your browser — the program is not sent anywhere, we neither see nor store it. If you pick a folder, the browser may ask whether to “upload” the files to the site: that is the browser’s standard wording, the files are only read on your computer.

How to check a program:

Pick the file you downloaded: an installer, an archive (.zip, .tar.gz, .deb) or the executable itself.
Or pick the folder where the program is already installed: on Windows C:\Program Files\…, on Linux /usr/lib/… or /opt/…, on a Mac the program’s contents in Applications.
Wait for the report. A large program takes a minute or two.

or drop a file here

Limitations

The check shows what is built into a program, not what it actually sends. SDK code is not proof of data transfer, and an address in the code is not a request.
Many installers are compressed or encrypted, so little is visible inside. Checking the folder of the installed program is more reliable.
The browser cannot unpack xz or zstd archives (including many .deb files) — unpack them with an archiver or check the installed program.
If an SDK is missing from the report, that does not prove it is absent: the code may have been renamed at build time.

Our reviews

What programs actually do — see Program reviews.