Terms of use
Terms of Use - Online Server Monitor
These terms describe responsible use of Online Server Monitor for Linux server monitoring, alerts and safe maintenance actions.
Service
Service is provided as-is
Online Server Monitor is provided as-is for server monitoring and operational assistance. No uptime guarantee, data availability guarantee or incident response guarantee is provided.
Responsibility
You are responsible for connected servers
You must have permission to install the agent and manage every server you connect. Do not use the service on systems you do not own or administer.
Credentials
The service does not request SSH passwords
The bot does not request SSH passwords, root passwords, private SSH keys, hosting panel passwords, database passwords, FTP passwords or cloud provider credentials. Do not send these secrets through Telegram or support channels.
Maintenance
Maintenance actions may affect availability
Restarting services, cleaning logs and rebooting servers can interrupt websites, mail, databases and background jobs. Use these actions carefully and only when you understand the impact.
Abuse
Unauthorized use is prohibited
Do not attempt to bypass pairing, abuse Telegram messages, attack the backend, extract data from other users, or use the service to control systems without permission.
Telegram
Telegram account and chat responsibility
You are responsible for choosing the Telegram chats where the bot is used. If you add the bot to a group, make sure group members are allowed to see server names, metrics, alerts and maintenance controls. Remove the bot from chats that no longer need access.
Data
Operational data and retention
The service may process operational data needed for pairing, alerts, status cards, thresholds and command results. Data handling is described in the privacy policy. You should not use the bot to transmit unrelated personal data or secrets.
Availability
No replacement for backups or emergency access
Monitoring can help you react faster, but it does not replace backups, provider console access, SSH access, disaster recovery planning or application-level logging. Keep independent recovery options for important servers.
Changes
Service changes
Features, commands, thresholds and agent behavior may change as the service improves. When a change affects production use, review the setup, security model and command reference before relying on new maintenance actions.
Security
Security and privacy links
Read the security model, privacy policy, setup guide and contact page before using the service in production. Security reports can be sent to security@server.howprog.one.
Start monitoring
Connect a Linux server from Telegram.
Open the bot, request a one-time pairing command, run it on the server and receive the first status report in Telegram.