Privacy · April 23, 2026

What your ISP knows about you (and how a home proxy doesn't change that)

One of the most common misconceptions we hear: "I'm getting a ProxyBox to hide from my ISP." That's not what it does, and being clear about that matters. Your ISP sees everything the ProxyBox sends out, because the ProxyBox is literally on your home connection.

Start from what's actually on the wire

Your home internet connection is a cable or fiber run from your house to your ISP's local pop. Every packet your home sends to the internet crosses that wire. Your ISP sees:

• The destination IP of every connection you make (to which server).
• The timing + size of every connection (when you started, when you stopped, how much bandwidth).
• Your DNS queries (which hostnames you looked up), unless you use encrypted DNS.
• For plaintext HTTP traffic (rare now), the actual content.

What they generally don't see:

• The content of HTTPS connections (encrypted between your browser and the destination server).
• The content of any VPN or WireGuard tunnel you've set up.
• Application-layer metadata hidden inside encrypted tunnels.

That gap, "they see destinations and timing but not content", is the fundamental trust model of the modern internet. HTTPS made it much harder for ISPs to read your traffic, but it didn't eliminate metadata.

Why a ProxyBox doesn't hide you from your ISP

The ProxyBox lives on your home network. When your phone in Lisbon routes a request through your home ProxyBox to LinkedIn, the path is:

1. Your phone → Portuguese Wi-Fi → internet → your home ISP → your ProxyBox
2. Your ProxyBox → your home ISP → internet → LinkedIn's server

In step 2, your home ISP sees the outbound connection from your ProxyBox to LinkedIn. They always see that. The ProxyBox doesn't hide your home's outbound traffic from your own ISP; it just hides it from LinkedIn's perspective as a datacenter IP.

This is sometimes useful to state plainly because people ask the wrong question.

What actually hides you from your ISP

Standard answer: a VPN you trust. When you connect to a VPN, your ISP sees one long encrypted tunnel to the VPN provider, and nothing else. They know you're using a VPN (the destination IP is obvious). They don't know which sites you're visiting through it.

Better answer: a VPN and encrypted DNS. If you use 1.1.1.1 over HTTPS (DoH), your ISP can't even see which hostnames you're resolving.

Best answer if you need serious privacy: don't use residential internet for the activity that needs privacy. Separate the channels. Use a mobile hotspot for sensitive work. Rotate IPs at a layer your ISP doesn't control.

So what are ISPs actually doing with the data?

Depends on the country:

• US (post-2017): The FCC's broadband privacy rules were repealed. ISPs can legally sell customer browsing data to advertisers. Several large ISPs do exactly this through subsidiaries.
• EU (GDPR): ISPs face much stricter consent requirements for data use. Selling browsing data without explicit opt-in is illegal.
• Five Eyes + adjacent: ISPs retain connection logs for law-enforcement use (18 months is typical). Served with a warrant, they hand it over.

Whether you care depends on your threat model. For the average user, the practical concern is ad targeting, not surveillance. Commercial VPN + encrypted DNS is adequate for that. For journalists, activists, or anyone with a reason to be careful, more serious separation is warranted.

Where ProxyBox fits in the picture

ProxyBox is an egress tool: it changes how your traffic looks when it reaches a destination. It's not an ingress tool: it doesn't hide what you're doing from the wire between your home and your ISP.

If you want to:

• Have LinkedIn, Instagram, banks see your home IP from anywhere → ProxyBox.
• Keep your ISP from logging your browsing to build a profile → VPN + DoH, not ProxyBox.
• Both, stacked → Run a VPN on your device, pointed at a cloud VPS, then proxy through ProxyBox. The VPN hides you from your local ISP (and the coffee shop); the ProxyBox hides you from the destination as a residential user.

We'd rather be clear about this than let customers arrive at the wrong mental model. ProxyBox is a great tool for the specific problem it solves. It's the wrong tool for problems it doesn't solve.