For macOS · Windows version coming

Stop telemetry.
Take back your bandwidth.

Your Mac talks to Apple all day — even when you don't. Weimer Network Defender silences the chatter at the process and firewall level. No internet connection required.

No subscription · No tracking · Free updates within v3.x

The problem

Your device talks too much.

Without you noticing, your device sends personal data to remote servers around the clock. The privacy settings in System Preferences don't stop most of it.

Photos
Uploaded
Image recognition, location metadata, face indexing
Location
Tracked
GPS coordinates, WiFi-based positioning, movement history
Contacts & Calendar
Synced
Address book, events, meetings, communication graph
Voice & Siri
Recorded
Voice samples, queries, command history
Diagnostics
Reported
App usage patterns, crash data, device identifiers
System resources
Consumed
Bandwidth, CPU cycles, battery life — for traffic you never asked for
Three layers of defense

Kill. Block. Watch.

01 · KILL

Process-level termination

The defender watches outbound traffic and terminates any tracked process the moment it sends data. Reaction time is under 100 ms. An aggressive mode kills known telemetry processes on sight.

~100ms reaction · sender-reactive
02 · BLOCK

IP-level firewall

Each known-telemetry destination is registered with the system firewall. Outbound packets to over 700 endpoints get dropped before they leave your device. No internet round-trip, no DNS leak window.

Endpoints blocked · kernel-level drop
03 · WATCH

Real-time monitoring

Every service, every PID, every connection — visible in a single sortable list. Cumulative sent/received counters per service. Spot the noisy processes; decide what to allow, what to kill, what to firewall.

Services catalogued · live updates · sortable
How it works

Built for power users. Easy to use.

Services window

See everything talking on your device.

250+ services pre-catalogued with descriptions, sorted by traffic. Filter by Allowed, Auto-Kill, Auto-IP, or Undefined. Cumulative bytes since first run.

Click any row to see PIDs, connections, and destination IPs. The data you needed Activity Monitor to give you, but never did.

Services window with sortable columns and filter chips
Services window with sortable columns and filter chips
Detail control

Per-service decisions in two clicks.

Double-click a service to open detail. See every PID, every IP it's reaching, every byte counter. Then decide: Allow, Auto-Kill, or — for fast-respawning services — Instant-Kill.

Dangerous decisions get an explicit confirmation modal. Safe ones are one click.

Data sources

See what each service touches on your disk.

The detail popover lists every file a service has open right now — SQLite databases, plists, caches, system files. Each row shows the path, the filename, and the on-disk size.

Double-click any row to reveal the file in Finder. Verify what a service actually touches before deciding whether to allow it, kill it on send, or kill it on sight.

Detail popover showing data source files for UsageTrackingAgent
Services window with sortable columns and filter chips
The result

~99% reduction. Verified.

Outbound telemetry drops from kilobytes per minute to nearly zero. Background services that previously synced photos, locations, contacts, voice, and diagnostics fall silent — only the connections you explicitly allow get through.

Measure it yourself with any system network monitor. No marketing claims, no inflated numbers — the values you see are the values you get.

New in 3.1.0 · Safety net

Safe Recovery Mode at every boot.

Configured an aggressive kill rule that turned out to be too aggressive? At every boot, the defender pauses killing until you confirm in a recovery dialog. Click × next to any service you want to keep running — it's allowed permanently. Press OK to resume killing the rest.

Default ON for new installs. Power users can switch it off in Configuration. Your fallback if a rule ever locks you out at startup.

Configuration window with Safe Recovery Mode toggle
Our privacy promise

We don't take your data.
Because we don't need to.

We don't collect

No analytics, no usage tracking, no fingerprinting. The defender runs entirely on your device.

We don't use

Nothing leaves your Mac. No telemetry, no crash reports, no "anonymous" data we promise to anonymize.

We don't share

No third parties, no ad networks, no government partnerships. The privacy commitment is structural, not promotional.

The defender connects to a server only once — to verify your license key on activation. No other outbound traffic.

Frequently asked

What you should know.

Will this break my Mac?
No. The standard Auto-Kill mode is sender-reactive — it only terminates PIDs that have been observed sending data. Idle services are never touched. The stronger "Instant-Kill" mode is gated behind an explicit warning modal that names the risks (potential freeze on system-critical services). If anything goes wrong, boot into Safe Mode and run --remove <service> to undo it.
Does the defender itself track me?
No. No analytics, no telemetry, no crash reports, no update checks. The only outbound connection is the one-time license activation: a single HTTPS request to verify your purchase key. After that, nothing. The privacy commitment is structural, not promotional.
What about updates? How do I get them?
Updates within version 3.x are free and delivered as new DMGs via email to your purchase address. The app does not check for updates automatically. When v4.0 ships (sometime in the future), existing users get a discounted upgrade.
What operating systems do you support?
macOS 11.0 (Big Sur) or later is available now. Universal binary — runs natively on Intel and Apple Silicon. Tested on macOS Tahoe (26.x) on Apple Silicon. A Windows version is in development; reach out if you'd like to be notified when it's ready.
What if Apple changes things and you stop working?
The defender uses macOS's own nettop, pf, and launchctl — system tools Apple has shipped for over a decade and is unlikely to remove. If a macOS update changes the daemon names or service structure, we release a compatibility patch as a v3.x update.
Refund policy?
14 days, no questions asked, processed through Polar (our payment processor). Drop us a line and you get your money back. We'd rather have a happy non-customer than an unhappy one.