Contents
Compartmentalising what you do — why, and how far
Everything you do from one connection and one browser can be cross-referenced. Here is where the line runs, and how far to push it.
update Updated
Compartmentalising means deciding for yourself what is linked to what.
Three legitimate reasons to separate
1. Not exposing your private life alongside your professional activity
A professional seller who browses their own listings, compares competitors and manages their account from the same connection as their personal browsing hands every platform a unified profile they never agreed to build.
Separating contexts follows the same logic as a work phone distinct from a personal one. Nobody finds that suspicious offline.
2. Not paying for a stranger's mistake
Public IP addresses are massively shared. On mobile networks, CGNAT puts hundreds of subscribers behind a single address. On a consumer VPN, thousands.
The consequence: when a service decides to block an address, it blocks everyone behind it. Blameless users hit a wall over something they did not do and will never hear about. That is the subject of Collective punishment.
3. Not depending on an address you do not control
Your home address changes at your provider's discretion. It may have been assigned yesterday to someone else, along with that person's history. A dedicated, stable address whose use you know removes that uncertainty.
Where the line runs
This site explains how to control your exposure. It does not explain how to escape a sanction.
Multiplying identities to get around a ban, inflate ratings or fool a trust system breaches the terms of every service concerned, and that is not what is being discussed here. Legitimate compartmentalisation can be said out loud: "I do not want my professional activity and my private life cross-referenced" is a sentence you can stand behind in front of the platform itself.
If your reason cannot be phrased that way, no tool on this page will solve your problem — it will only make it more expensive the day it turns against you.
What technically links two contexts
Understanding the links means understanding which ones are worth cutting.
| Link | Strength | How to compartmentalise it |
|---|---|---|
| IP address | 🔴 very strong | One dedicated address per context |
Cookies, localStorage, cache |
🔴 very strong | One browser profile per context |
| Canvas / WebGL / font fingerprint | 🟠 strong | Antidetect browser, or a separate machine |
User-Agent, resolution, time zone, language |
🟡 medium | Profile settings |
| WebRTC disclosing the real IP | 🔴 very strong | Must be neutralised — otherwise all the rest is pointless |
That last row deserves attention: it is the only one that cancels all the others. Perfect compartmentalisation with WebRTC active hands your real address to the first page that asks.
One address per context, and for the long run
A counter-intuitive point: stability beats change.
An activity run from a constant address looks like someone who has a home. The same activity seen from a different address every day looks like someone about whom nothing is known — and trust services treat the unknown with caution.
Changing address is a tool for breaking away — starting cleanly after a collective block, opening a genuinely new context — not a daily-use tool. See Changing your IP.
Basic hygiene, whatever the context
- One browser profile per context, no shared cookies
- Time zone and language consistent with the address in use
- WebRTC neutralised
- DNS resolved through the proxy, not by your internet provider
- No extension that sends your history to a third party
These five points are ordinary digital hygiene. They protect your privacy whatever you use it for — which is exactly why they are worth recommending.
See also: Collective punishment · WebRTC and DNS leaks · Why a French IP
Need a French mobile proxy? A real French 4G line, one HTTP port and one SOCKS5 port, IP rotation on demand.
See the offersarrow_forward