Is Your Free App Spying on You? Here's How to Actually Find Out
Let's be honest: most of us download free software with a vague, nagging feeling that something might be going on under the hood. Maybe it's the pop-up that asks for more permissions than it should need. Maybe it's the privacy policy that's seventeen pages long and written in legalese. Or maybe you've just been on the internet long enough to know that nothing is truly free — somebody, somewhere, is always getting something.
The good news is you don't have to just shrug and hope for the best. Whether you're running open-source tools or closed freeware, there are real, practical ways to figure out what your software is actually doing when you're not looking. This guide breaks it all down.
Why "Open Source" Doesn't Automatically Mean "Safe"
There's a common assumption floating around that if something is open source, it's automatically trustworthy. The reasoning makes sense on the surface — the code is public, so anyone can check it, right? Sure. But here's the thing: most people don't.
The open-source ecosystem runs on a kind of collective trust. We assume that someone has reviewed the code, even if we haven't personally. And for major projects like Firefox, VLC, or LibreOffice, that's probably a reasonable assumption. But what about that handy little open-source utility you grabbed from GitHub last week with 200 stars and a single contributor? That code could contain anything.
Telemetry — the practice of quietly collecting usage data and sending it back to developers — is also increasingly common in open-source projects. Some projects are upfront about it and give you an opt-out. Others bury it in settings menus nobody visits. A few just... do it, and hope you don't notice.
Closed freeware is a whole different animal. When there's no source code to read, you're entirely dependent on the developer's honesty and whatever a network monitor can catch.
Step One: Check the Privacy Policy (Yes, Really)
Before you groan and skip this section — hear me out. You don't have to read the whole thing. You just need to know what to look for.
Search the privacy policy for keywords like "telemetry," "analytics," "usage data," "third-party," and "share." These words will tell you quickly whether data collection is happening and who it might be going to. If the policy is vague, that's a red flag. If there isn't one at all, that's an even bigger red flag.
For open-source projects, check the project's GitHub repository or documentation for any mention of analytics libraries. Common ones include Sentry (error reporting), Segment, Mixpanel, and Google Analytics. Their presence doesn't automatically make an app shady, but it's worth knowing.
Step Two: Watch the Network Traffic
This is where things get genuinely interesting. Even if you can't read source code, you can watch what your computer is saying to the outside world. A few tools make this surprisingly accessible:
Wireshark is the gold standard for network analysis and it's completely free and open source. It captures every packet your machine sends and receives. The learning curve is real, but even a beginner can filter by the app's process name and see what domains it's connecting to.
Little Snitch is a macOS option (paid, but worth knowing about) that alerts you in real time when an app tries to make an outbound connection. For Windows users, GlassWire offers a free tier that does something similar — showing you a visual breakdown of which apps are talking to which servers.
Windows Sysinternals' TCPView is a no-frills, free Microsoft tool that gives you a live view of all active network connections on your PC. Open it right after launching a new piece of freeware and watch what lights up.
Once you've got a list of domains an app is contacting, run them through a service like VirusTotal or just Google them. You'll quickly learn whether those connections are routine update checks or something more eyebrow-raising.
Step Three: Audit App Permissions
On Windows 10 and 11, head to Settings > Privacy & Security and dig through the permissions section. You'll see which apps have access to your camera, microphone, location, contacts, and more. It's shocking how many people have never looked at this screen.
For browser extensions — which are among the sneakiest data collectors in the freeware world — go to your extensions manager and click "Details" on any extension you're unsure about. Check what permissions it's requested. An extension that needs to "read and change all your data on the websites you visit" for what's supposed to be a simple color picker? That's a problem.
Step Four: Use a Sandbox for Anything Sketchy
If you really want to know what a piece of freeware does when it first runs — before it has a chance to integrate itself into your system — run it in a sandbox environment first.
Windows Sandbox (built into Windows 10/11 Pro) spins up a temporary, isolated virtual environment. Install the software there, let it run for a few minutes while you monitor network traffic, and then close the sandbox. Everything disappears. Nothing touched your real system.
Sandboxie-Plus is a free, open-source alternative that works on more Windows versions and gives you more control over what the sandboxed app can access.
What Telemetry Actually Looks Like in the Wild
To give you a real-world example: VSCode, Microsoft's hugely popular free code editor, collects telemetry by default. It sends crash reports, feature usage data, and error diagnostics back to Microsoft. The data is documented, and there's a clear setting to disable it. That's actually a relatively ethical implementation.
Contrast that with some freeware download managers or PDF tools you'll find on random software aggregator sites — apps that install browser toolbars without asking, change your default search engine, and report your browsing habits to ad networks. That's the darker end of the spectrum.
The difference between those two scenarios isn't just about open vs. closed source. It's about transparency and respect for the user.
Building a Personal Verification Habit
You don't need to run a full network audit every time you install something. But a lightweight routine goes a long way:
- Google the app name + "telemetry" or "privacy" before installing.
- Check permissions right after installation.
- Glance at TCPView or GlassWire the first time you run it.
- Look for opt-out settings in preferences, especially anything labeled "Help improve" or "Send usage data."
None of this takes more than five minutes, and it'll catch the vast majority of problematic behavior before it becomes a real issue.
The Bottom Line
Free software is one of the best things about the modern tech landscape. But "free" has never meant "no strings attached," and in 2024, data is the string that gets attached most often. The tools to protect yourself are out there — and most of them are free too, which feels appropriate.
Trust your instincts when something feels off. And when in doubt, watch the network traffic. Apps don't lie to packet sniffers.