Privacy

Public proof, limited data.

What Admon reads

Anyone can check a public GitHub username without signing in. For a public preview, Admon reads that profile's public repositories, public commit activity, stars, languages, account age, and contribution timing. After you sign in with GitHub, Admon also confirms your GitHub identity. It records your connected wallet address and mint transaction only when you mint.

What Admon does not read

Admon does not request access to private repositories, private source code, GitHub write permissions, or your wallet private key. GitHub OAuth uses the read-only read:user scope.

Why GitHub sign-in is required

Checking a username creates a public preview only. It does not create a database record, mint authorization, or NFT. GitHub OAuth is required to mint because it confirms that the person requesting the record controls that exact GitHub account. This protects builders before the record is bound to a wallet.

Cookies

Admon uses two strictly necessary, HTTP-only cookies only during GitHub OAuth: admon_github_oauth_state protects the sign-in flow for up to 10 minutes, and admon_github_session keeps your signed-in GitHub identity for up to 7 days. They are not used for advertising, cross-site tracking, or profiling. You can clear the session by disconnecting GitHub or clearing browser cookies.

Builder connections

If you send or receive a builder connection request, Admon stores the two builder profiles, request status, and response time. After both builders accept a connection, Admon stores the private messages they choose to send in that conversation. Requests and conversations are visible only to the two connected builders and are not used for advertising.

Public records

Once minted, the build record, its traits, wallet address, transaction, and NFT metadata are public by design. The Garage and Monad are public systems, so do not mint information you do not want to be publicly associated with your wallet.