QueryPort

Privacy notice

What data this site collects, what the AI gateway processes, how long anything is kept, and how to have it deleted.

In force from 8 August 2026.

1. Who is responsible

QueryPort operates this website and the API gateway described on it. Questions about anything below go to info@queryport.com, and we answer them ourselves rather than routing them to a form.

2. What this website collects

  • Nothing at all if you only read. There is no account, no login and no tracking of you across other sites.
  • What you type into the contact form — your message and the address you want a reply at. It reaches us as email. We keep the correspondence for as long as the conversation is live, and delete it on request.
  • Ordinary server logs — request address, time, response code, browser string. They exist to find faults and are not used to build a profile of you.
  • A cookie for the consent banner, which records only that you dismissed it.

3. Analytics

This domain uses Google Analytics 4 (Google Ireland Limited) to count visits and see which pages are read. Specifically:

  • Nothing is stored until you agree. The tag loads with analytics storage denied by default and only starts writing cookies after you press the button on the cookie notice. Close the notice without agreeing and no analytics cookie is set at all.
  • IP addresses are anonymised before processing.
  • No advertising features, no remarketing and no data sharing for advertising are enabled.
  • Session recording (screen replay) is not used on this domain, by any provider.

Our Russian-language site uses a different provider, and its own notice says so there. We do not run one counter across both domains.

4. What the gateway processes

If you have been granted access, requests you send through the gateway contain the text or files you chose to send, and they are forwarded to an external model provider in order to answer. That means:

  • The content of a request leaves our infrastructure and reaches the provider selected by the routing rule for your key.
  • What we retain — and for how long — is agreed with you before a key is issued, and written down. The default is metadata only: timing, size, cost and outcome, not the text.
  • Whether a provider may train on your data is a setting we check explicitly per provider rather than assume, and we tell you what we found.

Do not send personal data of other people through the gateway unless that has been agreed in writing first.

5. Where data goes

The site runs on servers in the European Union. Model providers may process requests outside the EU; which ones apply to your key is named at onboarding, because it depends on the routing rule and changes when providers do.

6. Your rights

You can ask what we hold about you, ask for a copy, ask for correction, or ask for deletion. Write to the address in section 1. We do not require a particular form of words and we do not charge for it.

7. Changes

When this notice changes materially, the date at the top changes with it. We do not backdate.


Honest note. This notice was written by the engineers who built the system, so that it describes what the code actually does. It has not yet been reviewed by a lawyer. If you need a document that carries legal weight for your own compliance file, ask us and we will tell you where it stands rather than let you assume.