Terms of Service

01

Service Overview

OFFSHORE sells server infrastructure: KVM virtual servers, dedicated servers, Windows RDP, GPU servers and shared web hosting at six sites. The catalogue on this website is the authoritative description of each offer, its site, its hardware and its price in US dollars. An order is placed against that catalogue, and the configuration stored with the order is the configuration that is built.

Every service is prepared manually by staff. The platform does not create virtual machines, install operating systems or issue access details on its own, and an order does not become a running server at the moment of payment. Offers marked as preorder, such as the Chisinau virtual servers, are built to order and are confirmed before setup.

The service is infrastructure, not anonymity. A server placed in another country is subject to the law and network rules where it stands, and the customer remains responsible for what runs on it. No claim of untraceability, anonymity or immunity is made anywhere in these terms.

02

Account Registration

Registration creates an account without a name, an email address or a telephone number. The panel generates a login ID in the form OF-XXXX-XXXX, a strong password and a one-time recovery code in the form RC-…. The credentials are shown once and are not sent anywhere; there is no email-based recovery.

The password and the recovery code are the only keys to the account. Store both offline and treat them as confidential. Staff cannot read the password, cannot read the recovery code and cannot reset either value from the administration panel. If both are lost, the account and the services attached to it may be lost as well.

An account may be suspended when these terms are breached, when a payment is under investigation, or when the platform is used in a way that puts other customers or the network at risk. Suspension is described further in section 8.

03

Acceptable Use Policy

Services may be used only for lawful purposes. Nothing in these terms permits unlawful activity, and the following uses are prohibited at every site:

• Any activity that breaks the law that applies to the customer or to the server's location.
• Attacks against other systems, including scanning, flooding, denial of service, unauthorised access and credential attacks.
• Malware, botnets, command-and-control infrastructure and distribution of malicious code.
• Spam, phishing, fraud, impersonation and schemes that deceive other people.
• Content that exploits or endangers minors, or that infringes copyright, trademark or other rights.
• Attempts to evade a suspension, a resource limit or the acceptable-use rules through another account or service.

The list is not exhaustive. The customer is responsible for the users of their service and for the content hosted on it. Reported abuse is reviewed manually, and a service may be suspended while a report is investigated. Abuse reports are opened as Security tickets through the contact page.

04

Orders and Manual Provisioning

An order moves through defined states: awaiting payment, payment confirmed, pending setup, active. Payment must be confirmed before setup begins. Once the balance or the payment intent covers the total, the order enters the setup queue and staff prepare the machine, install the chosen operating system and record the access details on the service.

No lead time is guaranteed. Setup depends on staff availability and on the site; a preorder is built after the order is confirmed. The price is calculated from the catalogue when the order is created and is stored with the order snapshot, so a later catalogue change does not rewrite an existing order.

An unpaid order can be cancelled. A paid order is not cancelled automatically; requests are handled through a Billing ticket under section 7. The platform never provisions a machine without a confirmed payment.

05

Cryptocurrency Payments

The wallet is funded with crypto only. Seven rails are verified by the payment service:

• Bitcoin (BTC) on the Bitcoin mainnet — 3 confirmations.
• Ethereum (ETH) on Ethereum mainnet — 12 confirmations.
• Tether (USDT) on TRON, TRC20 — 19 confirmations.
• Tether (USDT) on BNB Smart Chain, BEP20 — 15 confirmations.
• Solana (SOL) on Solana mainnet-beta — 1 confirmation.
• TRON (TRX) on TRON — 19 confirmations.
• BNB (BNB) on BNB Smart Chain — 15 confirmations.

Each payment intent locks a quote when it is created. Bitcoin, Ethereum, Solana, TRON and BNB are priced at the market rate read at that moment; USDT is pegged at exactly one US dollar per token. The required amount is fixed in the intent, and a transfer is matched against it after the listed confirmations.

On-chain verification is followed by manual administrator approval before the wallet is credited. One transfer can credit one intent only. The minimum top-up is USD 30. Network fees are paid by the sender. A transfer sent on the wrong network, to the wrong address or with a different amount is not credited automatically, and recovery is not guaranteed — the corresponding wallet may not be able to return the funds.

Blockchain transactions are final. A confirmed transfer cannot be reversed by the platform, and it is not a chargeback instrument. Open a Billing ticket with the PAY-… reference, the transaction hash and the transfer details if a credit does not appear after the confirmations.

06

Wallet Balance and Billing

The wallet is a prepaid balance in US dollars, stored as integer cents and shown in the dashboard. It is credited only by verified top-ups and by refunds or adjustments applied by staff; it is debited when an order is paid. Every movement is written to an append-only ledger with the resulting balance.

