Privacy Policy

0200project runs paid API tools for AI agents. The tools are designed to need as little of your data as possible, and this policy is short because there is genuinely little to describe. No accounts exist, so there is no profile of you to build, sell, or leak.

What we process

Two things reach our servers when you call a tool:

• The transaction hash you submit. This identifies data that is already public on the Base blockchain. We look it up, decode it, and return the result.
• Your IP address. We hold it transiently in memory to enforce the 60-requests-per-minute rate limit and to meter the free tier. It is never written to a database, the service does not have one.

What we don't do

• No accounts and no signup, so we never ask for a name, email, or password.
• No cookies on this website.
• No analytics or tracking pixels.
• No sale or sharing of data with anyone.
• No profiling. We do not build histories of who asked about which transactions.

Third parties

These are the external systems your browser or your payment touches, found by enumerating the requests our pages make, checked 2026-09-06.

• Google Fonts. This website loads the Geist and Geist Mono typefaces from Google Fonts, so your browser makes a request to Google's servers when a page loads.
• Base RPC providers. The token page reads balances directly from Base when you scroll to that section, using a public endpoint at mainnet.base.org and falling back to base-rpc.publicnode.com. Your browser contacts whichever answers, and we run neither. We also name that same endpoint if you add Base to your wallet from our pay flow; whether your wallet uses it is your wallet's decision, not ours.
• The x402 facilitator. The status page checks whether facilitator.payai.network is reachable when it loads and when you press Re-check, so your browser contacts PayAI's servers on that page. We run neither the facilitator nor its host.
• Fly.io. Our own servers run on Fly.io. Every page contacts them when it loads, for the status line in the footer, not only when you use the tool.
• The Base blockchain. If you pay for calls via x402, the payment settles on Base and is public by the nature of blockchains. A payment links your wallet address to a tool call. If that linkage matters to you, use a wallet accordingly.
• Stripe. Card payments for passes and subscriptions are handled by Stripe on their own pages at buy.stripe.com and billing.stripe.com. We never see or store your card details; Stripe does.

Data retention

Our infrastructure provider keeps standard, short-lived operational logs, as effectively all hosting does. Beyond that we keep one thing, and this page previously said we kept nothing.

The service writes an append-only event log, a single file on a persistent disk, one line per event, rebuilt into memory when the service restarts. There is no database, but the file is a record of requests, so calling it “not a request archive” would be a distinction that serves us rather than you.

What each line can contain, and what it cannot.

Every line records how a call went, not what was asked. No line contains the transaction you looked up, the answer we returned, or anything else you sent us. That boundary holds as we add operational fields; if it ever stops holding, this page changes before the code does.

Within it, these are the kinds of line that can appear, and not every call produces one of each:

• A call: the time, whether it was charged, free or on a pass, whether it succeeded, whether a risk check was unavailable, which interface it arrived through, and a coarse client identifier.
• An outcome: the time, the interface, whether the decode succeeded, and a short code for why it did not, a malformed hash, an upstream failure, a transaction we could not find. This one records why your request failed, which is more than the operational fields above it. It does not record what you asked about.
• A settled payment: the time, the amount, the payment’s transaction hash, and the paying wallet address.
• A failed payment: the time, which stage failed, the reason, and the paying wallet address.

It holds no names, no email addresses and no account records, because there are no accounts. It does hold wallet addresses for payments, and it is not currently bounded by any retention period: entries are not deleted on a schedule. If that changes, this page changes with it.

Corrected 2026-09-04. The previous wording said “no database, no request archive, no user records”. The first was true on a technicality and the other two were not true at all.

Updated 2026-09-04. The service now records why a call failed; the outcome line and the boundary sentence above were added with it.

Changes

If this policy changes, the new version is posted on this page with an updated date at the top.

Contact

Questions about privacy: contact@0200project.com. For anything sensitive, file a private security advisory on GitHub instead.