Scraper.io Terms of Service

These terms are an implementation draft for Scraper.io. They are not intended to become binding until the contracting legal entity, registered address, governing law, tax treatment, liability terms and final service process have been reviewed and inserted.

A customer should receive the reviewed terms before payment and should be able to save a copy of the version accepted at checkout.

Scraper.io turns a plain-English data job into a sample, a fixed quote, and a file or feed. Before paid work begins, the customer should be able to see sample rows, columns, the source, and the price on screen.

Self-serve jobs and repeating feeds are quoted in chat. Managed work is scoped on a demo. Deliverables depend on the accepted quote: a one-off export, a repeating extract, or a monitored feed. Empty fields are preferred over invented values. Source availability can change without notice.

The price is the fixed quote shown before checkout, or the written quote emailed after a demo for managed work. The checkout must state whether VAT or other taxes are included and identify the merchant of record. No recurring charge should begin automatically unless the customer expressly accepts a feed or other repeating plan.

Bespoke sources, licensed data, or additional review may require a separate written scope. Changing the job after payment may require a new quote.

If a paid job is not delivered as quoted — sample rows, agreed fields, or the export described at checkout — Scraper.io will refund the fee for that job. The reviewed terms must specify how the request is made, the payment method used for the refund and the treatment of taxes.

The customer may retain a supplied export unless the final written scope says otherwise. A refund does not authorise use of Scraper.io software, credentials or non-exported service materials after access ends.

The customer should provide accurate scope information, have authority to share submitted files and credentials, and use delivered information lawfully. Confidential information or personal data that is unnecessary for the market should be removed before submission.

The customer remains responsible for decisions and actions taken using a market. It should independently review evidence before relying on a result for legal, regulatory, financial, employment, safety-critical or similarly high-impact decisions.

The standard service is intended for approved public sources. Source availability, page structure and published information can change without notice. A source that fails to load must not be represented as proof that the underlying fact did not change.

Scraper.io should identify direct observations, inferences and conflicts. Unsupported fields may remain empty. The service does not promise exhaustive coverage of the web, access to every site, or authenticated and paywalled sources unless a separate reviewed agreement explicitly includes them.

The service must not be used to violate law, source terms, intellectual-property rights, privacy rights or access controls; collect unnecessary sensitive or personal information; facilitate discrimination or surveillance; deliver malware; or make deceptive claims about the provenance of supplied data.

Scraper.io should be able to refuse or stop a source or workflow that creates legal, security or rights risk. The final terms must describe notice, suspension and any effect on fees.

The customer should retain ownership of its submitted briefs, private criteria and feedback. The reviewed agreement must define the customer's licence to use and export delivered job data while respecting third-party source rights and any restrictions attached to licensed material.

Scraper.io should retain its software, schemas, collection methods, evaluators and other platform materials. No term should imply ownership of third-party source content or grant rights that Scraper.io does not hold.

Each party should protect confidential information received from the other and use it only to deliver or receive the agreed service. The final terms must define exclusions, required disclosures and what happens to confidential information at termination.

Personal information should be handled under the reviewed privacy notice and any data-processing agreement required for the customer's use case.

Public web information may be incomplete, ambiguous, outdated or wrong. Human and model review reduce some errors but do not eliminate them. The final terms should describe the service with reasonable care while avoiding guarantees of completeness, uninterrupted availability or fitness for an unspecified decision.

Any warranty disclaimer must be reviewed for the law governing the final contract and must not exclude rights that cannot legally be excluded.

No liability cap or exclusion is stated in this draft. The final terms must set commercially appropriate limits, identify categories that cannot be excluded and address indirect loss, data loss, source-rights claims and customer misuse.

The final wording must be reviewed alongside the actual legal entity, insurance position, buyer type and governing law.

Access to a one-off job ends when the export is delivered, unless a feed or other repeating plan is accepted. A repeating plan should be cancellable for the next billing period under the notice process shown at purchase. The customer should be able to receive the agreed export when access ends.

The final terms must explain termination for breach, source or security risk, non-payment and legal requirement, together with any provisions that survive termination.

The verified contracting entity, registered address, governing law, courts and notice process must be added after legal review. Material changes should not apply retroactively without an appropriate notice and acceptance process.

Commercial questions can be sent to sales@scraper.io. Legal notices require a verified address and process before these terms become operative.