CanerAkar This Acceptable Use Policy explains what you may not do on FPS.ms. It applies to every account, user, team, subuser, server, container, app, website, database, file, backup, snapshot, domain, DNS zone, email account, public URL, proxy, deployment, and any traffic or content connected to FPS.ms. This policy is not exhaustive. If something is harmful, illegal, abusive, deceptive, unsafe, or likely to damage FPS.ms, our users, our suppliers, or the public, we may treat it as a violation even if it is not listed word-for-word below.
1. Your Responsibility
You are responsible for your account and for activity by anyone who uses your account, services, teams, subusers, API keys, SSH keys, GitHub deployments, domains, DNS records, websites, apps, servers, or containers. You must keep your services secure. A compromised service that sends spam, joins a botnet, hosts malware, attacks others, mines cryptocurrency, or stores illegal content is still an AUP issue. You may not help, allow, encourage, sell, advertise, or facilitate activity that would violate this policy if you performed it yourself.2. Illegal and Harmful Content
You may not use FPS.ms to host, store, publish, link to, distribute, promote, sell, or facilitate illegal or harmful content or activity, including:- child sexual abuse material, sexual exploitation of minors, grooming, or any attempt to obtain, generate, distribute, or normalize such content;
- non-consensual intimate images, revenge pornography, sexual extortion, or sexual content involving people who did not consent;
- terrorism, violent extremism, credible threats, incitement to violence, or instructions for serious harm;
- hate, harassment, stalking, doxxing, threats, or targeted abuse;
- content that unlawfully exposes personal data, credentials, private keys, tokens, payment details, identity documents, logs, databases, or other private information;
- counterfeit goods, illegal drugs, illegal weapons, illegal gambling, fraudulent schemes, scams, pyramid schemes, or money-mule activity;
- content or services that violate Dutch law, EU law, the law where you live, or the law that applies to the affected people or systems.
3. Security Abuse
You may not use FPS.ms for security abuse, including:- DDoS attacks, DoS attacks, stressers, booters, flooders, amplifiers, reflection attacks, botnets, command-and-control systems, or services that enable them;
- malware, ransomware, spyware, worms, trojans, stealers, loaders, droppers, keyloggers, backdoors, rootkits, cryptojackers, or malicious scripts;
- phishing, pharming, credential theft, token grabbing, session hijacking, fake login pages, fake payment pages, or impersonation;
- credential stuffing, password spraying, account checkers, account generators, account shops, stolen account lists, token lists, combo lists, or tools designed for account compromise;
- unauthorized access, attempted unauthorized access, exploitation, scanning, probing, vulnerability testing, scraping, crawling, or enumeration against systems you do not own or have permission to test;
- spoofing, fake packet headers, source-IP forgery, email header forgery, misleading origin information, or attempts to hide abusive traffic origin;
- interception, packet capture, monitoring, or collection of traffic without permission;
- storing, selling, publishing, or distributing exploit kits, malware builders, bypasses, stolen credentials, or stolen personal data.
4. Network Abuse
You may not use FPS.ms in a way that disrupts, overloads, degrades, attacks, scans, or interferes with FPS.ms, other FPS.ms users, suppliers, third-party networks, or the internet. Prohibited network activity includes:- denial-of-service activity or preparation for it;
- open proxies, open mail relays, open recursive DNS resolvers, Tor exit nodes, public VPN/proxy services, traffic relays, or tunnelling services unless explicitly approved in writing;
- bandwidth abuse, excessive connections, excessive crawling, excessive API traffic, or traffic patterns that harm service quality;
- public file mirrors, software mirrors, CDN-like workloads, bulk download services, or high-volume redistribution unless the product explicitly allows it;
- activity likely to place FPS.ms IP addresses, domains, mail systems, or suppliers on abuse lists, blacklists, blocklists, or reputation feeds;
- attempts to bypass rate limits, port limits, storage limits, CPU limits, memory limits, bandwidth limits, plan limits, hibernation, renewal, or anti-abuse systems.
5. Email and Messaging Abuse
You may not use FPS.ms to send, relay, facilitate, or advertise spam or abusive messages, including:- unsolicited bulk email, unsolicited commercial email, or unsolicited messages through chat, forums, games, bots, social platforms, or APIs;
- phishing, impersonation, misleading sender identities, forged headers, reply-to deception, or spoofed domains;
- mailing lists without valid consent, unsubscribe handling, and complaint handling;
- mail or message campaigns that cause complaints, bounces, blocklisting, provider warnings, or reputation harm;
- using third-party mail systems to promote or link to abusive content hosted on FPS.ms.
6. Intellectual Property and Software Abuse
You may not use FPS.ms to infringe or facilitate infringement of copyrights, trademarks, trade secrets, licenses, or other rights. Prohibited activity includes:- cracked, nulled, pirated, leaked, or stolen software, plugins, themes, mods, modpacks, maps, assets, accounts, keys, or licenses;
- warez, piracy portals, illegal streaming, illegal IPTV, torrent trackers, seedboxes, or indexes for infringing material;
- tools or instructions primarily designed to bypass DRM, license checks, anti-cheat, copy protection, paywalls, or access controls;
- using game, software, or platform assets in a way that violates the applicable EULA, license, or platform rules.
7. Game, Bot, and Community Abuse
FPS.ms hosts game servers, bots, and community infrastructure. You may not use those services for:- cheat sales, cheat distribution, cheat loaders, cheat panels, injectors, bypasses, or paid access to cheating tools;
- stolen game accounts, account generators, account checkers, token grabbers, or session theft;
- cracked servers, license-bypass servers, or EULA-violating monetization;
- harassment, raids, brigading, extortion, threats, doxxing, or abusive community behavior;
- gambling, betting, casino mechanics, real-money trading, or lootbox-style monetization where illegal or unsafe;
- bots designed for spam, scams, raids, scraping, credential theft, or platform abuse.
8. Resource Abuse and Misuse
You may not use FPS.ms resources in a way that is outside the intended product category or unfair to other users. Prohibited resource abuse includes:- cryptocurrency mining, plotting, farming, validating, or similar compute-for-token workloads;
- AI mining, proof-of-work systems, or reward farming that primarily consumes CPU, GPU, memory, disk, or bandwidth;
- AFK bots, fake players, keepalive scripts, artificial traffic, or automation designed to keep free game containers online when real users are not playing;
- using game, bot, or app containers as general virtual machines unless the product explicitly allows it;
- using storage for photo sharing, video sharing, streaming, archive hosting, backups unrelated to the service, mirrors, or file repositories;
- running heavy pre-generation, indexing, transcoding, scraping, crawling, compiling, or batch jobs that disrupt other users or exceed the product purpose;
- reselling free plans, pooling accounts, account sharing networks, or bundling multiple accounts to bypass limits.
9. Domains, DNS, Webhosting, and Email
You may not use FPS.ms domains, DNS, webhosting, or email-related services for:- phishing, malware, spam, scam shops, counterfeit goods, illegal marketplaces, or brand impersonation;
- domain fronting, fast flux, DNS tunnelling, domain generation algorithms, malicious redirects, or abuse infrastructure;
- false registrant data, domain hijacking, unauthorized DNS zones, or domains you do not have the right to manage;
- trademark infringement, cybersquatting, typosquatting, deceptive domains, or impersonation;
- hosting leaked databases, stolen personal data, card data, credential dumps, or other unlawful datasets.
10. High-Risk and Regulated Use
You may not use FPS.ms for high-risk services where failure, downtime, latency, data loss, or security issues could cause serious harm. This includes life-safety, emergency response, medical systems, critical infrastructure, industrial control, financial trading, and other mission-critical workloads. Regulated services, financial services, medical services, gambling, adult services, age-restricted services, weapons, controlled substances, and similar activities may be refused or removed where we believe they create legal, safety, payment, supplier, or abuse risk.11. Reporting Illegal Content or Abuse
Anyone can report suspected illegal content or AUP violations involving FPS.ms. Reports should include:- your name and contact details;
- the affected URL, domain, IP address, server address, email header, or other precise location;
- why you believe the content or activity is illegal or violates this policy;
- evidence such as screenshots, logs, timestamps, message headers, or registry details;
- whether there is an urgent threat to life, safety, or security.
[email protected]. Authorities can contact us at [email protected] as well. If there is an imminent threat to life or safety, contact the competent emergency or law-enforcement authority first.
Knowingly false or abusive reports may be rejected and may lead to action where allowed by law.
12. How We Handle Reports and Violations
We review reports and detected violations as quickly as reasonably possible. We aim to make decisions carefully, objectively, proportionately, and consistently. Depending on the issue, we may:- request more information;
- forward a report to the customer for remediation;
- remove or disable content;
- block traffic, ports, domains, DNS records, email, or public URLs;
- rate-limit, isolate, quarantine, suspend, or terminate services;
- suspend or terminate accounts;
- preserve evidence, generate abuse bundles, or apply legal hold;
- notify affected providers, registries, payment processors, or authorities;
- refuse future service.