Refund Policy explains when a proxy purchase can be refunded and when it cannot. In short, eligibility is usually limited to a first order, a short window (3–14 days), and very low usage; crypto payments, trial fees, and consumed traffic are commonly excluded.
For a wider context across vendors, see provider policies. Before paying, always check the exact terms on the provider’s site.
What this refund policy covers
Refunds typically apply to the first purchase of a proxy service when the service does not meet the stated terms, within a short window and under low usage. Subsequent renewals or heavily used plans are usually excluded.
This page explains common industry patterns so you can set correct expectations before buying. We describe how providers handle subscription bundles, per-IP plans, and traffic-based products, when a request is valid, what evidence to attach, and the path to resolution. Always read the specific terms on the provider’s site before payment.
Eligibility by plan type
Refunds are most often available on subscriptions and per-IP bundles if usage stays below a small threshold. Pay-as-you-go traffic and one-time trial fees are commonly excluded.
Typical scope:
- Subscriptions and per-IP bundles: First purchase is usually eligible if requested within the window and under usage caps. Renewals are often non-refundable unless there is a documented service failure.
- Pay-as-you-go (per-GB): Traffic already consumed is rarely refundable.
- Add-ons (geo add-ons, extra ports, custom gateways): Often non-refundable unless the add-on itself is broken from the start.
Common refund windows (3–14 days)
Most providers offer a short refund window between 3 and 14 days starting from purchase or service delivery. Some also provide a 24-hour DOA window to report non-working proxies.
Timeframes you will see in practice:
- 24 hours: Dead-on-arrival checks for fresh allocations.
- 3–7 days: Typical money-back period for first-time subscribers.
- Up to 14 days: Upper bound seen at a minority of vendors, still subject to usage caps.
Usage caps (≤ 10–20% of quota or ≤ 1 GB)
Refund rights usually depend on low consumption. Passing the cap generally voids eligibility. Caps are defined as a percentage of quota or an absolute traffic ceiling.
Typical caps
| Plan type | Window example | Usage cap example |
| Per-IP subscription | 3–7 days | ≤ 10–20% of IPs used or tested |
| Per-GB subscription | 3–7 days | ≤ 1 GB total traffic |
| Pay-as-you-go traffic | Not offered | Consumed GB are non-refundable |
| Trial package | 24 hours to 3 days | Trial fees non-refundable |
Notes:
- Caps may combine metrics, for example ≤ 10% of ports and ≤ 1 GB total.
- Tests that hit rate limits, captchas, or bans still count toward usage unless the provider states otherwise.
Non-refundable cases
Crypto payments, trial fees, and charges after heavy use are the most common non-refundable scenarios.
Typical exclusions:
- Cryptocurrency payments: Marked final due to settlement irreversibility and fees.
- Trial or setup fees: Treated as non-refundable evaluation charges.
- Used traffic beyond caps: Exceeds “inspection” usage; no refunds.
- Non-first purchases: Renewals, plan upgrades, and top-ups commonly excluded unless the provider caused a clear outage.
Abuse, AUP breaches, and late requests
Violations of the Acceptable Use Policy void refund rights immediately. Requests made after the stated window are routinely declined.
Examples that forfeit eligibility:
- Fraud, spam, scanning, or prohibited automation.
- Chargeback threats or misuse of the dispute process.
- Requests opened after the deadline or without the required evidence.
DOA proxies and SLA exceptions
If the delivered proxies are dead on arrival or a provider-side fault prevents normal use, a refund or account credit is often approved when reported promptly with proof.
What usually qualifies:
- Fresh allocations that never authenticate or never pass a basic HTTP(S) request.
- Sustained provider-side outage documented by status pages or incident IDs.
- Misprovisioned plan (wrong protocol, wrong geo) not fixed in a reasonable time.
Credits vs full refunds
Many providers resolve service issues with account credits that you can use later; cash refunds are reserved for clear DOA or failure to deliver.
Common outcomes:
- Account credit: Granted for partial degradation, brief outages, or goodwill.
- Full refund: Granted for undelivered service, verified DOA, or statutory obligations where applicable.
- Partial refund: Granted when only part of the order is affected and usage occurred elsewhere.
How to file a refund
File a ticket in the billing or support portal within the allowed window, include evidence, and keep usage under the cap while the case is open.
A clean request template:
- Order details: Order ID, plan name, purchase time, payment method.
- Problem summary: One-line description (e.g., “all new IPs return 407”).
- Impact and scope: How many IPs/ports affected, which endpoints.
- Actions taken: What you tested and any provider guidance you followed.
- Requested remedy: Refund or credit.
Evidence to include
Provide specific artifacts that show the failure clearly and reproducibly. Lack of evidence is a common reason for denial.
Attach:
- Timestamps and time zone for each test.
- Command outputs (e.g., curl with -x), brief logs, and HTTP status codes.
- Configuration screenshots from your app or browser.
- Sample target URLs demonstrating the issue, with sensitive data redacted.
- Traceroute or DNS output if connectivity is in question.
Timeline and resolution path
Most cases are acknowledged within hours and resolved in 1–7 business days, depending on escalation.
What to expect:
- Triage: Support reviews evidence and may ask for one more test.
- Fix attempt: Replacements or reallocation are offered when appropriate.
- Decision: Credit or refund based on terms and your usage level.
- Escalation: If unresolved, ask for a billing escalation ticket and a written summary of findings.
Refund policy FAQ
Do I qualify if my targets block proxies?
Blocks by third-party targets generally do not qualify. Refunds cover provider-side failures, not target-site rules.
Can I get a refund after heavy testing?
Usually no. Usage above the cap is treated as acceptance of the service.
What about mixed results across IPs?
Providers may replace the bad subset or issue a partial credit if only a portion is affected and you reported early.
Are crypto payments refundable?
Commonly not. If a provider makes an exception, it is typically issued as account credit.
How long does it take to receive funds?
Credits are instant once approved. Card or PayPal refunds depend on the processor and may take several business days to appear.