Fair Use Policy
Last Updated: November 12, 2025
1. Purpose
This Fair Use Policy (FUP) is designed to ensure a high-quality, stable experience for all users by preventing excessive or abusive use of shared resources. Our services are hosted on shared infrastructure, and individual usage patterns can significantly impact other users' experiences. This policy outlines the standards we enforce to maintain service quality and fairness for the entire community.
2. CPU Usage
Your CPU resources are managed through a shared pool model. If you have multiple servers, your total CPU usage across ALL servers is aggregated and compared against your plan's total CPU allocation. Our resource pool system monitors this aggregate usage in real-time.
When aggregate CPU usage exceeds your pool limit, the system automatically applies proportional scaling: all your servers' CPU allocations are scaled down proportionally to bring total usage back within your limit. Once usage returns to normal, allocations are restored.
This policy primarily targets activities not typical for a game server, such as:
- Compiling software or source code for extended periods
- Running complex mathematical calculations or scientific simulations unrelated to the game
- Rendering or video transcoding
- Cryptocurrency mining or proof-of-work calculations
- Any other CPU-intensive process unrelated to game server operation
Legitimate game server operations, including server plugins, mods, and standard game mechanics, are always permitted. Brief bursts up to 120% of your allocated limit are allowed to accommodate normal traffic spikes.
3. Memory (RAM) Usage
Your server is allocated a specific amount of RAM as defined in your service plan (e.g., 1024 MB). Our resource pool system monitors aggregate memory usage across ALL your servers. If your total memory usage across all servers exceeds your allocated pool limit, our system will automatically apply proportional scaling to bring usage back within limits.
Prohibited memory abuse includes:
- Running memory-intensive applications unrelated to game server operation
- Memory leaks from poorly written plugins or mods
- Intentionally allocating excessive memory to degrade performance
We continuously monitor memory usage patterns. If aggregate memory usage persistently exceeds your limits, the system will automatically proportionally scale down allocations across your servers to enforce the limit. The allocation can be restored once usage returns to normal.
4. Disk and Storage
Your allocated disk space is managed through the shared pool model. The aggregate disk usage across ALL your servers is monitored and compared against your plan's total disk allocation. Our resource pool system enforces this limit automatically.
When aggregate disk usage exceeds your pool limit, the system will automatically proportionally scale down allocations to bring usage back within limits. Disk space is intended exclusively for files directly related to the operation of your game servers, including:
- Game worlds, maps, and saves
- Plugins and mods
- Configuration files
- Server logs (within reason)
- Legitimate server-related backups
Using your server's disk as a general-purpose file storage service, personal backup drive, or media library is strictly prohibited. Specifically prohibited activities include:
- Operating a file-sharing or file-hosting site
- Hosting video, movie, or music libraries
- Storing personal or corporate documents unrelated to your server
- Backup services for personal computers or other systems
- "Disk fillers" or scripts designed to intentionally fill up storage space
- Storing large quantities of ISO files, archives, or media
Violation of disk storage policies will result in immediate suspension without warning. Repeated violations will result in permanent account termination.
5. Network Usage and Bandwidth
Your network connection is allocated for normal game server traffic. While we do not enforce a strict bandwidth cap, we actively monitor for usage patterns indicative of abuse or misuse. The following activities are strictly prohibited:
- DDoS Attacks: Participating in, being the target of, or launching Layer 4 (L4) or Layer 7 (L7) DDoS attacks. Repeated targets of attack may result in account suspension.
- Web Scraping and Data Crawling: Automated scraping, crawling, or bulk downloading of data from any website or service.
- Public Proxies/VPNs: Running public proxy services, VPN endpoints, or tunnel services.
- Botnet/C2 Servers: Hosting command-and-control servers, botnets, or similar infrastructure.
- P2P Abuse: Operating as a BitTorrent seed node or participating in unauthorized peer-to-peer networks.
- DNS Abuse: Running open DNS resolvers or performing DNS amplification attacks.
In essence, as long as you are using your server for its intended purpose of hosting a legitimate game server or application, your network usage will be considered fair. Normal game traffic, legitimate backups, and standard web requests are always permitted.
6. Enforcement and Monitoring
We continuously monitor server resource usage across your entire resource pool using automated systems and real-time metrics. When aggregate resource usage exceeds your plan limits, our enforcement system automatically takes action:
- Automatic Scaling: When total usage across all your servers exceeds your pool limit, the system automatically applies proportional scaling. All server allocations are scaled down proportionally to bring usage back within your limit.
- Allocation Restoration: Once usage returns to normal and is within limits, allocations are automatically restored. The system distributes available capacity fairly among your servers.
- Manual Escalation: For severe violations (illegal content, malware, attacks), we take immediate manual action including server suspension or account termination.
Severity-based responses:
- Minor Violations: Automatic resource scaling via the pool system.
- Moderate/Repeated Violations: Manual warning, throttling, and temporary suspension (24-72 hours).
- Severe Violations: Immediate manual account termination and forfeiture of all credits without warning.
7. Resource Allocation by Plan
Different service plans come with different resource allocations. It is your responsibility to select a plan that meets your needs. Resource downgrades or limiting your service will not result in refunds.
8. Shared Pool Model and Burst Allowance
Resource Pool System: Your resource limits work as a shared pool across all your servers. If you have 5 servers and a 500 MB total memory allocation, the combined memory usage of all 5 servers should not exceed 500 MB. Our system monitors and enforces this aggregate limit automatically.
Burst Allowance: We allow up to a 20% burst allowance for brief spikes in CPU and memory usage to accommodate normal server operations and sudden traffic increases. Bursts are allowed for short durations, but sustained usage above your allocated limit will trigger automatic proportional scaling of your server allocations.
How Scaling Works: If your total usage consistently exceeds your pool limit, all your servers' resource allocations are scaled down proportionally. For example, if total CPU usage is 20% over limit, each server's CPU allocation is reduced by 20% to bring the aggregate back within limits. Allocations return to normal once usage normalizes.
9. Policy Updates
We reserve the right to update this Fair Use Policy at any time to address emerging abuse vectors or maintain service quality. Changes will be posted with an updated date. Your continued use of the service constitutes acceptance of policy updates.
10. Appeals
If you believe your account has been suspended or terminated in error, you may submit an appeal through our support system within 14 days of the action. Provide detailed information about your use case, and we will review your case. Appeals for severe violations (illegal content, malware hosting, attacks) are unlikely to be successful.
11. Contact Support
If you have questions about whether a specific activity violates our Fair Use Policy, please contact our support team before implementing it. We're happy to clarify what is and isn't permitted for your specific use case.