PROXYWING ACCEPTABLE USE POLICY

1 Purpose and application

1.1. This Acceptable Use Policy (the “Policy” or “AUP”) forms part of the Terms of Service (TOS) between Travchis LLC (the “Company” or “ProxyWing”) and the Customer. It governs use of the Company's proxies, VPN services, dashboard, API, extensions, free testing utilities, and other tools, subject to their valid acceptance under the TOS. Terms have the meanings given in the TOS.

1.2. The Customer must comply with applicable law, third-party rights, the restrictions of the purchased product, and this Policy. The Customer is responsible for invited users' actions, the automation they use, and, within the scope of the reseller agreement, end customers. A prohibition also extends to organizing, attempting, knowingly assisting, or providing access for the prohibited activity.

1.3. The availability of a technical feature does not authorize every possible use of it. The sale of a proxy does not grant the target resource owner's permission, override access restrictions, or guarantee that a particular data collection activity is permitted. Company approval of a use case does not replace necessary third-party rights and permissions.

2 Permitted use cases

2.1. Subject to Sections 3–7, the services may be used to analyze publicly available prices and product selections, monitor search results, verify advertising placements without artificially inflating metrics, protect brands, test localized presentation of the Customer's own websites, research publicly available business information, and lawfully automate permitted workflows.

2.2. Use of a VPN, mobile proxy, or other proxy for lawful network access, gaming, or viewing content is permitted within the Customer's rights and the product's restrictions. This does not authorize circumvention of paywalls, sanctions, or territorial licensing restrictions contrary to applicable law, or any other activity prohibited by this Policy.

2.3. The Customer must obtain advance approval for a non-standard use case involving increased load, resale, or permission under Section 5. The approval must expressly describe the permitted use case and restrictions in a ticket, email, or another official channel that creates a record. Permission cannot be inferred from a lack of response, the sale of a package, or assistance with connection.

3 Automated data collection and use

3.1. Automated collection of publicly available information is permitted where there is a lawful basis, the necessary rights have been obtained, and the source's restrictions are respected. Public availability does not mean that copyright, database rights, or personal data protection requirements do not apply.

3.2. Automated collection, export, extraction, and accumulation of non-public information are prohibited, including information behind authentication or a paywall, information in a closed group, private correspondence, and private profiles. This prohibition applies even if the Customer has an account or the resource owner's permission. Ordinary lawful human access to one's own account, correspondence, or materials one is entitled to access does not, by itself, constitute prohibited automated collection. This exception does not authorize bulk export of non-public data, SMTP, prohibited transactions, or other activities prohibited by this Policy. Obtaining other persons' sessions, passwords, or tokens, using stolen data, and circumventing access controls are prohibited.

3.3. The services must not be used to circumvent robots.txt directives, API restrictions, established request limits, or other access restrictions. This is an independent contractual restriction that applies alongside the law and the target resource's terms. A permitted use case under Section 2 does not create an exception to this prohibition.

3.4. Ordinary address rotation, browser automation, and the technical ability to obtain a response do not independently authorize circumvention of the source's protections. The restrictions in Section 3.3 apply; separate Company approval does not replace the target owner's permission.

3.5. Collecting, combining, selling, or disclosing personal data without the necessary grounds and notices, creating databases for harassment or unlawful profiling, and extracting other persons' passwords, payment secrets, or documents for fraud are prohibited. A lawful source does not, by itself, make subsequent use lawful.

3.6. Targeted collection and creation of datasets containing special categories of personal data, biometric data used for identification, health information, information about intimate life or criminal convictions, or children's data are prohibited. The incidental appearance of such data in a permitted public data stream does not authorize its targeted extraction, combination, or distribution. The Customer must stop the relevant processing and take the measures required by law.

3.7. The Customer is responsible for determining a lawful retention period for the data they collect, safeguarding it, and complying with applicable data subject requests. If acting on behalf of another party, the Customer must obtain the necessary permissions to engage ProxyWing and other parties involved in the processing.

4 Activities prohibited without exception

