What changes
| Property | With a proxy | Without |
|---|---|---|
| Apparent origin | The exit's address | Your own address |
| Path visibility to your local network | Reduced, if the tunnel is encrypted and captures the traffic | Visible to the local network operator |
| Visibility to the destination | Sees the exit, not your address | Sees your address |
| Who else can observe the path | The exit operator | Your ISP or network operator |
Notice the last row: a proxy does not remove an observer, it substitutes one. Whether that is an improvement depends entirely on who the new observer is and what they do with it.
What does not change
- Login identity. If you sign in, the service knows who you are.
- Browser and device signals. Screen size, fonts, time zone, language and a long list of other values remain.
- Session behaviour. Frequency, timing and patterns are visible to the destination regardless of address.
- Data you submit. A proxy does not anonymise what you type.
- Payment identity. Card details, billing address and account history are unaffected.
“No logs” is a claim, not a measurement
Every provider says something about logging. What can actually be assessed is narrower: who operates the service, what jurisdiction and legal process apply, whether an independent party has examined the claim, and what the terms say about retention and disclosure. Those are all inputs to a judgement, not proof.
For a free or shared service, add the incentive question: the servers cost money, so who is paying, and what do they get? That question does not answer itself either way, but it is more informative than a slogan.
Threat models worth separating
| Concern | Does a proxy help | Note |
|---|---|---|
| Local network seeing destinations | Yes, if encrypted and captured | The exit now sees them instead |
| Destination seeing your home address | Yes | Assuming the exit is not attributable to you |
| A service identifying your account | No | Authentication is the identity |
| A provider retaining records | Depends on the provider | You are choosing whom to trust, not removing trust |
| Traffic analysis by a large network | Partially | Volume, timing and endpoints still leak information |
Practical consequences
- Do not treat an exit as anonymity for accounts you care about.
- Do not put traffic through an operator you would not want observing it. That is the whole decision.
- Encryption still matters; a proxy is not a substitute for HTTPS.
- Fewer accounts and less submitted data do more for privacy than any node choice.
- If a source requires installing a root certificate, understand that this changes who can vouch for certificates on your device — a far larger step than routing.
What to record when evaluating a service
- Who operates it, and where.
- What the terms say about logging, retention and disclosure.
- Whether any independent examination exists, and its scope.
- What the payment and account relationship reveals about you.
- Whether the client requires permissions beyond routing traffic.
Write “unverified” where you have no evidence. A privacy claim you cannot check is not a property you can rely on.
Scope
This page describes limits, not endorsements. It makes no assertion about any provider's logging, and it does not claim that any configuration makes a user anonymous.