Terms of Service

1. The agreement and the parties

These Terms of Service form a binding agreement between you (the customer) and the operating entity behind Anonymous Server Hosting (referred to as "we", "us", "our"). The agreement is formed when you submit payment for any service we offer. Browsing this website without becoming a customer does not create a contractual relationship; only your privacy is governed in that case (see our Privacy Policy).

For corporate identity, registered office and operating jurisdiction, contact us directly. We provide that information to active and prospective customers on request. We do not publish it on the website.

2. Services we provide

We provide hosting infrastructure: dedicated and virtual private servers, SMTP relay services, IP warming services, and the addons listed in our service catalogue. The technical specifications, included resources, and service-level commitments for your specific tier are documented at the time of order and form part of this agreement.

We are an infrastructure provider, not an Email Service Provider. We do not write your marketing copy, run your campaigns, manage your subscriber lists, or operate your business on your behalf. Configuration and operation of your sending stack are your responsibility, with our engineering support available via Telegram and ticket.

3. Payment

All services are paid in cryptocurrency. The cryptocurrencies we accept are listed on our payment page; we may add or remove specific cryptocurrencies as their on-chain characteristics change. Invoices are denominated in EUR and converted to the chosen cryptocurrency at the time of invoice generation, using market rates from a public price oracle.

Network fees (BTC miner fees, ETH gas, etc.) are paid by the customer on top of the invoiced amount. We recommend Lightning Network for invoices below €100 to keep fees negligible.

Service is activated when the payment confirms on-chain. Confirmation requirements vary by cryptocurrency and are documented on the payment page. We do not extend credit or invoice in arrears for new customers.

Recurring services (monthly subscriptions) are renewed on the anniversary date following the same payment process. We do not auto-charge any wallet. You initiate each renewal payment.

4. No partial-period crediting

Once a service period (typically one month) has been activated, the full period is treated as delivered upon activation. We do not issue partial-period credits for services voluntarily terminated mid-period. Customers planning to terminate should do so at the end of an active period to avoid paying for unused capacity.

Where we suspend a service for reasons attributable to our infrastructure (extended outage, datacenter failure, etc.), customers receive an extension of the active period equal to the duration of the unavailability. This is the standard remedy for infrastructure failures.

5. Your obligations as a customer

By using our services you commit to:

• Comply with our Acceptable Use Policy. The current version of the AUP is available at /legal/aup/ and forms part of this agreement.
• Operate within applicable law. Your use of the infrastructure must comply with the laws of every jurisdiction in which you do business and from which your recipients receive your communications.
• Maintain the security of your access credentials. SMTP credentials, SSH keys, control-panel passwords and DKIM private keys are your responsibility once delivered. Notify us immediately if you suspect compromise.
• Provide accurate technical contact information. We need a working Telegram handle or email to reach you about urgent operational matters (incidents, abuse complaints, scheduled maintenance).
• Pay for the service you ordered. Renewal payments are due on the anniversary date; service is suspended after a short grace period if payment is not received.

6. Acceptable Use Policy summary

The full AUP is published separately. Categorical exclusions, which are content or activities that immediately disqualify a customer from using our services regardless of any with no other consideration, include:

• Material that sexually exploits children, in any form, on any infrastructure we operate.
• Malware command-and-control, ransomware delivery infrastructure, exploit kits.
• Phishing infrastructure targeting individuals or institutions.
• Denial-of-service attack infrastructure (booter / stresser / "DDoS-for-hire").
• Romance-scam, advance-fee-fraud, fake-investment and fake-charity operations.
• Operations that have been the subject of valid criminal indictments anywhere our infrastructure runs.

These categories are non-negotiable, are not subject to jurisdictional reinterpretation, and are excluded from the privacy protections this agreement otherwise provides. Customers operating in these categories receive immediate termination, full cooperation with investigating authorities, and forfeit any unused service period.

7. Suspension and termination

We may suspend or terminate service in the following circumstances:

• Non-payment. Suspension after 7 days past renewal date; full termination and data deletion 30 days later if payment is still not received.
• AUP violation. Suspension is immediate for categorical exclusions (section 6). For other violations we provide a cure period proportional to the severity, typically 24 to 72 hours.
• Infrastructure abuse. Behaviour that puts our network at risk (port scanning of third parties, unauthorised vulnerability scans, misuse of shared resources) results in immediate suspension pending review.
• Court order. A valid court order from a court of competent jurisdiction directing us to disable specific services.

We notify the customer as soon as suspension takes effect and explain the reason and the cure path, except where notification is itself prohibited by court order.

On termination, customer data is retained for the periods described in the Privacy Policy and then permanently deleted. Customers wishing to migrate are responsible for retrieving their data, configuration files and DKIM keys before the deletion date.

8. Service availability and limits of liability

