Stop Mac Apps from Phoning Home
Block Telemetry & Background Tracking
Key Takeaways
Most Mac apps send telemetry, analytics, and usage data without clear consent
macOS provides no built-in way to see or block these outbound connections
A per-app firewall lets you decide which apps get internet access
What Does "Phoning Home" Mean?
When an app "phones home," it connects to its developer's servers to send data back. This can include usage analytics, crash reports, feature flags, license checks, or behavioral tracking.
Some of this is benign (crash reporting helps developers fix bugs). Some of it is not (detailed usage tracking sold to advertisers). The problem is you often can't tell which is which, and macOS doesn't give you visibility into it.
Common Apps That Phone Home
- •
Adobe Creative Cloud — telemetry, license validation, Experience Platform analytics
- •
Microsoft Office — diagnostic data, connected experiences, cloud features
- •
Electron apps — analytics, crash reports, update checks running in the background
- •
Antivirus software — threat intelligence uploads, scan results
- •
Cloud storage clients — constant sync, usage analytics
- •
Game launchers — playtime tracking, store telemetry
How to See What Your Apps Are Doing
Before blocking anything, you might want to see the scope of the problem. Open Activity Monitor and look at the Network tab. You'll see data being sent and received by processes you may not recognize.
Activity Monitor shows bandwidth but not which servers your apps connect to. For that level of visibility, you'd need a network monitoring tool like Little Snitch or Wireshark.
The Disable-Settings Approach (Limited)
Many apps offer telemetry opt-outs in their settings. The catch:
- •
Not all telemetry can be disabled through settings
- •
Some apps may re-enable telemetry settings after updates
- •
Some apps may continue sending data even when you opt out of telemetry
- •
You have to find and configure the setting in every app individually
The Hosts File Approach (Maintenance Burden)
You can block known telemetry domains in /etc/hosts. Community-maintained blocklists exist for popular apps. But domains change, new ones appear, and you're constantly updating the list.
Per-App Blocking (Recommended)
Instead of chasing individual domains, block the app entirely. If an app can't reach the internet, it can't phone home — regardless of which domains or IP addresses it tries to contact.
Install SplitTunnel on your Mac
Identify apps you want to silence
Set each one to "Block" from the menu bar
Start with apps you use offline — design tools, editors, IDEs. These work fine without internet access and are often the worst telemetry offenders.
A Practical Blocking Strategy
Not every app should be blocked. A reasonable approach:
- •
Block — apps that work offline and don't need internet for core function
- •
Block — apps you suspect of excessive telemetry
- •
Allow — browsers, email, chat, and apps that need internet to function
- •
Allow — apps you trust and that need cloud features
Privacy vs. Functionality Trade-offs
Blocking internet access means losing cloud features, auto-updates, and sync. For most productivity apps that work locally, this is a worthwhile trade. For cloud-native apps, it's not practical.
The goal isn't to block everything — it's to make deliberate choices about which apps deserve internet access instead of giving blanket permission to all of them.
Frequently Asked Questions
Your Apps, Your Rules
Decide which apps get internet access. Block the rest with one click.
7-day free trial · Cancel anytime