Acceptable use

The rule

Use the feed for your own systems. Do not use our infrastructure to send packets at people who did not ask for them.

Specifically not allowed

Nominating an address you do not control. Verification exists precisely to prevent this. Attempting to point the stream at somebody else's machine is grounds for immediate termination without refund, and it is the one thing here we treat as deliberate rather than careless.

Using the verification challenge as a probe. Each destination may change address three times a day. That limit is not bureaucratic: it is what stops a paid slot becoming a way to send unsolicited packets to arbitrary hosts.

Reselling or redistributing the feed without agreement. If you want to build a product on top of this, that is a conversation we are happy to have, and it is a conversation rather than something to assume.

Interfering with the service for other customers, including attempting to exceed your destination count, or probing our infrastructure for weaknesses without asking first.

Security research

If you find a vulnerability, tell us before you tell anyone else and we will work with you. We will not threaten you for reporting something in good faith. Do not test against production in a way that degrades service for paying customers.

What happens if you breach this

We suspend or terminate access without refund. For anything involving sending traffic at a third party, we will also cooperate with whoever asks.

Reporting abuse

If traffic from our infrastructure is reaching you and you did not ask for it, tell us and we will stop it. That is a bug on our side and we want to know immediately.