1. readfetch
  2. privacy

Privacy policy

What this service records

readfetch.com sells per-call web reading. There is no account, no API key, and no sign-up, so there is no profile to build. What exists is a request record, described below in full. Last updated 2026-11-20.

What we do not collect

  • No accountno email, password, or profile
  • No cookiesthe API sets none; the site sets none
  • No trackersno third-party analytics or ad scripts on the API or the site
  • No sellingrequest data is not sold, rented, or shared for advertising

Payment is a signed stablecoin authorization. The wallet that signs it is the only credential, and it is never linked to a name by this service.

What one call records

Every request writes one row to a local database on the operator's server. For a call to /v1/… that row holds:

  • Endpoint and methode.g. POST /v1/text
  • OutcomeHTTP status, error code, latency, response size
  • Caller addressthe source IP, and a salted hash of it
  • User-Agentthe client string you send
  • Wallet addressonly for a paid call that settled, plus its transaction hash
  • Bodiesrequest and response, when body recording is enabled (see below)

The IP address is used for rate limiting, for the per-address free-probe allowance, and for abuse handling. It is not used to identify you to a third party.

Request and response bodies

Bodies are recorded so an operator can answer "why was this call billed this way" with evidence rather than a guess. Each body is capped at roughly 32 KB and stored compressed; anything beyond the cap is dropped, not sampled. Credential-shaped values (authorization headers, cookies, private keys) are redacted before storage. Operators can disable body recording entirely, and when it is off nothing is written.

Retention

  • 30 daysrequest and response bodies
  • 400 dayscall rows — endpoint, status, timing, IP, wallet
  • In memory onlythe free-probe counter: it is not written to disk and resets when the service restarts

A sweep deletes expired rows continuously. The operator sets both windows; the values above are what readfetch.com runs today. Records older than the window are not archived anywhere else.

Payments are public

A settled call is a USDC transfer on Base. The transfer — payer address, payee address, amount, transaction hash — is public chain data that anyone can read, independent of this service. We keep the payer address next to the call so billing disputes can be settled against a receipt. We do not attempt to attribute that address to a person, and we cannot delete it from the chain.

What the sites you read see

When you ask us to read a URL, we request it from our own egress, with a browser User-Agent and standard headers. The origin sees that address, not yours, and not the wallet that paid. That origin's own logging and privacy practices apply to its side of the exchange.

Feedback and claims

A message you send to POST /v1/feedback is stored with the request id it references. A claim under POST /v1/claims is stored with the receipt, the reason, and a signature that proves the wallet that paid made the request. Do not put personal data in either; if you must, say so and it is removed on request.

The network in front of us

TLS terminates at a reverse proxy and the edge network in front of it, which keeps its own standard request logs (IP, URL, timestamp) under its operator's policy. Those logs exist to route and protect traffic; this service does not receive or store anything from them beyond the request itself.

Removal and questions

There is no account to close. If you need a specific request removed before its retention window ends, send POST /v1/feedback with the X-Request-Id from that response, or open an issue at github.com/readfetch/readfetch. Include the id and what to remove; the operator acts on it and replies in the same channel. The same two channels take questions about this policy.

If this policy changes materially, the date at the top changes and the previous text is in the repository history at github.com/readfetch/readfetch.