saler.ai Acceptable Use Policy

AUP · Last updated: 2026-09-21

This policy is referenced by the Terms of Service and is equally binding.

Language and precedence: the Chinese text of this policy is the master. This English version is a faithful translation provided for convenience and for payment-provider (MoR) onboarding. In the event of any conflict or ambiguity, the Chinese version governs.

1. No Unfair Competition

  1. Bulk-scraping competitors for the purpose of unfair competition is prohibited (direct response: legal checklist, section 8 D2).
  2. Forwarding raw data as-is, with no value added is prohibited (a flow-down obligation from our upstream terms, and the legal rationale for our value-added layer).

2. No Circumvention or Attacks

  1. Circumventing rate limits, bypassing billing, or probing or attacking the service is prohibited.
  2. Unlawful use, sanctioned parties, and infringing content are prohibited.

3. No Unauthorised Crawling (the legal basis for our SSRF defences)

  1. Inducing the service to crawl targets we have not authorised is prohibited (in particular where it is done to use the service for SSRF probing of internal networks or metadata endpoints). The service already filters private, loopback, link-local and reserved ranges at the kernel layer and re-validates every redirect hop, but this clause is the legal basis for those defences.

4. Accounts and Keys

  1. Sharing an account or API key is prohibited, and reselling the key itself is prohibited.
  2. Responsibility for API key security rests with the user (see ToS §2.2).

5. Consequences of Breach

  1. Escalation ladder: warning → rate limiting → revocation → termination.
  2. The balance-handling rule must be explicit: on termination, unused credits are handled consistently with the Refund Policy and are not confiscated unilaterally.

6. Compliance of Data Sources

  1. Users must comply with the terms of upstream vendors (DataForSEO and others); using the service to circumvent upstream terms is prohibited.
  2. Publishing derived data externally must respect the k≥5 aggregation threshold and attribution obligations (see ToS §7 / §5).