This document establishes the legally binding terms and operational conditions governing the use of the Signal.ge automated monitoring platform, cross-platform system agents, public status planes, and dynamic notification dispatch infrastructure.
Signal.ge delivers an enterprise-grade software platform and a geographically distributed worker framework engineered for perimeter tracking of public websites, automated APIs, SSL/TLS certificate lifecycles, liveness beacons (Heartbeats), network integrity (Ping, UDP, DNS), and isolated private infrastructure backend components.
The customer retains sole and exclusive liability for the lawful authorization and explicit ownership of all target endpoints, host machines, credentials, and alert communication channels provisioned within the workspace. Private network monitoring layers must only be initialized inside computational environments where the customer holds verifiable, statutory administrative authorization to execute infrastructure auditing.
The customer is entirely responsible for restricting access to and maintaining the active confidentiality of project API application keys. System daemon feature components and granular routing permissions must be mapped strictly adherence to the Principle of Least Privilege (PoLP).
Down-range alert dispatch loops, upstream escalation layers, and branded status publishing pages function relying explicitly on user-defined parameters. The customer remains systematically responsible for the logical accuracy of endpoint recipients and any narrative incident descriptions published onto public-facing status pages.
The cloud platform is delivered on a best-effort basis. Signal.ge waives all structural liability for operational anomalies resulting from public transit network degradation, customer-side infrastructure collapse, upstream third-party dependency outages, or unverified runtime configurations. Absolute transaction thresholds and check rate frequencies are strictly bounded by your active subscription tier.
Workspace properties, telemetry history arrays, historical incident metadata, resource capacity metrics, and local daemon inventory specs are stored exclusively for operational reliability, engineering support delivery, and administrative troubleshooting workflows in alignment with data safety standards.
One workspace for a flexible control panel, developer-friendly API, global external checks, and local agents for monitoring infrastructure of any complexity.
