Cookie Policy
Every cookie Builder Hut sets. Site owners and template developers each have their own section below.
Last updated 12 September 2026
Site Policy
Cookies are small files a site stores in your browser. This policy lists the ones Builder Hut uses, on our own applications and on the sites published with it.
1. On Builder Hut’s own applications
When you sign in to builder-hut.com or app.builder-hut.com, our identity provider Clerk sets session cookies. These are strictly necessary — without them you cannot stay signed in.
We also store your light or dark theme preference and, in the editor, which design system you last had selected.
If you allow it in the cookie banner, FullStory also sets cookies on our applications to group the pages of one visit and to recognise your browser on later visits. The banner’s answer is itself stored in a cookie, so you are not asked again on each of our applications.
2. On sites published with Builder Hut
Sites built on the platform set the cookies below. As the site owner you should reproduce this list in your own privacy notice.
3. The cookies in full
| Cookie | Purpose | Lifetime | Where |
|---|---|---|---|
| Clerk session cookies | Keeps you signed in. Strictly necessary. | Managed by Clerk | Builder Hut apps |
| bh_vid | Pseudonymous visitor identifier used to count returning visitors in first-party analytics. Not readable by JavaScript. | About 2 years | Published sites |
| bh_sid | Groups events into a single visit and prevents the same visit being counted twice. Not readable by JavaScript. | 30 minutes, extended while browsing | Published sites |
| bh_vw | Records your viewport width so the server can render the right layout on first paint. Functional. | Short-lived | Published sites |
| bh_sds_* | Remembers the selected design system. Functional. | Short-lived | Editor and published sites |
| Theme preference | Remembers light or dark mode. Functional. | Persistent | All applications |
| bh_analytics_consent | Remembers whether you allowed or declined analytics recording, so the banner does not ask again. Shared by builder-hut.com and our applications. Functional. | 12 months | Builder Hut apps |
| fs_uid, fs_cid, fs_lua | Set by FullStory, and only after you allow analytics. Recognise your browser across visits, record your consent state, and group activity into one session. Analytics. | Up to 1 year | Builder Hut apps |
4. Local storage
Some information is kept in your browser’s local storage rather than in cookies, and is never sent to us automatically.
- Your shopping cart on a published site, so it survives a page reload.
- Your storefront customer session token, if you sign in to a site as a shopper.
- Interface preferences such as currency selection and editor panel positions.
- If you allow analytics, a note of which account FullStory last linked to on this browser, so that signing out ends the link.
5. Consent
On our own applications we ask before any analytics recording starts. FullStory is not loaded until you choose Allow in the cookie banner, and if you choose Decline — or never answer — nothing is sent to it. You can change your answer at any time from “Cookie settings” in the footer or the dashboard sidebar; declining after allowing stops recording and removes FullStory’s cookies from your browser.
On sites published with Builder Hut, the platform does not add a consent banner by itself. If you publish a site and the law that applies to you or to your visitors requires consent before analytics or functional cookies are set, obtaining that consent is your responsibility as the site owner. This is set out in our Terms of Service.
6. Managing cookies
Every major browser lets you view, block, and delete cookies in its settings. Blocking the strictly necessary authentication cookies will stop you being able to sign in. Blocking the analytics cookies affects only the accuracy of visit counts; the site continues to work normally.
7. Contact
Questions about cookies can be sent to contact@builder-hut.com.
Developer Policy
Cookies are small files a site stores in your browser. The developer portal uses very few — it is an authoring tool behind a login, with no advertising. Analytics cookies are set only if you allow them.
1. The cookies we use
| Cookie | Purpose | Lifetime |
|---|---|---|
| Clerk session cookies | Keeps you signed in to the portal. Strictly necessary — without them you cannot use the portal at all. | Managed by Clerk |
| Theme preference | Remembers whether you chose light or dark mode. Functional. | Persistent |
| bh_sds_* | Remembers which design system you last had selected in the editor. Functional. | Short-lived |
| bh_analytics_consent | Remembers whether you allowed or declined analytics recording, so the banner does not ask again. Shared with builder-hut.com and the console. Functional. | 12 months |
| fs_uid, fs_cid, fs_lua | Set by FullStory, and only after you allow analytics. Recognise your browser across visits, record your consent state, and group activity into one session. Analytics. | Up to 1 year |
2. Analytics and advertising
We do not set advertising cookies on the developer portal. If you choose Allow in the cookie banner, we use FullStory to understand how the portal is used — section 10 of the Developer Privacy Policy describes what it records. Nothing is recorded until you allow it, and you can change your answer at any time from “Cookie settings” in the sidebar; declining after allowing stops recording and removes FullStory’s cookies.
Note that the first-party visit analytics described in the Site Policy section above apply to live sites published on the Builder Hut platform — not to this portal. If you preview a template on a templates subdomain, that preview is served by the platform and may set those cookies.
3. Local storage
Some interface preferences — editor panel positions and sizes, sidebar state — are kept in your browser's local storage rather than in cookies, and are never sent to us automatically.
If you allow analytics, the portal also keeps a note of which account FullStory last linked to on this browser, so that signing out ends the link.
4. Managing cookies
Every major browser lets you view, block, and delete cookies in its settings. Blocking the Clerk authentication cookies will stop you being able to sign in to the portal.
5. Contact
Questions about cookies can be sent to contact@builder-hut.com.
Related policies