Privacy Policy
Last updated: 12 August 2026
The short version
Hero Builder does not collect anything about you. There is no account to make, no server that stores your work, and no tracking of any kind. One item is saved inside your own browser so that reloading the page does not lose your build. Nothing else.
If that is all you wanted to know, you can stop reading here. The rest of this page explains it in detail, and is honest about what will change when advertising is added later.
Who this is
Hero Builder (herobuilder.io) is a free build planner for the game Hero Siege. It is run by one person, not a company: OWNER NAME TO BE ADDED.
Hero Builder is an unofficial fan tool. It is not affiliated with, endorsed by, or connected to Panic Art Studios, the developer of Hero Siege.
What the site collects about you
Nothing.
That is not a figure of speech, it is a consequence of how the site is built. Hero Builder is a set of static files: HTML, a stylesheet, some JavaScript, and game data. There is no application server, no database and no code running anywhere except inside your own browser. There is nowhere for your information to be sent, and nothing to store it in.
So, specifically, there is:
- no sign up, no login, and no user account
- no contact form, comment box, or newsletter
- no email address, name, or payment detail requested at any point
- no profile, no visitor ID, and no fingerprinting
- no sale or sharing of personal information, because none is held
The one thing saved on your device
The site saves a single entry in your browser's local storage, under the key herobuilder.build.v1.
What it holds
Exactly the same short piece of text that a share link carries, and nothing more: the description of the build you are working on, such as the class, the level, the gear, and the points you have spent. It contains no identifier, no timestamp, and nothing about you or your device.
What it is for
So that closing the tab or reloading the page does not throw away your work. That is its whole purpose. It is a functional store, not a tracking one: nothing reads it except the planner running in your own browser, and it is never transmitted anywhere.
How to get rid of it
It is yours, and you do not have to ask anyone to delete it:
- Clear site data for herobuilder.io in your browser settings. In most browsers this is under Privacy, then site or cookie settings. This removes the saved build immediately.
- Use a private or incognito window, where it is discarded when you close the window.
- If a build ever fails to load, the page offers a Start fresh button, which deletes the saved build and reloads with an empty planner.
If your browser has storage disabled, the planner still works. It simply will not remember your build between visits.
Your build stays in your browser
This one is worth stating plainly, because it is unusual.
When you build something in the planner, the build is stored in the part of the address after the # symbol, which is called the fragment. Web browsers never send the fragment to the server. It is handled entirely on your machine.
The practical result: when you share a build link, the build itself is never sent to us. We do not receive it, cannot log it, and have no copy of it. There is no gallery of everyone's builds sitting on a server somewhere, because there is no server.
The other side of that is worth knowing too. Because the build travels inside the link, anyone you give the link to can open the build, and so can anyone they pass it on to. Treat a build link as public once you have shared it.
What your browser downloads
When you open the planner, it downloads its game data files from herobuilder.io itself. That is the only kind of request the site makes.
No third party is contacted at any point. There are no external fonts, no embedded videos, no social media buttons, no comment platform, and no third-party scripts of any kind. The site is served with a Content Security Policy that blocks outside content rather than merely avoiding it, so third-party code cannot run here even if something tried to insert it.
Cookies
The site sets no cookies at all. There is no cookie banner because, at present, there is nothing to ask you about.
Hosting and server logs
The site is hosted on Cloudflare Pages. This is the one place where data about your visit genuinely is processed, so it should not be glossed over.
Like every web host, Cloudflare receives the technical information your browser sends with each request. That normally includes your IP address, your browser and operating system (the user agent), which file you asked for, and when. Cloudflare uses it to deliver the site and to protect it against attacks and abuse.
That processing is Cloudflare's, as the infrastructure provider. We do not receive these logs, do not store them, do not have an analytics product reading them, and do not build any profile from them. What Cloudflare does with them is described in the Cloudflare privacy policy.
Analytics
There is no analytics installed on this site today. No page view counter, no heatmap, no session recorder, and no visitor statistics product of any kind.
Advertising
No ads are served on this site today, and no ad network is contacted.
You may notice empty boxes in the layout where ads would sit. Those are deliberately reserved space and nothing more. They hold their size so that adding advertising later cannot make the page jump around while you are reading it. Nothing is loaded into them.
Planned: advertising, and possibly analytics
None of this is in place yet. It is set out here so that the plan is not a surprise, not because it is happening now. Everything above describes the site as it actually is today.
The intention is to add advertising, most likely Google AdSense, to help cover the cost of running the site. Some form of analytics may follow.
Being straightforward about what that would mean:
- It will introduce cookies, or similar storage, placed by the advertising provider rather than by us.
- The advertising provider will receive information about your visit directly, including your IP address, and may use it to select ads.
- For visitors in the EEA and the UK, a consent mechanism will be shown before any non-essential cookie is set, and refusing will be a real option rather than a formality.
- This page will be rewritten to describe exactly what is used, and the "last updated" date at the top will change, before any of it goes live. It will not be switched on quietly and documented afterwards.
Two things will not change: your build will still live in the URL fragment and still never be sent to us, and the autosave will remain a single first-party key holding nothing but the build.
Your rights
Rather than reciting a list of rights copied from somewhere else, here is the honest position.
We hold no personal data about you. There is no account, no record, and no file with your name on it, so a request to access, correct, export, or delete your personal data would find nothing to act on. This is not a refusal, there is simply nothing there.
The only data connected to you is the single autosave entry in your own browser, described above. You do not need our permission or cooperation to read or delete it: it is on your machine and it is under your control.
Server logs are held by Cloudflare as the host, not by us, and are governed by the Cloudflare privacy policy linked above.
If advertising is added, this changes, because the advertising provider will process data about you. This section will be rewritten at that point to say who they are and what you can do about it.
Children
The site collects no personal information from anyone, of any age, including children.
Changes to this policy
This page will be updated when the site changes, and in particular before advertising or analytics is introduced. The date at the top always reflects the current version. Material changes will be made here before the change takes effect, not after.
Contact
Questions about this policy, or about how the site works, can be sent to: CONTACT EMAIL TO BE ADDED