Joy Services Joy Services

Updated on 30 Dec 2025

Return Policy

This Return Policy explains how cancellations and return-equivalent requests are handled for Joy Services digital infrastructure, network services, and subscriptions. Because most Services are provisioned instantly, “returns” are typically managed as cancellations, adjustments, or service credits.

Policy Overview

Digital Services Business-Grade Infrastructure Fair-Use & Abuse Controls

1) Scope

This Return Policy applies to services purchased directly from Joy Services, including but not limited to: cloud compute (VPS/RDP/instances), dedicated servers, hosting, CDN services, DDoS protection, DNS, IP transit/peering-related services, S3-compatible storage, analytics services, and proxy services (“Services”).

2) What “Return” means for digital Services

Because our offerings are primarily digital and provisioned on-demand, a “return” typically means:

  • Cancellation before provisioning (or while provisioning is incomplete), where technically feasible.
  • Service credit or account adjustment where a traditional return is not possible.

3) Eligibility window

  • Before provisioning: If you request cancellation before the Service is provisioned/activated, we will generally process a cancellation without penalty.
  • Short window after provisioning: Where applicable and at our discretion, we may consider a cancellation request submitted within 24 hours of activation, provided the Service has not been materially used and no abuse/security issues are involved.

4) Non-returnable situations

Returns/cancellations are typically not available once a Service is provisioned or used, including:

  • Compute/VPS/RDP instances that have been deployed, booted, or used for workload execution.
  • Dedicated servers once the server is allocated, installed, or delivered into production.
  • CDN traffic delivered, cached content served, or bandwidth/requests consumed.
  • DDoS mitigation engaged, scrubbing resources allocated, or filtering rules applied.
  • DNS zones created/updated and actively served; domain-related third-party purchases.
  • Peering/IP transit and port/IX resources once configured or committed.
  • S3/object storage where storage, API calls, egress, or lifecycle operations have occurred.
  • Analytics/AI services where processing has been performed or resources consumed.
  • Proxy services once credentials are issued, endpoints activated, or traffic observed.

5) How to request a cancellation / return review

Contact us through the customer portal or email support and include:

  • Your account identifier and order/invoice reference
  • The Service name/ID (instance ID, server ID, port ID, etc.)
  • Reason for the request (brief, factual)
  • Expected resolution (cancel, plan change, service credit)

6) Investigations, fraud, and abuse controls

We maintain operational and security controls. If we detect policy violations, abuse patterns, or chargeback risk, we may decline a return/cancellation request and/or suspend Service as permitted by our Terms of Service.

7) Operational logs

To protect infrastructure and customers, we maintain login and access logs, security event logs, API logs, and network telemetry (including flow records where applicable). These logs are used for security, fraud prevention, capacity planning, and incident response, and are handled in accordance with our Privacy Policy and applicable law.

8) Policy precedence

If a specific product page, enterprise agreement, or order form states a different cancellation rule, that document controls for that Service.

Change notice: This policy may be updated periodically to reflect operational, security, legal, or product changes. The latest version published on our website prevails. Where required, material changes will be communicated through the customer portal or email.