Privacy Policy
Last updated: October 29, 2026
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, so we never ask for a name or a password. We ask for an email address only if you choose to join the XO2 wallet waitlist.
- 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.
The XO2 wallet waitlist
If you join the waitlist, our server stores the email address you enter and the date you joined, in a file kept apart from the event log described under Data retention. If you also give a phone number and tick the box to get a launch text, it stores the number and the exact words you agreed to; without the tick, the number is not kept. We use these only to tell you about the XO2 wallet, and we don’t share them. We keep them until XO2 launches.
Third parties
These are the external systems that receive data from your visit, your request or your payment. We found them by recording every request each of our pages makes in a browser and by reading the code of our pages and our server, checked 2026-10-29.
- GitHub Pages. GitHub hosts this website, so every page you open is a request to GitHub’s servers. GitHub receives your IP address, your browser’s user agent and the full address of the page, including any transaction hash in a playground link and the checkout session id when Stripe sends you back from a card payment.
- 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.
- Your wallet. If you pay with a wallet on the playground or pricing page, our page does not contact Base itself. It asks your wallet, which reaches Base through its own provider, and that provider can see your address and the balance check before you sign. If your wallet does not know Base yet, we suggest mainnet.base.org and basescan.org when adding it. Whether your wallet uses them is your wallet’s decision, not ours.
- Base RPC providers. To decode a transaction, our server asks a Base RPC provider for it: mainnet.base.org first, then base-rpc.publicnode.com and base.llamarpc.com if the one before fails. The provider receives the transaction hash you sent us and the addresses of the tokens and contracts in that transaction. It sees our server, not your IP address.
- Contract and history lookups. For the risk checks, our server sends addresses taken from that transaction, never the hash you sent and never your IP address. Contract addresses go to Sourcify (sourcify.dev), to check whether their code is published and to name events we do not recognise. A function identifier we do not recognise goes to Sourcify’s signature database (api.4byte.sourcify.dev). The transaction’s sender and block number go to Blockscout (api.blockscout.com), to check whether the sender has dealt with the other party before. When Sourcify or Blockscout does not answer, the same lookups go to Etherscan (api.etherscan.io). As of 2026-10-29, Etherscan refuses these lookups for Base and the history check gets no answer from either service, so it reports itself unavailable, but both services still receive the lookups.
- The x402 facilitators. When you pay via x402, our server sends your signed payment authorization, which includes your wallet address, to a facilitator to verify and settle it: PayAI’s at facilitator.payai.network, Coinbase’s at api.cdp.coinbase.com, or both. Which one receives it first depends on what you are paying for and on our configuration, and we do not count how often each is used. We run neither.
- Fly.io. Our own servers, at api.0200project.com, run on Fly.io. The home, about and status pages contact them when they load, the home page to show how many calls we have served, and the status page again when you press Re-check. The playground contacts them when you explain a transaction, including when you open a link that carries one, and when you pay. The pricing page contacts them when you pay with a wallet or come back from a card payment. The XO2 wallet page contacts them when you join the waitlist. Other pages do not.
- The Base blockchain. If you pay via x402, for calls or for a pass, the payment settles on Base and is public by the nature of blockchains: anyone can see that your wallet paid ours, how much, and when. Our own log also records the payment with your wallet address, as described under Data retention. If that linkage matters to you, use a wallet accordingly.
- Proton Mail. Our mailbox, contact@0200project.com, is hosted by Proton Mail, so any email you send us, including a request to leave the waitlist, is received and stored by Proton.
- 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. When Stripe sends you back to our pricing page, that page passes the checkout session’s id to our server to confirm the purchase.
Data retention
Our infrastructure provider keeps standard, short-lived operational logs, as effectively all hosting does. For a paid call, our server’s own line in those logs names the payment, which identifies the paying wallet, and for a paid decode through our REST API, the transaction it paid for. 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.
Lines record how a call went, not what was asked, with one exception. On a paid decode, one line records the transaction you asked us to decode, beside the wallet that paid for it. Apart from that, 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, the paying wallet address, and, for a paid decode, the hash of the transaction you paid to have decoded.
- 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.
Corrected 2026-10-29. Since 2026-09-06 a settled payment for a decode has recorded which transaction it paid for; this page did not say so until now.
Changes
If this policy changes, the new version is posted on this page with an updated date at the top.
Contact
Questions about privacy, and anything sensitive, including security reports: contact@0200project.com.