4.1. Unauthorized access, password guessing, credential stuffing, use of stolen accounts, session hijacking, bypassing authentication, and exploitation of vulnerabilities without authority are prohibited. The services must not be used to access internal addresses, cloud environment metadata, or management infrastructure unless that access has been specifically granted.

4.2. DoS and DDoS attacks, network flooding, botnets, and distribution or control of malware, ransomware, data-stealing software, or other tools used to cause harm are prohibited. The stability of third-party resources and ProxyWing infrastructure must not be disrupted.

4.3. Phishing, financial and payment fraud, identity theft, forged documents, unauthorized transactions, fraudulent chargebacks, money laundering, and deception of users are prohibited. Impersonating another person or organization is prohibited where it infringes the law or another party's rights.

4.4. Child sexual exploitation, child sexual abuse material, involving minors in exploitation, human trafficking, terrorist activities and their financing, credible threats of violence, unlawful stalking or harassment, and disclosure of personal information with intent to cause harm are prohibited.

4.5. Distribution of pirated materials, unlawful circumvention of digital rights management (DRM) or paywalls, and infringement of copyright, trademarks, database rights, trade secrets, or privacy rights are prohibited. The services must not be used for unlawful trade or distribution of prohibited goods or services.

4.6. The following are prohibited: spam and unsolicited bulk messages or mailings, regardless of channel; fake reviews, artificial advertising clicks, fabricated votes or engagement metrics; and creation of accounts for fraud or to circumvent platform blocks, quotas, promotional restrictions, or other limitations. Managing multiple accounts lawfully held by the Customer does not exempt the Customer from these prohibitions.

4.7. Participating in polls, completing surveys, or automating either through the services is prohibited, including paid surveys and manipulation of results. Analyzing already published research results does not, by itself, constitute survey participation if Section 3 is complied with.

4.8. Automated ticket purchases and other purchases that circumvent established quantity limits, queues, identity requirements, or prohibitions under applicable law are prohibited. Lawful purchasing automation without such circumvention remains subject to the general rules and the target resource's terms.

4.9. Interfering with the platform, bypassing billing or traffic metering, manipulating discounts, exploiting balance errors, or circumventing API or connection limits through multiple accounts or distributed sources is prohibited. A discovered vulnerability must be reported to the Company without further exploitation or disclosure of other parties' data.

4.10. Unrestricted access must not be provided to an indeterminate group of persons through an open proxy, Tor exit node, public gateway, or the Customer's own VPN service. Restricted-access resale is permitted only within an approved program under Section 8 and does not authorize an open relay.

4.11. ProxyWing services and IP addresses must not be connected to bandwidth monetization or resale systems, proxyware, bandwidth-sharing, DePIN, or other networks in which third parties use those resources as their own exit nodes or a participant is rewarded for making them available. Installing the corresponding agents or providing access credentials to those networks is prohibited, including indirect connection through the Customer's own server or software. Approval of ordinary restricted-access resale under Section 8 does not, by itself, authorize such activity.

5 Specific categories of use

5.1. SMTP traffic is prohibited. IMAP support in a particular product permits ordinary synchronization of the Customer's own email and does not authorize spam, testing stolen credentials, or extracting mailbox contents into separate datasets. Such ordinary access is subject to Section 3.2 and the product's technical capabilities.

5.2. Security testing of the Customer's own systems or a commissioning client's systems is permitted after prior written approval from ProxyWing through an official channel, provided there is authorization from the target owner and documented permission for the specific methods. The addresses, timing, load, and scope of testing must be agreed. DoS and DDoS attacks, interference with unrelated systems, extraction of other parties' data, and breaches of restrictions outside the owner's permission are prohibited. Testing ProxyWing infrastructure requires the Company's separate express permission. Obtaining technical responses and the tester's own test data strictly within an authorized test does not constitute a separate automated collection activity under Section 3.2; this does not authorize bulk export of non-public data.

5.3. The services must not be used to distribute pornographic material, engage in sexual exploitation, provide sexual services, or provide services facilitating such activities. Betting, wagering with bookmakers, gambling, casinos, and lotteries involving money or anything of value as a stake are prohibited, including access to, automation, servicing, and promotion of those activities, regardless of licensing or legality in the Customer's country. Ordinary video games without wagering are not, by themselves, covered by this prohibition; all other restrictions remain in effect.

