Tracking is invisible. A web page can contact a dozen other companies, ad networks, analytics services, data brokers, font providers, before any content even shows up, and nothing on screen tells you. Browser extensions, developer tools and paid scanners can show it, but they assume you already know how to read them. And plenty of site owners don’t know what their own pages send out either.
Watchkeeper is a small free browser built to show it. Beside the page sits a panel that lists, in plain words, the other sites the page contacts about your visit, the cookies it leaves, what it writes to your computer and which scripts read the features used to fingerprint your device. It runs on Windows, macOS and Linux, and the whole session is wiped when you close it.
The Pitch in Four Numbers
- 14 of 14 test addresses a test tracker was asked for showed up in the panel, checked against the server’s own log.
- 73,827 junk events thrown by a hostile test page built to hide the tracker. Each was counted as left out, and the tracker was still caught.
- 28 checks in the end-to-end self-test, run on each installer before release.
- About 2 MB installers, because it uses the web engine already on your system.
How It Works
Watchkeeper is built with Tauri 2 and Rust on top of the system’s own web engine: WebView2 on Windows, WKWebView on macOS and WebKitGTK on Linux. That’s why the installers are tiny. The Linux AppImage bundles its own libraries, so it’s bigger.
A detection script runs in every frame before the page’s own code. The page can’t switch it off, and its results can only be read with a secret the page never sees. Every session starts empty, with no cookies, logins or history, and everything is deleted when the app closes. Watchkeeper doesn’t phone home and has no account or analytics of its own. The only thing it keeps is a short per-site record for its “Last visit” section, which you can turn off, plus any reports you choose to save.
It doesn’t block anything. Pages load as they normally would, because the point is to watch what they do.
What It Shows
The project’s case studies make it concrete. A recipe blog added a data broker and a video ad network between two visits. A shop page called five other sites before anyone answered its cookie banner. An agency got a landing page report from the client who’d hired it. The site also explains how to tell a real fingerprinting script from a page that’s just drawing its own chart, and how to check a staging site on localhost before it goes live.
Who It’s For
- Curious people who want to see who’s watching, in plain language.
- Site owners checking what their own pages send, especially before the cookie banner is answered.
- Agencies and their clients reviewing a site’s tracking before or after a handover.
- Developers checking a staging site for new third parties before launch.
Limits
It doesn’t block trackers. It shows domain names, not the companies behind them yet, because naming companies needs a tracker list whose licence fits Apache 2.0. A site can try to hide by adding false entries about itself, and heavy activity can push some addresses out of the count, which the panel reports. A site can’t erase what Watchkeeper has already recorded. And it isn’t an everyday browser: no tabs, bookmarks or saved passwords, and downloads are refused for now.
The Four-Question Screening
Every project featured here gets the same four questions, the way you’d screen a startup idea.
1. Where is the money in it?
Watchkeeper is free, with no paid tier. Its users split two ways. For ordinary people it’s a teaching tool and a curiosity, and money there would come from sponsorship or a privacy-focused partner. The paying side is professional: agencies, site owners and compliance teams who need to show what a page sends. A paid edition could add company names from a licensed tracker database, saved and shareable reports, comparisons between visits and monitoring of many pages over time.
2. What real problem does it solve?
You can’t object to what you can’t see. Most people have no idea how many companies hear about each page they visit, and many site owners don’t either. Watchkeeper makes that traffic visible to anyone, without developer tools.
3. The technology in plain words
Picture a shop with a window into the back office. While you browse the shelves, you can watch the staff phone other companies to tell them you’re there. Watchkeeper is that window, with a notepad that lists every call.
4. Moat and differentiation
Ad blockers block and say little. Developer tools show everything and explain nothing. Watchkeeper sits between them: it lets the page behave normally and explains what it did in words a non-specialist can follow. The detection that a page can’t switch off, and the hostile-page testing behind it, are what make it trustworthy. The moat that can grow is the explanations and the case-study library that teaches people what they’re seeing.
Why It Matters
Privacy rules depend on people knowing what happens to their data, and most tracking happens out of sight. A tool that shows it plainly, to anyone, changes who gets to ask the questions.
Follow the Project
Start with the quick start, get it from the download page, read the case studies, or see the code in the Watchkeeper repository on GitHub. Watchkeeper is listed with the other open-source projects on SoftDevStudio.com, and more featured projects are in the Projects section.