What this browser is holding
One record in this browser's local storage that the design tools read and write. Never uploaded, never synced.
What this browser is holding
One record, in this browser's local storage, that the design tools read and write. It is never uploaded, never synced, and clearing your site data deletes it.
Where each thing came from
What is stored, and what is not
One JSON object under a single key. It holds the last colour you used, a palette, a ramp, a theme's roles and a token set — whatever the tools you have used have written.
It is not a sync service. There is no account, no server and no copy anywhere else. A different browser, a different device or a private window is a different workspace, and clearing site data removes it entirely.
Nothing is put in a URL by this page. The palette studio can build a share link containing colours, and that is the only thing that ever travels — and only when you press the button.
Export before you clear if any of it matters. There is no undo and no recovery.
Why local storage rather than an account
An account would mean a server, a server would mean your work leaving your machine, and the whole claim of this category is that it does not. The trade is real: a workspace that lives in one browser is easy to lose.
The export is the mitigation. A downloaded file is portable, diffable and yours, and it can be loaded back into any browser.
What travels between tools
A palette made in the studio arrives in the ramp generator, the theme generator and the SVG recolourer. A theme's roles arrive in the token generator. Nothing else moves, and nothing moves without you having used the tool that wrote it.