Privacy policy.
BuildSite has no accounts, no database and no server of its own. Almost everything below is a description of what other parties see, because that is where the only real data flows are.
BuildSite (“BuildSite”, “we”) is a static web application. It is delivered as plain HTML, CSS and JavaScript from IPFS and from static hosting, and it runs entirely in your browser. There is no BuildSite backend, no user account, no login and no database in which we could store anything about you.
What we do not collect
- No account, email address, name or password — there is nothing to sign up for.
- No analytics, telemetry or product-usage tracking. Wallet-connection analytics are explicitly disabled in our Reown AppKit configuration.
- No advertising, no tracking pixels, no third-party marketing scripts.
- No cookies set by BuildSite itself.
What stays in your browser
The wizard keeps your work in progress — the ENS name you chose, the template you picked and the content you typed — in your browser’s own storage so a refresh does not lose it. It never leaves your device until you publish. Clearing your browser storage deletes it.
Your wallet connection is managed by Reown AppKit and WalletConnect, which store session data in your browser so the connection survives a reload. Disconnecting your wallet clears it.
What third parties see
Using BuildSite necessarily involves services we do not control. Each has its own privacy policy, and none of them acts on our instructions in respect of your data.
Your wallet, and WalletConnect / Reown
Connecting a wallet exposes your public Ethereum address to this application. If you connect over WalletConnect, relay servers operated by Reown carry the encrypted session between your wallet and this page.
Ethereum RPC providers
To read your ENS names, resolvers and records, and to submit transactions, the app makes requests to an Ethereum JSON-RPC endpoint. That provider can see your IP address, your wallet address and the calls being made.
Pinata and IPFS
When you publish, the generated HTML page — and any images you uploaded into it — are sent to Pinata and pinned to IPFS. See the section below on permanence.
Whoever serves you this page
Standard web server and gateway logs (IP address, user agent, requested path) may be kept by whichever host or IPFS gateway delivered this page to you. We do not operate those gateways and do not receive their logs.
Publishing is public and permanent
This is the most important thing on this page, so it is stated plainly: anything you put into a site and publish becomes public, permanent and impossible for us to delete.
- Your page is pinned to IPFS. IPFS content is public by design and addressed by its hash. Anyone who has the address can fetch it.
- Once content has been retrieved by other nodes it can be re-pinned by anyone, anywhere. Unpinning our copy does not remove it from the network.
- Writing the contenthash to your ENS name is an Ethereum transaction. It is public, permanent and attributable to your address.
Do not put anything into a template that you would not want published to a permanent, worldwide, un-deletable index. That includes personal contact details, photographs of other people, and anything you are not free to distribute.
Your rights, and their practical limits
Where data protection law applies to you, it grants rights of access, correction and erasure. We can honour those requests only in respect of data we actually hold — and we hold none. We cannot delete content from IPFS, we cannot alter or remove an Ethereum transaction, and we cannot act on your behalf against a third party’s logs.
What you can do: point your ENS contenthash at different content, or clear it, from your own wallet at any time. Your name stops resolving to the old page, though the old page may remain reachable by its IPFS address.
Children
BuildSite is not directed at anyone under 18 and should not be used by them.
Changes
We may update this policy. The date at the top of this page is the version in force. Because the site is published to IPFS, earlier versions may remain reachable at their own addresses; the copy served at buildsite.eth is the current one.
Questions about any of this? Reach us on X — there is no support inbox, because there are no accounts to support.
@ENSbuildsite