Acceptable Use Policy.
The boundaries every account on the NexusHub grid agrees to. Six violation categories, exactly what triggers them, and exactly what happens next — filed in full, not softened.
99.998%
clean traffic ratio, grid-wide
Six violation categories.
Filed in the order they're checked. Engaging in any one triggers the enforcement procedure below.
Malicious payloads & botnets
critical purgeDistributing trojans, rootkits, command-and-control backdoors, ransomware, or any executable payload built to gain unauthorized access.
Phishing & deceptive mimicry
critical purgeHostile credential harvesting, deceptive banking interfaces, or brand impersonation intended to extract personal or financial data.
Terrorism, violence & hate
critical purgeHosting propaganda, violent extremism, self-harm encouragement, or coordinated harassment against protected groups. Absolute zero tolerance.
Computational & edge abuse
high isolationCrypto mining scripts, continuous stress-testing bots, or runaway processes intended to degrade neighboring instance throughput.
Unsolicited bulk mail
high isolationOperating spam relay clusters, purchasing unvetted email lists, or hosting landing funnels for deceptive mass solicitation.
Illicit trade & darknet commerce
critical purgeUnregulated narcotics distribution, counterfeit licensing, unlicensed weapons commerce, or unlawful digital contraband.
What happens after a flag.
Four steps, in order, every time — from automated detection to a formal appeal window.
Autonomous detection
Real-time edge heuristic scanners or verified external telemetry reports trigger automated forensic isolation.
Security review
Trust & Safety engineers audit the flagged instance's logs and sandbox its payloads by hand.
Targeted action
Malicious payloads are severed from the edge routing table and the affected account is suspended.
Formal appeal
Account holders get a 48-hour window to submit signed counter-evidence if flagged in error.
Fair Use & Shared Edge Quotas
NexusHub executes instances across shared sovereign clusters. To maintain deterministic latency for every neighboring workload, individual accounts cannot trigger abusive CPU looping or unmetered bandwidth hoarding.
Active Abuse on the Grid?
If an instance operating on NexusHub infrastructure violates this policy, skip normal support queues and dispatch a priority report straight to Trust & Safety.
Automated triage SLA: < 45 minutes guaranteed