Terms of Service

1. Definitions

The terms below have the meanings set out in this section across the body of this document and the related documents linked from /legal. The defined terms are capitalised on first use and lowercase thereafter. Counsel finalises the precise definitional language before deploy.

“Operator” refers to the legal entity identified in the operator footer of every BulletHost page. “Customer” refers to the natural or legal person who has procured a Service from Operator under these Terms. “Service” refers to the dedicated server, VPS, or addon procured by Customer from the Operator catalog at /server, /vps, or as listed on /price.

“BTCPay Self-Host” refers to the Operator-hosted instance of the BTCPay Server payment processor located at the endpoint disclosed at /payments. “Procured-Infrastructure Jurisdiction” refers to the jurisdictions in which Operator procures the physical infrastructure used to deliver the Service, currently the Russian Federation, the Republic of Belarus, and the Republic of Kazakhstan. “AUP” refers to the Acceptable Use Policy at /legal/aup.

“SLA” refers to the Service Level Agreement at /legal/sla. “Privacy Policy” refers to the Privacy Policy at /legal/privacy. “Refund Policy” refers to the Refund Policy at /legal/refund. “Order” refers to the Customer-initiated procurement transaction completed at /order/success.

2. Scope

These Terms govern the contractual relationship between Operator and Customer in relation to the Service. They do not govern third-party services that the Customer may invoke from within the Service environment. Counsel finalises the scope-of-application boundary before deploy.

By placing an Order at /order, Customer accepts these Terms together with the AUP, the SLA, the Refund Policy, and the Privacy Policy. The accepted bundle constitutes the entire agreement between Operator and Customer in relation to the Service. Prior representations made on the BulletHost site are superseded by the accepted bundle.

Operator may amend these Terms by publishing a revised version at /legal/tos with a new lastUpdated date. Material amendments take effect on the effectiveFrom date specified in the revised frontmatter. Customer may terminate under section 9 if Customer does not accept a material amendment.

3. Account terms

Customer accounts are created at /signup and managed at /cabinet. Operator collects the data set listed in the Privacy Policy at signup. Operator does not perform customer-side identity verification on the standard catalog tiers — see the Privacy Policy and the AUP for the full data inventory and the corresponding compliance posture.

Customer is responsible for keeping the account email and authentication credentials current and confidential. Operator is not liable for losses resulting from Customer’s failure to keep credentials confidential. Operator may suspend access on reasonable suspicion of credential compromise pending re-verification by the Customer through the contact channels listed in the operator footer.

Customer may operate one or more accounts under separate Order trails subject to the AUP and these Terms. Operator does not link separate Customer accounts on the operator-side beyond the data minimisation set out in the Privacy Policy.

4. Acceptable use cross-reference

The Acceptable Use Policy at /legal/aup forms part of these Terms. Customer accepts the AUP as a condition of Service use; the AUP enumerates the prohibited workloads, the response process, and the repeat-offender threshold. Counsel-finalised AUP wording governs in the event of any divergence between these Terms and the AUP.

5. Payment

Payment is settled in cryptocurrency only — the assets and rails enumerated at /payments. Operator does not accept fiat, does not accept payment cards, and does not invoke any third-party card processor in the payment loop. The brand stance on processor neutrality is documented at /payments and at /legal/refund.

All payments are processed via BTCPay Self-Host, the Operator-hosted instance of the BTCPay Server payment processor. The customer-visible invoice flow rotates the receiving address per Order; an address is never reused across Orders. The confirmation thresholds for each accepted asset are documented at /payments.

Customer is responsible for paying the network gas fee for the asset selected. Operator does not subsidise gas fees and does not refund a gas fee paid in error. The accepted asset triple (BTC, USDT-TRC20, XMR) is documented at /payments together with the per-asset operational notes.

Recurring billing is settled on the cycle selected at Order time (monthly, quarterly, or annually). Operator emits a renewal invoice the number of days before the cycle end specified in the operator-disclosed billing schedule. Customer may cancel before the renewal invoice issues to avoid the next-cycle charge.

6. Refund cross-reference

