Terms of Service
This is a simplified Terms of Service template for OffshoreHost.info. Replace this text with your final, jurisdiction‑specific legal terms before going into production.
- OffshoreHost.info provides infrastructure “as‑is” with no guarantee of uninterrupted service.
- Clients are solely responsible for the legality of the content and activities hosted on their services.
- We reserve the right to suspend or terminate services that violate the Acceptable Use Policy.
- Billing is crypto‑only; refunds, if any, are handled on a best‑effort basis and may be subject to fees.
Service scope and responsibilities
OffshoreHost.info provides infrastructure services, not legal advisory or business compliance guarantees. Clients are responsible for application-level security, software updates, data handling decisions, and lawful operation of workloads hosted on purchased services.
Provider responsibilities
- Provisioning and maintaining infrastructure availability within operational constraints.
- Applying platform-level controls to protect network integrity and service reliability.
- Processing abuse and security incidents through documented triage and response workflows.
Client responsibilities
- Securing operating systems and applications deployed on VPS or dedicated servers.
- Maintaining backups, credentials, and recovery procedures appropriate to workload criticality.
- Ensuring hosted content and behavior comply with applicable law and provider policy.
Billing, renewals, and payment terms
Billing is crypto-only. Invoices are generated with due dates and remain payable until expiration. Service suspension and lifecycle actions may apply when invoices stay unpaid beyond grace conditions.
For recurring services, clients are expected to monitor invoice schedules and maintain sufficient funds. Failure to pay on time may result in suspension or eventual termination according to lifecycle policy.
Refund requests, where applicable, are reviewed case-by-case under published policy limits and operational verification of service state.
Service availability and maintenance
Planned maintenance can occur for security patching, hardware lifecycle tasks, and control-plane upgrades. Emergency maintenance may be required to protect infrastructure and connected customers.
We recommend that production users implement high-availability architecture, external monitoring, and tested recovery plans rather than relying on a single host as a sole continuity strategy.
Suspension and termination triggers
- Confirmed prohibited activity under Acceptable Use Policy.
- Repeated security negligence causing network or abuse incidents.
- Non-payment beyond operationally defined grace windows.
- Legal requirements requiring immediate action by provider.
Dispute handling and communication
Clients may submit disputes with technical evidence, timestamps, and relevant identifiers. We review disputes in good faith and provide response context where policy and legal constraints permit.
For service questions, use the contact channels listed on the contact page so requests can be routed correctly and tracked through support workflow.