Last updated: 29 October 2026 · Version 1.7
Qeries is an AI analytics platform that lets people ask questions about their organisation's data in plain language.
Qeries is in private preview and is not yet a registered company. Until it is, the controller responsible for the personal data described here is Alexander Metlewicz, based in Dubai, United Arab Emirates. A company is being formed; when it is, this notice will be reissued naming it, and anyone who has given us their details will be told.
For any question about this notice, or to exercise any of the rights in section 8, contact privacy@qeries.com. We answer privacy requests within one month.
There are two different relationships, and it matters which one applies to you.
Information about you as a visitor to our website or as a user of the Qeries product: your contact details, your account, and how you use the service. This notice explains what we do with it.
When an organisation uses Qeries to analyse its own business data, that organisation decides what data to load and why. We process it only on their instructions. A data processing agreement will govern this once the Qeries company is incorporated; until then we do not take customers' personal data into the product, except for testing that an organisation has agreed with us in writing. If your employer uses Qeries and you want to know what they have loaded or ask them to delete it, please contact them — they are the controller, not us.
| What | Why | Legal basis |
|---|---|---|
| Name, email address, company, industry, company size, department, job title, and anything you write in the message field | To reply to you and to understand who is interested in Qeries | Your consent, given when you submit the form |
| What | Why | Legal basis |
|---|---|---|
| Your email address, and a one-time link we send to it | To confirm the address is yours and give you access to a demo that runs on synthetic sample data — never on anyone's real data | Your consent |
Your questions are sent to our AI provider to generate an answer (see section 5). Please do not enter personal or confidential information into it.
| What | Why | Legal basis |
|---|---|---|
| Username, email address, display name, job title, role | To create and run your account | Performance of a contract |
| Password, stored only as a salted hash — never in readable form | To sign you in securely | Performance of a contract |
| If you turn on two-factor sign-in: the authenticator key (stored encrypted) and your recovery codes (stored only as hashes — never in readable form) | To sign you in securely | Performance of a contract |
| If you sign in with Microsoft or Google: your name, email address and the account identifier they give us (for Microsoft, also your organisation's directory identifier). We keep the email address and the identifiers with your account | To recognise you when you sign in through your organisation's Microsoft or Google account | Performance of a contract |
| Security log: who did what, when, and from which IP address — sign-ins, permission changes, password resets, data exports | To detect and investigate unauthorised access, and so that an organisation can see who did what in its workspace | Our legitimate interest in keeping the service secure |
| Usage records: which features and dashboards are used, which data sources are read, what is exported, and how long requests take | To keep the service reliable and decide what to improve | Our legitimate interest in operating and improving the service |
| The questions you ask in a workspace, when you asked them, and how many credits each answer used | To answer your questions and count the credits your organisation uses. Your organisation's administrators can see every question asked in their workspaces, who asked it, and its credit cost, so they can see how Qeries is used and what it costs. They cannot see your answer preferences or files you add to a question | Performance of a contract with your organisation; showing usage to your administrators is part of the service your organisation chose |
| Your Ask Q chats in each workspace: your questions, the answers, and the figures and tables shown in them | So your chats are still there after you sign out and on another device. Only you can see them; your organisation's administrators cannot (they can see the questions, as described above). The figures are your organisation's data, and they follow its access rules: if a dataset or data source is removed, or your access changes, the figures in older answers are removed and you can ask again | Performance of a contract with your organisation (a feature it switches on) |
| Email addresses you enter to invite colleagues or to receive scheduled reports | To send the invitation or the report | Performance of a contract |
| Your name, email address, job title and message when you contact support from inside the product | To answer you and to keep a record of what was agreed | Performance of a contract |
Microsoft and Google act as your organisation's sign-in provider, under your organisation's own agreement with them. They are not providers working for us, and we send them nothing about you except the redirect to their sign-in page. Their own privacy notices apply to what they do.
If a sign-in is refused — for example because no Qeries account exists for the address, or a personal rather than a company account was used — we record the attempt, including the email address, in the security log. We do this even if you have no account, to detect and investigate attempts to get in (our legitimate interest in keeping the service secure). These records are kept like the rest of the security log (section 7) and are never used for marketing. If you press "Ask Qeries to get in touch" on that page, we treat your email address as an enquiry (section 3.1).
When you use the Qeries application (app.qeries.com), our web server records each request: your IP address, the time, the address requested (with sign-in links and tokens removed), the result, and your browser's identifying string. We use this to detect and investigate attacks and faults (our legitimate interest in keeping the service secure). It is kept for 90 days, then deleted.
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.
What we do use:
| Name | Purpose | Expires |
|---|---|---|
qeries_session (on our site: __Host-qeries_session) | Keeps you signed in | 30 days |
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_demo | Your temporary demo session | 60 minutes |
| Browser local storage | 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. Signing out removes this browser's copy. The questions themselves are also stored with us when you ask them (section 3.4) | Until you sign out or clear it |
These are strictly necessary to provide a service you have asked for, so we do not ask for consent to set them.
We do not sell personal data and we do not share it for advertising. We use the following providers to run the service:
| Provider | What it does | Company based in | Where your data is processed |
|---|---|---|---|
| Anthropic | The AI model behind our analytics features (see section 5) | Anthropic, PBC (United States) | Anthropic's global infrastructure, outside the UAE; not necessarily in the EU |
| DigitalOcean | Hosting and backups — where your data is stored | DigitalOcean, LLC (United States) | Frankfurt, Germany (EU) |
| Apple iCloud Mail | Sending email, such as invitations and reports | Not stated | EU / United States |
| Sentry | Error reports, so we can find and fix faults | Functional Software, Inc. (United States) | European Union (stored); see section 6 |
| Better Stack | Checking the service is online | Better Stack, Inc. (United States) | EU / United States |
| Tavily | Web search, only if your workspace switches it on | Not stated | Not stated |
Error reports are configured to exclude personal data: request contents, cookies, authentication headers and user identity are stripped before an error leaves our servers.
This is the part most worth reading. Qeries answers questions by sending some of your data to an AI model operated by Anthropic. We think you should know exactly what.
When you ask a question, the following may be sent:
Under our agreement with Anthropic, this data is not used to train their models.
You can stop specific columns from ever being sent.
Any column in a data source can be marked as withheld from the AI. Its values are then never included — not in result rows on any of the paths above, and not in the sample values used to match filters — while the column stays fully visible to people on screen and in dashboards. This is the right setting for names, email addresses and free-text notes.
Organisations that prefer their data to go to Anthropic under their own contract rather than ours can supply their own API key in the product settings. We recommend this for sensitive data.
We do not use AI to make automated decisions that produce legal effects or similarly significant effects about you.
Your data is stored in the European Union (Frankfurt, Germany). Parts of it are sent outside the EU when the service needs them — most importantly to Anthropic when you ask a question (section 5), which processes it outside the UAE and not necessarily in the EU. Some providers in section 4 are based outside the EU, and we access the service from the United Arab Emirates, so personal data may be transferred to those countries.
Where that happens, these are the safeguards it relies on:
| Provider | Safeguard |
|---|---|
| Anthropic (processing outside the UAE; company in the United States) | The European Commission's Standard Contractual Clauses, incorporated into Anthropic's Data Processing Addendum, which forms part of the terms we contract under |
| DigitalOcean (hosting in the EU; company in the United States) | Certification under the EU–US Data Privacy Framework, with the Standard Contractual Clauses applying if that framework ceases to be valid |
| Sentry | Stored in Sentry's European region. Sentry is a US company and its terms allow processing elsewhere; this is covered by the EU Standard Contractual Clauses and the EU–US Data Privacy Framework. Error reports are stripped of personal data before they leave our servers. |
You can ask us for details of any of these at privacy@qeries.com.
We keep personal data only for as long as we need it for the purpose we collected it. When a period below expires, the data is deleted. You can ask us to delete it sooner — see section 8.
| Data | Kept for | Why that long |
|---|---|---|
| Enquiries and demo requests | 36 months from your last contact with us | Business software decisions are made slowly, and an enquiry today often becomes a conversation a year or two later |
| Account data | For as long as the account exists, then 90 days | So an account closed by mistake can be restored, and any billing question can be settled |
| Security logs, including IP addresses and the email addresses of refused sign-in attempts | 24 months | Security incidents are often discovered long after they happen, and investigating one needs history to compare against |
| Web server access log, including IP addresses | 90 days | Long enough to investigate an attack or fault found within a quarter |
| Usage records | 24 months, after which we keep only aggregate figures that cannot be traced back to anyone | To understand which parts of the product are used and to compare one year with the next |
| Questions asked in a workspace, with their credit cost | 24 months, or until your organisation's workspace is deleted, if sooner | Long enough for your organisation to compare usage and cost year on year, and to settle a question about credits charged |
| Your Ask Q chats | Your most recent chats in each workspace, up to the number you choose (at most 100). A chat is deleted 12 months after you last used it, and in any case 24 months after it started; sooner if you delete it, your account is deleted, you are removed from the workspace, or your organisation's workspace is deleted. If your account is deactivated, your chats are kept for 30 days and Qeries shows them to no one, not you, your administrators or our staff; they are then deleted in our next daily deletion run. If your account is reactivated within those 30 days, your questions come back, but the figures in the earlier answers do not; you can ask again | So you can return to a chat, and so that a deactivation made by mistake can be undone. An old answer shows what you saw then; asking again gives today's figures. If you ask for a copy of your data while your account is deactivated, we give you your questions from our record of the questions you asked (section 3.4) and tell you when the chats will be deleted; for the figures, which are your organisation's data, please ask your organisation (section 2) |
| Links from a suggestion in an answer, with your question | 30 days, then deleted | So the link works. Only you see your question when the link is opened. |
| Invoices and billing records | 7 years after the end of the financial year of the invoice, as tax law requires | Kept after the workspace is deleted. |
| Invitations | Deleted 30 days after they are used or expire | An invitation has no purpose once it has been accepted |
| Support requests | 36 months | To handle follow-up questions and keep a record of what was agreed |
| Files added to a question | 24 hours, then deleted; never backed up. Any figures from the file in your saved Ask Q chats are removed at the same time | Visible only to the person who added it. Copies held by our AI provider follow its retention (see section 5) |
| Customer business data | For as long as the customer's agreement runs, then 30 days | The customer decides this, not us — see section 2. The 30 days are a grace period before permanent deletion |
We keep a record longer than shown above only where the law requires it, or where we need that record for a specific legal claim or a regulator's request, and only until the matter ends.
If the GDPR applies to your data, you have the right to:
To exercise any of these, email privacy@qeries.com. We will respond within one month. We may need to confirm who you are before we act, so that we do not disclose your data to someone else.
If your employer loaded the data into Qeries, please ask them — see section 2.
You also have the right to complain to a data protection supervisory authority. Because we are not established in the European Union, the authority to approach is the one for the country where you live or work, or where you believe the problem occurred. In Austria that is the Österreichische Datenschutzbehörde; every other EU and EEA country has an equivalent. We would rather hear from you first, at privacy@qeries.com, but you are not obliged to contact us before complaining.
No service can promise perfect security, but we will tell affected customers without undue delay if a breach affects their data.
Qeries is a business product and is not directed at children. We do not knowingly collect data about anyone under 16.
If we change how we use personal data, we will update this page and change the date at the top. If the change is significant, we will tell account holders directly.