Nexos Acceptable Use Policy
This Acceptable Use Policy ("AUP") is part of the Nexos Terms of Service and applies to everything you do on or through the Service — every account, API key, workload, preview environment, exposed endpoint, and node. Because Nexos runs many tenants' workloads on shared infrastructure, abuse doesn't just harm us: it harms every other user whose code runs beside yours. We enforce this policy accordingly.
1. Illegal or harmful content
You may not use the Service to store, deploy, serve, or transmit content that:
- is illegal under the laws of Serbia, your jurisdiction, or the jurisdiction where the workload runs;
- sexually exploits or endangers minors in any form (zero tolerance — reported to authorities);
- infringes copyright, trademarks, trade secrets, or other proprietary rights;
- consists of malware, ransomware, spyware, or other malicious code intended to harm third parties;
- constitutes fraud, phishing, or deceptive impersonation of any person or organization;
- violates the privacy of others, including doxxing and unlawfully obtained personal data.
2. Prohibited activities
You may not use the Service to:
- attack, scan, flood, or disrupt any network, system, or service you are not explicitly authorized to test — including other Nexos tenants, nodes, and the platform itself;
- operate botnets, command-and-control infrastructure, or infrastructure for distributing malware;
- send spam or bulk unsolicited messages, or run open relays/resolvers;
- mine cryptocurrency or run similar proof-of-work/proof-of-space workloads (this is a development-preview platform, not general compute);
- operate open proxies, VPN exit points, Tor exit relays, or traffic-anonymization services for third parties;
- host production workloads that misrepresent themselves as previews to evade the platform's limits, where this circumvents plan restrictions;
- violate GitHub's, Paddle's, or another integrated service's terms through the Service.
3. Platform integrity and fair use
You may not:
- circumvent, or attempt to circumvent, quotas, resource limits, build admission, or billing — including by creating multiple free accounts to stack quotas;
- tamper with the node agent, container isolation, or the WireGuard mesh, or attempt to escape a container or access another tenant's workloads or data;
- resell or white-label the Service without a written agreement;
- use shared credentials or let others use your account in ways that mask who is responsible for activity.
4. Additional rules for node operators
If you connect nodes to the Service, you additionally may not:
- inspect, copy, modify, exfiltrate, or interfere with tenant workloads, images, secrets, or data processed on your node;
- run a modified or tampered node agent, or misreport your node's capacity, identity, or availability;
- intercept or manipulate tenant network traffic beyond what routine network operation requires.
5. Security research
We welcome good-faith security research into the Nexos platform itself. Report vulnerabilities privately to legal@nexos.rs and give us reasonable time to fix them before disclosure. Good-faith research must never target other tenants' data or workloads, nodes you do not own, or degrade the Service; testing within your own accounts and environments is the boundary. We will not pursue action for good-faith research conducted within these rules.
6. Enforcement
- We may investigate suspected violations and may throttle, quarantine, or stop workloads, revoke endpoints and API keys, deregister nodes, and suspend or terminate accounts.
- For minor violations we will normally warn you and give you a chance to cure; for serious violations (Sections 1, 2, and 4) we may act immediately and without notice.
- We report unlawful content and activity to competent authorities where required or appropriate.
7. Reporting abuse
To report content or behaviour that violates this policy, email legal@nexos.rs with the preview URL, endpoint, or other identifying details. We review all reports.
8. Changes
We may update this AUP as the platform and the threat landscape evolve. It shares a version identifier with the Terms of Service; material changes will be presented for your review in the dashboard.