How to Block Game Telemetry on Mac
Find and Block Telemetry Domains
Key Takeaways
Game launchers send analytics, hardware surveys, and crash data continuously, including when you aren't playing
Domain rules block a telemetry hostname at the DNS layer for your whole Mac, which is usually what you want for endpoints that carry nothing but telemetry
To silence one launcher completely, block the app instead. Domain rules and app blocks are separate tools
What Telemetry Do Game Launchers Send?
Game launchers don't just launch games. They collect and send data constantly, including while you sit idle on the store page. Blocking game telemetry on a Mac comes down to two questions: which domains carry it, and what else on your Mac depends on those domains.
- •
Usage analytics — What you play, how long, when you play
- •
Hardware surveys — GPU, RAM, CPU, display info
- •
Crash reports and diagnostics
- •
Ad tracking and conversion data
- •
Social features — Friends, achievements, activity status
Why Block It?
- •
Privacy — Game companies monetize aggregated data
- •
Bandwidth — Constant background network calls
- •
Battery — Network activity keeps radios active on laptops
- •
Principle — Most of this collection isn't transparent or opt-in
The Usual Approaches
- •
/etc/hosts — Every hostname has to be listed by hand, with no subdomain coverage and no easy way to see what to add
- •
Pi-hole or a filtering resolver — Same DNS layer, applied to your whole network. Good if you want every device covered, more to run and maintain
- •
Per-connection firewalls — Approve or deny connections as they happen, which gives fine-grained rules at the cost of a steady stream of prompts
SplitTunnel sits at the same DNS layer as the first two, so its rules are machine-wide as well. What it adds is the part that's usually missing: seeing which domains a launcher actually contacts, and turning one of them into a rule with a click.
How Domain Blocking Works in SplitTunnel
SplitTunnel answers your Mac's DNS lookups. Add a hostname to Domain Rules and that name stops resolving, so the connection is never made. The launcher never learns the address to connect to.
Two things follow from that. Rules cover subdomains automatically, so a rule on a hostname also covers anything underneath it. And rules are global: the domain is blocked for every app and every browser on the Mac, not only for the launcher you were watching.
Domain rules are machine-wide by design: what a Pi-hole does for a whole network, a domain rule does for this Mac. SplitTunnel doesn't scope a domain rule to one app, so there's no "block this domain, but only for that launcher."
Global Blocking Is Usually Fine for Telemetry
Dedicated telemetry endpoints serve telemetry and nothing else. A hostname built for analytics isn't carrying your downloads, your sign-in, or your match traffic, so blocking it everywhere costs you nothing. It also covers the launcher, the games it installs, and the vendor's other apps in one rule.
Shared services are where care is needed. Analytics and crash-reporting platforms sit behind domains that hundreds of unrelated apps use. Block one of those and you're switching it off for everything on your Mac, not just the game.
Block the specific hostname you saw, not its parent. Because a rule covers everything beneath it, blocking a vendor's root domain to stop one tracking host would take the store and sign-in with it.
Find the Domains Your Launcher Contacts
Static blocklists go stale as vendors move endpoints. The reliable method is to watch what the launcher does on your own Mac.
Install SplitTunnel and start the tunnel — Activity shows live connections once the extension is running
Open the launcher and leave it idle on the store or library page for a few minutes
Open the Activity panel, click Clear for a clean read, and watch for that launcher's connections as they appear
Read the domains — names containing analytics, telemetry, metrics, tracking, datarouter, or events are the usual candidates
Select a connection to open its details and click Block. The rule applies immediately and appears in Domain Rules
Domain Rules is where every rule lives. You can search it, add a hostname by hand with Add Domain, and unblock anything in one click if a rule turns out to cost you something you wanted.
What Telemetry Domains Look Like
- •
Steam — Hardware survey and store analytics endpoints
- •
Epic Games — datarouter.ol.epicgames.com and related tracking hosts
- •
Battle.net — Blizzard's telemetry and diagnostics hosts
- •
EA App — Telemetry and analytics hosts under the vendor's domain
- •
Cross-vendor — Shared analytics and crash-reporting services such as Google Analytics, Sentry, and Crashlytics
Treat that as orientation rather than a blocklist. Endpoints change, and the cross-vendor services in the last row are exactly the shared kind to think twice about, because a rule on one affects every app on your Mac that uses it. Confirm against the Activity panel before you block.
What NOT to Block
Not every connection a launcher makes is telemetry. Leave these alone:
- •
CDN and content domains — Game downloads will break
- •
Auth domains — You won't be able to sign in
- •
Matchmaking and game server domains — Can't play online
- •
Update and patch endpoints — You'll miss updates
- •
Friends, chat, and presence — If you use those features
- •
Anything a shared service also serves to other apps on your Mac
When in doubt, don't block it. If something breaks after you add a rule, open Domain Rules and unblock it. Every rule is one click to remove.
When You Want to Silence a Launcher Completely
Domain rules are the wrong tool if your goal is "this launcher should stop talking to the internet at all." For that, use the app-level block: open the Apps panel, find the launcher, and switch it to Block. That cuts all of its network access, not just its telemetry.
It's deliberately blunt. A blocked launcher won't sign in, update, or download, so it suits launchers you keep installed but rarely open. Switch it back to Allow when you want to play. Our firewall guides cover this per-app side in more detail.
The two controls are independent: domain rules act on names for the whole Mac, the app block acts on one app's traffic. Combining them into "this domain, but only for that app" isn't something SplitTunnel does today.
Verifying Your Rules
Open Domain Rules — every rule you've added is listed there
Reopen the connection in Activity — the button reads Unblock once a rule is in place
Leave the launcher running and watch Activity — new connections to that host should stop appearing
Play a session. If something you needed broke, unblock the domain and try a narrower hostname
If a Block Doesn't Seem to Work
- •
DNS caching — A name your Mac already resolved can stay cached until it expires. Quit and reopen the launcher, or give it time
- •
Browsers on encrypted DNS — Chrome and Firefox can send lookups over their own encrypted DNS instead of the system resolver. Turn on Block Encrypted DNS under Strict Mode in Settings to keep them on the path domain rules can see
- •
Apps with their own resolver — A few apps pin encrypted DNS or a fixed provider. SplitTunnel doesn't inspect encrypted traffic, so those stay out of reach and the app-level block is the fallback
- •
Connections straight to an IP address — No lookup happens, so there's no name for a rule to catch
Game launchers are native apps that use the system resolver, which is why domain rules work well for this job. Browsers are the case that needs Strict Mode, and it's opt-in because it forces them off the encrypted DNS provider they picked.
Frequently Asked Questions
Your Games, Your Privacy
See the domains your launchers contact and block the ones you don't want. One click to block, one click to undo.
7-day free trial · Cancel anytime