ThreadsHost logo

1. Introduction

By accessing and using the services offered by ThreadsHost, the user acknowledges and agrees to be bound by these Terms and Conditions. These provisions may be modified from time to time, and any relevant changes will be communicated through our official channels.

This website and all related services are managed by ThreadsHost. Throughout this document, references to “we,” “our,” or “the company” refer directly to ThreadsHost. Our platform provides users with information, tools, and features, always with the understanding that their use implies compliance with the terms, conditions, policies, and warnings specified herein.

By browsing the site, registering, or contracting any service, you are making use of our resources (“Services”) and agree to be bound by both these Terms and any supplemental policies indicated or linked from this document. These conditions apply to all users, without distinction, including visitors, customers, developers, collaborators, and suppliers.

We recommend that you read these Terms carefully before using our services. If you do not agree with any of the points set forth herein, we ask that you refrain from using the platform. Accessing, browsing, or purchasing any product shall constitute full and irrevocable acceptance of these terms.

All future features or tools that are integrated into the site will also be subject to these conditions. ThreadsHost reserves the right to update or modify the Terms and Conditions at any time. It is the responsibility of the user to periodically review this section to be aware of possible changes. Continued use of our services after an update will be considered tacit acceptance of the new terms.

2. User Account

2.1. ThreadsHost reserves the right to suspend or delete any account at any time, with or without prior notice, if it considers that there are justified reasons.

2.2. When contracting a server or other service, the customer is paying exclusively for its use. All resources and infrastructure remain the property of ThreadsHost.

2.3. It is the customer's responsibility to maintain the confidentiality of their credentials and to monitor the use of their account. In the event of unauthorized access or security incidents, they must notify us immediately. To share access with third parties (such as configurators or technicians), they must use the sub-user option provided in the panel.

3. Billing and Payments

3.1. ThreadsHost services are activated only after payment confirmation and verification of its validity. Normally, this process is automatic, but in specific cases it may require manual validation. If fraudulent activity is detected or suspected, ThreadsHost may request additional documentation to confirm the buyer’s identity.

3.2. If an active service is not renewed before its expiration date, it will be automatically suspended and become inaccessible. During this suspension period, the data associated with the service will be stored for a maximum of 7 days.

3.3. If payment is not made within the aforementioned period, the service will be permanently canceled and all files will be deleted with no possibility of recovery.

3.4. Any attempt to manipulate the payment system or carry out malicious transactions will result in the immediate cancellation of the account and the irreversible deletion of all associated services.

4. Cancellation and Refund Policy

Cancellations

4.1. To cancel a service, the client must submit a request through the ThreadsHost client area. If this action is not taken, it will be assumed that the client wishes to continue with the service, and renewal and billing notifications will continue to be sent.

4.2. In the case of recurring payments through platforms such as PayPal, the user must manually cancel the automatic subscription from their own account. If this is not done, payments will continue to be processed and will be credited as account balance for future purchases. We recommend reviewing our refund policy for more details.

4.3. Once a cancellation request has been submitted, the remaining days of the contracted service will not be refunded. Please consult the current policy if you have any additional questions.

Refunds

4.4. Refunds will only be issued if it is proven that ThreadsHost incurred a direct failure. Each case will be evaluated individually. Please note that we are not responsible for errors in internal configurations made by the client; our commitment is to ensure a proper operating environment.

4.5. No refunds will be granted if the account was suspended or canceled due to non-compliance with these Terms.

4.6. Refunds will be processed exclusively through the same payment method used for the purchase and in the name of the original account holder. Refunds will not be issued to third parties.

4.7. Any attempt at a chargeback, bank dispute, or unjustified claim will result in the permanent suspension of all associated services and the closure of the account, regardless of the outcome of such a dispute.