The Refund Policy at /legal/refund forms part of these Terms. Counsel-finalised refund wording governs in the event of any divergence between these Terms and the Refund Policy. The 7-day no-questions guarantee for the first invoice of any Service tier is documented at /legal/refund together with the per-asset refund mechanics and the addon-exclusion list.

7. SLA cross-reference

The Service Level Agreement at /legal/sla forms part of these Terms. The headline uptime targets — currently 99.9% for VPS tiers and 99.95% for dedicated tiers, both pre-launch placeholder pending Operator’s confirmation with the upstream procured-infrastructure provider — are documented at /legal/sla together with the credit ladder and the exclusion list. Counsel-finalised SLA wording governs in the event of divergence.

8. Suspension

Operator may suspend the Service on reasonable suspicion of an AUP violation pending investigation. The investigation timeline and the customer-side response window are documented at /legal/aup. The suspension does not constitute termination unless Operator subsequently terminates under section 9.

Operator may suspend the Service for non-payment after the grace period documented in the operator-disclosed billing schedule. Operator emits a non-payment notice to the Customer’s account email before suspension. The Service is reinstated on payment of the outstanding invoice plus any operator-disclosed reinstatement fee.

9. Termination

Customer may terminate the Service at any time from /cabinet. Termination takes effect at the end of the current paid cycle; Operator does not pro-rate refunds for early termination outside the Refund Policy at /legal/refund. The Service environment is destroyed on termination per the data-retention schedule documented at /legal/privacy.

Operator may terminate the Service for material breach of these Terms or the AUP, on the timeline documented at /legal/aup for AUP-driven terminations. Operator emits a termination notice to the Customer’s account email. The Customer’s data is retained for the data-retention period documented at /legal/privacy after termination, then destroyed.

10. Dispute resolution

Disputes arising under these Terms are resolved by arbitration seated in the operator-disclosed arbitral seat — pre-launch placeholder pending counsel’s recommendation on the seat appropriate to the operator’s home jurisdiction and the procured-infrastructure jurisdictions. The arbitration language is the language of these Terms.

The arbitration is conducted under the rules of the operator-disclosed arbitral institution, also pre-launch placeholder pending counsel’s recommendation. The arbitral award is final and binding on both parties; either party may apply to a court of competent jurisdiction for the purpose of enforcing the award.

Class actions and consolidated arbitrations are excluded to the extent permitted by the law of the arbitral seat. Counsel finalises the class-action exclusion language and confirms the exclusion’s enforceability under the seat’s law before deploy.

11. Governing law

These Terms are governed by the law of the operator-disclosed governing-law jurisdiction — pre-launch placeholder pending counsel’s recommendation on the choice-of-law appropriate to the operator’s home jurisdiction and the procured-infrastructure jurisdictions. Counsel finalises the governing-law clause before deploy.

The choice-of-law clause does not displace any mandatory consumer-protection law of the Customer’s residence jurisdiction to the extent that such mandatory law applies to the Customer-Operator relationship. Counsel confirms the consumer-protection carve-out scope before deploy.

12. Force majeure

Neither party is liable for delay or failure to perform under these Terms attributable to events outside the affected party’s reasonable control. The customary force-majeure events apply: acts of state, armed conflict, civil disturbance, natural disaster, pandemic, upstream-provider outage, internet-backbone disruption, and acts of cyber-warfare attributable to a state actor. Counsel finalises the enumerated event list before deploy.

The affected party notifies the other party of a force-majeure event within a reasonable time of becoming aware of the event. The affected party uses reasonable efforts to mitigate the event’s impact on Service delivery. The SLA exclusion list at /legal/sla expressly carves out force-majeure events from the credit ladder.

13. Severability

If a provision of these Terms is held unenforceable by a court of competent jurisdiction, the remainder of these Terms remains in full force and effect. The unenforceable provision is reformed to the minimum extent necessary to render it enforceable while preserving the parties’ original intent. Counsel finalises the severability clause before deploy.

14. Notices

Notices to Operator are sent to the email address listed in the per-doc contact-routing footer of these Terms — currently the legal@ alias. Notices to Customer are sent to the account email recorded in the Customer’s /cabinet profile. Counsel confirms the notice protocol satisfies any mandatory notice-form requirement of the governing-law jurisdiction.