Skip to content

Acceptable Use Policy

What you may not run on nodejshost.

Not allowed

  • Cryptocurrency mining, or anything that keeps CPUs pegged for its own sake.
  • Spam, bulk unsolicited messages, or sending email over SMTP from bots.
  • Scanning, attacking or flooding other systems (port scans, DDoS, brute force, credential stuffing).
  • Malware, phishing, scams, or hosting stolen data or credentials.
  • Running a proxy, VPN, SOCKS relay or tunnel (for example with http-proxy, socks, ngrok or localtunnel), or anything that passes other people's traffic through our network addresses.
  • Content or activity that is illegal where we or you operate, or that infringes others' rights, including copyright, trademark and privacy.
  • Content that sexually exploits minors, promotes violence or terrorism, or harasses, threatens or targets people for who they are.
  • Breaking the terms of platforms your bot uses (for example Discord's or Telegram's), including automating normal user accounts where the platform forbids it.
  • Collecting or processing other people's personal data without the right to.
  • Trying to break out of your container, reach other customers' bots, or reach our infrastructure, or going around the limits, monitoring or blocks we apply.
  • Using many accounts to get more than one Free pack, or reselling the service without our written consent.
  • Anything else that, in our reasonable view, harms the service, other customers, our servers, our network addresses or our reputation.

Discord and Telegram limits

  • Discord and Telegram limit how fast a bot may send requests, and they limit by network address as well as by bot. Every bot on nodejshost shares addresses with other customers, so a bot that ignores the limits can get the address blocked for all of them.
  • Discord limits each bot to about 50 requests per second, and each route has its own limit. If a bot makes too many invalid requests (bad token, missing permissions, or being rate limited, about 10,000 in 10 minutes), Discord blocks the address for a while. Logging in again and again with the same token is also limited.
  • Telegram allows a bot to send about 30 messages per second in total, about 1 message per second to the same chat and about 20 messages per minute to the same group. Over that, Telegram answers with a wait time that your bot must respect.
  • These numbers are set by the platforms and can change. Read their documentation and make your bot wait when it is told to, and never retry in a tight loop. A bot that retries forever is the most common reason for a block.

How we enforce it

  • We watch for abuse signals such as sustained 100% CPU, network misuse, and the number of requests your bots send and how many of them the platforms reject. We may slow a bot down to keep it inside the platform limits.
  • If a bot keeps failing (for example five errors in a row) or floods a platform, we stop it automatically and show the reason on the bot's page and in its console. The first stops last a few minutes and the bot can then be started again. If this happens repeatedly within 24 hours, the bot is blocked permanently and we email you the reason.
  • Serious abuse can lead to an immediate block, to suspending or ending the account, to removing code and data, or to a report to the authorities. We decide what is a breach and what action to take, and we may act on the first breach, with or without warning.
  • If a bot was blocked and you fixed the cause, write to us. We may lift the block and give you another try, but we are not required to, and then the same rules apply again.

Changes to this policy

We may change this policy at any time. The version on the website is always the current one.

Reporting abuse

Write to [email protected] with details. We investigate every report.