Privacy

What the site sees, and what it keeps

No accounts

There is no sign-up. You connect a wallet; the site reads public chain state for that address. Disconnecting ends the session.

What passes through our servers

  • RPC proxy. Read and broadcast calls are forwarded to an RPC provider so its key stays off the client. Requests are rate-limited per IP and not logged beyond what is needed to operate the limiter.
  • Upload relay. Launch metadata and images you choose to publish are relayed to permanent storage. Anything you publish is public and permanent.
  • Database reads. Pages read gate grades, pool snapshots and mint registrations written by the engine. These are derived from public chain and market data.

What the engine records

Loan and order lifecycle state indexed from the chain, attestation logs, gate grades and a notification outbox for borrowers who opt in. Wallet addresses are public keys; the engine stores no names, emails or device identifiers unless you provide a contact for notifications, in which case it is used only for that purpose.

Cookies and analytics

No advertising trackers. The site may use local storage for interface preferences such as the last wallet used. No third-party analytics scripts are loaded.

Third parties

Your browser also talks directly to the launch router, storage gateways and price APIs listed in the site's content-security policy. Their privacy practices are their own.

Requests

Chain data cannot be deleted. For anything held off chain that identifies you, contact the operator through the source repository linked in the footer.