Fresh402 service terms and privacy - October 15, 2026

Fresh402 is an individually owned and operated online API service based in Alaska (sole proprietor). Customer support, private billing, refunds and account-closure requests: fresh402@proton.me.

Fresh402 provides on-demand processing of public HTTPS HTML, JSON, text and supported JSON OpenAPI contracts. It does not run page JavaScript, access authenticated pages, resolve remote OpenAPI references, continuously poll watches or guarantee compatibility classifications. Security, response size, retention, rate, daily operation and infrastructure limits apply. Availability is not guaranteed; an outage or exhausted budget can delay execution without removing your credits.

Starter costs 2.50 native USDC for 1,000 credits; Developer costs 15 native USDC for 10,000 credits. Current tariff 3 uses Check 2, Extract 3, Smart Diff 4 and OpenAPI Contract Diff 5 credits. Historical purchased tariffs remain unchanged. Standalone x402 prices remain 0.005, 0.010, 0.015 and 0.020 USDC respectively. Payments use Base Mainnet (8453) and native USDC. Confirm the exact quote in your wallet; never provide a seed phrase or private key. Contract-wallet signatures are not supported.

Prepaid credits do not expire under this policy. API keys expire separately after one year and can be replaced through the original wallet. Credits are service units, not a financial investment, interest-bearing balance or a transferable token. Successful completed operations consume the quoted credits. Rejected or unexecuted work does not. Replaying the same retained operation with the same inputs and idempotency key does not debit again. Results are retained for seven days; payment and accounting evidence is retained separately.

Full purchased credit entitlement requires a successful, canonical, finalized native-USDC authorization and matching transfer evidence. When enabled, independently corroborated recent successful L2 inclusion may unlock a limited provisional early tranche (at most 50 Starter or 100 Developer credits), subject to account, payer, project exposure and verification limits. A signature, transaction hash, broadcast acknowledgement, facilitator response or mempool observation alone grants no credits. Early inclusion is not finality. Unused early credits may be frozen or revoked if evidence is uncertain or invalidated; consumed early usage remains bounded merchant risk and is not charged against unrelated finalized funds. Finalization activates only the remaining package entitlement, preserving earlier usage. The nonexpiration policy applies to purchased finalized credits; provisional access is conditional. The service checks pending payments automatically. Do not authorize another payment after a timeout or uncertain outcome. Reconnect the same wallet to recover access, inspect the original purchase or replace a lost key; recovery does not require another payment. Claiming/replacing a key revokes older account keys. Ordinary top-ups preserve existing keys.

No automated USDC refund mechanism is provided. Report a suspected duplicate payment, missing finalized credit or an unused-balance refund request for review, subject to applicable mandatory rights. Completed valid usage is not automatically refundable. Account closure must not silently forfeit an unused balance; its treatment requires review with the funding wallet. Do not publish sensitive evidence in an issue. This policy does not limit rights that applicable law makes mandatory.

Watch URLs, identifiers and legacy snapshot history are shared public service data. Submit only public resources and do not put credentials or personal secrets in target URLs. Wallet addresses, purchase references, signed payment authorizations, receipts and accounting records are retained privately to verify settlement, prevent duplicates and recover payments. On-chain transfers are public. The service stores API-key verifiers, not wallet private keys. This account page encrypts its saved authorizations and claimed keys in browser storage; clearing that storage removes the local copy, while wallet-based account recovery remains available. Operational request counts use aggregate categories and time buckets; IP addresses, payment signatures, API keys and page contents are not written into those aggregates. Cloudflare, Coinbase/CDP and Base infrastructure process the requests needed to deliver the service. Coinbase receives payment authorization and transaction data for verification, screening and settlement. No advertising tracking or sale of customer data is used by this service.

Email fresh402@proton.me to request access to, correction of or deletion of your account data. Requests are reviewed subject to ownership verification and applicable rights. Required accounting, payment-security and dispute evidence may need to be retained; public blockchain records cannot be erased by Fresh402. Do not send private keys or seed phrases. Private billing evidence belongs in the support channel, not a public issue.

The official Fresh402 project is https://github.com/kirillradchenko96/fresh402 . Nonconfidential technical reports may use https://github.com/kirillradchenko96/fresh402/issues without keys, signatures or private URLs. Use fresh402@proton.me for confidential customer support. Current account-creation and purchasing availability is published at /v2/prepaid/plans; publication of this policy does not imply that new purchases are enabled. Use of the service must comply with applicable law and payment-provider restrictions, including applicable sanctions.