Acceptable Use Policy

1. Scope and acceptance

This Acceptable Use Policy ("AUP") governs all use of the ProxyFalcon network, including rotating residential, mobile 4G/LTE and static ISP access, every sub-account issued under a client account, and any access obtained through a reseller of ProxyFalcon services. ProxyFalcon is a brand operated by LeadifyCPA.

By purchasing, activating or using any ProxyFalcon credentials you accept this AUP on behalf of yourself and every person or system you allow to use those credentials. If you resell or share access, you are responsible for the conduct of your downstream users as if it were your own.

This policy exists for a practical reason as much as a legal one: our capacity is supplied by upstream networks that withdraw access when abuse is detected. Enforcing this policy protects every legitimate client on the network.

2. Permitted use

ProxyFalcon is provisioned for a deliberately narrow set of workloads. Permitted use is limited to the following categories, conducted against publicly accessible content:

• Ad verification and creative compliance — loading your own offers, creatives and landing pages from a target geography to confirm correct rendering, redirects and compliance.
• Geo-targeted SERP and landing page monitoring — observing publicly returned search results and public landing pages from a given location.
• Competitor and market research on publicly available ad libraries — reviewing publicly published advertising and creative material.
• Brand protection — identifying unauthorised use of your offers, trademarks and creative assets on public pages.
• Public web data collection for campaign research — collecting publicly available page data at a considerate request rate.

If your intended use is not clearly inside one of these categories, you must describe it to us before purchase and receive written confirmation. Use outside these categories is a breach of this AUP even if it is not specifically listed in Section 3.

3. Prohibited activities

The following are strictly prohibited on the ProxyFalcon network. This list is illustrative, not exhaustive.

3.1 Account and authentication abuse

• Automated creation, registration or verification of accounts on any platform.
• Automated login, session establishment or authentication of any kind, including against your own accounts.
• Credential stuffing, password spraying, brute-force attempts, or the testing of stolen or leaked credential lists.
• Bypassing, defeating or automating the solving of authentication challenges, two-factor prompts or human verification systems.

3.2 Advertising and payment fraud

• Click fraud, impression fraud, conversion fraud, cookie stuffing, forced clicks or any manipulation of advertising or affiliate metrics.
• Generating traffic intended to appear organic or human when it is automated.
• Carding, card testing, gift-card or voucher enumeration, and any use of stolen payment instruments.
• Creating, testing or distributing cloaked pages designed to deceive an advertising network's review systems.

3.3 Messaging and spam

• Sending unsolicited email, SMS, direct messages, comments, form submissions or contact-form traffic.
• Connecting to SMTP, IMAP, POP3 or any other mail transport service.
• Automated posting, mass account interaction or engagement farming on social platforms.

3.4 Security and infrastructure abuse

• Port scanning, vulnerability scanning, fuzzing or penetration testing of systems you do not own and are not contractually authorised to test.
• Denial-of-service traffic, amplification, or any volumetric attack.
• Distributing malware, exploit kits, phishing pages or command-and-control traffic.
• Attempting to identify, deanonymise, contact or interfere with the peers, devices or subscribers whose connections make up the network.
• Reselling, sublicensing or re-routing ProxyFalcon capacity through a public or shared proxy, VPN or gateway service without a written reseller agreement.

3.5 Content and legal violations

• Accessing, distributing or facilitating child sexual abuse material, which is reported to the relevant authorities without exception or notice.
• Copyright infringement, torrenting, media piracy and unauthorised redistribution of licensed content.
• Streaming-service access, sneaker and ticket checkout automation, and limited-release purchase automation.
• Harassment, stalking, doxxing, threats, or the collection of personal data about identifiable individuals without a lawful basis.
• Any activity unlawful in your jurisdiction, in the jurisdiction of the exit IP, or in the jurisdiction of the target system.

4. Prohibited target categories

Regardless of your stated purpose, ProxyFalcon traffic must never be directed at the following categories of destination. Requests to these destinations may be blocked at the gateway and will trigger review of your account.

