What your internet provider can track

When people say “being tracked by your internet provider” they usually mean that the provider can observe parts of your internet activity. Exactly what is visible depends on the network setup and your device/browser behavior, but common categories are:

  • Connection metadata: when you connect, how long you stay connected, and often the IP address(es) involved.
  • Destination and domain patterns: whether your traffic is going to certain servers, and in many cases which hostnames are requested.
  • Traffic characteristics: timing, volume, and other patterns that can sometimes be correlated with activity.

Important limitation: even when the content of your browsing is protected, metadata visibility may remain. That’s why “not being tracked” needs to be framed as reducing what the ISP can associate with you, not as removing all observability.

How encryption and tunneling change what’s visible

Two technologies are often confused: protecting the web content itself (e.g., HTTPS) versus rerouting traffic so the ISP sees a different endpoint.

HTTPS: protects page content, not everything

If you browse with HTTPS, the provider generally can’t read the webpage contents in transit. However, the provider may still be able to observe:

  • The fact that you’re making secure connections.
  • The IP addresses you connect to.
  • Potentially some information derived from the connection process (the exact details vary).

So HTTPS can reduce “what you read,” but it may not fully address “what you visit” from the provider’s perspective.

VPN: changes who sees your traffic’s destination

A VPN typically creates a protected tunnel between your tablet and a VPN server. In many normal setups, this means the ISP sees traffic to the VPN server rather than directly to each website.

What this can help with:

  • Reducing the ability of the ISP to associate your activity with specific destinations.

What this may not fully solve:

  • The ISP can still see that you’re using a VPN and can still observe connection metadata such as timing and the VPN server IP.
  • Your overall privacy also depends on preventing leaks (for example, DNS resolution behavior) and on how the browser/device uses networking features.

Practical differences to consider: “content,” “destinations,” and “identifiers”

To reason clearly, separate three layers:

  1. Content layer (what pages or requests contain): encryption helps here.
  2. Destination layer (which sites/services): tunneling (often via a VPN) helps here more than HTTPS alone.
  3. Identifiers and patterns (how activity can be linked to you): this can include your IP address, session behavior, and network-level metadata.

A common real-world outcome is:

  • With HTTPS only, the ISP may still infer destinations via network-level signals.
  • With a VPN, the ISP may see fewer destination details, but you still have identifiers (the VPN server connection) and metadata.

Differences and limits that can change the result

Several boundaries can make the outcome weaker than expected:

  • No universal “guarantee”: Even with strong encryption, some metadata is usually visible because the provider must route traffic.
  • Leaks and misconfiguration: If DNS queries or other traffic bypass the tunnel, the ISP (or other observers) may learn more than intended.
  • Device and browser features: Some connectivity options can cause behavior that isn’t fully covered by simple assumptions.
  • Third parties: Avoiding ISP visibility does not automatically prevent tracking by websites, apps, or advertising networks.

When evaluating any approach, focus on what you want to reduce (ISP-level destination knowledge, ISP-level content knowledge, or linkability via identifiers) and then verify those aspects.

Practical checks you can run on your tablet

You can’t fully prove what your ISP logs, but you can validate whether common signals are consistent with your expectations.

  • Check your visible IP from the tablet: Compare an “external IP” value (from a test page) with and without your privacy tool. A change typically indicates that routing has changed.
  • Test DNS behavior: Use a DNS-related test to see what resolver your requests appear to use. If DNS is still handled directly by your ISP, that may reduce the benefit for ISP-level visibility.
  • Confirm browser connections are encrypted: Look for secure connection indicators when loading sites that support HTTPS.
  • Detect obvious IP/DNS leaks: Run leak-check style diagnostics (for IP and, if available, DNS). Treat results as practical signals, not absolute proof.

If a check shows that IP/DNS is not behaving as expected, the most likely causes are misconfiguration, app/browser settings, or networking features that bypass the intended protection.

To place the topic correctly, keep these related ideas in mind:

  • Tracking vs. observability: “Tracking” often refers to linking activity to you; “observability” is what someone can see.
  • Metadata vs. content: Encryption mostly targets content, while tunneling can change who sees destinations.
  • Session behavior: Logging and correlation can happen over time even if content is hidden.

A clear approach is to reduce the ISP-visible link between you and destinations, while separately managing website/app tracking via browser settings and account choices.