The balance is not a bank deposit, does not earn interest, and cannot be transferred to another account or withdrawn. It is a credit for services sold on this site. A negative balance is not possible, and an order cannot be paid with funds that have not cleared the review step.

07

Refunds and Cancellations

Refunds are handled case by case through a Billing ticket. There is no automatic refund right and no published refund window. The outcome depends on what was delivered and what was consumed: a service that has already been set up and handed over, or a balance that has already been spent, is normally not refundable.

An unpaid order can be cancelled without a charge. For a paid order, open a ticket with the order reference and the reason; support will review the state of the service and reply with the decision. When a refund is granted it is recorded as a credit on the wallet ledger; no automatic transfer back to a crypto address is provided.

Automatic renewal is off. A service runs for the term purchased, and a renewal is a manual arrangement; no charge is taken from the renewal panel on its own.

08

Service Suspension and Termination

A service or an account may be suspended when these terms are breached, when an abuse report is being investigated, when a payment is disputed or looks fraudulent, or when a legal or security obligation requires it. Where the situation allows, a ticket explains the reason and what is needed to restore the service; an active attack or a legal requirement may leave no room for advance notice.

A suspended account loses access to the dashboard. Services attached to it may also be stopped or cancelled when that is needed to end a breach, and a legal or security obligation may require it without advance notice. Records are kept as described in the Privacy Policy; deletion is not immediate and is not automatic. Suspension does not cancel an amount already owed, and it does not by itself create a refund.

09

Customer Responsibilities

The customer is responsible for:

• keeping the login ID, password and recovery code safe, and for every action taken with them;
• the content, software and services running on the ordered machine, including licences for proprietary software;
• configuring and securing the operating system, the firewall and any application installed on it;
• keeping independent backups of everything that matters, as described in section 10;
• watching service expiry and arranging a renewal manually before the term ends;
• responding to support tickets and providing the references needed to investigate a problem;
• following the law that applies to the customer and to the server's location.

10

Backups and Data Responsibility

No backup service is included with a server. The platform does not copy, snapshot or restore customer disks, and a deleted file, a failed upgrade or a compromised application is the customer's loss to recover. Keep independent backups outside the service, test that they restore, and do not treat the running machine as the only copy.

Platform records — orders, wallet movements, payment intents and tickets — are kept in the application database and are not a substitute for a customer backup.

11

Service Availability and Limitations

No service level agreement is published and no uptime percentage is promised. The service depends on data centres, upstream networks, hardware and staff, and any of them can fail or need maintenance. Preorder offers depend on a manual build and take longer than an in-stock order.

Hardware limits are the limits of the purchased plan: vCPU count, memory, NVMe storage, monthly traffic and one IPv4 address. The guest system is under the customer's control; the hypervisor, the facility and the network remain with the host. Nothing in this section promises anonymity, untraceability or a particular network path.

12

Intellectual Property and Abuse Reports

The customer keeps ownership of the content and software uploaded to a service and grants the operator the limited licence needed to host, transmit and back it up operationally. The site, the brand, the catalogue and the platform software remain the property of their respective owners.

Copyright or abuse reports should be opened as a Security ticket and include the affected hostname or service reference, the material concerned, the time it was observed and evidence of the right or the harm. Reports are reviewed manually. The platform may remove content or suspend a service while a report is assessed, and may refuse reports that do not identify the material or the right holder.

13

Limitation of Liability

The service is provided as available. To the maximum extent the law that applies to the operator allows, the operator is not liable for indirect or consequential loss, lost profit, lost data, or damage caused by the customer's configuration, by third-party software or by an upstream network or facility.

Because the governing law is not yet published (section 14), the exact scope of this limitation is not stated as a fixed cap. Nothing in these terms excludes liability that cannot be excluded by the law that applies, and nothing here should be read as a promise of a legal protection that the operator cannot give.

14

Governing Law and Contact

The operator's registered business name, address and the governing law of these terms have not been published yet. No jurisdiction is named here because none has been confirmed for publication; this section will be completed when those details are available, and the “last updated” date will change with it.

Until then, raise any dispute or question through a support ticket so it can be addressed directly. Contact runs through the dashboard; the contact page explains the categories and the references to include. There is no public email address, telephone number or postal address.

15

Changes to These Terms

These terms may change when the service changes or when a legal requirement applies. The “last updated” date at the top of the page records the current version, and a material change is described in the document rather than silently edited into an old clause.

No email notification is possible because no email address is collected. Check this page before an order when the rules matter to you; continued use of the site or a service after a change means the new version applies.