• Login, authentication and session endpoints — sign-in pages, OAuth and SSO flows, token endpoints, password-reset flows, and account-recovery systems on any platform.
• Financial institutions and payment systems — banks, credit unions, brokerages, card networks, payment processors, payment gateways, remittance services, lenders, insurers and cryptocurrency exchanges.
• Government and public-sector services — tax, immigration, visa, customs, licensing, court, law-enforcement, electoral and municipal systems, at any level of government.
• Healthcare systems — patient portals, hospital and clinic systems, pharmacy and prescription services, insurance claim portals, and any system holding medical records.
• Mail and messaging servers — SMTP, IMAP, POP3 and webmail interfaces, SMS gateways and messaging APIs.
• Children's services and platforms — services directed primarily at minors, including school portals and children's social platforms.
• Critical infrastructure and internal systems — utility control systems, transport operations systems, and private corporate systems you are not authorised to access.

5. Technical conduct requirements

Even for permitted purposes, you must operate responsibly:

• Request rate. Keep concurrency and request rates at a level that does not degrade the target service. Back off on 429 and 5xx responses rather than retrying aggressively.
• Robots and terms. You are responsible for your own compliance with the terms of service and published crawling directives of the sites you access.
• Personal data. Do not collect personal data through the network without a lawful basis, and never collect special-category data.
• Credential hygiene. Keep your credentials confidential, rotate them if exposed, and use IP allowlisting where practical. You are responsible for all traffic on your sub-accounts, including traffic caused by leaked credentials.
• Accurate disclosure. Your stated use case at verification must remain accurate. If your workload changes materially, tell us before you change it.

6. Enforcement and consequences

We monitor the network for policy violations using aggregate signals, destination categories, upstream abuse notifications and third-party reports. We do not need to prove intent to act on a violation.

6.1 Immediate suspension

Where a violation is detected or credibly reported, access to the affected sub-account or the entire client account is suspended immediately and without prior notice. Suspension carries no refund of remaining bandwidth, and remaining balance is forfeited where the violation falls into a serious category.

6.2 Serious categories — permanent termination

The following result in permanent termination, forfeiture of all remaining balance, a bar on future accounts, and reporting to our upstream provider and, where applicable, to law enforcement: credential attacks; fraud against advertising or payment systems; traffic directed at financial, government, healthcare or authentication endpoints; malware or phishing distribution; denial-of-service activity; and child sexual abuse material.

6.3 Lesser violations

For a first, clearly unintentional and low-impact violation — for example an excessive request rate or a misconfigured target list — we may instead issue a written warning and require a documented remediation before access is restored. This is discretionary and is not available where a serious category is involved.

6.4 Cooperation and disclosure

We cooperate with our upstream network providers and with lawful requests from competent authorities. This may include disclosing your account identity, verification information, connection metadata and destination information associated with a reported violation. We may also share abuse indicators with upstream providers to prevent recurrence.

7. Reporting abuse

If you believe ProxyFalcon traffic has been used against your systems or in violation of this policy, report it and we will act.

• Where to send it: media@leadifycpa.com with ABUSE REPORT in the subject line.
• What to include: the exit IP address, timestamps with time zone, the targeted hostname or endpoint, request volume, and any log excerpts or headers you can share.
• Our commitment: reports are triaged and actioned within 24 hours of receipt. Actioning means we identify the responsible sub-account and suspend or restrict it where the report is substantiated.
• Follow-up: we confirm to the reporter what action was taken. We do not disclose client identity to reporters except where legally required.

Urgent reports involving active attacks, fraud or illegal content are prioritised ahead of the standard queue.

8. Upstream provider policies

ProxyFalcon capacity is supplied by upstream residential and mobile network providers. Your use of ProxyFalcon is subject to those providers' acceptable use policies in addition to this one, and the stricter requirement always applies.

This means an upstream provider can require us to restrict or terminate your access, or to block a destination category, and we will comply. Where we are notified of a new upstream restriction that affects you, we will pass it on as soon as we are permitted to. Continued use after such notice is your acceptance of the change.

9. Changes to this policy

We may update this AUP as the service, the threat landscape or our upstream obligations change. The current version is always published on this page with the "Last updated" date at the top. Material changes are communicated to active clients by email. Continued use of the service after a change constitutes acceptance.

Questions about whether a specific workload is permitted should be sent to media@leadifycpa.com before you begin it. We would rather answer a question than enforce a suspension.