Private Preview. Launching Soon!

Request early access

Cookies

Last updated: 18 November 2026 · Version 1.1

In short: Qeries uses no advertising cookies, no analytics cookies and no third-party trackers. Our website sets no cookies; it keeps two settings in your browser: your language, and whether it is shown light or dark. The Qeries application uses a small number of its own cookies and browser storage to sign you in, keep your account secure and remember your settings.

What we use

The full list, with what each item does and how long it lasts, is in section 3.5 of our Privacy Notice, repeated below word for word. If the two ever differ, the Privacy Notice applies.

We use no advertising cookies, no analytics cookies and no third-party trackers. The website and the product make no requests to third-party domains: fonts, scripts and images are all served from our own servers.

Our website (qeries.com) sets no cookies. It keeps two settings in your browser, listed below. The Qeries application (app.qeries.com) uses the cookies and browser storage listed below, all from our own domain. If you choose to sign in with Microsoft or Google, you go to their sign-in page, where they set their own cookies under their own policies.

What we do use:

NamePurposeExpires
On our website (qeries.com)
qeries_lang (browser local storage) Remembers the language the website is shown in Until you clear it
qeries_theme (browser local storage) Remembers whether the website is shown light or dark Until you clear it
In the Qeries application (app.qeries.com): cookies
qeries_session (on our site: __Host-qeries_session) Keeps you signed in After 8 hours without activity, unless your organisation has set a different limit for its workspace (never more than 30 days). Removed when you sign out
qeries_site, qeries_viewas (on our site: __Host-qeries_site, __Host-qeries_viewas) Remembers which workspace you are viewing, and administrator preview mode 30 days / 8 hours
qeries_stepup, qeries_ssofresh (on our site: __Host-qeries_stepup, __Host-qeries_ssofresh) Records that you entered your second factor, or signed in again with Microsoft or Google, in the last few minutes, for actions that need a recent check 10 minutes
qeries_sso Protects a Microsoft or Google sign-in while it is in progress 10 minutes, or when the sign-in ends
qeries_mfa_pending Qeries platform staff only: holds a sign-in until the second factor is entered 5 minutes
qeries_demoYour temporary demo session60 minutes
In the Qeries application: browser storage
Browser local storage, kept for your account Display settings, and a copy of your recent Ask Q chats so they open quickly. Where chat history is switched on, your chats are kept with your account in each workspace (section 3.4); elsewhere they are kept only in this browser. The questions themselves are also stored with us when you ask them (section 3.4). Also a dashboard you are building and have not saved yet, with the figures shown in it, so it survives a page reload, builder settings (field display names, saved segments and value groupings, drill paths, folders, starred and recently opened items; segments and groupings can contain values from your organisation's data), and the name you last signed in with on this browser Signing out removes them; switching workspace removes the unsaved dashboard. If your session simply runs out, they stay until you sign out or clear them
Browser local storage, kept for this browser Layout and display settings (for example a pinned side panel, the start page, where Ask Q answers open, or the light or dark theme of our documentation), notes that you have seen or agreed to a message (for example that files you attach to a chat are read by the AI), and a marker that older settings in this browser have been converted to the current format Until you clear it
Browser session storage Two short-lived items for this tab: "remind me later" on the two-factor prompt, and where to return after you confirm who you are When you close the tab, or as soon as it is used

Why there is no cookie banner

Everything listed is strictly necessary for a service you asked for, or remembers a setting such as your language. These do not need your consent, so we do not ask for it. If we ever add anything that is not strictly necessary, such as analytics, we will ask for your consent before it is set, with a choice to refuse that is as easy as accepting, and we will update this page and our Privacy Notice before it goes live.

"Do Not Track" and Global Privacy Control

We set nothing optional, so there is nothing for these signals to switch off. We do not track you whether or not your browser sends them.

Sign in with Microsoft or Google

If you choose to sign in with Microsoft or Google, you leave our site for theirs. They set their own cookies there, under their own policies.

How to remove them

Your browser lets you see and delete cookies and site data for qeries.com and app.qeries.com at any time, usually under its privacy or site settings. If you delete them, you are signed out of the application, the website goes back to its default language and look, and a dashboard you have not saved is lost.

Who we are, and your rights

See our Privacy Notice: who is responsible for your data (section 1) and your rights (section 8). Questions: privacy@qeries.com.

Changes

We update this page whenever section 3.5 of our Privacy Notice changes. The date and version above show the latest change.