Proxy Sourcing

1. Why this page exists

Residential proxy traffic leaves from the connections of ordinary people. How those connections end up in a proxy pool is the single question that separates a service you can put in front of a compliance review from one you cannot. This page answers it.

We publish this because business customers ask, and because the answer should not depend on who is asking.

2. Where the addresses come from

The residential addresses we use come from people who agreed to share part of their connection and are compensated for it. They install an application, they are told what it does, and they can stop at any time — at which point their connection leaves the pool.

We do not use addresses obtained without the knowledge of the person whose connection it is. That rules out bandwidth taken by software bundled into an unrelated application, hidden in a browser extension, or acquired through compromised devices.

3. Withdrawing consent, and what we can see

Users who share their connection with us can withdraw that consent at any time — through the same application that enrolled the connection — and have the withdrawn connection removed from the pool.

We do not know the identity of the people behind individual addresses. All we see is which exit address served a given request, because that is what billing and the handling of misuse require.

4. What we do about misuse

Supply sourced properly can still be pointed at the wrong target. Our Acceptable Use Policy sets out what may and may not be done through our infrastructure, and section 8 of that policy describes what happens when it is broken.

Site operators who believe our infrastructure is being used against them can write to abuse@vectrawatch.com and request that their domains be excluded from collection. We honour such requests unless prevented by law.