5.4. The services must not be used for anonymous access to cryptocurrency exchanges, trading platforms, or currency exchange platforms, or for anonymous transactions through them, including concealing a participant or their location to circumvent identification, sanctions, or territorial restrictions. A proxy does not authorize circumvention of KYC, anti-money laundering (AML) requirements, or a financial platform's rules. Mining through the services, fraudulent investment schemes, and unlawful financial or payment services are also prohibited. Analysis of publicly available market quotations is permitted within Section 3; paying for ProxyWing services with cryptocurrency through an authorized channel is not, by itself, prohibited. Lawful use of an identified account is assessed under these restrictions and is not treated as anonymous merely because a proxy is used.

5.5. The Company may reject a use case that creates an unacceptable legal, payment, or network risk. Changes to the general policy on permitted use cases are made under the TOS; lawful obligations relating to a paid service that becomes unavailable are addressed under the TOS, rather than by arbitrary retention of payment.

6 Sanctions and access restrictions

6.1. Use that violates sanctions, export restrictions, or other mandatory restrictions applicable to the Company or the relevant transaction is prohibited. As a US company, Travchis LLC is subject to applicable US requirements; mandatory requirements of other relevant jurisdictions may also apply.

6.2. The Customer must not conceal identity, location, beneficial ownership, the end user, or the purpose of the service to circumvent such restrictions. The Customer must provide necessary information upon a justified request. The Company may refuse or restrict service or stop a prohibited transaction, including a financial settlement that is itself prohibited by law.

6.3. This Policy does not automatically prohibit all transactions involving nationals of a particular country. The applicability of restrictions depends on the relevant regime, person, territory, and transaction. Additional commercial restrictions imposed by the Company may be published separately.

6.4. The Company may block certain ports, addresses, and categories of targets for security reasons, mandatory compliance, or network requirements. A full list of technical safeguards is not published; the Customer may ask support about access to a necessary port before purchase. Unblocking is not promised. Material known product limitations must be disclosed before sale to the extent required by law.

7 Traffic and network protection

7.1. Datacenter and ISP proxies are subject to the FUP in the TOS: 100 GB per IP for each 30-day period, pooled across the IPs in a single package (order). For N IPs, the total allowance is 100 × N GB separately for inbound traffic and for outbound traffic. Usage by all IPs in the package is added together within the relevant direction; the directions are not added to each other. For 5 IPs, the threshold is 500 GB in either direction; 300 GB inbound and 300 GB outbound do not reach it. Allowances cannot be transferred between separate orders; replacing an IP does not reset package usage. Automatic warnings that usage is approaching the limit are not currently provided. One-day plans are not offered. A hard upper limit of 2,500 simultaneous connections applies per IP. During increased load or a threat to stability or security, the limit may be temporarily reduced without advance notice for the period necessary to protect the network; availability of all 2,500 connections is not guaranteed.

7.2. Reaching the FUP threshold or unusual load may result in a request for a description of the use case, speed and connection limits, package suspension, or an offer of additional volume at an agreed price. The Company may intervene before the allowance is exceeded if a particular traffic stream threatens network stability or other customers. No universal minimum speed is guaranteed while restrictions apply.

7.3. The scope of a restriction depends on the risk and the technical ability to isolate the load. If an offending IP is part of a package, the restriction may affect the entire package. Other packages retain access unless there are grounds to extend the measure to them or to the entire account. The Customer must not resume prohibited traffic through another package or account.

7.4. The Company may request an explanation of the load and necessary corrective action. Refusal to cooperate or a continuing violation may lead to termination of affected services. High-load use may be agreed in advance on special terms; the Company is not obliged to accept every proposed use case.

8 Resale

8.1. Resale requires prior written approval from Travchis LLC through the official channels in Section 2.5 of the TOS and must remain within the approved terms. A separate signed agreement is required if specified as part of the approval. The reseller must communicate restrictions at least as strict as the AUP to end customers and ensure that violations stop. White-label arrangements do not relieve the reseller of these obligations or authorize open relays or prohibited traffic monetization networks.

