Cookie policy

A cookie is a small piece of text that a website asks your browser to keep and send back on the next request. Some cookies are needed for a site to work at all — for example, to remember that you are signed in. Others exist to measure how a site is used, and others again to advertise. Datwise uses the first two kinds and none of the third.

Neither of these can be turned off while you use Datwise: one is your session, the other is your language.

Datwise uses Google Analytics 4 to see how many people come, which pages and features they use, and where they give up. Two cookies come with it. Both are set on this website, both stay in your browser, and neither is an advertising cookie: the tag is loaded with Google’s advertising uses refused, so no advertising cookie is set and nothing measured here can be used to target you. Section 6 says what Google receives and what it does not.

Two of these four cookies are strictly necessary and Datwise cannot work without them: one signs you in, the other remembers your language. The two analytics cookies are not necessary, and Datwise does not show a consent banner before setting them — so this page will not pretend that you were asked. You can refuse them at any moment: any ordinary content blocker stops Google Analytics from loading, and blocking cookies for this site does the same. Datwise behaves exactly as before if you do — nothing is withheld, nothing is slower, and nothing asks you again. If you think we should ask first, write to info@getdatwise.com; it is a decision we are willing to revisit.

Separately from cookies, Datwise keeps a few preferences in your browser’s own storage. They stay on your device, none of them is sent to our servers, and none of them identifies you. This is the whole list:

• theme — whether you chose light or dark mode.
• datwise-dark-style — which dark palette you picked.
• datwise:workspace — the workspace you had open last, so you return to it instead of choosing again.
• datwise:announcements and datwise:brag-dismissed — the announcements and prompts you have dismissed, so you are not shown them twice.
• datwise:tours — the product tours you have already seen.
• datwise:ref and datwise:plan-link — a referral or plan link code, if you arrived through one, so the right plan or credit is applied when you sign up.
• datwise:snapshot — your SnapShot preferences, such as the size and style you used last.
• datwise:checkout — which plan or credit pack you were buying when you left for Stripe, so that coming back can be counted as a completed purchase in Analytics. It is kept in per-tab storage, it holds a plan or pack name and nothing else, and it is deleted the moment it is read.
• Whether an explanatory panel in the interface is expanded or collapsed.
• datwise:public-password — the password you typed to open a password-protected public dashboard. This one is kept in per-tab storage: it is forgotten as soon as you close the tab, and it is never stored for another tab.
• Clearing your browser’s site data removes all of it. Those preferences return to their defaults and nothing else is lost.

Datwise carries one measurement tool — Google Analytics — and no advertising pixel of any kind. From us it receives the page you opened and a short, fixed list of product moments: an account created and by which method, a file imported, a dashboard generated, a template chosen, a question asked of the assistant, a link shared, a checkout started. It never receives your name, your email address, a workspace, dashboard or column name, a file name, or anything at all from inside your data; row counts and file sizes are rounded into bands before they are sent, so a figure in Analytics can never be one of your figures. Google’s own tag adds the address of the page, the page that sent you, your browser and screen, and an approximate location worked out from your IP address — for visitors in the European Union, the United Kingdom and Switzerland, Google derives that location on servers in those regions and discards the IP address without logging it. The tag is loaded with Google’s advertising uses refused and Google Signals is switched off for this property: we run no advertising, we build no advertising profiles, and we neither sell nor share anything about your visit. Analytics is not loaded at all on a shared dashboard link or an embedded dashboard — the people who open those are our customers’ audience, not ours — and those visits are still counted only by the one-way daily hash the privacy policy describes. There is still no theme cookie: the theme is a browser preference, as described above, and never reaches us.

Four parts of the product involve someone else’s code or site. On the sign-in and sign-up pages, Datwise loads Google’s sign-in library, because Google requires its own button to be drawn by its own code; if you choose to connect a private Google Sheet, Datwise loads Google’s file picker for the same reason. Google may set its own cookies and storage on those pages, under Google’s policies, and we can neither read nor control them. Both are loaded only where they are needed, and if Google’s script is blocked the email and password form still works. Third, when you pay, you are taken to a page hosted by Stripe, which sets its own cookies on its own site. Fourth, Google Analytics runs on the marketing pages and inside the application, as section 3 describes; it is the only third-party code on a marketing page, and blocking it costs you nothing.

Every browser can block or delete cookies, usually under privacy or site settings. If you block the Datwise sign-in cookie you can still read public dashboards, but you will not be able to stay signed in. If you block or clear the language cookie, Datwise simply uses the language in the address you opened. The two analytics cookies are the ones you can refuse without losing anything: block cookies for this site, or use any content blocker or privacy extension — most of them already stop Google Analytics — and the product behaves exactly as it does now. Google also publishes a browser add-on that opts you out of Google Analytics on every site.

If we ever add a cookie, we will list it in the tables above and update the effective date at the top of this page before the cookie is set. The same applies when one is removed.

Questions about cookies or about what your browser stores: info@getdatwise.com.