Privacy
We process what a call needs and keep as little as possible.
Effective 2026-10-20. No accounts, no cookies, no advertising, no sale of data. Contact: naxytra@gmail.com.
Data
What we process
undefined
- Request content: the arguments a tool call needs, used to produce the result. We do not keep request bodies after the call; a delivery receipt keeps only hashes of the request and the result.
- Payment facts: the payer address, network, asset, amount and settlement transaction of an x402 payment. These are public on the Base blockchain by design.
- Credits: the balance and spend history of a credits account, keyed by the account id you chose or the paying address.
- Operational events: request id, route or tool, outcome, latency, a truncated client name, a salted hash of the payer address, and a coarse client family. Raw IP addresses and payment signatures are not stored in this event log.
- Hosting logs: our hosting providers keep standard server logs for a limited period.
Retention
Where it lives and for how long
undefined
- Runtime state (credits, quotes, receipts, events) is stored in a managed database with encrypted off-site backups; the event log is a bounded rolling window and daily counters are kept for 30 days.
- Delivery receipts are kept in a bounded rolling store so they can be fetched and re-verified.
- Providers we rely on: Render (hosting), Vercel (this site), Supabase (state), the Coinbase CDP facilitator (x402 settlement) and the Base network (public ledger). Each processes only what its role needs.
- No cookies or trackers are set by naxytra.com.
Rights
Your choices
Ask us what we hold about a payer address, account id or request id, or ask us to delete credits-account records once the balance is zero, by emailing naxytra@gmail.com. We cannot alter public blockchain records. Pay on Base Sepolia (test USDC) if you want to try the service without touching real funds.