Cookies and local storage
Cookies and local storage
Last updated: August 28, 2026 - version 1.2
What this covers
This page lists everything Stackable stores in your browser when you use stackable.studio, what each item is for, and how long it stays.
Most of it is not technically a cookie. Browsers give sites several ways to keep small pieces of data, and we mostly use local storage rather than cookies. The rules are the same either way, so we list all of it here and call the page "cookies" because that is the word people search for.
The Stackable app on your phone is covered by the privacy policy instead. This page is about the website.
Your choice
When you first visit, a bar at the bottom of the page asks whether we may measure how the site is used. You can accept or reject, and rejecting is one tap in the same place - we do not make it harder.
You can change your mind at any time: select Cookie settings in the footer.
If your browser sends a Global Privacy Control signal, we treat that as a rejection and do not show the bar at all.
Essential
These are needed for the site to work. They cannot be turned off, because without them there is no working site to consent to.
"Until cleared" means the item stays until you clear this site's data in your browser. None of it expires on its own.
| Item | Type | Purpose | How long |
|---|---|---|---|
sb-<project>-auth-token | Local storage | Your anonymous session. It is what lets you make a build without creating an account, and what keeps a build yours while you are on the page. | Until cleared |
stackable.consent.v1 | Local storage | Your choice on this page, so we do not ask again on every visit. | Until cleared |
stackable.webCreate.consent.v1 | Local storage | Your separate agreement to AI processing, which is required before a build can be made. | Until cleared |
stackable.deviceId | Local storage | A random id used only to count free builds per browser, so one visitor cannot exhaust the free allowance. It is not linked to your identity. | Until cleared |
stackable.webCreate.quota.v1 | Local storage | The count of builds you have started today, so the free allowance can be shown and applied. | Daily |
cf_clearance, __cf_bm | Cookie | Set by Cloudflare's bot check when you submit something - an upload, or the notify-me form - to confirm you are a person. We do not read them. | 30 minutes |
We also count page views using Cloudflare Web Analytics. It is listed here as essential because it sets nothing in your browser at all - no cookie, no local storage, no identifier - and cannot recognize you or follow you between sites. It tells us how many people opened a page and which site sent them, and nothing about who they are.
Analytics
Off unless you accept.
| Item | Type | Purpose | How long |
|---|---|---|---|
AMP_… | Local storage | Our analytics tool's own record of a random id for your browser and the current visit, so the steps of one visit can be read as one visit. | Until cleared |
stackable.attribution.v1 | Local storage | Which link or ad brought you here the first time, and most recently - so we can tell which ones are worth running. It holds the campaign tags from the link you arrived on, not anything about you. | Until cleared |
It records which journeys you start and finish against that random id, so we can see where people get stuck. It never includes your photos, the text you write, or your name or email.
The events go to Amplitude, in the EU. Nothing is sent, and the tool is not even downloaded, unless you have accepted - decline and the code never loads.
Marketing
Off unless you accept.
| Item | Type | Purpose | How long |
|---|---|---|---|
| None | - | We do not run ads and set nothing for advertising. If that changes, this table will list each item before it ships, and it will only run if you have accepted. | - |
Storage set by pages you visit from here
Selecting a link to the App Store, or to one of our social accounts, takes you to a site we do not control, and that site may set its own storage under its own policy. We do not share your choice on this page with them.
Turning it off yourself
Rejecting on the bar stops everything optional. Beyond that, every browser lets you clear or block site data in its settings - blocking it entirely will sign you out of your anonymous session and lose any build that was not claimed into an account.
Contact
Questions about this page: privacy@stackable.studio