Provider Policies

Where the conditions are written

A topic does not need a separate document bearing its name to affect an order. A refund window might appear in the general terms, a traffic allowance on a product page, and an identity check in the access requirements for a particular network. A negotiated business agreement can add commitments that an ordinary dashboard purchase does not include.

The scope can also change within one provider's catalogue. Datacenter access, a residential pool, a dedicated mobile connection, and a managed scraping tool can have different approval, billing, and data-handling conditions. A statement about one product does not automatically describe the others. The relevant conditions are those attached to the selected product, plan, and purchase.

A trial is useful when it tests the service the customer will actually receive. Opening an IP-check page proves less than completing a real task on the intended website. A free sample from one country may also say little about a different country or product available after purchase.

Trial access can be free, paid, linked to a card, or arranged individually for a company. A temporary card hold is different from payment for a test. A money-back offer starts with a purchase and makes recovery of that payment conditional. None of these labels alone establishes whether a regular subscription will begin automatically.

For a static package, keeping the tested IPs can be a major benefit. If a separate sample is replaced, the customer receives addresses that have not yet passed the same tests. For a rotating pool, the useful continuity may instead be the same product, locations, and connection settings. An unchanged gateway does not promise an unchanged exit IP.

A refund deadline is only one part of refund eligibility. A customer can apply within the stated period and still exceed a traffic allowance, be requesting a refund for an excluded renewal, or have bought a non-refundable test package.

The reason for the request matters too. A proxy that cannot establish connections presents a different issue from an IP rejected by one store. The latter may qualify under a satisfaction guarantee or an explicit promise about that store, while a policy covering network faults alone may treat it differently. “The service did not complete my task” and “the provider failed to deliver the agreed service” need not describe the same situation.

The outcome can be a full refund, a partial amount, account credit, replacement addresses, or restored access. These are different remedies. Money credited to a dashboard cannot necessarily be withdrawn, and cancelling a subscription may stop the next renewal without reversing an earlier charge.

Changing the IP shown to websites does not make the buyer unknown to the proxy company. Know Your Customer, or KYC, is the provider's process for identifying a customer and deciding whether to grant access to the requested service.

The process can range from confirming contact details to submitting an identity document and a selfie. Business customers may be asked for company information or an explanation of the project. A check can occur before activation, after a payment concern, or when a customer requests additional access. Passing one check does not necessarily complete the others.

Identity and intended use are separate questions. A person with valid documents can still be ineligible for a company-only product, while an approved customer can be refused permission for a prohibited task. Payment also does not automatically settle access: an account balance and approval to use a particular network can be separate states.

Unlimited traffic does not by itself promise unlimited speed or parallel work. A Fair Use Policy, or FUP, governs resource consumption and the provider's response when usage exceeds the plan's allowance or starts affecting the network.

Imagine a customer running a permitted price-monitoring job across a large IP package. Each request is ordinary, but together the workers generate sustained traffic far above the workload the plan supports. Depending on the service, the result can be fewer simultaneous connections, a lower transfer rate, additional usage charges, or a request to move to a larger plan.

The allowance may belong to one IP, an order, or the whole account. That distinction changes what the customer can do with a large package. Replacing an address does not create a new account allowance, and buying more IPs does not necessarily cancel charges already incurred.

A fixed connection cap that applies from the first minute is also different from a restriction introduced after heavy consumption. Similar symptoms can have different causes.

The Acceptable Use Policy, or AUP, concerns what the customer does through the network. It can prohibit a task even when that task uses little traffic and the account is fully paid.

Advertising verification and fabricated paid clicks can use similar software but serve very different purposes. The same distinction separates authorized security testing from an attack on someone else's system. Policies can also govern resale, sharing accounts, repeated trial registrations, and access to data the customer is not permitted to collect.

An abuse complaint can arrive through the target website, a hosting company, or another network supplier. The provider may investigate, request an explanation, restrict part of the service, or suspend access. A complaint and a confirmed violation are separate events; the service's review process determines how it handles the case.

FUP and AUP therefore answer different questions. A permitted task can consume too many resources. A prohibited task can stay well below every traffic limit. Paying for a larger package resolves neither a prohibition nor missing authorization.

A proxy can hide the customer's IP from a website while leaving records with the provider. Those records may concern the account, payments, connections, or the content processed by a particular product. The phrase “no logs” needs a defined scope to explain which records are excluded.

An ordinary HTTPS tunnel keeps page contents encrypted between the customer's application and the destination. The proxy company can still handle connection information, such as a requested hostname, timing, and traffic volume. This gives the provider a different view from the one available when it inspects HTTPS or retrieves pages itself.

With a Scraping API or a provider-hosted browser, the service processes the task and the website's response. URLs, submitted options, cookies, or other supported inputs may contain commercially sensitive information. Technical access to those details does not establish that every request is stored or that employees routinely read it. Processing, storage, and staff access are separate questions.

IP sourcing explains whose addresses and connections make the proxy network possible, and how the provider obtains permission to use them. This affects both the origin of the service and its practical behavior.

Datacenter and ISP products can involve leased address ranges, rented servers, and agreements with network operators. Residential pools can route traffic through participant devices. Mobile access can come from smartphones in a distributed network or equipment operated with SIM cards. A provider may also buy access from a wholesale supplier.

These arrangements create different dependencies. A participant's phone can disappear from a pool, a leased range can be replaced when an agreement ends, and a modem farm depends on its carrier connections. The proxy seller, address holder, and hardware owner need not be the same company.

For participant devices, a clear opt-in, a disclosure buried in app terms, and use without permission describe very different origins. An IP checker identifying an address as residential cannot establish which of these applies.

An SLA defines a service commitment, its measurement, and the remedy if it is missed. The percentage alone does not explain what the customer can rely on.

A provider can measure the availability of its gateway while a particular exit IP or target website remains unavailable. Another agreement can cover specified addresses or successful requests under defined conditions. An initial support response and restoration of the service are also different commitments.

Timing can matter more to a customer than a monthly average. At 99.9% availability, a 30-day month permits 43 minutes and 12 seconds of counted downtime. A half-hour interruption can ruin a scheduled job while that monthly target is still met.

If there is a breach, compensation may take the form of service credit calculated from an eligible charge. That is different from reimbursement of the customer's business losses. A refund policy and an SLA can both concern money after a problem, but they define different grounds and calculations.

How the policies work together

A single purchase can move through several of these rules. A trial establishes that the chosen proxies work on a store. Payment starts the subscription, but residential approval may still be pending. Once access is granted, a larger production workload can meet a fair-use threshold. If the account is later suspended after a complaint, the AUP governs the activity review, while the refund terms determine how a repayment request is considered.

The distinction also prevents the wrong explanation for a failure. A successful identity check does not make a blocked website accessible. An unused balance does not establish refund eligibility. A technically reachable gateway does not establish that the customer's data-collection job succeeded.

Fixed limits on simultaneous connections, blocked websites and apps, and blocked ports describe the available capacity or destinations. They can implement a policy, but have their own technical scope. Detailed treatment belongs to the separate Proxy Usage Limits section of the knowledge base.

Provider policies make the boundaries of the purchase visible: what the customer is allowed to do, what information they entrust to the service, and what the service owes them. Understanding the relevant boundary makes the detailed article useful immediately, whether the question arises before payment or after something has gone wrong.