Skip to content

Acceptable Use Policy

What you may and may not do with the network. Written so that an engineer can read it in five minutes and know where the lines are.

Effective date: 2026-11-03

1. Scope

This policy applies to all traffic sent through the ScalarData network by any account, proxy user, teammate or integration, whether it is paid for with a subscription, a GB pack, dollar credit or free credit. It is part of the Terms of Service. Not knowing that something was prohibited is not a defence; if you are unsure whether a use is allowed, ask us before you start.

2. Account integrity

  1. Do not resell access to the network unless you have a written reseller agreement with us. Proxy users exist so that your own team and integrations can be told apart, not so that third parties can use your account.
  2. Do not create additional accounts to evade a limit or a suspension.

3. Prohibited uses

You may not use the Service to do, attempt or assist any of the following:

  1. Fraud. Payment fraud, identity theft, ad fraud (including click and impression fraud), affiliate fraud, fake reviews, or creating accounts to deceive a platform or its users.
  2. Credential stuffing and account takeover. Testing stolen or guessed credentials, password spraying, brute-force attempts or any attempt to log in to an account that is not yours.
  3. Unauthorized access. Probing, scanning or exploiting systems without the written permission of their owner, including during penetration testing you have not been engaged to perform.
  4. Denial of service. Any traffic intended to degrade, overload or take down a target, whether or not it succeeds.
  5. Spam. Bulk unsolicited messages by email, SMS, comment, direct message or form submission, and mass account registration to support them.
  6. Child sexual abuse material. Accessing, distributing or hosting material that sexually exploits children. We report every instance to the relevant authority and preserve evidence for law enforcement.
  7. Harassment and surveillance of individuals. Stalking, doxxing, tracking or monitoring a specific person, or collecting personal data without a lawful basis.
  8. Malware and phishing. Distributing malicious software, hosting or driving traffic to phishing pages, or operating command-and-control infrastructure.
  9. Ban evasion. Getting around a suspension or ban that a platform has applied to you personally or to accounts you control.
  10. Sanctions violations. Using the Service from, or to reach, a country, entity or person subject to sanctions we are required to observe.
  11. Interfering with the network. Attacking the gateway or our upstream providers, or trying to identify the people behind exit IPs.

You may not send traffic to the following destinations either. The gateway does not detect these categories for you: sending traffic to them breaches this policy whether or not it gets through.

DestinationWhat it covers
Government, military and law-enforcement networksAny address space or domain operated by a government body, armed force or police service.
Banking, payment and crypto-exchange transaction flowsLogin, transfer and checkout endpoints of banks, card networks, payment processors and exchanges.
Healthcare providers and health insurersPatient portals, clinical systems and insurer member areas.
Critical infrastructureControl and management systems for energy, water, transport and telecom operators.
Schools and services for childrenLearning platforms, school administration systems and products aimed at minors.
Ticket sales and limited-release checkout flowsPurchase flows for event tickets and drops where automation deprives other people of access.
Phishing, malware and command-and-control hostsDestinations known to host phishing pages or malware, or to control infected machines.

If you have a legitimate need to reach one of these destinations (for example, a penetration test you have been engaged to run), contact us before you start. We will ask for written authorization from the owner of the target.

4. Blocked destinations

The gateway refuses private, loopback, link-local and other reserved addresses, hostnames that resolve only to them, local and intranet names, and ports 0, 25, 465, 587 and 2525. The list is applied automatically:

BlockedWhat it covers
Reserved addressesLoopback, private, link-local, shared (carrier-grade NAT), multicast and cloud metadata addresses in IPv4 and IPv6, however the address is spelled and whichever hostname points at it.
Local and intranet namesNames without a dot, localhost, and names under special-use or intranet suffixes such as .local, .internal, .lan and .home.arpa.
Outgoing mailSMTP ports 25, 465, 587 and 2525.
Networks that asked to be excludedAddress ranges whose operator asked us not to route to them, reached by address or by a hostname that resolves into them.

The gateway resolves every hostname itself and connects only to an address it checked, so a name that points at a private address is refused like the address. Requests to a blocked destination fail at the gateway with a specific error, and repeated attempts may lead us to close the account.

5. Technical conduct

  1. Keep request rates within what the target can reasonably absorb. Back off when you see errors instead of retrying in a tight loop.
  2. Do not use the network to get around a rate limit in a way that degrades the target for its other users.
  3. Give each integration its own proxy user so that traffic can be attributed and, if necessary, stopped without affecting the rest of your account.

6. Reporting abuse

If you believe traffic from our network is breaching this policy, write to [email protected] with the time in UTC, the target that was affected and, if you have them, the exit IP address or the session name the upstream provider reported. We acknowledge every report, match the time, destination and upstream session against our connection log (kept 30 days), act on it, and tell you the outcome. Network operators can also ask us to stop routing to their IP ranges; we block connections to those ranges, by address or by hostname.

7. Enforcement

  1. Depending on severity we may warn you or close the account. Serious breaches lead straight to closure.
  2. Accounts closed for breach of this policy are not refunded, and prepaid balances are forfeited to the extent the law allows.
  3. We preserve evidence of a breach, cooperate with law enforcement where we are legally required to, and report child sexual abuse material in every case.
  4. We may share the fact of a closure with the operator of the affected target.

8. Changes

We may update this policy, including the blocked-destination list, as threats and legal requirements change. Changes to the list take effect when published; other material changes are announced by email to the address on your account.

Read the rules, then try the network.

Every account starts with $3 of free credit, unlocked with a $1 card payment, added to your dollar credit, or a crypto payment of $5 or more. Sales can walk through any of these documents with you before you commit.