We operate Tier III+ datacenters with redundant power, redundant network paths and Tier 1 BGP transit. We aim for industry-standard uptime but we do not promise zero downtime, and you should design your sending stack with retries and queuing appropriate to email's "store and forward" nature.

Our liability under this agreement is limited, to the extent permitted by applicable law, to the amount paid by the customer for the affected service period. We are not liable for indirect, consequential, or punitive damages: lost profits, lost reputation damages, lost subscribers, opportunity cost of campaigns missed, or claims arising from third parties. This limitation applies regardless of the legal theory under which the claim is brought.

We do not warrant the inbox placement of your specific messages, the engagement rates of your specific recipients, or the absence of any specific blocklist listing on any specific day. We warrant the technical configuration of your infrastructure as documented in your service tier; outcomes depend on factors outside our control (your content, your audience, receiver-side policy changes).

9. Indemnification

You indemnify us and hold us harmless against claims, damages, costs and expenses arising from your use of our infrastructure, including but not limited to: claims from message recipients, claims from regulators, claims from blocklist operators, and claims from any third party affected by your operations on our infrastructure.

This indemnification does not extend to claims arising from our own gross negligence or wilful misconduct, which remain our responsibility under section 8.

10. Dispute resolution

We try to resolve every dispute through Telegram or ticket conversation. Most operational disagreements (configuration, scope of work, billing clarification) get resolved within hours through that channel.

Where a dispute cannot be resolved by direct conversation:

• Governing law: the laws of the jurisdiction where the affected infrastructure is operated. Where multiple jurisdictions are involved, the laws of the operating entity's registered domicile govern by default.
• Venue: the competent courts of the operating jurisdiction. Both parties expressly waive jurisdiction-shopping arguments based on the geographic location of the customer.
• Foreign judgements require domestication in the operating jurisdiction before they can be enforced against our infrastructure (see Privacy Policy section 7).

11. Multi-jurisdictional operation and governing law

Our infrastructure operates across seven jurisdictions: Bulgaria, Romania, Moldova, Ukraine, Panama, Hong Kong, and Singapore. Customer service agreements are governed by the law of the jurisdiction where the customer infrastructure is racked. A customer with a VPS in Bulgaria operates under Bulgarian law for that VPS; a customer with infrastructure across multiple jurisdictions operates under each respective jurisdiction for each component. Disputes are resolved at the appropriate court in the relevant jurisdiction.

This multi-jurisdictional structure is deliberate. It distributes legal-process risk across jurisdictions rather than concentrating it at a single choke point, and it ensures that the legal framework governing each piece of customer infrastructure matches the actual physical and operational location of that infrastructure. Customers can choose primary and secondary jurisdictions for their infrastructure based on their own threat model; we maintain the operational capability in each location to support those choices.

For customers operating in regulated industries (healthcare adjacent, financial services, EU-resident businesses subject to GDPR), we can structure deployments to keep all customer data within a single specified jurisdiction. This addresses data residency requirements that some compliance frameworks mandate. The arrangement is documented in the service order and operates as a contractual commitment beyond the baseline terms.

12. Pricing structure and changes

Service pricing is documented in the catalogue on this site and is in EUR. The actual payment amount in cryptocurrency is calculated at invoice generation using the prevailing EUR rate at that moment. We do not adjust invoiced amounts after generation for cryptocurrency volatility in either direction. Customers who prefer stable amounts month-to-month can pay in stablecoins (USDT, USDC, DAI) on the chain of their choice.

Pricing changes on existing customer services follow a notification commitment: customers receive 60 days advance notice before pricing changes take effect on their current services. The notice describes the specific change, the effective date, and the customer right to terminate before the new pricing applies (with pro-rata refund for the unused portion of the current billing period). We do not silently change prices on existing customers and do not require customers to accept new pricing as a condition of continued service for the remainder of their current billing period.

Pricing on new orders or upgrades follows the rates published in the catalogue at the time of order. We do not run discount programmes, promotional pricing, or contract-length discounts on the standard catalogue (annual prepayment is the only structural discount, at 5% for the prepayment commitment). Customers with unusual volume commitments or custom configurations can negotiate specific terms during discovery; published pricing is the standard rate for standard configurations.

13. Changes to these terms

We update these Terms of Service when material changes occur. The effective date is shown at the top of the document. Substantial changes are announced via the customer Telegram channel at least 30 days before they take effect, giving customers the opportunity to terminate before the change becomes binding.

Continued use of the service after the effective date of a change constitutes acceptance of the updated terms.

14. Contact

Questions about these Terms of Service, requests for clarification, or disputes about specific clauses are addressed via:

• Telegram: anonymousserverhosting, fastest channel, median response 12 minutes.
• Ticket: open a ticket at /contact/, answered within 4 hours during operating hours.
• Tor mirror: our .onion address for visitors who prefer to reach us over the Tor network is shown in the footer.