Return Policy for digital infrastructure and service-based products

Section 1

1. Scope

This Return Policy applies to services purchased directly from Joy Services, including but not limited to cloud compute products such as VPS, RDP, and virtual instances; dedicated servers; shared or managed hosting products; CDN services; DDoS protection and mitigation products; DNS services; IP transit, peering-related services, and port-based network services; S3-compatible object storage and related storage products; analytics or processing services; and proxy-related products or access services.

This policy is intended for digital, on-demand, or infrastructure-based services. It does not create a general right to reverse engineering work, network allocation, port activation, route configuration, storage operations, mitigation actions, or other resource-consuming activity once the relevant service has been activated, provisioned, configured, delivered, or materially consumed.

For clarity, the term “Service” includes associated operational work such as provisioning, deployment, network turn-up, policy application, account-side enablement, route and filter preparation, identity or fraud review, storage allocation, object handling, security controls, support-side technical checks, or any other step that directly commits platform resources for a customer order.

This policy applies unless a specific product page, custom quote, order form, enterprise agreement, partner agreement, or written commercial schedule states a different return or cancellation rule for the covered service.

Section 2

2. What “Return” means for digital services

Because Joy Services primarily provides digital and infrastructure-based products that are created, activated, routed, or assigned on demand, the meaning of a “return” differs from the meaning of return used for physical consumer goods. In most cases, a return does not mean physical product recovery. Instead, it typically refers to cancellation before provisioning, cancellation while provisioning is incomplete, a limited review shortly after activation where technically and operationally appropriate, or an account-side adjustment such as a service credit where a traditional return is not technically possible.

Once a digital service is activated, compute may already be reserved, network capacity may already be allocated, routing policies may have been created, DNS or CDN endpoints may have started serving, mitigation systems may have been engaged, storage may have started recording data, and engineering work may already have been performed. For that reason, a service can become consumed or non-returnable much earlier than a customer might expect in a physical-goods model.

A return review under this policy may therefore result in one of several outcomes: cancellation without penalty before provisioning; cancellation with no refund after provisioning but before material consumption; a partial commercial adjustment; service credit for future use; plan modification; migration to a better-fit service; or a denial where the service has already been materially used, delivered, consumed, or exposed to abuse or security risk.

The fact that a service is no longer wanted does not by itself make it returnable. Return handling is based on provisioning state, usage state, resource commitment, abuse and fraud review, and the real operational impact of the request.

Section 3

3. Eligibility window

Before provisioning, if you request cancellation before the service is provisioned, deployed, activated, assigned, or otherwise committed, Joy Services will generally process the cancellation without penalty. This is the clearest and most favorable stage for a return-style outcome because resources have not yet been fully assigned or consumed.

In cases where provisioning is underway but incomplete, Joy Services may still approve cancellation, but the decision depends on how much work has already been performed. For example, a pending order that has triggered manual review, custom setup, engineering-side changes, inventory reservation, or network preparation may not be treated the same way as a purely unprocessed order.

Where applicable and at Joy Services’ discretion, a short review window may exist after activation, typically within 24 hours of service activation, provided the service has not been materially used, the customer has not consumed meaningful platform resources, and no abuse, fraud, policy, or security concerns are present. This does not create an automatic right of return. It is a limited discretionary review window designed to address obvious activation mismatch or early ordering error under controlled circumstances.

Requests made after the service has been used, booted, routed, connected, consumed, served, assigned, or meaningfully interacted with are much less likely to qualify. The longer the service remains active after provisioning, the more likely it is that it has crossed into the non-returnable state under this policy.

Section 4

4. Non-returnable situations

Returns or cancellations are typically not available once a service has been provisioned or used in a way that consumes compute, storage, network, mitigation, routing, support, or operational resources. The following situations are generally non-returnable.

The above list is illustrative rather than exhaustive. Any service may become non-returnable once it has been materially delivered, assigned, used, consumed, or exposed to operational and security cost on the platform.

Section 5

5. How to request a cancellation or return review

If you want Joy Services to review a return-style request, cancellation, or commercial adjustment, you should contact us through the customer portal or the official support channel associated with your service. A good request should be clear, factual, and submitted as soon as possible after the issue is identified.

To help us evaluate the request accurately and quickly, include the following information:

A customer request that merely states “cancel” without context may still be reviewed, but missing details can slow down response time and may lead to a narrower outcome. If the issue is technical, describe the problem in factual terms rather than only commercial terms. This helps us distinguish between activation mismatch, configuration error, expectation mismatch, genuine service defect, and post-provisioning preference change.

Submission of a request does not guarantee approval. Requests are reviewed according to service state, order history, actual usage, provisioning work completed, and platform-side operational impact.

Section 6

6. Investigations, fraud, and abuse controls

Joy Services maintains operational, commercial, and security controls to protect platform stability, reduce fraud exposure, and protect customers and upstream providers from abuse-related risk. If we detect policy violations, fraudulent order patterns, unauthorized payment behavior, chargeback risk, identity inconsistencies, network abuse, suspicious provisioning patterns, or other material risk, we may decline a return or cancellation request and may also suspend or restrict the service as permitted by our Terms of Service and applicable law.

