A proxy network is only as trustworthy as the way its IP addresses are sourced. Behind every residential IP address is a real person, and behind every request is a customer we are responsible for. This page explains where Proxonym's IP addresses come from, how the people who share their connections are treated, what we block and how we handle abuse.
Our commitments
- Every residential IP address comes from a person who opted in and can opt out at any time.
- Peers share idle bandwidth only, and neither we nor our customers have access to the content of their devices.
- We block high-risk targets and ports at our gateways.
- We verify customers for sensitive use cases and large accounts.
- We investigate suspicious traffic and act on confirmed abuse.
- We never store the content of proxy traffic.
Where residential IPs come from
Our residential IP addresses belong to real consumer devices whose owners chose to join our network through partner apps and SDKs. We call these people peers. Here is how participation works:
- Opt-in through partner apps. App developers who work with us integrate an SDK that lets their users share idle bandwidth. When someone uses one of these apps, the app asks whether they want to take part in exchange for a benefit.
- Clear consent screens. The request appears on a dedicated screen in plain language, not as a clause buried in a long terms document. It explains that the device's internet connection will be used to route web traffic for businesses, and what the person gets in return. Nothing is shared until the person agrees.
- Opt-out at any time. Peers can turn sharing off in the app's settings whenever they like. Uninstalling the app also ends participation.
- Idle bandwidth only. The SDK only uses a device when it is idle and under battery-friendly conditions, for example when it is connected to Wi-Fi and charging. The person's own use of their device and connection always comes first.
- No access to personal data. Customer traffic only passes through the device's internet connection. Neither we nor our customers can access the files, photos, messages, browsing history or any other content on the device.
In practice, a peer's device acts as an exit point. A customer's request travels through our gateway to the device and from there to the target website, which sees the device's IP address. The response travels back the same way. Nothing is installed on the device beyond the partner app itself.
This model only works if peers stay informed and in control, so we treat consent as a requirement, not a formality.
How peers are compensated
Sharing bandwidth is a value exchange, and peers should get something real in return. Partners compensate peers, for example with premium features or an app experience without ads. The benefit is shown on the consent screen, so people know what they give and what they get before they agree.
How we vet partners
We only work with app developers who meet our standards, and we check them before and after launch:
- Review before launch. We review each partner app's consent screen, disclosure text and opt-out before any of its users can join the network.
- Clear rules. Partners must collect explicit consent, comply with the policies of the app stores where they publish and follow applicable privacy laws.
- No hidden use. Partners may not hide the SDK, mislead users about what it does or include it in apps directed at children.
- Ongoing checks. We re-check partner apps periodically and investigate any sign of a consent problem.
- Removal. If a partner breaks these rules, we stop routing traffic through its users' devices and end the partnership.
How ISP, datacenter and mobile IPs are sourced
Our other products are sourced differently:
- ISP proxies: we lease IP ranges from internet service providers and host them on servers in data centers. The addresses are registered to consumer ISPs, but no one's home connection or personal device is involved.
- Datacenter and dedicated datacenter proxies: these use our own IP allocations from hosting providers.
- Mobile proxies: these come from carrier-connected devices on 3G, 4G and 5G networks, used with the consent of their owners.
What we block and why
Some destinations carry a high risk of fraud or attacks, and traffic to them could expose peers to suspicion for something they did not do. Our gateways block these categories by default:
- government and military websites;
- online banking and payment portals;
- mail ports 25, 465, 587, 110, 143, 993 and 995, to stop spam and attacks on mailboxes; and
- remote access ports 22 (SSH), 23 (Telnet) and 3389 (RDP), to stop brute-force attacks and unauthorized access.
Requests to blocked targets return a 403 error. We add targets to the list when we see new abuse patterns. If a customer with a dedicated datacenter plan has a legitimate business need to reach a blocked category, they can ask in a ticket, and we may enable specific access after verification.
Our Acceptable Use Policy lists every prohibited activity, from fraud and credential stuffing to spam and the unlawful collection of personal data.
Customer verification
Blocking risky targets is only part of the job. We also look at who uses the network. For sensitive use cases and large accounts, we ask customers to verify their identity or business and describe what they plan to do, a process known as know your customer (KYC). Verification covers who the customer is, which targets they plan to access, the volume they expect and whether the use case is lawful. Until verification is complete, we may limit access. If a use case does not fit our policies, we decline it.
How we handle abuse
Every abuse case follows the same three steps:
- Detect. Gateway blocks, per-account rate limits and traffic monitoring flag suspicious activity. Anyone who sees abusive traffic from one of our IP addresses can also report it to the network that operates the address, through the abuse contact in its WHOIS record, with the IP address, an exact timestamp with time zone, the target and a description of the activity.
- Investigate. We match the case against our connection metadata to identify the account involved and review its activity against our policies.
- Act. Depending on severity, we warn the customer, throttle traffic, suspend or close the account, and report to the authorities when the law requires it or the harm is serious.
Peers stay in control: if you believe your device is part of our network without your consent, turn sharing off in the partner app's settings or uninstall the app, and participation ends right away.
How we handle data
- No content logging. Our gateways never store the content of requests or responses.
- Limited metadata. For billing, abuse prevention and troubleshooting, we keep connection metadata (account, timestamp, target hostname, bytes transferred and status) for up to 30 days, then delete it.
- Minimal peer data. We process only the technical data needed to route traffic through a peer's connection.
- Separation. Peers and partner app developers do not receive customer account details, and customers see only the IP address their traffic exits from.
- No data sales. We do not sell personal data about customers or peers.
Our Privacy Policy has the full details.
Using proxies legally
Proxies are a standard tool for working with public web data. Companies use them to monitor prices, verify ads, track search rankings, protect their brands and research markets.
In most places, using a proxy is legal in itself. What matters is what you do with it. A proxy does not make an unlawful activity lawful, and it does not override a website's terms. Collect public data, keep request rates reasonable, respect robots.txt and handle personal data in line with the law. Some projects need extra care, such as collecting data that includes personal information or automating actions on platforms that restrict automation. If you are unsure about a use case, get legal advice before you start.
Questions
The help center answers common questions about our network, and the Acceptable Use Policy and Privacy Policy go into the details. We do not take messages by e-mail.