8.2. When a complaint is received, the Company normally works with the reseller, who contacts the end customer and reports the outcome. The Company retains the right to restrict an affected service immediately where there is a threat. A reseller must not promise exceptions, unlimited anonymity, freedom from blocking, or permission for unlawful activities on behalf of ProxyWing.

9 Complaint review and enforcement

9.1. Complaints are accepted through the official website contacts and ticket system. Reports should include the IP, date and time with time zone, purpose of the report, nature of the activity, and available evidence. Do not send other parties' passwords, payment secrets, or unlawful content; a safe description and available identifiers are sufficient. Incomplete information does not preclude review, but may make it harder to establish what occurred.

9.2. The Company assesses the credibility of the complaint, available technical information, and the Customer's response. A third-party complaint is not automatically proof of a violation. The Company may require a description of the use case, evidence of rights, and cessation of specified activities. The right to investigate does not mean continuous inspection of the contents of every connection or retention of an unlimited volume of traffic.

9.3. Information is processed for security and investigation on an applicable lawful basis, subject to applicable law and the DPA within its scope. The Company does not disclose details of its safeguards where doing so creates a risk, but does not use confidentiality to override mandatory notice of processing and Customer rights.

9.4. Measures include warnings, feature restrictions, key revocation, IP or order blocking, temporary suspension, and account termination. The Company may immediately apply a necessary measure without three prior warnings in the event of a material violation, reasonable suspicion of fraud, a serious threat, a mandatory requirement, or a material legal, financial, reputational, or technical risk under Section 12.1 of the TOS. The examples are not exhaustive; reasonable grounds and a connection between the measure and the risk are required. An honest negative review or lawful complaint does not, by itself, justify a restriction. Notice, review, the scope of the measure, and financial settlement are governed by Section 12 of the TOS.

9.5. The Company provides notice of the restriction and an explanation of its grounds to the extent it can be provided under Section 12.2 of the TOS, subject to the exceptions there for legal compliance, security, and investigation. The deadline for Customer action is set according to urgency. Requests are handled under Section 11.1 of the TOS, with mandatory deadlines taking precedence. Decisions are made by a person duly authorized by the Company.

9.6. During review, the Company may restrict affected services and disputed funds or, where there is a substantiated risk to the entire account, access to the account as a whole. Repeated violations, refusal to cooperate, and circumvention of a measure are taken into account when deciding further action. Final financial settlement, permissible set-off, and release of unaffected funds are governed by the TOS; blocking does not, by itself, mean forfeiture of the entire balance as a penalty.

9.7. The Customer may request manual review through an official ticket, identifying the decision, reasons for disagreement, and new information. An authorized person reviews the request, corrects any established error, and communicates the outcome to the extent permitted. Restricting chat because of abuse does not prevent lawful challenge of a decision.

9.8. The Company complies with lawful requirements of competent authorities and reviews complaints from rights holders. Data disclosure, preservation of evidence, and notification of the Customer are carried out to the extent permitted or required by applicable law. A traffic transmission service does not control removal of materials from independent target websites.

10 Amendments and contact details

10.1. Amendments to the AUP, email notice, and acceptance of new terms through continued use are governed by Section 17 of the TOS, including its notice periods, right to decline, and mandatory exceptions. A permanent change to permitted use cases follows that procedure. Urgent protective action does not require waiting for a new version; financial settlement for a terminated paid service is governed by Section 12 of the TOS.

10.2. The Company is Travchis LLC, Delaware, United States, with an address at 131 Continental Dr, Suite 305, Newark, DE 19713, United States. Reports of abuse and violations of this Policy are accepted at abuse@proxywing.com; legal notices and claims are accepted at legal@proxywing.com. To assist review, where possible identify the affected IP or product, the date and time with time zone, the violation, and supporting materials, without sending unnecessary personal data or access secrets. An incomplete report does not, by itself, preclude review of the information available. Additional contact methods are available on the contact page and through the ticket system. The registered agent is Legalinc Corporate Services Inc., 131 Continental Dr, Suite 305, Newark, DE 19713, United States; the purpose of that address and the rules for legal communications are set out in Section 19 of the TOS.