Closebook · Legal
Cookies and local storage
Closebook sets no cookies and runs no analytics. It keeps your session and four interface preferences in your browser's local storage — this page lists all five by name.
Last updated 10 September 2026
Closebook does not set cookies
That is the short version, and it is unusual enough to state first. Browsing closebook.io sets no cookies — not for analytics, not for advertising, not for measuring you. There is no consent banner on this site because there is nothing to consent to.
What Closebook does use is your browser's local storage: a small store, on your device, that is never transmitted with your requests the way a cookie is. It holds your session and a handful of interface preferences, listed below.
Exactly what we keep in your browser
| Key | What it is for | How long |
|---|---|---|
| sb-<project>-auth-token | Your signed-in session, written by our authentication provider. Without it you would be signed out on every page load. | Until you sign out or it expires |
| nova.workspace | Which workspace you were last looking at, so a reload does not dump you somewhere else. | Until you clear it |
| nova.entity | Which entity you had selected inside that workspace. | Until you clear it |
| nova.sidebar.collapsed | Whether you collapsed the sidebar to the icon rail. | Until you clear it |
| nova-mapping-presets | Column-mapping presets you saved while importing a statement, kept locally so they survive a refresh mid-import. | Until you clear it |
All five are strictly necessary or a convenience you chose by using the interface. None of them profile you, and none are shared with anyone.
No analytics, no trackers, no pixels
Closebook loads no analytics library, no tag manager, no session recorder, no advertising pixel and no social embed. We do not know which pages you visited or how long you spent on them.
The only third-party request a page makes is to Google Fonts, which serves the two typefaces the interface uses. That request is made by your browser and Google may log the IP address that made it, as it does for any font request; nothing about you or your workspace is sent with it.
Our server keeps ordinary request logs — the kind any web server keeps to stay debuggable — and those are covered in the privacy policy.
Clearing it
Signing out removes your session. To clear the rest, use your browser's "clear site data" for closebook.io, or clear local storage in developer tools. Nothing breaks permanently: you will simply be signed out and your interface preferences will go back to their defaults.
Blocking local storage entirely will stop you from staying signed in, because that is where the session lives.
If this changes
If we ever add analytics or anything that sets a cookie, we will update this page before it ships, and where the law requires consent we will ask for it properly rather than assuming it. Questions: privacy@vizio.ai.