Privacy

The short version: no accounts, no tracking, no analytics, and uploaded files are deleted after processing.

This website

Static pages with no JavaScript, no cookies, no analytics and no third-party requests of any kind. Nothing is loaded from a CDN, an ad network or a font service, so no third party learns that you visited. Your browser fetches HTML and CSS from one origin and that is all.

The API

What is stored

• Request records — endpoint called, timestamp, duration, outcome and error code. Used to operate the service and to show the operator whether it is working.
• Payment records — the payer wallet address, amount, asset, network, transaction reference and settlement state. This is the accounting record for money actually received, and it is also public on-chain.

What is not stored

• Your request bodies and uploaded files. Documents and images are processed in memory or in a temporary file and removed when the request finishes, including when it times out or fails. They are not archived, not indexed, and not used to train anything.
• No account data — there are no accounts. No email address, no name, no password, nothing to breach.
• No private keys, ever. The platform cannot receive one. It holds only a public receiving address, and it has no code path that could accept, store or use a key, seed phrase or signature of yours beyond the payment authorisation you sign for a single call.
• No behavioural profiling. Requests are not linked into a profile of a caller beyond what the payment ledger inherently records.

Errors never carry your data back out

Validation errors name the field that failed but do not echo the value you sent. That is deliberate: echoing input into an error body relays your content into logs, dashboards and anything else that renders it.

Content you submit about other people

Some endpoints accept documents that may contain personal data — invoices, contracts, tenders. You are responsible for having the right to process that content. The platform keeps none of it after your response is returned.

The public contact-extraction endpoint deliberately returns only role addresses (info@, sales@, support@ and similar) and filters out personal-looking ones, so its output is business contact data rather than a harvested list of individuals.

Operator access

The operator dashboard shows aggregate statistics, service health and payment records. Payer addresses are masked in that interface: it exists to show that payments happened, not to build a browsable register of who paid.

On-chain payments are public

Payment settles on a public blockchain. The transfer, the amount and the addresses involved are visible to anyone, permanently, and neither we nor you can remove them. That is a property of the payment rail, not a choice made here — but it is worth being explicit about before you pay.

Requests about your data

Since no account exists and request content is not retained, there is normally nothing to export or delete. Payment records are financial records and are kept for the period applicable law requires. If you need to ask about a specific transaction, quote the request_id from your response.