Privacy policy
Privacy in QueryAlerts starts with the architecture: the local agent runs queries inside the customer environment and the platform receives only what is required for history, operations, and notification delivery.
Overview
QueryAlerts works with a local agent installed in the customer environment. The agent connects to the database, runs the query, and sends only the result required to register the execution and deliver the configured notifications.
This model reduces credential exposure and keeps sensitive processing as close as possible to the customer infrastructure. Instead of requiring direct internet-facing access to the database, the product prioritizes a local execution flow with controlled synchronization between the agent and the SaaS.
What we store
We store the data required to operate the platform, such as users, registered agents, query settings, execution history, notification deliveries, and subscription information.
We also store the configured SQL text, the message template, and operational metadata such as agent name, primary database label, and the last observed agent IP address. These records support the normal product workflow and the monitoring of configured automations.
What is not stored on our server
Customer database credentials and database connectivity remain in the local agent, inside the environment controlled by the customer.
The QueryAlerts SaaS does not connect directly to the customer database and does not require that database to be publicly exposed to the internet. That reduces the risk surface and helps keep technical control where it would normally belong.
How results are handled
When a query runs, the agent sends to the SaaS only the data needed to register the execution and deliver notifications by email and/or WhatsApp.
We recommend avoiding sensitive or unnecessary data in queries. Whenever possible, keep templates and results focused only on the operational information that must be delivered, without moving more data than the workflow actually requires.
Security and best practices
Communication between agent and SaaS happens over HTTPS and shared-secret validation.
We recommend keeping the agent updated, restricting access to the server where it runs, and periodically reviewing published queries and configured recipients. Privacy and security also depend on how each team structures its queries and outgoing messages.
Contact
For privacy, operational, or account data questions, contact [email protected].