SystemBeat Privacy Policy
SystemBeat is a monitoring service for scheduled jobs, websites, certificates and network endpoints. It sends notifications through the Telegram bot @systembeat_bot. This policy explains how the operator of SystemBeat processes information when you use the bot, API or website. SystemBeat is independent of Telegram.
1. Operator and contact
The operator responsible for SystemBeat is Kensley Weiss. Mason Williams handles privacy questions and requests on the operator's behalf. To request access to, correction or deletion of your data, email support@systembeat.info. We may ask you to confirm control of the relevant Telegram account before disclosing or changing account data.
2. Information we process
- Account and bot use: your Telegram user ID, private chat ID, username if available, account creation time and time of your most recent action in the bot. We record Telegram update IDs and receipt times to prevent duplicate processing. We do not receive your phone number merely because you use the bot.
- Group alerts: if you connect a group, its chat ID and title. The owner must be a group administrator. Group members can read alerts posted to that group, but they cannot manage the owner's monitors through SystemBeat.
- Support tickets: the text of your request, replies, ticket status and timestamps. Do not include passwords or API keys. A private operator group receives a copy of each request; its administrators can answer through the bot. Your personal Telegram profile is not included in the group notice.
- Billing: your selected plan, monitor limit, order and payment status, amount in Telegram Stars, transaction identifiers, payment and expiry times, plan changes and refund history. We receive payment confirmations from Telegram; we do not receive your card number or payment card details.
- Monitor data: monitor names, public hostnames, URLs, port numbers, selected DNS records, HTTP or JSON expectations, check results, timestamps, uptime and incident history. A cron job may submit an exit code and error output. Do not submit passwords, personal data or other secrets in monitor names, URLs or cron output.
- Delivery and operation: message destinations, queued notifications, delivery attempts and error details. API keys and heartbeat tokens are stored as hashes; issued values may temporarily appear in a queued setup message until it is sent. Delivered setup messages are replaced by a marker in our outbox. Incident alert text can remain in the outbox.
- Website connection: when you visit our public page or API, Cloudflare and our hosting infrastructure may process connection information such as your IP address, user agent and security events. Application access logs are disabled for heartbeat paths to avoid logging secret tokens.
3. Why we use it
We use this information to identify your account, run the monitors you configure, detect outages, deliver alerts and weekly reports, process plan purchases and refunds, keep payment records, prevent duplicate bot actions, troubleshoot delivery and protect the service from abuse. We do not sell personal data. Where the GDPR applies, service operation relies on providing the service you request, our legitimate interests in security and reliable operation, and applicable legal obligations.
4. Who receives information
Telegram processes bot interactions and delivers messages under its own Privacy Policy. A connected Telegram group receives the alerts and recoveries you direct there. SystemBeat's private operator group receives support requests and is accessible to its members. Cloudflare handles website and API traffic at the edge; the server hosting provider stores the application and database. These providers may process data under their own terms and in locations outside your country. We may disclose data when legally required. We do not give group members API keys, heartbeat URLs or cron output through group alerts.
5. Storage and retention
Account, monitor and support ticket records are kept while your account is active and until an operator processes a deletion request, unless a longer period is required by law. Payment and plan-change records may be retained longer where needed for accounting, refunds or legal obligations. Closing a ticket does not delete its history. Network check samples and Telegram update IDs are automatically removed after 30 days; incident history and the latest bot activity time remain with the account. Routine database backups rotate after 14 days. Protected recovery or rollback copies may be retained longer while needed for service recovery and are then removed. Telegram retains messages according to its own policy; removing a message from SystemBeat cannot recall a message already delivered to Telegram or a group.
6. Your choices and rights
You can stop using the bot and disconnect a group in the private Team alerts menu. You can ask us to provide, correct or delete information linked to your account, or object to or restrict processing where applicable, using the contact above. Some information may need to be retained for legal or security reasons. You may also have the right to complain to your local data protection authority. Stopping or deleting your Telegram account does not automatically delete SystemBeat data; contact us for a SystemBeat deletion request.
7. Security and changes
We use HTTPS, access controls, hashed API credentials and backups to protect the service. No method of transmission or storage can guarantee absolute security. We may update this policy when the service changes; the effective date at the top will show when the current version took effect. Material changes will be communicated through the service where practical.