Acceptable Use & Fair-Use Policy
The rules for the optional Beamfall Hosted Relay, and an honest statement of what the relay can and cannot see.
Last updated July 2026. This is a beta-period policy and will be reviewed with legal counsel before general availability.
1. Scope
This policy applies to the optional Beamfall Hosted Relay. It does not restrict the self-hosted Beamfall Core software, which you run on your own hardware under the AGPL v3.
2. What the relay can and cannot see
The Hosted Relay is a byte-blind SNI relay. It routes by peeking the SNI hostname in the TLS ClientHello and forwarding raw encrypted bytes. It can observe SNI hostnames, connection metadata, and traffic volumes; it cannot see media content, titles, or your library.
This is stated, not hidden: the relay authorizes a tunnel, not a history of what you watched. Metadata is used only for routing, abuse handling, and capacity.
3. Fair use
Published, honest fair-use guidance for the hosted relay is approximately 1–2 TB per month per account and up to 3 concurrent remote streams. There is no hard bitrate cap; sustained multi-viewer fan-out that looks like redistribution rather than personal remote access may trigger anomaly alerts and review.
4. Prohibited use
You may not use the relay to distribute content you have no right to distribute, to route child sexual abuse material (see the CSAM policy), to attack or overload infrastructure, or to evade the fair-use guidance through automated redistribution. Repeat copyright infringement is handled under the Copyright/DMCA policy.
5. Enforcement
Violations may result in throttling, tunnel suspension, or account termination. Report abuse to abuse@beamfall.com.
6. What happens when an anomaly alert fires
The relay is byte-blind: an anomaly alert means the traffic pattern looks like sustained multi-viewer fan-out, not that we inspected your content. We never adjudicate content to respond to an alert. Response is content-blind, policy-based, and staged: (1) a fair-use review of the account's volume and stream-count pattern against the published thresholds, (2) a throttle-by-policy conversation with the account holder about the pattern, (3) an account review if the pattern persists, and (4) AUP termination of hosted-relay access for egregious or repeated fan-out that looks like reselling access, never for what the relay cannot see. Each alert and its disposition is logged for consistent enforcement.