A scraping API is not a permission slip.

This policy applies to the API, the dashboard, saved projects, schedules and batches. It forms part of the Terms of Service. Breaking it is a breach of the agreement, whether the request came from your key, your session or a script you delegated.

• You must be entitled to access the page you request. Public availability is not the same as permission to collect at scale.
• You are responsible for the target site's terms, its robots.txt and the law where you and the site operate. Scraply does not check these for you and does not enforce them automatically.
• You must have a lawful basis for any personal data you collect, and must not collect more of it than that basis supports.
• You must respect copyright and database rights in the content you retrieve.

• Collecting special-category data — health, biometric, genetic, political, religious, trade-union or sexual data — without an explicit lawful basis.
• Collecting personal data about children, or building profiles of identifiable people for surveillance, scoring or targeting.
• Reaching content behind a login, paywall or other access control that you are not authorised to use.
• Bypassing a technical protection measure, or obtaining credentials by guessing, stuffing, phishing or buying them.
• Fetching material that is itself unlawful to possess or distribute.
• Using the service to attack: denial of service, port or endpoint scanning, exploiting a vulnerability, sending spam, or probing a network you do not own.
• Fraud, money laundering, sanctions evasion, harassment, or interference with an election or a public emergency service.
• Reselling raw API capacity, keys or accounts to third parties without a written agreement.
• Presenting scraped output as licensed data, or as the target site's own data feed.

Do not send credentials for a third-party site unless you are authorised to use them there. Do not attempt to defeat an authentication check, a captcha farm, or an account-level rate limit on a target site. If a site has told you to stop, stop: continuing through a rotating proxy is exactly the conduct this clause forbids.

Keep your Scraply keys private. A key found in a public repository, a client-side bundle or a shared log is revoked, and repeated leaks can end the account.

Each API key can carry a daily successful-request limit, set in the dashboard. The limit exists to keep one workload from exhausting shared capacity. Deliberately spreading a workload across keys or accounts to exceed it is a breach of this policy.

Automated requests that ignore backoff after a target returns 429 or 503 are throttled. If a target is failing, the retry budget is not a licence to hammer it.

Depending on severity, an account may be:

• throttled, with a written reason and a route to appeal;
• suspended while a report is investigated;
• terminated, with remaining credits handled under the Refund Policy;
• reported to a competent authority where the conduct is criminal.

Where the law or the safety of a third party prevents it, notice is given after the action rather than before. An appeal goes to support@scraply.net and is answered within 5 business days.

If a Scraply request is hitting your site in a way you believe is unlawful or harmful, write to support@scraply.net with the subject "Abuse report", the URL, timestamps and a short description. Include the request headers if you have them: the user agent identifies Scraply traffic. Reports are reviewed and the account behind the traffic is contacted or suspended.