System Policies

Acceptable Use Policy (AUP) • DDoS • Abuse • Chargeback / Fraud

 

Company: LLC “MyGO” (Brand: SERVER1.GE)
Client Console/Portal: console.server1.ge
Last updated: February 05, 2026  |  Version: 3.6.9

1. Purpose and Scope

  1. This document regulates the rules for the safe, lawful, and stable use of SERVER1.GE infrastructure.
  2. The policies apply to all users/accounts, including sub-users (Reseller/Delegated access).
  3. The Company is authorized to carry out technical measures to ensure network/service stability and security, including rate-limit, filtering, shaping, blackhole/null-route, quarantine, and others.

2. Acceptable Use Policy (AUP) - Prohibited Activities

Any action/content that violates Georgian law or third-party rights, or creates infrastructure risk, is prohibited, including:

  • Malicious activity: malware, botnet, exploit, phishing, credential theft, ransomware, organizing or supporting DDoS/DoS.
  • Spam/email abuse: unsolicited bulk email (UBE), spoofing, open relay attempts, causing blacklisting, mass-mailing.
  • Illegal content: child exploitation materials, support for violence/terrorism, illegal trade/drugs/weapons, fraud.
  • Intellectual property: copyright/trademark infringement, pirated software/media, crack/keygen.
  • Unauthorized access: scanning/bruteforce, intrusion into other systems, MITM, credential stuffing.
  • Resource abuse (Fair Use): in a shared environment, any load that harms other users (CPU/RAM/I/O/IOPS/inodes/connection flood).
  • Crypto mining: prohibited by default, including VPS/Dedicated/GPU, unless permitted in writing for a specific package/client.
  • Gambling/betting: allowed only legally and with relevant licenses/regulations; upon request, the Company may require documentation and restrict the service based on risk assessment.

3. DDoS Policy - Protection, Limits, and Response

  1. Web Hosting / WordPress / Reseller services include limited DDoS protection (best-effort). We do not provide unlimited protection.
  2. During an attack, the Company is authorized to apply filtering/rate-limit, temporary IP/port block, or, in severe cases, null-route/blackhole to protect the infrastructure.
  3. In case of targeted L7 (HTTP) attacks, additional protection service/configuration (add-on), WAF rules, cache, CDN, or architectural changes may be required.
  4. If the Client is the source of an attack, or does not implement the mitigation measures requested by the Company, the Company is authorized to restrict network access until the incident is localized.

4. Abuse / Incident Handling - Reporting and Sanctions

Abuse Report channels:

Standard sanctions logic:

  1. First detection: temporary block/restriction, such as outbound mail block, HTTP quarantine, IP block, and a request to resolve the issue.
  2. Repeated violation or non-compliance: full block/suspension or contract termination.
  3. Critical cases: child exploitation, serious fraud, active malware/botnet - immediate disconnection may occur without prior notice.
  4. The Client is required to maintain system security, perform patching/hardening, and ensure that their account is not abused by third parties.

5. Chargeback / Fraud Policy - Chargeback, Dispute, and Suspension

  1. If the Client initiates a chargeback or payment dispute with a bank/PSP, the Company is authorized to temporarily suspend all related services until the dispute is resolved.
  2. In case of a chargeback, the Client is required to reimburse: (a) the disputed amount; (b) third-party fees/penalties; (c) administrative costs, if any arise.
  3. If the dispute is confirmed as fraudulent/incorrect, the Company is authorized to terminate the service and block the account to prevent recurrence.
  4. Refunds/returns, where applicable to a specific product, are regulated by the Terms & Conditions and/or the product description.

6. Changes to Policies

  1. The Company is authorized to update the policies at any time. The updated version is published on the website and becomes effective upon publication, unless otherwise specified.
  2. The Client’s continued use of the service after the update is considered acceptance.