Legal

Scraper.io Terms of Service

Proposed terms for the guided Live Market pilot and monthly continuation.

Draft for legal and commercial review

These terms are not ready for customer acceptance. The contracting entity, registered address, VAT treatment, liability terms, governing law and checkout process must be verified before payment is taken.

Draft updated 5 August 2026

1. Status of this draft

These terms are an implementation draft for the proposed Scraper.io Live Market pilot. 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.

2. The pilot service

The standard pilot is intended to cover one agreed market for 14 days. Before work begins, Scraper.io and the customer should agree the market definition, representative sources, fields, expected output, refresh approach and acceptance criteria.

The proposed deliverables are a reviewed source-backed table, customer-specific fields or watchlist where agreed, two change briefs during the pilot and a CSV export. First reviewed rows are targeted within 48 hours after scope is agreed; this is a delivery target rather than an uptime or universal coverage guarantee.

3. Fees, taxes and continuation

The proposed validation pilot price is £500 as a one-off charge. The final 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 it.

If the customer chooses to continue after the pilot, the proposed price is £1,250 per month for the accepted market on an agreed refresh schedule. Bespoke sources, several markets, licensed data or additional review may require a separate written scope.

4. Pilot refund

The proposed commercial promise is straightforward: if the customer tells Scraper.io before the end of the 14-day pilot that the delivered market was not useful, Scraper.io will refund the £500 pilot fee. 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 the supplied CSV 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.

5. Customer responsibilities

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.

6. Sources and coverage

The standard pilot 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.

7. Acceptable use

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.

8. Ownership and permitted use

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 market 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.

9. Confidentiality and privacy

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.

10. Service limitations and warranties

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.

11. Liability

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.

12. Ending the service

Pilot access is intended to end after 14 days unless the customer continues. A monthly continuation 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.

13. Governing law, changes and contact

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.