01 / Scope & definitions
1.1 Services and service terms
This agreement describes the use of WebCare360 services and the responsibilities associated with them. Read it together with the service description, accepted order and any terms expressly applicable to the service you purchase.
1.2 Customer, account and end users
“Customer” means the person or organization obtaining a service. An “account” is the customer relationship used to administer services and communications. “End users” are people the customer authorizes to use the service. “Content” includes material, data, applications and other information the customer stores, publishes, transmits or operates.
1.3 Service and management scope
“Service” refers to the hosting, infrastructure or associated work described in the applicable order. A managed service includes an agreed administration scope; an unmanaged service leaves administration of the customer environment with the customer. A product name alone does not determine which tasks, licences or recovery services are included.
02 / Customer & provider responsibilities
2.1 Content and use within your control
You are responsible for lawful use of the content, applications, systems and users you control, including activity through your service or account. Obtain the rights, licences and permissions required for material you upload, store, publish, transmit or execute. Apply the relevant service conditions to authorized end users.
2.2 Account and environment security
Keep account contact information accurate and protect credentials within your control. For an unmanaged environment, maintain the operating system, applications, updates and security configuration. The division of work is different where platform operation or management tasks are included in your service.
2.3 WebCare360’s role
WebCare360 provides the services included in the purchased plan and remains responsible for its applicable infrastructure, support, management and legal obligations. Customer responsibility does not remove obligations that apply to WebCare360.
2.4 Content visibility
WebCare360 does not routinely pre-screen or continuously inspect customer content. Customer administration, encryption, installed software and changing content can limit visibility. Issues may become known through reports, legal process, infrastructure or security events, operational monitoring, support interactions and other legitimate means.
03 / Offshore hosting & applicable law
3.1 Jurisdictional differences
Offshore hosting involves infrastructure provided from jurisdictions that may differ from those of the customer or complainant. Laws, procedures and complaint-handling frameworks can differ. Services remain subject to applicable law and their service conditions; server location alone does not settle every legal obligation.
3.2 Not bulletproof hosting
Offshore hosting is not bulletproof hosting. It does not grant immunity from law, authorize illegal activity, guarantee anonymity or promise refusal of valid legal process. Privacy and customer control must be exercised alongside lawful use and responsibility.
3.3 Copyright and DMCA
The Digital Millennium Copyright Act (DMCA) is a United States legal framework. Its direct applicability depends on the relevant legal and service context. Copyright and infringement laws also exist elsewhere. WebCare360 may review complaints, requests and orders under applicable law and service conditions.
3.4 Requests require context
An unsupported, invalid, misdirected or jurisdictionally inapplicable request may not automatically result in action. This does not mean complaints are ignored. The information supplied, legal basis, affected service and circumstances inform the response; valid process may require action.
04 / Acceptable use & prohibited activities
4.1 Illegal and harmful content
Do not use a service to create, possess, distribute or facilitate Child Sexual Abuse Material (CSAM), unlawful threats, unlawful incitement or material that supports unlawful violent activity. Content and conduct that create a credible threat to health or safety are prohibited.
4.2 Fraud and deception
Do not use a service for fraud, phishing, scams, illegal pyramid schemes or deceptive activity intended to obtain money, credentials or other information unlawfully. Required rights, permissions and regulatory authorizations remain the customer’s responsibility.
4.3 Network and security abuse
Do not conduct unauthorized attacks, DDoS or flooding, amplification, address spoofing, malicious scanning or exploitation, or interference with another system. Purchasing DDoS protection does not authorize outbound attacks or abuse.
4.4 Malware and compromised systems
Do not operate malicious botnets or use the service to deploy malware, compromise systems or control unauthorized access. A claim of testing or research does not itself authorize conduct that violates service conditions or another party’s rights.
4.5 Spam and unsolicited communication
Do not use the service to send spam or facilitate abusive unsolicited communication. This includes using hosted resources as part of an abusive campaign. A report or reputation listing may require investigation of the activity and its relationship to the affected service.
4.6 Service-specific restrictions
Additional content, application and resource restrictions may apply to a selected service. Check the applicable service conditions before ordering where your intended workload may be restricted. Accepting cryptocurrency payments does not authorize unlawful financial activity, manipulation or resource use outside the service scope.
05 / Abuse reports & enforcement
5.1 Reporting a concern
Send abuse reports to abuse@webcare360.com. Identify the affected service, URL or IP address, describe the conduct, and provide relevant dates, times, evidence and a way to contact you. Do not include account passwords or unrelated personal information.
5.2 Different reports, different review
General abuse, copyright complaints, legal process, urgent safety concerns and infrastructure incidents require different assessments. Further information may be needed where a report is incomplete. A customer response may be appropriate where the circumstances and applicable law permit it.
5.3 Proportionate action
WebCare360 may act where required by applicable law or valid legal process, or in response to a material policy violation, credible abuse or a security or safety concern. Depending on the circumstances, action may include a request to remedy, temporary restriction, suspension, termination or legal or security escalation.
5.4 Urgent risks and restoration
Urgent or severe risk may require restriction or suspension before a customer response. Notice and an opportunity to remedy depend on the circumstances and applicable obligations. Restoration depends on addressing the reason for the restriction and meeting the applicable service requirements.
06 / Service-specific responsibilities
6.1 Shared hosting
Shared hosting provides account-level controls on a provider-operated platform. WebCare360 operates the included hosting environment; the customer remains responsible for website content, applications, account access and activity within their control. Shared hosting does not imply server-level administrative access.
6.2 VPS and dedicated environments
Unmanaged VPS and Dedicated services leave operating-system and application administration with the customer unless specified otherwise. Linux administrative access, Windows Administrator or RDP access, and optional out-of-band access are different capabilities. Available access depends on the product, operating environment and agreed configuration.
6.3 Managed services
Managed VPS or Dedicated service adds the tasks agreed for that service. Management does not transfer responsibility for lawful content or every application to WebCare360. Confirm the scope of updates, monitoring, security, backups and application work rather than assuming the same inclusions across managed offers.
6.4 Specialized infrastructure
Storage, Streaming and GPU services describe different workloads and configurations. Storage capacity or RAID is not an independent backup service. A network port rate does not determine application throughput or audience capacity. Software, drivers, licences and administration remain subject to the selected service scope.
6.5 Protection, location and additional services
Protected dedicated infrastructure and website reverse-proxy protection have different delivery and mitigation scopes. Onshore services may have additional jurisdiction-specific terms. Where IP leasing or reseller services are separately contracted, their allocation, permitted use and operating responsibilities must be established in the applicable service terms.
07 / Resources & fair use
7.1 Use within the service allocation
Operate within the resource allocation and restrictions applicable to your selected service. Shared platform resource isolation and virtual server allocation are different from a dedicated physical machine. A vCPU allocation does not by itself mean a dedicated physical core.
7.2 Impact on shared infrastructure
Activity that disrupts shared infrastructure or other customers may require investigation and proportionate restriction. Applicable limits, alerts and remediation depend on the service. Do not assume an alert will precede every resource intervention.
08 / Backups & data
8.1 Backup inclusion varies
Backup inclusion varies by service. Unless backup service is expressly included or ordered, maintain your own independent backups. Even where backup service is provided, keep appropriate independent copies of critical data and test recovery.
8.2 Recovery scope
Frequency, retention, storage location, protected data and restore responsibilities depend on the agreed backup service. A backup label, storage server or redundant disk arrangement does not establish a recovery-time commitment. Agree the recovery requirements for your workload.
8.3 Data responsibilities
Customer backup responsibilities do not remove WebCare360’s obligations under an included or purchased backup service. Data-loss responsibility must be assessed against the agreed service, circumstances and applicable law.
09 / Availability & protection
9.1 Service availability
Availability depends on the service, its operating scope and the circumstances of an interruption. Network connectivity, infrastructure availability and the availability of customer applications are distinct. Review any availability terms expressly applicable to the selected service.
9.2 Service interruptions and remedies
When reporting an interruption, identify the affected service and relevant times and symptoms. Any applicable availability commitment and remedy must be assessed under the terms governing that service and applicable law. A general support or marketing statement is not a substitute for defined service-level terms.
9.3 DDoS protection is scoped
Attack mitigation addresses supported traffic within the purchased protection scope. It does not establish uninterrupted availability or coverage of every attack. Availability terms and mitigation obligations must be read together without treating a generic attack exclusion as cancellation of purchased protection.
10 / Support & management
10.1 Technical support
Use the Client Area for account-linked technical support about an existing service. Infrastructure and network support are different from ongoing administration of an operating system, application or third-party software. A support channel does not by itself establish a response-time or resolution-time guarantee.
10.2 Included work and additional assistance
Support and management work depend on the purchased service. If additional assistance is requested, establish its scope and any agreed charges before the work proceeds. Customer responsibilities for an unmanaged environment must be distinguished from problems within WebCare360’s own service obligations.
10.3 Communication
Provide accurate service details and communicate respectfully with support staff. Threatening or abusive conduct may require an appropriate response. General or sales enquiries and technical support are separate channels; technical support availability should not be assumed to apply to sales.
11 / Billing, payments & renewals
11.1 Invoices and service records
Check the amount, billing period and due date shown for your service. Keep account contact details current so service and billing communications can reach you. If an invoice appears incorrect, contact billing through the Client Area.
11.2 Payment instructions
Use the payment options and instructions available for the applicable invoice. Confirm uncertain payment details with billing before sending funds. Payment methods, transfer networks and settlement requirements are not interchangeable.
11.3 Payment and provisioning
Payment confirmation and service provisioning are separate steps. Availability, configuration and service requirements affect provisioning. Do not assume a payment establishes immediate activation or an automatic renewal arrangement.
12 / Cancellation & refunds
12.1 Cancelling a service
Review the cancellation conditions applicable to your service and contact billing through the Client Area if the process is unclear. Cancellation, the end of a service period and a refund are separate matters. Arrange access to needed data before a service ends.
12.2 Refund scope
Refund eligibility depends on the product, circumstances and applicable terms. A refund rule for one service should not be generalized across other services. Review eligibility, exclusions and any separately charged work or licences before ordering.
12.3 Requests and applicable rights
Contact billing about the affected service and the reason for a refund request. Cancellation policies and service-specific exclusions remain subject to rights and remedies that applicable law does not permit the parties to exclude. Cryptocurrency refund arrangements require confirmation with billing.
13 / Suspension, termination & retention
13.1 Nonpayment
Failure to pay under the applicable service terms may lead to restriction, suspension or termination. Confirm the due date and resolve payment issues through the account’s billing channel. Service-specific notice and nonpayment procedures apply.
13.2 Ending service
A service may also be restricted or ended for the policy, security or legal reasons described in this agreement. Ending a service can affect access to its systems and data. Plan for continuity and maintain independent copies of information you need.
13.3 Data after termination
Service deprovisioning, expiry of backup copies and retention of account, billing, support or security records are different processes. Do not rely on a terminated service as a recoverable data store. Retention and recovery depend on the applicable obligations and agreed service scope.
14 / Onshore & service addenda
14.1 Additional conditions
Onshore services may be subject to the Onshore Servers Terms and Policy in addition to the applicable order and service agreement. Review the terms identified for the particular service rather than assuming a location label describes every content, complaint or operating rule.
14.2 Jurisdiction-specific handling
Different jurisdictions and service conditions can require different handling of complaints, restrictions and legal process. Onshore and offshore should not be treated as simple strict-versus-permissive categories. Resolve a conflict between applicable documents with WebCare360 before relying on an interpretation.
15 / Reseller & affiliate relationships
15.1 Reseller responsibilities
Where a reseller service is contracted, the reseller’s customer relationship and support duties must be understood alongside WebCare360’s infrastructure obligations. Resellers are responsible for ensuring that authorized downstream use complies with the applicable service conditions.
15.2 Affiliate arrangements
Affiliate participation is governed by the applicable program terms. Referral eligibility, commission validation and payout conditions are distinct from the terms for a customer’s hosting service.
16 / Liability, indemnity & warranties
16.1 Responsibilities and remedies
Responsibility for loss or disruption depends on the applicable service obligations, the circumstances and applicable law. Nothing in this agreement is intended to exclude a right or liability that cannot lawfully be excluded.
16.2 Claims involving customer use
Claims arising from customer-controlled content, rights or use must be considered in light of the customer’s responsibilities and the applicable legal framework. Any obligation to defend, reimburse or indemnify another party must be determined under the terms applicable to the claim.
16.3 Service commitments
The scope of a service commitment is established by the applicable service terms. The suitability of customer software or a workload should be assessed against that scope. Statutory rights and any expressly agreed obligations remain subject to applicable law.
17 / Events beyond reasonable control
17.1 Effect on performance
An event beyond a party’s reasonable control may affect its ability to perform a service obligation. The event, its actual effect and the applicable service terms must be considered together. A general event label does not by itself determine responsibility.
17.2 Response and service scope
Reasonable mitigation, communication and recovery measures should be considered in the circumstances. This section must be read alongside any purchased protection or recovery obligation, including service-specific DDoS mitigation.
18 / Documents, changes & versions
18.1 Read applicable documents together
The service agreement, acceptable use rules, accepted order and any expressly applicable service-specific terms describe different aspects of the relationship. Ask for clarification if documents appear inconsistent; do not assume a general marketing statement changes a specific service obligation.
18.2 Changes to terms
A change to terms must be considered with its effective date, applicable notice requirements and the terms governing the affected service. Keep a copy of the documents applicable to your order. A later page update should not be assumed to settle how an earlier agreement applies.
19 / Contact & legal requests
19.1 Use the appropriate channel
For account support, use the Client Area. For general questions, use the Contact page. Report abuse to abuse@webcare360.com with enough information to identify the issue. These channels have different purposes.
19.2 Legal process
Legal requests must be assessed for authenticity, scope and applicable obligations. A publicly listed support or abuse address should not be assumed to establish an authorized address for formal service of legal process.
19.3 Necessary information handling
Operating a service and responding to payment, security, abuse or legal matters can require handling relevant information. Information handling remains subject to applicable obligations; this agreement does not promise disclosure will be refused in every circumstance.
20 / Applicable rights & disputes
20.1 Applicable obligations
The location of infrastructure does not by itself determine the law governing every aspect of the customer relationship. Applicable legal obligations and rights must be considered in the context of the service, parties and relevant conduct.
20.2 Raising a dispute
Identify the affected service, relevant facts and requested resolution when raising a concern with WebCare360. Nothing in this proposed process should be read as waiving rights or imposing an unagreed court, arbitration forum or dispute deadline.
CONTACT & SUPPORT
Questions about these terms?
Use the appropriate channel so your question reaches the right team.