Legal
Privacy
Last updated 17 September 2026.
1What this site stores about you
The site does not use advertising analytics or tracking pixels. If you create or access an embedded wallet, thirdweb processes your email or Google sign-in to authenticate you and provide the wallet. Its SDK stores session information in your browser so you can reconnect. CO-FEE stores a local connection preference and displays your public wallet address. Your private key is not sent to the CO-FEE server. You can disconnect from the wallet menu. Authentication is subject to the thirdweb privacy policy.
2What is public by nature
Everything on chain is public: the token, its fees, each vault's balance and its collections. The repository is recorded by its id and shown by its name. Payouts are published with their amount, the address or sponsor page paid and the reference of the proof they relied on, so that anyone can check them, or dispute them.
3What your browser asks of GitHub and Hugging Face
When you type a repository into the launch form, your browser asks the public API of GitHub and of Hugging Face whether it exists. Those requests go from you to them directly, not through us, and each site applies its own rate limit to your address. CO-FEE keeps nothing from them.
4What CO-FEE keeps in order to pay out
The FUNDING.json file on the repository's default branch, on GitHub or Hugging Face, or its FUNDING.yml file on GitHub, and the address or sponsor page it names. For a sponsor page, the receipt of the payment, which is published with the transfer. Nothing else is asked, and nothing at all is asked before a payout is due.
5Removal
Maintainers who do not want their project to appear can ask to be removed. The name comes off the site. Records on chain cannot be erased by anyone.
6Contact
Through the account linked in the footer.