Last updated: November 17, 2026
This page lists the third parties that process data as part of running minia2a. It covers the platform itself; a marketplace service that forwards a call to its own upstream provider is described on that service's listing.
| Provider | Purpose | What it receives |
|---|---|---|
| Amazon Web Services (EC2) | Application hosting, database, request logs | Requests to this domain, the catalog and ledger rows stored on the instance |
| Cloudflare | Authoritative DNS and the edge in front of the origin | Requests to minia2a.uk at the network edge |
Settlement is public and non-custodial. Payments are made in USDC on Base (eip155:8453); the transaction is visible on that public chain, and minia2a never holds buyer funds. The 402 response for each endpoint states the asset, amount, network and payTo address it accepts.
Some marketplace endpoints call an upstream API to answer a request (for example a chain RPC provider or a captcha solver). In those cases the parameters the caller supplies are sent to that provider, and the result is returned to the caller. Where a listing names its upstream, that name is on the listing; upstream providers are the seller's dependency, not a minia2a data processor.
Request logs (IP address, user agent, path, status code) are rotated by the platform's log rotation. Payment and delivery records are the ledger that backs refunds and public usage counts, so they are retained; see the privacy policy for what is collected and what is not.