Privacy

Infrabond keeps the data it needs to run and nothing else. There is no analytics, no advertising and no tracking pixel on the site. We never ask for an email address, a name or an identity document.

What we hold

• Public chain data. Addresses, payments, backing and claims are public on Robinhood Chain. The site reads and displays them; it cannot hide or erase them.
• Your passkey account. The passkey stays on your device. Its public key and your account address are stored in your browser. Our relayer sees the transactions you ask it to submit, and counts them per day under the passkey's public key for two days, to enforce the daily limit.
• Payout links. When you name a payout address for a payment, we store which payment it belongs to (the transaction hash and the payout address) for 180 days. Only the compensation publisher reads it. It is never shown on the site, in the API or onchain; compensation documents and claims name the payout address alone.
• Sealed services. The URL of a sealed service reaches us encrypted to the prober's key, and our store keeps only that ciphertext, in the request queue, for its last 500 requests. The prober decrypts it on its own machine and keeps the URL there, in a file only it can read. Public pages show the commitment.
• Paid watches and claims. The endpoint you asked us to watch or claim, its kind and name, the operator address of a claim and the payment's transaction hash. We do not keep the payer's address with a watch.
• Payments we settle. The nonce of each x402 authorization for one day, so it cannot be replayed, and daily counters.
• Probe records. For every probe: the time, the block it was anchored to, whether it passed, how long it took, a reason code and a hash of the response. Never the response itself. They stay 30 days on the site; the aggregates stay onchain.
• Waitlist. Your account address, or your Google account identifier if you sign in with Google, and your place in line.
• Google sign-in, when enabled. Google sends us a signed token with your account identifier and first name. We keep the identifier and a session cookie; we do not receive your email address, your contacts or your email history.
• Server logs. Our host keeps standard request logs (IP address, time, path) for a short period to run and protect the service. We do not copy them into our store.

Why

To run the product you asked for (legitimate interest and contract): to measure services, to pay compensation to the address you chose, to pay gas for your passkey account, and to keep the waitlist. We do not sell data and do not use it for advertising.

Who else

Our hosting provider and our key-value store process data on our behalf. Google processes sign-in when you choose it. The chain is public by design.

What privacy does not cover

A payout address hides the link between a payment and its compensation from the public record. It does not hide the payment: the paying wallet, the amount and the service's address stay visible in public USDG transfers, and anyone who later moves funds between your wallets can link them. Nothing here makes you anonymous.

Your rights under the GDPR

If you are in the European Economic Area or the United Kingdom, you can ask what we hold about you, have it corrected or erased, restrict or object to its use, and receive it in a portable form. Onchain data cannot be erased by anyone. You can also complain to your data protection authority. Write to us through the X account and we will answer within a month.

How long

Payout links for 180 days, waitlist entries for a year, sessions for 30 days, relayer counters for two days, authorization nonces for one day, probe records for 30 days on the site, server logs for the host's short retention.

Cookies

See the cookies policy.