# RelayWatch Privacy Policy
**Last Updated:** September 20, 2026
At RelayWatch ("we," "our," or "us"), we respect your privacy and are committed to handling your data transparently. This Privacy Policy explains what information we collect when you use our website, dashboard, and monitoring endpoints (collectively, the "Service"), how we use that information, and your rights regarding your data.
---
### 1. Information We Collect
We only collect information necessary to deliver hybrid endpoint monitoring, health tracking, and alert notifications.
#### A. Account Information
* **Email Address:** When you register for an account, we collect your email address. This is used for account authentication, billing updates, and dispatching monitoring alerts (if enabled).
#### B. Monitoring & Ping Data
When your servers or background jobs check in with RelayWatch via `/ingest/{slug}` (using `GET` or `POST`), our servers automatically process operational data, including:
* **Endpoint Identification:** The unique endpoint slug (`/ingest/YOUR_SLUG`) associated with your account.
* **HTTP Metadata:** Request timestamps, source IP addresses, HTTP method, user-agent strings, and response status codes.
* **Upstream Health Metrics:** Status codes, response headers, latency, and error messages returned by your target upstream endpoints when active monitoring is performed.
#### C. Webhook & Integration Data
To dispatch alerts on your behalf, we store configuration parameters provided by you, including:
* **Slack Webhook URLs:** Incoming webhook destination endpoints.
* **Notification Webhooks:** Custom HTTP endpoints configured to receive JSON alert payloads.
* **`ntfy` Topics:** Custom push notification channel topics and associated API access tokens.
#### D. Cookies & Session Data
* **Essential Session Cookies:** We use first-party cookies strictly for essential session management and account authentication (keeping you securely logged in while navigating the dashboard). We do not use tracking, analytics, or third-party advertising cookies.
---
### 2. How We Use Your Information
We use the collected information solely to operate, maintain, and improve the Service:
* **Monitoring & Alerting:** Evaluating expected ping intervals, tracking overdue heartbeats, verifying upstream availability, and dispatching failure or recovery notifications.
* **System Diagnostics & Security:** Monitoring server load, preventing rate-limit abuse or denial-of-service (DoS) attempts, and troubleshooting failed check-ins.
* **Service Communication:** Sending essential system updates, operational alerts, or transactional emails regarding your account.
We **do not** sell, rent, or monetize your personal information, ping logs, or endpoint data to third parties or advertising networks.
---
### 3. Third-Party Alert Dispatching
When RelayWatch triggers an alert, we transmit necessary alert payload data (such as endpoint name, slug, status code, failure message, and timestamp) to the third-party notification services you explicitly configure:
* **Slack:** Transmitted directly to your provided Slack Webhook URL.
* **`ntfy` Infrastructure:** Transmitted to your specified `ntfy` topic.
* **Custom Webhooks:** Sent as a JSON POST payload to your designated HTTP endpoint.
* **Email Service Providers:** Delivered via transactional mail servers to your account email address.
*Note: Third-party services operate under their respective privacy policies. We encourage you to review the privacy practices of any third-party platforms you connect to RelayWatch.*
---
### 4. Data Retention & Deletion
* **Active Endpoint State:** Current endpoint status (last ping time, cooldown status, failure state) is maintained in memory and stored in our database for as long as the endpoint remains active.
* **Log Retention:** Historical ping logs and upstream HTTP response records are stored for a limited rolling period strictly for audit and status display purposes, after which they are automatically purged.
* **Endpoint Purging:** Disabling or deleting an endpoint immediately purges its tracking state and associated notification metadata from active monitoring memory.
* **Account Deletion:** If you delete your account, all associated endpoints, webhooks, and account data will be permanently deleted from our primary database.
---
### 5. Data Security
We implement industry-standard technical and organizational measures to safeguard your information. Sensitive integration parameters (such as webhook URLs and push notification tokens) are protected in transit using TLS encryption and stored securely. However, no method of transmission over the internet or electronic storage is 100% secure, and we cannot guarantee absolute security against all potential threats.
---
### 6. Updates to This Policy
We may update this Privacy Policy periodically to reflect changes in our Service or legal requirements. Updated versions will be posted on this page with an updated "Last Updated" date.
---
### 7. Contact Us
If you have any questions or concerns regarding this Privacy Policy or how your data is handled, please contact us at **privacy@relaywatch.io**.
RelayWatch