Cookie Policy
Web version (novaboard.app)
- PostHog — anonymous usage analytics, proxied through our own server. Until you opt in it runs cookieless: nothing is kept on your device and the visit is counted from a code our server derives fresh each day, so every visit is separate and anonymous. Saying yes lets PostHog store an id in a cookie and in localStorage, which is what ties your visits together, and turns on session recording.
- Google Ads — conversion tracking that runs only during an active ad campaign and only after you opt in through the consent banner. Sets cookies from google.com. Decline to keep it off.
- Cloudflare — may set infrastructure cookies for performance and DDoS protection.
What we store on your device
Your artwork and your preferences (theme, tool settings) live in your browser's storage. They stay on your device and are never sent to our servers.
Analytics also keeps a few small counters in your browser's localStorage, and those are written only after you allow analytics below. Until then they are held in memory for the current page and disappear when you close the tab, so nothing about your visits is kept on your device. They never leave your device except as anonymous properties on usage events, and we never save them on our servers.
- Session counts: how often and how recently you open Novaboard, so we can tell new visitors from returning ones.
- First visit details: the source, page, and date of your first visit, so we can see which channels bring people in.
- Editor progress: whether you have opened the editor and drawn anything, so we can measure how many visitors start creating.
- Prompt history: whether you have seen or closed the Discord and feedback prompts, so we do not keep asking.
- Visit count: how many separate times you have opened Novaboard and when the last one was, so those same prompts wait until you have been around a while before asking. It is one number and one date, and it holds nothing that identifies you. The date stays on your device; the number is attached to the prompt events only if you allow analytics.
- Experiment variant: which version of a page element you were shown (for example the landing video), so an A/B test measures each visitor consistently.
Prompt history, the visit count, and experiment variants are part of how the app behaves, so they are kept either way, and none of them identifies you. Prompt history stays on your device. The visit count does too, unless you allow analytics, and then it rides along on the prompt events so we can tell a first-week ask from a fiftieth-visit one. Your experiment variant is sent with the anonymous event that records which version you saw, which is what makes the test readable at all. The analytics counters, cookies, session recording, and cross-visit identification all stay off until you allow them in the section below.
Desktop and Itch.io versions
No cookies are used.
Manage your choice
You haven't made a choice yet.
Opt-out
You can also clear cookies via your browser settings. Disabling cookies may disable analytics but will not affect the editor's functionality.