Can a company see what you look at on their WiFi?

Q: Can a company see what you look at on their WiFi?

On most modern Wi‑Fi, others usually can’t read your exact web pages if HTTPS is used. A network owner may still see which devices connect and which domains you contact. Unencrypted traffic (HTTP or other plain protocols) can reveal content to anyone who can intercept it. What’s possible depends on encryption, your app behavior, and the network’s logging practices. The safest assumption is to treat your Wi‑Fi as not inherently private.

Direct answer and scope

A company typically cannot see the exact content of what you look at on a Wi‑Fi network if your traffic is encrypted end‑to‑end (for example, when websites use HTTPS and your apps follow the encryption). However, the company may still be able to observe certain non‑content details, such as that a device connected to the network, the timing of activity, and which servers or domain names you contacted.

A simple model: what can be seen vs. what stays hidden

Think in two layers:

Connection and destination information: Even with encryption, a Wi‑Fi operator can often see traffic patterns at the network level (e.g., which device talks when, and to what general destination). This does not automatically reveal the exact text you viewed.
Page or message content: The readable “what you looked at” part is protected when the content is encrypted and only decrypted by the endpoints (your device and the website/service).

So, the company might be able to answer questions like “what did your device connect to?” but not “what exact sentences did you read?”—provided encryption is actually in use.

Differences and important exceptions

The key exceptions are when content is not encrypted or when it’s encrypted in a way that the network can still access.

Unencrypted traffic: If you visit a site or use a service over plain HTTP or other non‑encrypted protocols, that content can be exposed to anyone who can capture the traffic on the same network path.
Partial encryption or mixed behavior: Some apps or pages may include elements that are fetched differently; if any part of the interaction is sent without encryption, some content can become visible.
Logging choices: Even when encryption is strong, what a company can learn depends on what it logs and how long it retains metadata. Different organizations handle this differently.

Practical checks you can do

To reason about your situation without guessing:

Check whether the site uses HTTPS: Most browsers indicate this visually; if a connection isn’t encrypted, content exposure is more likely.
Notice when behavior is inconsistent: If something loads unusually or prompts about security, it may indicate mixed or unencrypted requests.
Assume metadata can be visible: Even with encryption, treat Wi‑Fi providers/operators as able to see connection timing and destinations.
Recognize your limits: Without access to network logs or the exact traffic configuration, you can’t prove what a specific company sees—only what is technically plausible given encryption and your app/protocol behavior.