Costs, privacy & the law
What your internet provider actually sees — and what the law says
Widely misunderstood in both directions. Here is what is technically observable, and what the law in France and elsewhere actually provides for.
Updated 2026-09-01 · 5 min read
This page is a factual account of how monitoring and the law work, because the topic is surrounded by confident nonsense in both directions — "nobody can ever see anything" and "you will be fined for streaming". Neither is accurate.
What a provider can technically observe
| Visible to your ISP? | |
|---|---|
| Which sites you connect to (domain names, via DNS and SNI) | Yes, usually |
| The content of an HTTPS page | No — encrypted |
| How much data you transfer, and when | Yes, always |
| That you are using BitTorrent | Yes — the traffic pattern is distinctive |
| Which specific file you are sharing over BitTorrent | Not by the ISP. But by anyone in the swarm, which matters more. |
| What you stream from your own server over HTTPS | No |
The crucial row is the fifth. In France, detection is not done by your provider watching you — it is done from inside the swarm. BitTorrent is a public protocol: every participant sees the addresses of every other participant. Rights-holder agents join swarms and record what they see. Your provider is then asked to match an address to a subscriber.
What a Hadopi notice actually is
In France the graduated-response mechanism (now run by Arcom, following the merger with Hadopi) works in stages:
- 1
An agent records an address in a swarm
A sworn agent, on behalf of rights holders, notes the IP address, the file, the date and time.
- 2
Your provider identifies the subscriber
It is legally required to match the address to an account and forward a notice. The provider is not the accuser.
- 3
First notice — an email
A recommendation, with no penalty. Most cases stop here.
- 4
Second notice — email plus registered letter
If a new observation occurs within six months.
- 5
Referral to the prosecutor
Only after repeat observations, and it remains rare relative to the number of first notices. The offence charged is negligence in securing one's connection, punishable by a fine.
Elsewhere the shape differs — in the United States and much of Europe, rights holders send DMCA-style notices to the ISP, which forwards them; some providers apply their own escalation.
Streaming versus downloading, legally
- Watching an unlicensed stream is not a shared act: you receive, you do not distribute. It is why the graduated response does not target it — the mechanism is built on observing sharing. That does not make it lawful; a temporary reproduction is still a reproduction, and enforcement targets the sites rather than the viewers.
- Sharing over BitTorrent makes you a distributor, technically and legally, whether you intended to or not. That is what the mechanism observes.
- Private copying exists in French law and covers copies made by an individual, from a lawful source, for their own household. It does not authorise circumventing a technical protection measure — which is why ripping a protected DVD remains prohibited even for personal use.
Where a seedbox actually sits
Renting a server is lawful and unremarkable — the same service that hosts websites. Three factual observations, without any encouragement attached:
- 1The machine has its own address, not your home address. Your provider is not in the path of what it does.
- 2The host is in the path, and is subject to the law of its jurisdiction. It receives notices, and its terms of service say what it does with them — usually suspension of the account. Read them.
- 3Nothing about this makes an unlawful act lawful. It relocates it. Rights holders pursue hosts, and hosts comply.
+Can torrenting be traced?
Yes, and not by the mechanism people imagine. Your provider does not inspect your traffic; observation happens inside the swarm, where BitTorrent shows every participant the address of every other. Rights-holder agents join and record what they see, then ask the provider to match an address to a subscriber.
+Does torrenting expose your IP address?
To every other peer sharing that file, yes — it is how the protocol works, not a flaw or a setting. This is the single structural difference with Usenet, where you download from one provider and no swarm exists to observe from.
+What are the dangers of torrenting?
Legally, distributing works you have no right to is infringement, and BitTorrent makes you a distributor whether you intended it or not. Practically, public swarms also carry mislabelled and malicious files. Neither risk is removed by where the machine sits.
+Does a VPN make torrenting legal?
No. It changes what is observable, not what is lawful. A VPN is a privacy tool with legitimate uses; it is not a legal shield, and providers do respond to legal process.
+Can my ISP see that I use a seedbox?
It sees an encrypted connection to a hosting provider, and how much data it carries. That is an ordinary pattern, indistinguishable from remote working or cloud backup.
+I received a first notice. What happens?
Nothing automatic. It is a warning with no penalty attached, and it invites you to secure your connection. Do not ignore repeats: escalation depends on new observations.
+Is Usenet monitored the same way?
Not by the same mechanism, because there is no swarm to observe from — the graduated response is built on peer-to-peer observation. That is a factual difference in detection, not a difference in legality.