Valid cases for refunds:

  • Critical node overload: If node usage exceeds 95% for more than 24 hours and affects performance, the corresponding amount may be refunded.
  • Lack of technical support in urgent situations: If no response is provided within 24 hours to a serious incident, a refund may be considered.
  • Automatic charges after effective cancellation: If a payment is processed in error after the service has been properly canceled, the amount will be refunded.
  • Cases where refunds do not apply:
  • Failures caused by external plugins or mods.
  • Errors resulting from configurations made by the client.
  • Automatic renewals that were not canceled in time.
  • Lack of technical experience to manage the server.
  • Change of mind or voluntary decision not to continue after the purchase.

5. User Responsibilities

5.1. Account protection: The user is responsible for safeguarding their login credentials and avoiding sharing them with other people. If access needs to be granted to third parties (for example, technicians or collaborators), this must be done exclusively through the sub-user feature. Any unusual or suspicious activity must be reported immediately to the support team.

5.2. Timely payments: The client must ensure that payments are made within the corresponding deadline to avoid service suspension. If the situation is not regularized, data may be permanently deleted after the established period.

5.3. Control of automatic payments: If the client has enabled automatic renewals, they must manage and manually cancel them if they decide not to continue. Failure to disable them may result in unwanted charges.

5.4. Responsibility for backups: Although ThreadsHost may offer backup options, the user is primarily responsible for maintaining up-to-date copies of their information. We do not guarantee data recovery in all cases.

5.5. Acceptance of rules: It is the client’s obligation to comply with the Terms and Conditions, as well as all current ThreadsHost policies. Any violation may result in warnings, penalties, or service cancellation.

5.6. Responsible use of resources: The client must ensure that their configuration, use of plugins, or any other adjustments do not generate excessive consumption or affect the stability of the shared environment.

5.7. Proper handling of disputes: Any issue related to payments must be resolved through support. Initiating chargebacks or unfounded disputes may lead to the immediate cancellation of all contracted services and the deactivation of the account.

6. Backups

6.1. ThreadsHost does not provide automatic backups for dedicated servers or VPS. For game services such as Minecraft, periodic backups may be performed, but it is not guaranteed that the data will be fully protected against loss or corruption.

6.2. Some backups may become unusable due to errors in the files prior to being backed up or due to alterations during the backup process. This may compromise their functionality when attempting to restore them.

6.3. The ThreadsHost support team may assist in reviewing and troubleshooting issues related to backups, but does not commit to guaranteeing full recovery or the integrity of the stored data.

6.4. By contracting our services, the client accepts that it is their responsibility to maintain up-to-date backups of their critical information, as ThreadsHost assumes no responsibility for data loss.

7. Legality and Regulations

7.1. The contracted servers must comply with the terms of use and legal policies established by the developers of each game. In the case of Minecraft, all users are required to accept Mojang’s official EULA (https://www.minecraft.net/en-us/eula) before starting the server. ThreadsHost has no affiliation with Mojang AB, Rockstar Games, or other companies that own the supported games.

7.2. Although ThreadsHost implements security measures to protect its infrastructure, no system is infallible. The client understands and accepts that the use of digital services involves risks, including potential vulnerabilities or attacks. By using the platform, the user assumes this reality and releases ThreadsHost from any liability for damages caused by security incidents.

7.3. ThreadsHost may cooperate with official authorities of any jurisdiction by providing client information, without prior notice, when required for legal investigations, judicial proceedings, or in cases of suspected crimes such as fraud, cybercrime, or rights violations. The client acknowledges and accepts that such legal cooperation will not give rise to compensation or claims against the company.

8. Modifications to the Terms

ThreadsHost reserves the right to update or modify its Terms of Service and Privacy Policy at any time, without prior notice. Any changes made shall not be considered a valid justification for early service cancellation or for failing to pay outstanding balances.

The client acknowledges having been informed of the characteristics of the contracted service, as well as the costs and conditions in effect at the time of purchase. The client also accepts that such values may change occasionally due to factors such as resource availability, market fluctuations, or operational adjustments. In the event of an increase in rates or charges, the client will be notified before the next billing cycle in which the change takes effect.