Fair Use Policy
Informational translation. Only the German version is legally binding.
As of: November 2026. Provider: ELEVAYTE Online UG (haftungsbeschränkt), Rüdigerstraße 16, 40472 Düsseldorf, Local Court (Amtsgericht) Düsseldorf HRB 110380, [email protected].
Related documents: Terms · Right of withdrawal · Data processing agreement (DPA) · Sub-processors · Open-source licences
This policy is part of the Terms (§ 14). It sets out how much data traffic, metrics and API usage each plan includes and what happens if you need more. Our principle: We throttle, we do not charge extra. Additional data traffic only costs money if you have expressly ordered a (larger) PRO bundle beforehand.
1. Data traffic via the relay
(1) Data traffic means all data that passes between your devices and your computers via the relay, in both directions: SSH sessions, TCP forwarding, the browser terminal and, in future, HTTP tunnels. Not counted are the agent's reports to the API (heartbeat, metrics) and agent updates.
(2) Each plan includes the following amounts per month, shared by all devices of an account:
| Plan | Included data traffic per month | When exceeded |
|---|---|---|
| Free | 10 GB per account | port forwarding throttled to 1 Mbit/s until the end of the month |
| PRO bundles | 25 GB per device of the bundle, shared by all devices of the organisation: PRO5 125 GB, PRO10 250 GB, PRO25 625 GB, PRO50 1,250 GB, PRO100 2,500 GB | port forwarding throttled to 1 Mbit/s until the end of the month |
| With Enterprise add-on | as the booked plan | as the booked plan |
SSH sessions, the browser terminal and actions on devices (e.g. restart) are never throttled or interrupted, not even after the quota has been exceeded.
(3) The counter restarts with each billing month, on the Free plan on the first of each calendar month (Europe/Berlin). After switching to a larger bundle, the full quota of the new bundle applies immediately; data traffic already used is counted towards it. Unused data traffic expires.
(4) You see your current usage in the dashboard. Our measurement at the relay is authoritative.
2. What happens when the quota is used up
- At 80 % we send you an email.
- At 100 % we throttle only port forwarding to 1 Mbit/s until the end of the month. SSH, the browser terminal and actions remain fully usable. You receive an email.
- Larger bundle. In the dashboard you can lift the throttling by switching to a PRO bundle or a larger PRO bundle (§ 4(5) of the Terms). This only happens on your express order.
- Contact. If on a PRO bundle you exceed the quota by more than double in three consecutive months, we get in touch to find a suitable solution with you.
- Measures under § 15 of the Terms are only taken if the usage is due to a prohibited use under section 6 or endangers the operation of the relay for other customers.
There is no automatic additional charge or other extra cost for excess usage.
3. Connections
(1) Up to 20 simultaneous connections (e.g. SSH sessions or forwarded TCP connections) are possible per device, on the Free plan up to 5.
(2) A single connection via the relay is ended after 8 hours and can be re-established immediately. We may end idle browser terminal sessions after 30 minutes.
(3) Establishing new connections is limited to 30 per minute and device.
4. Device data and metrics
(1) Measuring interval and retention period depend on the plan, currently:
| Plan | Measuring interval | Retention |
|---|---|---|
| Free | 30 s | 7 days |
| PRO bundles | 10 s | 30 days |
| With Enterprise add-on (Free or PRO) | 5 s, plus live view | 365 days |
(2) The agent reports at fixed intervals; the API accepts at most 12 reports per minute and device. Do not modify the agent to report more often or to write third-party data into the metrics.
(3) Device data (e.g. host name, device name) must not contain any content that violates § 14 of the Terms.
(4) For locked devices (§ 4(6) of the Terms), the API continues to accept the online status but does not store any history of device data. Locked devices cannot be reached via the relay; therefore no data traffic arises for them.
5. API, CLI and integrations
(1) Requests to the API are limited to 60 per minute per access token or API key, with the Enterprise add-on to 300. API keys for your own automations and the MCP server are part of the Enterprise add-on; the dashboard and CLI use the API on all plans. If the limit is exceeded, the API responds with status 429 and an indication of when you can try again.
(2) Automations should detect errors and then pause instead of repeating requests in a loop. Actions for many devices (e.g. restarts) must be staggered over time.
(3) We deliver webhooks with limited retries. We may deactivate a target that permanently does not respond after notice.
(4) The same applies to the MCP server and other integrations built on the API.
6. Examples of prohibited use
| Behaviour | Why it is not allowed | What we do |
|---|---|---|
| Publicly providing videos, music or files to many people via a TCP forward | Mass traffic instead of remote access | Notice, throttling, locking the forward |
| Operating the Pi as an open proxy, VPN exit or Tor node for third parties | Risk of misuse, third-party traffic runs over our addresses | Locking the forward, termination if repeated |
| Torrent or peer-to-peer traffic via the relay | Mass traffic, liability risk | Notice, throttling, locking the forward |
| Scanning third-party ports or networks through a tunnel | Attack on third-party systems | Immediate lock, reasons given afterwards |
| Creating several Free accounts to circumvent the device limit | Circumventing plan limits | Notice, then termination of the additional Free contracts under § 7(1) of the Terms |
| Reselling access to the relay to third parties | Not covered by the plan | Notice, offer of the Enterprise add-on with sub-organisations (once available), otherwise termination |
| Modifying the agent so that it polls the API every second | Overload | Throttling, locking the device |
| Delivering malware or phishing pages via a forward | Unlawful | Immediate lock, report to authorities where applicable |
Permitted and expressly intended are, for example: maintenance via SSH, occasional file transfers, access to a web interface of the device (e.g. Home Assistant, Pi-hole, OctoPrint) for you and your team. Regular large backups (e.g. nightly images of entire SD cards) are permitted but count towards the quota.
7. Changes to this policy
Changes are governed by § 10 and § 12 of the Terms. A reduction of the included amounts in paid plans is a change to the service under § 10(3) and (4) of the Terms, with advance notice and a right to exit.