Privacy Policy

Last updated: October 21, 2026

Quinn's Conveyance ("we") is operated by John O'Malley in Washington, USA. Contact: john@quinnsconveyance.com. This policy covers quinnsconveyance.com, demo.quinnsconveyance.com (including the supplier portal), our x402 implementation and Operate services, the Agent Gateway, and the quinns-x402 SDK.

What we collect

Settlement ledger (our core record). For each payment challenge and settlement we record: transaction hash, payer wallet address, endpoint/tool called, call arguments for client deployments (as configured with the client), amount, timing/latency, and verification status (verify_status). Wallet addresses and transactions on Base are public on-chain by design.

Client and supplier data. Names, business contact details, email addresses, API documentation, a payTo/payout wallet address, and — for Gateway suppliers only — a dedicated API key you issue for the gateway. Gateway supplier keys are stored encrypted (AES-256-GCM), decrypted only in memory to make a call, and never logged or shared.

Supplier portal data. If you use the supplier portal, we also record: your sign-in email address, sign-in link requests (including the requesting IP address, for abuse prevention), your acceptance of the Supplier Terms (version and time), and the message signature you provide to bind your payout wallet.

Portal cookie. The supplier portal uses one first-party cookie (qc_supplier_session) to keep you signed in. It is HttpOnly, Secure, and SameSite=Lax, lasts 30 days, and contains only a random session token (stored server-side as a hash). It is never used for advertising or cross-site tracking. The public pages of this site set no cookies.

Communications. Emails and messages you send us, and records of approvals you give (for example case-study approval).

Server logs. Standard web server logs (IP address, time, path, status) for security and reliability. The demo and portal sites do not run third-party advertising or analytics trackers.

What we never do

How we use what we collect

Only to: operate the payment service and gateway; produce the client's own dashboard, reports, and settlement verification; pay out gateway suppliers; respond to you; keep the service secure and reliable; and improve the service.

Processors we rely on

Payment facilitators and wallet infrastructure (Coinbase CDP and PayAI) process settlements and gateway payouts under their own terms; cloud hosting (Oracle Cloud and Google Cloud); transactional email delivery for portal sign-in links (Resend). On-chain settlement data is public on Base (see BaseScan).

The Gateway difference

For direct implementations, payments settle wallet-to-wallet and we never hold funds. For Gateway listings, payments pass through the gateway wallet so supplier shares can be paid out; every call is logged per-call in the ledger above so suppliers can audit their balance. That logging is described here and in the Supplier Terms — it is not hidden.

Retention

Settlement records are kept while a client/supplier relationship is active and for 12 months afterwards for accounting and dispute purposes, then deleted or anonymised. Client deployment data is exported or deleted on request at any time, and on termination of a pilot within the timeframe in the agreement.

Your choices

Email john@quinnsconveyance.com to request: an export of your deployment data, deletion of your data, or correction of contact details. We respond within 30 days. Note that on-chain transactions cannot be altered or deleted by anyone; deletion applies to our own records.

Who this service is for

Our services are business services for API providers and developers. They are not directed to children, and we do not knowingly collect children's data.

Changes

We will post changes here and update the date above. Material changes affecting an active client or supplier will also be emailed to them before they take effect.