Quick answer
When can a traffic plan be credited back?
As of 15 October 2026, LocalSERP Proxy credits a traffic plan within 72 hours of purchase when less than 20% and no more than 1 GB is used. An unfixable service fault has separate rules. These are balance credits for no KYC, crypto purchases; top-ups are paid back only where law requires.
The complete product rule
Within 72 hours of purchase, a residential or rotating-mobile plan is credited back to your balance if you used less than 20% of its traffic and no more than 1 GB. A plan that does not work, and that support cannot fix within 24 hours, is credited back in full. Top-ups are credited to your balance and are not paid back, except where the law requires it. Dedicated ports: within 24 hours of delivery (2 hours for a 1-day port), the port is credited back to your balance in full if it does not work and we cannot fix or replace it, or if it has carried less than 500 MB. A port we cannot deliver within 24 hours is credited back in full. If a port stops working later and support cannot fix it within 24 hours, the lost days are credited back. Top-ups are not paid back, except where the law requires it.
Choose the rule that fits your purchase
| Situation | Window and outcome |
|---|---|
| Residential or rotating-mobile evaluation | Request within 72 hours of purchase; less than 20% of the traffic and no more than 1 GB used. Plan price credited to balance. |
| Traffic plan that does not work | Support cannot fix the fault within 24 hours: plan price credited in full. |
| Dedicated port, short evaluation | Within 24 hours of delivery, or 2 hours for a 1-day port; less than 500 MB carried: full balance credit. |
| Dedicated port that does not work at delivery | Within the product window, when we cannot fix or replace it: full balance credit. |
| Port not delivered | Not delivered within 24 hours: full price back to balance. |
| Later dedicated-port fault | Support cannot fix within 24 hours: lost days credited back. |
| Unused top-up balance | Not paid back, except where the law requires it. |
| Rights required by law | Mandatory remedies remain available; contact support about your circumstances. |
How do I request a credit for a local test?
Write to [email protected] and identify the product, plan or order reference, purchase time and time zone. Describe the check you attempted and the error you received. If it concerns a city, include the location requested and the location reported by the lookup and destination. Redact proxy passwords, API keys and account numbers. A short reproducible description helps support determine whether the issue lies in authentication, the gateway, current availability or the target’s own decision.
How do the two usage limits work together?
For a traffic-plan evaluation, both limits apply: less than one fifth of that plan’s volume, and no more than one gigabyte. Using 20% or more of the plan, or more than 1 GB, removes this evaluation route; it does not change the separate rule for a faulty plan that support cannot repair. Use the dashboard counter before planning a long assessment. Usage counts all data sent and received through the proxy (upload and download, headers included). 1 GB = 1,000,000,000 bytes. Connection attempts that fail before reaching the target are not counted. A screenshot or page count alone cannot show how many billable bytes were transferred.
Why is the remedy described as a balance credit?
A balance credit restores value for another purchase on the account. It differs from a transfer back to the crypto address that funded the balance. Unused balance stays on your account and never expires, but it is not paid back, except where the law requires it. Keep that distinction in mind before making the minimum top-up of $25. Buying a small plan does not make the unused portion of a larger top-up withdrawable. Any payment-back obligation imposed by applicable law is handled as that obligation requires, rather than removed by this policy.
Which limitations should I assess before purchase?
Confirm the requested place and product scope first. Residential targeting can include a US city, state or ZIP, while the rotating mobile product is country-level. A selected exit cannot force a target to show a result, accept a session or use the same geolocation database. A sticky session is not a permanent address. If your project requires those stronger conditions, discuss the requirement before buying rather than treating it as an assumed feature of the plan.
How are missing payments handled?
A payment enquiry differs from a plan-credit request. Send the payment reference, coin, network, exact amount, send time and available TXID to support. The TXID is optional when reporting the transfer on the payment page, but can help locate a disputed transaction later. Do not send funds again just to force progress. Support cannot promise recovery of a transfer sent to an incorrect address or network. A wallet or exchange withdrawal fee is not traffic purchased from us.
What happens after support reviews the request?
Support checks the order, usage and reported fault against the product rule. Where a credit applies, it is made to the account balance. A repair or replacement can resolve a connection fault under the relevant rule. There is no promised blockchain-crediting schedule or live availability percentage on this page. Keep the original report and any response while the case is handled. Consult the privacy policy for record retention and the Acceptable Use Policy for access restrictions.