Joy Services Joy Services

Updated on 30 Dec 2025

Terms of Service

These Terms of Service define acceptable use, account and security obligations, billing and renewals, logging, and product-specific considerations for Joy Services—including compute, hosting, CDN, DDoS protection, DNS, peering/transit, storage, analytics, and proxy services.

Policy Overview

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

1) Agreement and acceptance

  • By purchasing, accessing, or using Joy Services (“we”, “us”, “our”), you (“Customer”, “you”) agree to these Terms of Service (“ToS”).
  • You also agree to our Privacy Policy and any product-specific terms referenced in your order form, service page, portal, or enterprise agreement.
  • If you are using the Services on behalf of an organization, you represent that you have authority to bind that organization.
  • If there is a conflict between these ToS and an enterprise agreement, the enterprise agreement will control for the covered Services.

2) Service categories

  • Compute: VPS, RDP, cloud instances, managed compute, and related services.
  • Hosting: web hosting, WordPress hosting, control panels, and related products.
  • Networking: IP transit, peering, ports, BGP services, IP resources, and interconnects.
  • CDN: content delivery and edge caching services.
  • DDoS Protection: network-layer and application-layer mitigation, scrubbing, and filtering.
  • DNS: authoritative DNS and related resolution services.
  • Storage: S3-compatible object storage, backup, snapshots, and storage services.
  • AI / Analytics: monitoring, telemetry, analytics, and usage insights.
  • Proxy Services: proxy endpoints and related access services.

3) Account, identity, and security

  • You must provide accurate account, contact, and billing information and keep it current.
  • You are responsible for safeguarding credentials, API keys, and access tokens.
  • You are responsible for all activity under your account, whether authorized by you or not.
  • We may require verification steps to prevent fraud, abuse, or unauthorized access.
  • You must promptly notify us of suspected compromise, credential leakage, or security incidents.
  • You must apply reasonable security practices (patching, MFA where available, least privilege access).

4) Acceptable use and prohibited activities

  • You agree not to use the Services for illegal, harmful, or abusive activities.
  • Prohibited activities include malware, phishing, credential theft, spam, or unauthorized access attempts.
  • Operating botnets, scanners, exploit delivery, or command-and-control infrastructure is prohibited.
  • DDoS attacks, traffic amplification/reflection, or facilitating attacks is prohibited unless explicitly authorized in writing for controlled testing.
  • Hosting or distributing illegal content or content that violates third-party rights is prohibited.
  • Misuse of IP resources (route hijacking, unauthorized announcements, BGP abuse) is prohibited.
  • Using proxy services to evade lawful restrictions, sanctions, or law enforcement actions is prohibited.
  • Interference with platform integrity (abuse of limits, evasion of mitigations, repeated violations) is prohibited.
  • We may suspend, filter, rate-limit, null-route, or terminate Services to mitigate abuse or security risk.

5) Network and routing terms (BGP/peering/transit)

  • Route announcements must be authorized and consistent with industry practice (IRR/RPKI/LoA where applicable).
  • We may enforce prefix-length policies, max-prefix limits, and route validation behaviors.
  • We may filter routes, communities, attributes, and traffic for stability, security, and policy enforcement.
  • We may require standard NOC/security contacts for coordination of routing incidents.
  • Route leaks, repeated flaps, or unauthorized announcements may result in immediate session shutdown.
  • Peering/transit services may include fair-use protections, rate limits, and maintenance windows.
  • During incidents, we may apply emergency reroutes or filtering to protect network health.
  • Customers must not announce third-party prefixes without explicit authority and documentation.

6) CDN and DDoS service terms

  • CDN performance depends on origin configuration, cache rules, TLS configuration, and internet conditions beyond our control.
  • DDoS protection reduces attack impact, but no provider can guarantee prevention of all attacks.
  • Mitigation actions may include filtering, rate limiting, challenge mechanisms, or temporary blocking.
  • In severe cases, temporary null-routing may be applied to preserve network integrity and reduce collateral damage.
  • Clean-traffic capacity, mitigation behavior, and feature availability vary by plan and attack profile.
  • You are responsible for your origin security posture unless a managed security service is purchased.

7) Storage and data

  • You retain ownership of your data and are responsible for content legality and compliance.
  • You are responsible for backups unless a managed backup service is purchased.
  • We may impose technical limits and fair-use controls to protect platform reliability.
  • Retention periods vary by product and plan; data may be deleted after termination per retention schedules.
  • You are responsible for exporting data prior to termination or suspension where access is restricted.
  • We may restrict or remove content where required by law or to address material platform risk.

8) Logging, monitoring, and compliance

  • We maintain login/access logs, security event logs, API logs, and network telemetry (including flow records where applicable).
  • We use operational data for security, fraud prevention, troubleshooting, capacity planning, and compliance with applicable laws.
  • We handle personal data in accordance with our Privacy Policy.
  • We may contact you for urgent remediation when compromise or abuse is suspected.
  • Enterprise compliance requests may be supported subject to NDA, scope, and feasibility constraints.

9) Billing, renewals, and non-payment

  • Services may renew automatically unless cancelled in advance in the portal or via agreed process.
  • You are responsible for all fees, applicable taxes, and accurate billing details (legal entity, address, GST/VAT where applicable).
  • Non-payment may result in suspension and eventual termination, which may lead to data deletion per retention schedules.
  • Fees paid are generally non-refundable except as described in the Refund Policy or applicable order terms.
  • Billing disputes must be raised within a reasonable timeframe and include supporting details.
  • Where an SLA applies, service credits (if any) are governed by the SLA terms and may be the exclusive remedy.

10) Suspension and termination

  • We may suspend or terminate Services for policy violations, security risk, legal requirements, or non-payment.
  • We may take immediate action where necessary to protect the platform, upstreams, or third parties.
  • Upon termination, access may be restricted and resources may be reclaimed, including IP resources where applicable.
  • Customers remain responsible for charges incurred prior to termination and any applicable early termination fees if agreed.

11) Service availability and support

  • Service availability and response commitments vary by plan and may be governed by an SLA or enterprise agreement.
  • Maintenance windows may be required for upgrades, security patching, and capacity work.
  • We may publish notices via portal, email, or status page for material incidents or planned maintenance where feasible.

12) Limitation of liability

  • To the fullest extent permitted by law, Joy Services is not liable for indirect, incidental, special, consequential, or punitive damages.
  • Our aggregate liability is limited to the amount paid for the affected Service during the relevant billing period, except where prohibited by law.
  • We are not responsible for outages or losses caused by factors outside our reasonable control (including upstream failures, internet conditions, force majeure events, or customer misconfiguration).

13) Indemnity

  • You agree to defend, indemnify, and hold Joy Services harmless from claims arising out of your use of the Services, your content, or your violation of these ToS.
  • This includes claims related to intellectual property infringement, unlawful content, abuse, or violation of applicable laws.

14) Confidentiality

  • Each party may receive confidential information from the other; you agree to protect such information using reasonable care.
  • Confidential information excludes information that is public, independently developed, or lawfully obtained without breach of obligations.

15) Changes

  • We may update these Terms from time to time to reflect operational, security, legal, or product changes.
  • If changes are material, we will make reasonable efforts to notify customers through the portal or email.
  • The latest version published on our website prevails.
Contact: For policy questions, contact support via the portal or email support@joycloud.services.
Change notice: This policy may be updated periodically. Where required, material changes will be communicated through the customer portal or email.