Trust, Guarantees & Security

Terms of Service & Refund Policy

Clear, transparent policies governing deterministic crawls, on-chain micropayments, unguessable report sharing, and failure refund guarantees.

About CrawlPay

CrawlPay is an autonomous technical SEO, Answer Engine Optimization (AEO), and Generative Engine Optimization (GEO) platform designed for web developers, site owners, and autonomous AI agents. Unlike traditional SaaS tools that require recurring monthly retainers and user accounts, CrawlPay provides deterministic on-demand audits settled directly on Celo mainnet rails via x402 micropayments.

Failure & Refund Guarantee Policy

When you submit a payment transaction for an audit, the transaction is verified on the Celo blockchain.

  • Automatic Retry: If a crawl fails due to a network glitch, target host timeout, or transient rate limit, our backend crawler automatically attempts one immediate retry.
  • Irrecoverable Failures & Refunds: If the target website is completely unreachable, permanently blocking crawlers, or the system fails to produce an audit report after payment verification, you are entitled to a full refund.
  • How to Claim: To request a manual refund for an unfulfilled transaction, provide your Celo transaction hash to our support operator or submit an automated refund request with your linked payment ID.

Report Access & Privacy Policy

Unguessable URL Sharing: Audit reports generated by CrawlPay are assigned a high-entropy, cryptographically unguessable unique identifier. Anyone with the direct report link (/app/reports/[id]) can view the analysis. This enables frictionless sharing across engineering teams, agencies, and stakeholders without account provisioning.

CrawlPay does not make your report links publicly searchable unless you choose to share them or authorize public showcase.

Acceptable Use & SSRF Protections

Users and autonomous agents agree not to abuse the crawler to initiate denial-of-service attacks, scan internal private networks, or bypass security barriers.

CrawlPay actively enforces server-side SSRF filters: any attempt to audit private IP addresses (e.g. 10.0.0.0/8, 192.168.0.0/16, 127.0.0.1, AWS/GCP cloud metadata endpoints) will be strictly rejected with HTTP 400.