Privacy Notice
Last updated 2026-09-15
1. Who is responsible
Section titled “1. Who is responsible”Blockroad d.o.o., registered in Croatia under number 66566698686, is responsible for the personal data described in this notice. Questions and requests about your data go through the contact form on blockroad.hr.
2. What this notice covers
Section titled “2. What this notice covers”This notice covers the website at coffer.bond, the app, the documentation at docs.coffer.bond and the server behind the app. It does not cover your wallet or the Ethereum network. Those are run by others. The connector software the app loads to reach your wallet is covered in section 5.
3. What we process and why
Section titled “3. What we process and why”| Why we process it | What we process | Legal ground |
|---|---|---|
| Running the service, limiting abuse, finding faults | The time, the method, the path you requested, the result and how long it took. Your IP address in memory only, for rate limiting | Our legitimate interest |
| Publishing the listings and offers you sign | Your wallet address, the bond, the price, the expiry, your signature | Doing what you asked when you signed |
| Showing you public network data about your address | Your wallet address and its public chain data | Our legitimate interest |
| Keeping your offer fillable | For an offer: your WETH balance and the amount you have approved to the marketplace, re-read while the offer is live. For a maker whose address holds code: whether that code still approves the message | Doing what you asked when you signed |
| Remembering your choice of theme | The choice itself | Our legitimate interest |
| Remembering that you closed the claim notice | Your wallet address and the amount shown when you closed it, kept in your browser only | Our legitimate interest |
| Counting visits, if you accept it | A random number that stands for your browser, your IP address, the page you opened and an approximate location | Your consent |
Server logs. The server behind the app can log a request with the time, the method, the address you requested, the result and how long it took. In normal operation it logs only requests that failed. It does not record your IP address or your browser. It uses your IP address in memory to limit the number of requests per minute and does not store it. The web server in front of it and of the RPC proxy keeps no record of individual requests. Its own error log can hold an IP address when a connection fails before the request reaches us, for example a rejected TLS handshake. We use these logs to run the service, to limit abuse and to find faults.
Your wallet address. When you connect a wallet, the app reads public data about that address from the network and from our server. When you create a listing or an offer, you sign a message and the app sends it to our server. The server stores the signed message and the details it commits to: your address, the bond, the price, the expiry, the sequence numbers of the message, your signature and the time you sent it to us. Alongside it we record what happened to the listing or offer, whether it was filled, cancelled, expired or replaced by a newer one, and the transaction and the other party’s address if it was filled. We show the listing or offer to other users while it remains valid. It stops being shown when it is filled, when you cancel it, when it expires, or when something changes on the network that means it can no longer be accepted. We do this because you asked for it when you signed. Our server also keeps a copy of public data from the network, such as which address holds which bond. That data is public on the network already.
Checks that keep your offer fillable. An offer can only be filled if you still hold enough WETH and still allow the marketplace to spend it. While your offer is live we re-read those two numbers from the network and keep the latest pair, so that we do not show an offer nobody can accept. The pair is deleted once the offer is no longer active. If your address holds code, meaning a smart contract wallet, we also ask that contract whether it still approves the message, and keep its last answer for the same reason. That answer stays with the listing or offer and is deleted with it.
Our own cookies. The site stores your choice of light or dark theme in one cookie named coffer-ui-theme, and your answer to the analytics question in one named coffer-analytics-consent. Both are set for coffer.bond and its subdomains, both last one year, and neither holds anything except the choice itself. They track nothing.
Local storage. When you close the notice that says you have ETH to claim, the app keeps one entry in your browser’s local storage, holding the wallet address and the amount shown at the time. It is there so the notice can come back when the amount changes and stay away until then. The entry never leaves your browser, and you can delete it in your browser’s site data.
Analytics. If you accept it, we use Google Analytics to count visits and to see which pages people open. It sets its own cookies, named _ga and _ga_ followed by the code of the property, which hold a random number that stands for your browser. Google receives that number, your IP address, the page you opened and an approximate location worked out from the IP address. We use this only to understand how the site is used, never to identify you and never for advertising. Nothing is sent and no analytics cookie is set before you accept. The legal ground is your consent. You can change your answer at any time with the Cookies link at the bottom of coffer.bond, and one answer there covers the app and the docs as well. You can also delete the cookies in your browser.
4. What we do not do
Section titled “4. What we do not do”We have no user accounts and we do not ask for your name, email address or any other contact details. We use no advertising, and we do not follow you across other websites. We do not sell or rent data. Analytics runs only if you accept it, and the site works the same if you decline.
5. Who else handles the data
Section titled “5. Who else handles the data”Some companies handle data for us or receive it when you use the service.
- Vercel hosts the website, the app and the documentation. Your browser sends it your IP address and the pages you open when it loads them.
- Hetzner provides the machines that run the server behind the app and the RPC proxy.
- Infura is the fallback RPC provider. If our own node does not answer, the app sends your chain requests to Infura, which then receives your IP address and the requests. Infura does not work for us and acts under its own privacy notice.
- Google runs the analytics described in section 3, but only if you accept it. It receives the data named there.
- The wallet connectors in the app are software from MetaMask, Coinbase, Rainbow and WalletConnect. When you connect through one of them, that software talks to its maker’s servers, which receive your IP address and the details of the connection, and MetaMask and WalletConnect also count usage on their own servers. The WalletConnect window loads a font from Google. Each of these companies acts under its own privacy notice.
We have data processing agreements in place with the companies that handle personal data on our behalf.
Hetzner is in Germany. Vercel, Infura, Google and the wallet connector makers are in the United States. Vercel and Google are certified under the EU-US Data Privacy Framework, which the European Commission has recognised as providing adequate protection. Where a provider that works for us is not covered by that framework, the transfer is made under the standard contractual clauses approved by the European Commission. Infura and the wallet connector makers do not work for us. They receive data only because the app falls back to Infura or because you chose their wallet.
6. Data on the network
Section titled “6. Data on the network”Everything you do on the Ethereum network is public and permanent. That includes your address, your transactions, the bonds you hold and the listings and offers that were filled. We cannot change or delete anything on the network, and neither can anyone else.
Public network data can be analysed, and combining it with data from elsewhere can link an address to a person. That is a property of public blockchains rather than of Coffer, and neither we nor anyone else can undo it.
7. How long we keep data
Section titled “7. How long we keep data”Server logs are deleted after 90 days. Signed listings and offers are kept while they are valid, and for 30 days after they stop being valid, for support and fault finding. The balance and allowance pair is deleted once the offer is no longer active. The answer from a contract wallet is part of the stored listing or offer and is deleted with it. Analytics data is deleted after 14 months. The copy of public network data stays as long as we run the service.
8. Your rights
Section titled “8. Your rights”You have the right to ask what data we hold about you, to have it corrected or deleted, to limit how we use it, to object to our use of it and to receive a copy of it. Where we rely on your consent, you can withdraw it at any time. We do not make automated decisions about you and we do not profile you. These rights apply to data on our server, not to data on the network. To use these rights, use the contact form named in section 1. You can also complain to the Croatian Personal Data Protection Agency (AZOP) or to the authority where you live.
9. Children
Section titled “9. Children”The service is intended for a general audience and is not directed at children. Under the GDPR a child is anyone under 16. If you are under 16, do not send us personal data. We do not knowingly collect it. If you are a parent or guardian and believe a child has given us personal data, use the contact form named in section 1 and we will delete it.
10. Changes
Section titled “10. Changes”We can change this notice. The date at the top shows the current version.