FAQ

No. Peers join through partner SDKs that disclose the arrangement in plain language, get paid for the bandwidth they contribute, and can leave from a single toggle. Partners are audited monthly and anything that buries the disclosure is cut from the pool and not paid out. The slogan stays because it is funnier than a compliance page.

138.3 million unique residential IPs seen in a rolling 30 days, across 195 countries, with roughly 36.4 million online on an average day. The largest pools are the United States, Germany, the United Kingdom and Japan.

No. One product, done properly. No ISP plans, no datacenter ranges, no mobile. If you need those we will point you at someone decent rather than sell you something we run badly.

Not free, but a $3 test top up is available in the panel once an account has one confirmed payment. Trial abuse got out of hand, which is unfair on the honest majority.

HTTP, HTTPS via CONNECT, and SOCKS5. The gateway listens on 8080 for HTTP and 1080 for SOCKS5.

Dash separated flags on the username: -country-jp, -state-ny, -city-osaka, -asn-3320. Combine them freely.

A combination with no live peers returns a 502 with a readable reason rather than hanging, so a typo in a city name fails loudly instead of silently costing you an hour.

Up to 120 minutes, for as long as that peer stays online. If the peer drops, the session ID re-binds to another IP in the same location instead of failing the request.

No. No cap on concurrent connections, no cap per account, and no limit on how fast you open them. Run as many threads as your own hardware will carry.

The one thing a node will cut off is repeated bad credentials: twenty refusals from an address inside a minute and it stops answering that address for a while. Correct credentials are never rate limited.

REST, bearer token, JSON. Endpoint generation, usage statistics, sub user management and invoice creation. Documented in the client area under Developers.

Yes, up to 20 whitelisted IPs per account, from the panel or POST /v1/whitelist. It works alongside user and password auth.

Yes. The rate is fixed when you buy, so a balance keeps the price you paid for it even if the rate card moves later.

Card processors avoid proxy companies and chargeback fraud kills small providers. Bitcoin and Monero keep the rate card honest. Nothing else is planned.

Overpayment is credited to your balance automatically. Underpayment leaves the invoice open, so send the difference to the same address before it expires and it settles.

Consumed bandwidth is not refundable. Unused GB converts back to account credit at any time, and if the network genuinely did not work for you inside your first 24 hours we credit the whole top up.

Never. It sits on the account until you spend it, even if you disappear for a year.

Account email, password hash, balance, aggregate GB counters and invoice records. No request logs, no destination hostnames, no payloads. Full detail in the Privacy Policy.

Yes. Panel, gateway and payment flow all work over Tor. We do not block exit nodes and the panel does not require JavaScript to log in.

CSAM or anything involving minors, spam, phishing, carding, credential stuffing, malware distribution and C2, DDoS, and attacks on critical infrastructure. Accounts doing these are terminated without a refund. Full list in the Terms.

File a report on the abuse page with a UTC timestamp and the target. A source IP plus a timestamp maps to an account internally and we act on valid reports the same day.

Panel ticket, support@femboyproxies.com, or Telegram. Median first reply is under twenty minutes, from someone who can actually fix the problem.