Privacy policy

Effective October 1, 2026

QueryHost lets you query public game-server status through query.host and connected AI clients.

Information processed

QueryHost receives the game or protocol, hostname or public IP address, port, and supported query options you submit. Our servers resolve and contact the requested public target and process its status response. Responses may include server names, messages, versions, maps, and public player information. Do not submit passwords, credentials, or private server configuration.

When used through ChatGPT or another MCP client, QueryHost receives the tool arguments and protocol messages that client sends. It does not require a QueryHost account or request access to your chat history. Results are returned to that client; its own privacy policy governs its handling of conversations and results.

Purpose and recipients

We process these inputs to perform the requested query, compare results, return server cards and links, and keep the service reliable and protected against abuse. QueryHost uses Railway to host its services. The selected game server receives a network query from QueryHost infrastructure. Its operator may log that connection under its own practices.

Storage and operational logs

The query service uses a bounded, short-lived in-memory result cache to reduce repeated network work. It does not provide saved query accounts or a persistent query-history database. The API records operational events such as request identifiers, method, route, response status, duration, game, and cache outcome. Hosting and network infrastructure may also process connection metadata and access logs. Operational logs are retained under the hosting providers' configured retention policies. We do not promise that requests leave no logs. Contact us for information about logs associated with a particular request.

Contact and requests

Email lockerzmodding@gmail.com about access, correction, or deletion of information we hold about you. Please identify the relevant request without sending passwords or unrelated sensitive information.

Changes

We will update this page and its effective date when our data practices change.