Terms & Conditions

• Company - LLC “MyGO” (SERVER1.GE).
• Client - an individual or legal entity that places an order or creates an account.
• Console/Portal - console.server1.ge, where management, tickets, and invoices are handled.
• Service - domains, hosting, VPS, Dedicated/GPU, SSL, security, Google Workspace, and others.
• Third Party / Upstream Provider - UGT / OVH / Vultr / Hetzner / Cloud9 and other partners whose infrastructure may be used to deliver part of the service.

1. Ordering, paying for, or activating a service creates a service agreement relationship between the Client and the Company.
2. If special terms exist for a specific service, such as Managed VPS/Managed Server, those special terms shall prevail.
3. If part of the service is delivered through third-party infrastructure, the policies/restrictions of the upstream provider may also apply. Such restrictions are binding on the Client to the extent that they are technically or legally necessary.

1. The Client is responsible for protecting the passwords of the console, panels (Plesk/SSH/RDP), and for access control.
2. The Company is not liable for damage caused by the Client’s incorrect configuration, insecure passwords, or access obtained by a third party.
3. The Company may request account verification or supporting information to prevent fraud or regulatory risk.

1. Prices, packages, limits, and add-ons are listed in the console/site. Taxes, where applicable, are added in accordance with the law.
2. Most services are prepaid. In case of non-payment, the Company is authorized to suspend the service.
3. The Client is responsible for renewal unless automatic renewal is enabled for the specific product and there is sufficient balance.
4. Chargeback/Fraud: regulated by System Policies; in case of a dispute, the Company is authorized to suspend services until the dispute is resolved.
5. If the Client creates a significantly increased financial or operational risk, such as repeated chargebacks or suspected fraud, the Company is authorized to refuse service.

• Registrant: the domain owner is the registrant (Client). The Client is responsible for the accuracy of WHOIS/registry data.
• Registry rules: domains are subject to the policies of the relevant registry/registrar, including renewal, transfer, redemption, and dispute policies.
• Return/Refund: domain registration, renewal, and transfer fees are generally non-refundable, except where required by law or if the operation was not technically completed.
• Transfer: the Client is responsible for the auth/EPP code, lock/unlock status, registry timeframes, and third-party requirements.
• Disputes: in case of trademark/UDRP/court disputes, the Company acts in accordance with registry/legal requirements and may block domain operations.

1. “Managed” component: the Company is responsible for producing/storing backups under the condition above and providing the self-restore function in Plesk for the relevant packages.
2. CMS/Code/Applications: the Company does not accept responsibility for logical malfunction, hacking, malicious code, conflicts, SEO results, or Client-uploaded content related to WordPress/Plugins/Themes/CMS.
3. Self-Restore: on Web Hosting / WordPress / Reseller packages, the Client can restore data from the Plesk panel if the package includes this feature.
4. Best-effort note: backups reduce risk, but 0% risk does not exist (deletion, corruption, ransomware, upstream failure). For business-critical systems, an additional client-side off-site backup is recommended.
5. Fair Use: excessive resource usage in a shared environment (CPU/RAM/IOPS/inodes/processes) may become grounds for limitation.
6. DDoS: limited protection is available, not unlimited. In case of a severe attack, temporary blocking/filtering may be applied to protect the infrastructure.

1. Unmanaged VPS: the Company provides availability of the infrastructure/network/virtualization, while OS/applications/patching/hardening/data are the Client’s responsibility.
2. Managed VPS: the exact scope (updates, hardening, monitoring, incident handling) is defined by the package/order and may be limited.
3. Backups/Snapshot: if snapshot/backup is specified in a particular VPS plan, it is used as a best-effort component and is not disaster recovery (DR). If not specified, the Client is responsible for their own backups.
4. As a rule, the Company does not have access to the Client’s data inside the VPS; the Client is responsible for the content.

• Unmanaged: infrastructure/network - the Company’s side; OS/apps/security/backup - the Client’s side.
• Managed: the scope of management is defined by the package, such as OS updates, monitoring, and incident response.
• GPU servers: designed for AI/ML/HPC workloads. Crypto mining is prohibited by default, unless otherwise agreed in writing.

• SSL: certificate issuance/revocation depends on CA policy and domain validation. The Company cannot bypass the CA’s decision.
• Web/Email Security: protection/filtering results are best-effort; 100% blocking/protection does not exist (false positives/false negatives are possible).
• Google Workspace: this is a third-party product; Google’s terms apply. The Company provides sales/billing/initial configuration assistance where specified, but liability for outages on Google’s side is limited.

1. Part or all of the services may be delivered through third-party DC/network/cloud platforms: UGT / OVH / Vultr / Hetzner / Cloud9.
2. In such cases, compensation/SLA credit may be limited to the compensation actually received by the Company from the upstream provider (Back-to-Back).
3. The Company acts in good faith; however, liability for outages beyond the control of third parties does not exceed the limits defined by this document and the SLA.

1. The SLA is provided in detail on the SLA page.
2. SLA credit is the only form of compensation for an availability breach, except where required by law.
3. A credit request must be submitted within the timeframes defined in the SLA and must include the required details (service/ID/times).

1. The Company is authorized to restrict/suspend the service in case of non-payment, violation of System Policies, suspected fraud, or critical security risk.
2. After service cancellation/deactivation, unless otherwise agreed, the Client is given 3 business days to export data; after that, access may be revoked and data may be deleted.
3. For domains/registry operations, “deletion” of data does not apply to the part managed by the registry/registrar.

1. Services are provided on an “as-is / as-available” basis, unless otherwise required by law.
2. The Company does not guarantee that the service will be continuous or uninterrupted under all circumstances, such as DDoS, upstream failure, force majeure, or planned maintenance.
3. Verbal or written recommendations provided by the Company/support do not constitute legal/financial advice and do not create any additional warranty.

1. The Company is not liable for indirect/consequential damages, including profit, reputation, data loss, downtime, third-party claims, and penalties.
2. The Company’s total liability is limited to the last 1 month fee of the service to which the claim relates, except where required by law.
3. SLA credits are the only and final form of compensation for an availability breach, except where required by law.

The Client agrees to indemnify the Company for any damage/cost/claim arising from the Client’s: (a) violation of law/policies; (b) violation of third-party rights; (c) Client content/actions.

1. The Company is not liable for failure to perform obligations if such failure is caused by force majeure circumstances, including natural disasters, large-scale power/network outages, government restrictions, war, and others.