Return handling is not available as a method to avoid the consequences of abuse, prohibited use, policy breach, or intentional misuse. A customer whose service is suspended or terminated due to abuse, spam, malware activity, unauthorized scanning, route misuse, proxy misuse, content abuse, or other material policy violation should not expect a favorable return outcome merely because the service is no longer accessible.

Where fraud or abuse indicators are present, Joy Services may request additional verification or may preserve records needed for security review. We may also hold the request pending internal investigation, reject the request outright, or coordinate the matter according to our internal risk handling process.

Section 7

7. Operational logs and review evidence

To protect infrastructure and customers, Joy Services maintains login and access logs, security event logs, API logs, billing and provisioning metadata, support-side change records, and network telemetry including flow-related records where applicable. These records may be used in return reviews to determine whether a service was provisioned, whether it entered active state, whether traffic or compute was observed, whether resources were consumed, and whether abuse, fraud, or material usage occurred.

These logs are maintained for security, fraud prevention, troubleshooting, capacity planning, commercial review, and incident response. They may also be used to assess whether a requested return conflicts with observed service state. For example, if a customer states that a service was never used, but operational records show successful boot activity, object storage writes, DNS serving, active API calls, route session establishment, or delivered traffic, Joy Services may rely on those records when deciding the request.

Operational records are handled in accordance with the Privacy Policy, applicable law, and internal security practice. Joy Services is not required to disclose all internal detection logic, telemetry interpretation methods, fraud scoring criteria, or upstream-linked operational information as part of a return review.

Section 8

8. Policy precedence

If a specific product page, custom quote, enterprise agreement, order form, partner contract, or written commercial schedule states a different cancellation, adjustment, or service acceptance rule, that document controls for the covered service to the extent of the conflict. This policy is intended to operate as the general baseline return framework for standard Joy Services offerings.

Product-specific or enterprise-specific terms may differ because some services involve custom installation, committed capacity, reserved inventory, upstream commercial obligations, or custom engineering work that makes the standard return model unsuitable.

If you are uncertain which document controls your service, the safest approach is to review your order confirmation, invoice notes, signed quote, service page terms, and the customer portal information for the specific product.

Section 9

9. Service-specific return handling notes

Because Joy Services provides multiple categories of infrastructure products, return handling can differ by service type even where the general principles remain the same. The following notes help clarify that service-specific reality.

Section 10

10. Service credit, account adjustment, and alternative resolutions

In some circumstances, Joy Services may determine that a traditional return is not possible but that a commercial adjustment is reasonable. In such cases, the outcome may take the form of service credit, account balance adjustment, migration to another product, plan change, billing correction, or another commercially appropriate remedy.

Such outcomes are discretionary unless explicitly required by contract or law. They are not intended to create a standing right to compensation whenever a customer changes preference, orders the wrong plan, or no longer wishes to use a service after provisioning.

When evaluating whether a credit or adjustment is appropriate, Joy Services may consider factors such as how quickly the issue was reported, whether the service was materially used, whether the issue arose from product mismatch versus customer-side configuration, whether a replacement or migration is more appropriate than a return, and whether the account has a history of repeated commercial reversal requests.

Credits, where issued, may be limited to future use on the platform, subject to account standing, expiration conditions, service category limits, or anti-abuse restrictions. Credits generally have no cash value unless otherwise required by law or specifically stated in writing.

Section 11

11. Review process, timing, and customer cooperation

Joy Services reviews return and cancellation requests according to the nature of the service, the operational state of the order, any observed usage, the customer’s requested resolution, and the presence or absence of abuse, fraud, or policy concerns. Some requests can be handled quickly, especially if the service is still clearly unprovisioned. Others require more detailed checking.

Customers are expected to cooperate with reasonable verification and provide enough information for accurate review. If a request relates to a technical mismatch, we may ask for logs, service IDs, timestamps, screenshots, or a factual explanation of the issue. If the request relates to billing or identity, we may require the order reference, account confirmation, or payment-side context.

Failure to respond to follow-up questions, providing misleading statements, attempting repeated inconsistent explanations, or using a return request while simultaneously continuing to consume the service may negatively affect the review outcome.

Joy Services may close a request where the evidence clearly shows that the service has already crossed into the non-returnable state, or may instead offer a service modification route if that is more appropriate than a full cancellation review.

Section 12

12. Change notice and latest-version rule

This Return Policy may be updated periodically to reflect operational, security, legal, product, or commercial changes. The latest version published on the Joy Services website or customer-facing policy location prevails unless a different rule is required by law or a controlling written service-specific document.

Where required, material changes may be communicated through the customer portal, invoice notes, direct email, or another reasonable customer communication channel. Customers are responsible for reviewing current policy terms before purchasing new services or relying on a prior interpretation for a newly ordered product.

Continued purchase, retention, renewal, or use of services after an updated policy becomes effective may be treated as acceptance of the revised policy to the extent allowed by applicable law and any governing contract.

Important clarification

Practical interpretation of this policy

The practical core of this policy is simple: cancellation is generally easiest before provisioning; review becomes narrower after activation; materially used or consumed digital infrastructure is usually not returnable; and where a strict return is not possible, Joy Services may in limited cases consider credits or other account-side resolutions instead.

Customers should therefore review product fit, plan sizing, location, billing model, networking needs, and technical expectations before ordering. If there is uncertainty, it is better to clarify before provisioning than to rely on post-activation return assumptions that may not apply to digital infrastructure services.