This Privacy Policy governs the collection, storage, and use of data within our monitoring and keep-alive service. We are committed to transparency regarding how our automated systems interact with your infrastructure. By using our service to monitor or ping endpoints, you agree to the data handling practices outlined below, which prioritize data minimization and security.
We collect two categories of data: Account Information and Target Configuration. Account Information includes your authentication details and settings. Target Configuration includes the specific endpoint URLs, HTTP methods, and interval settings you provide. We strictly do not collect or store the content (body/payload) of the responses returned by your servers, except for status codes (e.g., 200 OK, 500 Error) and latency metrics required for uptime reporting.
To perform uptime checks and keep-alive functionality, our automated bot sends HTTP requests to the URLs you specify. These requests identify themselves using a custom User-Agent string to ensure transparency in your server logs. We do not inject malicious scripts, cookies, or unauthorized headers. The interaction is strictly limited to a standard network handshake to verify availability and prevent service hibernation.
A core feature of our service is the ability to display uptime status publicly. We recognize that endpoint URLs often contain sensitive routing information. On all public-facing status pages, we enforce strict data masking: full endpoint URLs, query parameters, and specific IP addresses are hidden or obfuscated. Only the service name, uptime percentage, and latency graphs are visible to the public to prevent information disclosure.
We operate with a strict 'No Exploitation' policy. The endpoints you monitor are your intellectual property. We do not aggregate your endpoint data to train algorithms, do not inspect your traffic for marketing insights, and do not sell your infrastructure data to third parties. Our business model is based on providing a utility, not monetizing your data.
If your endpoints require custom headers (such as Authorization tokens or API keys) for the keep-alive ping to function, these are stored using industry-standard encryption at rest. These credentials are used solely for the purpose of authenticating the ping request and are never displayed in the dashboard, logs, or public status pages. We strongly recommend using dedicated, low-privilege API keys for monitoring purposes rather than administrative credentials.
We retain historical uptime and latency data for a limited period to generate performance graphs and incident reports. Detailed logs of individual checks are rotated and permanently deleted after a set duration to reduce data footprint. If you choose to delete a monitor or close your account, all associated configuration data and historical logs are immediately purged from our active databases.
Our monitoring nodes are hosted on trusted cloud infrastructure providers. While data travels through these providers to reach your servers, it is protected by encryption in transit (TLS/SSL). We carefully select infrastructure partners who adhere to high security and privacy standards to ensure the integrity of the monitoring network.
We employ technical and organizational measures to protect your data, including encrypted database storage, secure HTTPS connections for all dashboard interactions, and rate-limiting to prevent abuse. While no service is immune to all risks, we continuously update our security practices to mitigate unauthorized access to your monitoring configurations.
Yes this is AI slop
Home