Why we don’t allow torrenting on TuxlerVPN Mobile

A reasonable question to ask any consumer VPN is: which of the things people use VPNs for are you actually built for? Two products that both call themselves “VPNs” can have opposite answers. This post explains the design choice we made (TuxlerVPN Mobile is for everyday browsing on Android, not for bulk download) and the reasons that choice is an engineering and policy decision rather than a marketing one.

”VPN” covers two very different products

If you skim the VPN market, you will notice that the providers fall into roughly two camps once you get past the homepage:

• Privacy tools for everyday browsing. Built around connection quality on phones and laptops, modest per-user bandwidth, and a small surface for legal exposure. They optimize for the case where most of your traffic is short HTTPS sessions: web pages, messengers, calendar sync, push notifications.
• Commercial overlay networks built around bulk download. Built around sustained high-throughput sessions, P2P-friendly NAT behavior, and an explicit acceptance that copyright complaints will be a constant operational cost. They optimize for the case where one user can saturate a 100 Mbit pipe for hours.

These are not adjacent products. They have opposite incentives at almost every layer:

• Capacity per user. A privacy tool can budget capacity assuming the average session is small. An overlay network has to assume the average session is enormous and price accordingly.
• Gateway-level abuse. A bulk-download network expects a steady flow of DMCA notices and abuse reports against gateway IPs and is staffed to triage them. A privacy tool that processed bulk download would see the same volume of complaints without the staffing or business model to absorb them.
• Shared blocklisting. Gateway IPs that show up in BitTorrent swarms get listed in tracker blocklists and in commercial threat feeds. Once that happens, every user (including the ones doing nothing remotely close to P2P) gets the same gateway IP flagged, which degrades everyone’s connection quality on the open web.

A consumer VPN that tries to serve both audiences usually ends up serving the bulk-download audience well and the everyday-browsing audience badly. We picked a side.

TuxlerVPN Mobile picks a side

TuxlerVPN Mobile is built and operated as a privacy tool for everyday browsing on Android. Concretely:

• Mobile-first. The product is an Android app today. There is no desktop client. The protocol choices and MTU defaults (discussed in How WireGuard works on Android) are tuned for mobile.
• Affordable consumer pricing. Premium is $5.99/month via Google Play, with a 30-day money-back guarantee. There is no annual plan and no free trial, as documented in Subscription Terms. That price assumes a normal consumer-browsing session profile.
• No P2P, by policy. Peer-to-peer file sharing and torrenting are not supported, regardless of whether the underlying content is lawful. P2P traffic patterns are subject to traffic shaping or termination. Source: Supported & Prohibited Use Cases and AUP §2.5, §2.6.

The “regardless of whether the underlying content is lawful” clause is intentional. The reason is not a moral judgment about your file. It is that the traffic pattern itself (long-lived, high-throughput, many-peer) is what the network was not built for, and what its capacity model and gateway hygiene cannot absorb.

What this means for you in practice

The trade-off has visible consequences if you actually use the service:

• Steady-state connection quality. Because the gateway capacity is not absorbed by long-lived bulk sessions, your short HTTPS sessions tend to feel responsive. Page loads are not competing with someone else’s 40-hour download.
• Less shared blocklisting at gateways. Gateway IPs that do not show up in P2P swarms tend to stay off tracker blocklists and commercial threat feeds. That keeps the gateway IP usable for ordinary web traffic without constant CAPTCHA challenges or “suspicious traffic from your network” prompts.
• Fewer ToS minefields. A clear “no P2P, no high-volume abuse” stance means the line between supported and prohibited activity is short and legible. The full list lives in Supported & Prohibited Use Cases and the Acceptable Use Policy.

The cost is real and worth naming: if your specific need is “high-throughput torrenting,” our network is not built for that and our policy will not change to accommodate it. We would rather be honest about that than have you pay $5.99/month for a tool that will throttle or terminate the workload you actually came for.

What to use instead if you want to torrent

If your intended use is bulk P2P, the category you are looking for is “P2P-permissive consumer VPN with port forwarding.” That is a different product category from ours. Pick a provider that explicitly lists P2P as supported, and read their abuse-handling and traffic-shaping language carefully. The honest test is whether the provider lists P2P in its supported-uses page in the same level of detail we list our prohibited-uses page.

Whichever provider you pick, two things are worth checking: whether the provider retains connection metadata that could later identify you in a torrent swarm, and whether the gateway IPs they assign you are likely to land you on tracker blocklists for everyone else who shares them.

FAQ

Is torrenting illegal?

That depends entirely on the file and on the jurisdiction. Our policy is not a statement about legality. It is a statement that the traffic pattern is not what our network is built or budgeted for, regardless of what the file is.

What happens if I try to torrent through TuxlerVPN Mobile anyway?

P2P traffic patterns are subject to traffic shaping or termination at the gateway level, as documented in Supported & Prohibited Use Cases. Repeat or large-scale violations can trigger termination per the AUP §2.5, §2.6.

Why not just charge more and allow it?

Because the second-order effects (gateway-IP blocklisting, sustained DMCA workload, capacity contention) would degrade the product for the audience we built it for. The right answer is not “everything for everyone” but “do one workload well.”

Where can I see the full supported and prohibited list?

In Supported & Prohibited Use Cases, with the legally binding version in the Acceptable Use Policy.