Privacy policy

There is no sign-up. v4 Builder never asks for a name, an email address or a phone number, runs no analytics and no advertising, and sets no tracking cookie. Nothing you do on the site is tied to a profile, because there is none to tie it to.

When you connect a browser wallet, the site learns your public address so it can read balances, price a deploy and prepare the transactions you are about to sign. Your wallet signs; the site never sees a private key or a seed phrase, and cannot move anything on its own.

A wallet address and everything it sends are public on the chain by design, readable by anyone through any explorer. That is a property of the chain, not something v4 Builder can change or delete.

The recipe you are building stays in your browser: the builder keeps your current draft in local storage, under v4builder:recipe, so a reload does not lose it. It does not leave your device while you edit it.

The Solidity is written in your browser. When you ask for a proof, the recipe is sent to the site's server, which compiles it and simulates it on the chain for that request, then answers. The recipe carries the numbers you chose and any addresses you typed into it, and nothing about you.

When you deploy a hook, its recipe is written on chain in the factory's Built event, next to your address. From then on it is public and permanent, like every transaction. Right after a deploy, the builder publishes the hook's source on Sourcify, a public verification service, with its creation transaction.

Like any website, the host that serves v4 Builder records standard request logs (IP address, time, page or endpoint, browser string) to keep the service running and to stop abuse, and keeps them for a short period. The proof endpoint counts requests per IP address over one minute to hold each address to 12 proofs a minute, and keeps no count after that.

Your browser reads the chain through a public RPC endpoint. That provider sees the requests it serves, as any web server does, under its own policy.

• Your wallet extension, under its own terms and policy.
• The block explorer and Sourcify, when you open a link to them or publish a source.
• v4 Marketplace, a separate site of the same team, when you list a stacked hook. Its own privacy policy applies there.

Request logs and the per-minute count rest on our legitimate interest in running a safe service. Reading your address and preparing transactions is done because you ask for it, to provide the service you are using. Nothing is sold, rented or shared for advertising.

You may ask to access the personal data we hold about you, to have it corrected or erased, to restrict or object to its processing, and to receive it in a portable form. In practice we hold almost nothing: no account, no profile, only short-lived request logs. What is on chain is outside anyone's power to erase.

Send a request through our X account. You may also complain to the data protection authority where you live.

If this policy changes, the new version is posted here with its date. See also the terms of use and the cookies policy.