Acceptable Use Rules

• Be lawful. Do not use Fliver to commit or facilitate crimes.
• Be truthful about authorship. Do not claim Fliver created or endorses your Endpoint payloads.
• Be a good tenant. Do not harm the platform, other customers, or the open internet.
• Minimize harm. Do not expose private data, secrets, or abusive content through public URLs.
• Cooperate with enforcement. Respond to abuse notices and fix issues promptly.

You are solely responsible for scripts, plugins, configurations, and upstream systems that produce Endpoint responses. This includes JSON bodies, error messages, headers you set, status codes, and side effects triggered by requests (kicks, bans, commands, writes).

• Do not publish credentials, session tokens, private keys, webhook secrets, or internal admin URLs.
• Do not expose private player messages, emails, IPs, real-life identities, or payment data unless you have a clear lawful basis and the data subjects expect that disclosure.
• Do not build Endpoints that execute arbitrary untrusted input as shell/game commands without strict allowlists and authentication.
• Authenticate and authorize sensitive Endpoints yourself (tokens, signatures, allowlists). Public-by-default does not mean unprotected-by-default for dangerous actions.
• Assume crawlers, scrapers, and hostile clients will call every public path you register.

You must not create, store, relay, or serve through Fliver any content that:

• Involves child sexual abuse material or sexual content depicting minors (zero tolerance; we will report to authorities where required).
• Incites violence, terrorism, or violent extremism.
• Constitutes illegal hate speech or unlawful harassment under applicable law.
• Facilitates scams, phishing, romance fraud, investment fraud, or impersonation of banks, platforms, or individuals.
• Distributes malware, exploit kits, ransomware instructions intended for misuse, or credential-stealing pages.
• Infringes copyrights, trademarks, or other IP rights (including piracy storefronts).
• Reveals non-public personal data for doxxing or stalking.
• Provides instructions primarily designed to commit cyberattacks against systems you do not own or lack authorization to test.

• Launching or amplifying DDoS, flood, or resource-exhaustion attacks via Fliver.
• Open proxies, open redirects, or generic traffic-laundering through Fliver hostnames.
• Cryptomining on Fliver infrastructure or forcing miners onto visitors.
• Brute forcing Fliver auth, pair codes, or other customers’ Projects.
• Attempting to escape sandboxing, read other tenants’ data, or compromise gateway/control-plane systems.
• Circumventing suspensions, creating ban-evasion accounts, or automating mass Project creation for abuse.
• Scraping Fliver Dashboard or internal APIs in ways that degrade service or violate access controls.

Fliver is commonly used with Minecraft and similar games. In addition to general rules:

• Do not use Endpoints to harass players off-platform with leaked private data.
• Do not expose operator-only commands to the public internet without strong authentication.
• Do not use Fliver to automate griefing, unauthorized economy duplication exploits against third-party servers, or attacks on networks you do not operate.
• Respect Mojang/Microsoft, Hytale, and other platform Terms where they apply to your server operations.
• If you publish ban lists or moderation data, ensure your community rules and privacy notices cover that disclosure.

Free and paid plans may include rate limits, concurrency limits, and feature gates. You must not attempt to bypass quotas. Sustained abnormal traffic that threatens platform stability may be throttled or blocked even if not intentionally malicious.

You should implement caching and sensible client behavior for high-traffic Endpoints. Fliver may introduce global protections (WAF, bot management, rate limits) that affect traffic patterns.

• Do not imply LogicByte or Fliver authored, verified, or endorses your Endpoint content.
• Do not spoof Fliver administrative notices or phishing pages that imitate Fliver login.
• You may state that your server is "powered by Fliver" in a factual way if you are a customer in good standing, unless we revoke that permission for misuse.

Report suspected violations to abuse@fliver.net. Include:

• The full Endpoint URL and timestamps (UTC).
• A description of the harm or illegal activity.
• Sample response bodies or screenshots if safe to share.
• Your contact details and relationship to the issue (target, researcher, rights holder, etc.).
• For copyright claims, information reasonably sufficient to identify the work and your rights.

Without prior notice when necessary, we may:

• Warn you and require remediation.
• Rate-limit, geotblock, or challenge traffic to a Project.
• Disable specific Endpoints or scripts sync.
• Revoke pair codes and tunnel sessions.
• Suspend or terminate Projects or the entire account.
• Refuse future registrations associated with abuse patterns.
• Share indicators of compromise with providers or authorities where appropriate.

Good-faith security research against Fliver itself may be welcome if it avoids privacy violations, data destruction, and service disruption, and if findings are reported responsibly to security@fliver.net (or abuse@fliver.net if that mailbox is the designated intake). Research that includes exploiting other customers’ Projects or players without authorization is not permitted.

We may maintain a clearer vulnerability disclosure policy later; until then, use common-sense coordinated disclosure.

• Keep contact emails reachable for abuse notices.
• Revoke compromised sessions immediately.
• Review scripts after Fliver or plugin upgrades for unintended public exposure.
• Accept Project responsibility checkboxes truthfully when creating Projects.
• Ensure teammates understand these Rules before receiving pair codes.

These Rules do not permit anything illegal even if not listed. Local law overrides where mandatory. Third-party platform rules (payment providers, game platforms, cloud hosts) may impose additional constraints.

Severe illegal content may be reported to authorities without advance notice to the account holder where legally required or where notice would increase risk of harm.

Abuse and Rules enforcement: abuse@fliver.net

Legal: legal@fliver.net

Privacy: privacy@fliver.net

Operator: LogicByte Studios — https://logicbyte.org