What we collect, said plainly.

This site (cloudana.io)

The homepage is a React app. It sets no cookies and runs no analytics or tracking scripts. To render it, your browser makes these requests:

• Google Fonts (fonts.googleapis.com, fonts.gstatic.com) — to load typefaces.
• Base public RPC (sepolia.base.org) — to read the latest Base Sepolia block, which seeds the in-browser proof demo. This endpoint is operated by a third party (Base), not by us, and like any server it sees your IP address and standard request metadata.
• Our own API — /v1/network and /v1/network/recent for live network figures, and the verifier endpoints if you check work in your browser.

If you verify work in your browser, the page keeps a random session id in your browser's local storage so your verifier credits carry over; it is not tied to your name, email, or wallet. If you arrive through a referral link, the referral code is kept there too until you join the waitlist.

The console and API

If you sign in or run a provider node, we process what the network needs to function:

• Account data — your wallet address. Sign-in is a signature over a one-time server nonce; the resulting short-lived session token stays in that browser tab.
• Provider data — the node's hardware manifest (CPU, GPU, RAM, disk), its benchmark results, and the node's public key, used to assign work and to check that messages really come from that node.
• Jobs and deployments — the inputs and results of compute jobs; for hosted sites, the files you upload and a hash of them used to probe that the node is serving what you uploaded; for containers, the image, ports and the names of environment variables. Sealed secrets are being rolled out: once they are on, secret values are encrypted in your browser to the assigned node's key and we store only ciphertext. We also keep uptime-probe results and the hourly charges for each deployment.
• Payment data — jobs are paid in CLD from your wallet; we record the escrow deposit and the fee for each job. Card payments are off during testnet; if they are ever enabled they will be handled by a payment provider and we will never see or store card numbers. Any swap from another asset into CLD happens in your own wallet, and we never hold customer assets other than escrowed CLD.
• Testnet credits — to limit abuse, the daily testnet credit is keyed to your sign-in identity and wallet, and we keep a short-lived record of the requesting IP address and network. Testnet credits have no monetary value.
• Abuse reports — if you report a deployment, we keep your report and our decision; if your deployment is stopped, we keep the reason (see Terms §4).
• Operational logs — our infrastructure runs on Cloudflare, which processes IP addresses and request metadata to serve and protect the service.

The waitlist

If you join the waitlist, we store your email, the role you picked, and whatever optional answers you give: the services you're interested in, your country, and the role-specific questions on the form. We also keep your referral code, the code of whoever referred you (if any), where you came from (such as a campaign tag), whether you opted into the newsletter, and when you signed up. We use this only to contact you about access to Cloudana. You'll get the newsletter only if you ticked the box. We don't sell or share the list with anyone. To have your entry deleted, ask us through the contact route below.

What we don't do

• We don't sell or rent your data. To anyone.
• We don't run advertising or cross-site tracking.
• We don't collect more than the network needs to work.

The blockchain caveat

Anything written on-chain — wallet addresses, settlement batches, the CLD you claim — is public by design and cannot be deleted by us or anyone. Don't put anything in an on-chain transaction you wouldn't want to be permanent.

Your choices & contact

To access or delete the off-chain data tied to your wallet or waitlist entry, or to ask anything about this policy, email [email protected]. To report illegal, infringing or harmful content served by the network, email [email protected] (the takedown process is in Terms §4). For anything public, you can also open an issue on GitHub — the project is built in the open.