Nothing on our side. Ledger has no backend account system, no analytics, no tracking pixels, and no first-party logging of users. The frontend is a Next.js app served by Vercel; we don’t pull your IP or behavioral data out of Vercel’s built-in logs.
When you click Connect Wallet, the auth flow is handled by Privy. Privy may collect your email address, phone number, or OAuth identifiers if you choose those login methods, and it manages the embedded wallet they create for you. Their privacy policy at privy.io/privacy-policy governs what they do with that data. Ledger never sees your email, phone, or private keys.
Once you sign a transaction, the resulting event is public on the relevant testnet (0G Galileo, Ethereum Sepolia, Base Sepolia). That’s how blockchains work; we don’t control it. The /proof page only displays addresses, tx hashes, CIDs, and digests that are already public on-chain.
We read from public RPC endpoints (PublicNode for Sepolia, the public 0G Galileo RPC, the Base Sepolia public RPC). Your wallet may also use its own RPC. RPC providers can in principle observe which addresses and contracts you query.
Resolving any *.ledger.eth name routes through our CCIP-Read gateway at resolver.fierypools.fun. The gateway logs the requested name and timestamp in process memory for observability; it doesn’t persist or share that log.
We don’t sell or share data with anyone, because we don’t collect any.
Issues, takedowns, or questions: @gabrielaxyeth on X.
