Privacy Policy

Data collected — supplied-record comparison. POST /commerce/reconcile processes the JSON records you submit and returns an exception report. The comparison handler does not persist the request body or response, cache results, make external calls or execute payments. It does not use a payment address or an IP-derived allowance key. Use synthetic or redacted records for evaluation.

Legacy API access. Metadata and storage practices depend on the tool and access route. They can include an IP-derived allowance key for free-tier access, a payment address for paid access, tool name, timestamp and payment amount. Some deterministic tool results are cached by input hash. These legacy practices do not describe the stateless comparison handler.

Retention. The comparison handler has no record-retention store. This does not mean infrastructure or security logs contain no request metadata. Legacy routes can retain operational records such as funnel events, settlement metadata and receipts according to their implementation. This draft does not establish a verified retention schedule for every route or infrastructure log; confirm data-handling and retention requirements before sharing sensitive records. Reports and any returned receipts can contain supplied data and should be handled accordingly.

Subprocessors and infrastructure. Cloudflare provides compute, storage and DNS infrastructure. Circle token infrastructure and public Base transactions concern the applicable legacy payment flows; the free comparison makes no payment or token-infrastructure call.

Contact. security@code402.dev.

Effective Date: October 14, 2026 | Version 1.2 Final · Reviewed by counsel.