// LEGAL

Acceptable Use Policy

Last updated 2026-07-10

Your Box runs on shared infrastructure accounts (Hetzner Cloud) — abuse from one Box risks the account every rel4i customer depends on. This policy mirrors our upstream providers' acceptable-use rules directly; it exists to keep those accounts, and everyone's boxes, alive.

Not allowed, ever

Cryptocurrency mining of any kind, on any resource level.
Port scanning or network scanning of hosts you don't own or have explicit authorization to test.
Spam — unsolicited bulk email, SMS, or messaging of any kind.
Malware — creating, hosting, or distributing viruses, ransomware, botnets, or other malicious software.
Open proxies or relays — running open SOCKS/HTTP proxies, VPN exit nodes, or Tor exit relays.
Denial-of-service activity — launching or participating in DoS/DDoS attacks against any target.
Illegal content — storing, hosting, or transmitting content that's illegal in Germany or the EU.
Copyright infringement — operating piracy services, torrent trackers for infringing content, or similar.
Phishing or credential harvesting of any kind.

Fair use of compute

Boxes run on shared-vCPU infrastructure with a baseline meant for agent workloads (builds, tests, dev servers) — not sustained 100% CPU compute farming. Reasonable bursts for builds and agent runs are exactly what the Box is for; sustained abuse that degrades the underlying host for others is not.

What happens if you violate this policy

Immediate suspension of the offending Box, without prior notice where required to protect the underlying infrastructure account, and without refund. Depending on severity, this may extend to your entire rel4i account. We report illegal activity to relevant authorities where legally required.

Appeals

If you believe a suspension was made in error, contact us via the details on the /impressum page. As a solo-founder alpha, expect a personal reply, not a ticket queue.

Reporting abuse

If you believe a rel4i Box is being used to attack, scan, or spam you, contact us via /impressum with the offending IP/hostname and timestamps (log excerpts help). We take abuse reports seriously — our own infrastructure account is on the line too.