Legal
Hostwover Legal Center

Policies, agreements, and legal information for using Hostwover services.

Web Hosting Agreement

Language note

The English version of Hostwover's legal agreements and policies is the authoritative version. Translated versions are provided for convenience. If there is any conflict between translations, the English version shall prevail.

Effective date: August 14, 2026

Last updated: August 14, 2026

1. Introduction

This Web Hosting Agreement ("Agreement") governs the purchase, provisioning, access, administration, renewal, suspension, cancellation, and use of Web Hosting Services provided through Hostwover.

This Agreement is entered into between:

  • Hostwover ("Hostwover", "we", "us", or "our"); and
  • the individual or organization purchasing, accessing, administering, or using the Web Hosting Service ("Customer", "you", or "your").

By ordering, activating, renewing, accessing, or using a Hostwover Web Hosting Service, you agree to this Agreement.

This Agreement forms part of Hostwover's Terms of Service.

2. Related Agreements and Policies

Your use of Web Hosting is also subject to applicable Hostwover legal documents, including:

  • Terms of Service.
  • Acceptable Use Agreement.
  • Acceptable Use Policy.
  • Abuse Handling Policy.
  • Privacy Policy.
  • Information Security Policy.
  • Refund Policy.
  • Service Level Agreement.
  • Customer Service Policy.
  • Responsible Disclosure Policy.
  • Trademark & Copyright Policy.
  • Complaints & Dispute Resolution; and
  • other terms expressly applicable to the purchased Service.

If a domain is purchased or managed through Hostwover, the applicable domain agreements also apply separately.

3. Definitions

For this Agreement:

Web Hosting

A hosting environment made available for websites, applications, files, databases, or related functionality according to the purchased plan.

Hosting Account

The technical hosting environment assigned to the Customer.

Hosting Plan

The specific Web Hosting package purchased by the Customer.

Control Panel

A hosting-management interface made available with an eligible Hosting Plan.

Customer Content

Any website, application, file, database, email, image, script, code, configuration, or other information uploaded, stored, processed, or transmitted by the Customer through the Web Hosting Service.

Resource Usage

Consumption of computing or hosting resources including storage, CPU, memory, processes, database resources, traffic, file-system resources, or other technical capacity.

4. Scope of the Service

Depending on the purchased Hosting Plan, Hostwover Web Hosting may provide functionality including:

  • website hosting.
  • domain association.
  • subdomains.
  • file storage.
  • FTP or similar file access.
  • databases.
  • PHP or other supported runtimes.
  • SSL functionality.
  • control-panel access.
  • application installers.
  • email-related functionality where included.
  • scheduled tasks where supported.
  • SSH access where included.
  • backups where expressly included.
  • migration assistance where offered.
  • DNS-related functionality.
  • monitoring.
  • security controls; and
  • customer support.

Only features included in the applicable Hosting Plan or Service description are contractually included.

5. Hosting Plan Specifications

Each Hosting Plan may define limits or characteristics including:

  • number of websites.
  • number of domains.
  • storage.
  • databases.
  • database size.
  • traffic.
  • email functionality.
  • FTP accounts.
  • CPU availability.
  • memory availability.
  • concurrent processes.
  • file-system limits.
  • scheduled tasks.
  • supported software versions.
  • backup functionality.
  • SSH access; and
  • other technical characteristics.

The specifications displayed for the purchased plan form part of the Service description.

6. Single-Site and Multi-Site Hosting

Some Hosting Plans may be intended for:

  • one website or domain; or
  • multiple websites or domains.

A plan intended for a single website does not create a right to host an unlimited number of unrelated websites.

Multi-site functionality is subject to the limits of the applicable plan.

7. Service Provisioning

After successful ordering, Hostwover will attempt to provision the Hosting Account.

Provisioning may require:

  • successful payment.
  • Account verification.
  • fraud screening.
  • technical availability.
  • domain information.
  • configuration information; or
  • other information necessary to create the Service.

8. Provisioning Completion

A Hosting Service is considered active when provisioning has successfully completed and the Hosting Account is made available for use.

An:

  • order.
  • invoice.
  • payment attempt; or
  • pending provisioning status

does not by itself guarantee that provisioning has completed.

9. Provisioning Failure

Provisioning may fail because of:

  • invalid information.
  • payment failure.
  • verification issues.
  • technical error.
  • unavailable capacity.
  • security concerns.
  • unsupported configuration; or
  • another legitimate operational reason.

If a paid Service cannot be provisioned, the affected payment will be handled according to the Terms of Service, Refund Policy, and applicable law.

10. Service Activation Information

After provisioning, Hostwover may provide information necessary to access the Hosting Account.

This may include:

  • hosting identifier.
  • control-panel access.
  • server information.
  • nameserver information.
  • temporary access details.
  • FTP information; or
  • other setup information.

Customers must protect all access credentials.

11. Control Panel

Eligible Hosting Plans may include access to a hosting control panel such as cPanel or another supported platform.

The control panel may allow management of features including:

  • files.
  • databases.
  • domains.
  • subdomains.
  • email functionality.
  • SSL.
  • backups.
  • DNS.
  • scheduled tasks.
  • statistics; and
  • supported applications.

The functionality available depends on the Hosting Plan and control-panel version.

12. Third-Party Control-Panel Software

Control-panel software may be licensed or developed by third parties.

Such software may:

  • change.
  • receive updates.
  • change its user interface.
  • add or remove functionality.
  • change licensing models; or
  • be replaced where operationally necessary.

Hostwover does not own third-party software merely because it is provided as part of a Hosting Plan.

13. Control-Panel Credentials

You are responsible for protecting control-panel credentials.

You must not:

  • publicly disclose them.
  • share them with unauthorized persons.
  • reuse compromised passwords; or
  • store them insecurely.

If you suspect compromise, you should change the relevant credentials immediately and contact Hostwover where assistance is required.

14. Domain Names Are Separate

Web Hosting and domain registration are separate Services unless expressly bundled.

Purchasing Web Hosting does not automatically:

  • register a domain.
  • renew a domain.
  • transfer a domain; or
  • create ownership rights in a domain.

Domain Services are governed by the applicable Hostwover domain agreements.

15. Connecting a Domain

To use a domain with Web Hosting, the domain may need to be configured using:

  • Hostwover nameservers.
  • DNS records.
  • an IP address.
  • verification records; or
  • another supported configuration.

The Customer is responsible for applying required DNS changes where the domain is not managed through Hostwover.

16. DNS Propagation

DNS changes may require time to propagate through distributed DNS systems and caches.

Hostwover does not guarantee that every resolver will reflect a DNS change immediately.

17. Customer Responsibility for DNS

Where the Customer controls DNS settings, the Customer is responsible for the accuracy of those settings.

Incorrect:

  • nameservers.
  • A records.
  • AAAA records.
  • CNAME records.
  • MX records.
  • TXT records; or
  • other DNS configuration

may cause websites, email, certificates, or other Services to stop functioning.

18. Customer Content

You retain ownership of Customer Content to the extent you lawfully own that Content.

Hostwover does not obtain ownership of your website merely because it is hosted on our infrastructure.

You grant Hostwover the limited rights technically necessary to:

  • store.
  • process.
  • transmit.
  • back up where applicable.
  • serve.
  • copy.
  • migrate; and
  • otherwise handle

Customer Content for purposes of providing, securing, maintaining, or supporting the Service.

19. Responsibility for Customer Content

You are responsible for Customer Content.

You represent that you have the rights and permissions necessary to:

  • upload it.
  • store it.
  • publish it.
  • process it; and
  • make it available through the Service.

20. Lawful Content

Customer Content must comply with:

  • applicable law.
  • Hostwover Terms of Service.
  • Acceptable Use Policy.
  • Abuse Handling Policy.
  • intellectual-property requirements; and
  • other applicable Hostwover policies.

21. Prohibited Content and Activity

Web Hosting must not be used to conduct or facilitate prohibited activity.

Examples may include:

  • phishing.
  • malware distribution.
  • credential theft.
  • fraud.
  • botnet activity.
  • unauthorized access.
  • malicious redirects.
  • unlawful spam.
  • deliberate distribution of stolen information.
  • illegal Content.
  • prohibited intellectual-property infringement.
  • malicious scripts.
  • attack infrastructure; or
  • other prohibited conduct defined in the Acceptable Use Policy.

22. Customer Applications

You are responsible for applications installed within your Hosting Account.

This may include:

  • WordPress.
  • Joomla.
  • Drupal.
  • e-commerce systems.
  • CMS software.
  • plugins.
  • themes.
  • frameworks.
  • scripts.
  • libraries.
  • custom applications; and
  • third-party packages.

23. Application Security

You are responsible for maintaining applications under your control.

You should:

  • install security updates.
  • remove unused software.
  • remove vulnerable plugins.
  • use strong passwords.
  • restrict administrative accounts.
  • maintain current dependencies; and
  • follow reasonable application-security practices.

24. Outdated Software

Hostwover may restrict or discontinue support for software versions that are:

  • end-of-life.
  • materially insecure.
  • incompatible with infrastructure.
  • unsupported by their maintainers; or
  • otherwise unsafe to continue operating.

Where reasonably practical, Hostwover may provide notice before a material compatibility change.

25. PHP and Runtime Versions

Hostwover may support selected versions of:

  • PHP.
  • databases.
  • web servers.
  • libraries.
  • extensions; or
  • other runtime components.

Not every historical or future software version will necessarily be supported.

Customers are responsible for ensuring their applications remain compatible with supported versions.

26. Application Installers

Some Hosting Plans may provide one-click or automated installation functionality for supported applications.

An installer is a convenience feature.

Hostwover does not guarantee that:

  • every application will always be available.
  • every installation will succeed.
  • third-party software will be free from vulnerabilities; or
  • every plugin or theme will be compatible.

27. Third-Party Applications

Third-party applications are subject to their own:

  • licenses.
  • terms.
  • privacy practices.
  • security practices.
  • maintenance.
  • documentation; and
  • support arrangements.

Hostwover does not become the developer of third-party software merely by making installation functionality available.

28. Databases

Eligible Hosting Plans may support databases.

The Customer is responsible for:

  • database users.
  • database passwords.
  • application queries.
  • data integrity.
  • schema design.
  • database Content; and
  • authorized access.

29. Database Resource Usage

Database usage must remain within the reasonable technical limits of the Hosting Plan and hosting environment.

Resource-intensive or abusive queries that materially affect shared infrastructure may require:

  • optimization.
  • restriction.
  • upgrade; or
  • migration to a more suitable Service.

30. File Storage

Hosting storage is intended primarily for data reasonably connected with hosted websites and supported hosting functionality.

Unless expressly included in the plan, Web Hosting should not be treated as:

  • general-purpose cloud storage.
  • an archival service.
  • an unlimited backup repository.
  • a public file-distribution network; or
  • unrelated bulk storage.

31. Storage Limits

The Customer must remain within the storage allocation of the purchased Hosting Plan.

If the Account reaches its applicable storage limit:

  • uploads may fail.
  • databases may be affected.
  • email functionality may be affected where included.
  • logs may be affected; or
  • other functionality may become limited.

Hostwover may notify the Customer or provide upgrade options where appropriate.

32. File-System Limits

Hosting environments may include technical file-system limits such as limits relating to:

  • number of files.
  • directories.
  • inodes.
  • file size.
  • filesystem operations; or
  • similar technical resources.

Where such a limit materially affects the purchased Service, Hostwover should make the relevant limitation reasonably available to the Customer.

33. CPU and Memory Usage

Shared Web Hosting involves shared infrastructure.

Customers must not continuously consume disproportionate CPU, memory, or process capacity in a manner that materially degrades the Service for other customers.

The precise available resources depend on the applicable Hosting Plan and technical environment.

34. Shared Hosting Environment

Web Hosting may operate in a shared environment where physical or virtual infrastructure is shared by multiple hosting accounts.

Hostwover applies isolation and security controls appropriate to the Service.

However, shared hosting does not provide the same level of administrative control or resource isolation as a VPS or VDS.

35. Appropriate Service Selection

Applications requiring:

  • sustained high CPU.
  • high memory.
  • specialized operating-system access.
  • root access.
  • custom services.
  • long-running processes.
  • specialized networking; or
  • dedicated resources

may be better suited to VPS or VDS Services.

Hostwover may recommend an upgrade or migration where a workload is inappropriate for shared Web Hosting.

36. Fair Resource Use

Customers must use shared resources reasonably.

Hostwover may take proportionate action where a Hosting Account causes a material and sustained adverse impact on:

  • platform performance.
  • other customers.
  • network stability.
  • database stability.
  • storage systems; or
  • infrastructure security.

37. Resource Investigation

Where abnormal Resource Usage occurs, Hostwover may investigate factors including:

  • CPU usage.
  • memory consumption.
  • process activity.
  • database activity.
  • traffic.
  • disk usage.
  • file count.
  • malicious activity.
  • scheduled tasks; and
  • application behavior.

38. Resource Remediation

Where reasonably possible, Hostwover may provide the Customer an opportunity to:

  • optimize the application.
  • remove abusive scripts.
  • reduce usage.
  • upgrade the plan.
  • migrate the workload; or
  • otherwise resolve excessive Resource Usage.

Immediate action may be necessary where the usage creates an urgent stability or security threat.

39. Resource Restrictions

Where necessary and proportionate, Hostwover may temporarily restrict:

  • processes.
  • requests.
  • scripts.
  • database activity.
  • outgoing messages.
  • access; or
  • other affected functionality

to protect infrastructure.

Such restrictions should be related to the identified technical or security issue.

40. Advertised Resource Limits

Hostwover seeks to accurately describe material limits associated with each Hosting Plan.

A plan should not be interpreted as including resources materially beyond its published specifications.

41. "Unlimited" Features

If Hostwover expressly describes a particular feature as "unlimited", that description means the feature does not have a normal fixed quota of the type specified for limited plans.

It does not mean:

  • infinite computing resources.
  • unlimited physical capacity.
  • immunity from technical limits.
  • permission to abuse infrastructure; or
  • permission to use the Service outside its intended Web Hosting purpose.

Any such feature remains subject to reasonable technical, security, and Acceptable Use requirements.

42. Traffic and Bandwidth

Hosting Plans may include:

  • a defined traffic allowance.
  • an unmetered traffic model.
  • or another disclosed network arrangement.

Actual transfer speeds may vary because of:

  • Internet routing.
  • congestion.
  • visitor location.
  • protocol overhead.
  • remote networks.
  • application performance.
  • infrastructure; and
  • other network conditions.

43. No Guaranteed Visitor Capacity

A Hosting Plan does not guarantee that a website will support a particular number of simultaneous visitors unless Hostwover expressly provides such a commitment.

Website capacity depends on factors including:

  • application efficiency.
  • caching.
  • database usage.
  • page complexity.
  • plugins.
  • traffic patterns; and
  • resource consumption.

44. Scheduled Tasks

Eligible Hosting Plans may permit scheduled tasks or cron jobs.

Customers must configure scheduled tasks responsibly.

Tasks must not be configured in a way that:

  • creates abusive resource usage.
  • sends prohibited communications.
  • repeatedly crashes applications.
  • conducts unauthorized scanning; or
  • otherwise violates Hostwover policies.

45. Background Processes

Shared Web Hosting may restrict:

  • persistent background processes.
  • daemons.
  • long-running jobs.
  • custom services.
  • or other functionality more suitable for VPS or VDS environments.

Availability depends on the Hosting Plan.

46. SSH Access

SSH access may be available on eligible Hosting Plans.

Where provided, SSH access is intended for authorized administration within the permissions of the Hosting Account.

SSH access does not provide root or unrestricted server-level access unless expressly stated otherwise.

47. SSH Security

Customers using SSH must protect:

  • passwords.
  • SSH keys.
  • private keys.
  • authorized key files; and
  • access credentials.

Compromised SSH credentials should be revoked or replaced promptly.

48. FTP and File Access

Where FTP, SFTP, or other file-access functionality is available, Customers are responsible for:

  • protecting credentials.
  • limiting authorized users.
  • reviewing uploaded files; and
  • removing unnecessary access.

Secure protocols should be used where available.

49. SSL/TLS

Eligible Hosting Plans may support SSL/TLS certificates.

SSL availability may include:

  • certificates provided as part of a plan.
  • automated certificate issuance.
  • Customer-provided certificates; or
  • other supported certificate arrangements.

The specific functionality depends on the plan and technical configuration.

50. Certificate Issuance

Certificate issuance may require:

  • valid DNS.
  • domain ownership validation.
  • reachable HTTP verification.
  • supported domain configuration; or
  • another validation method.

Hostwover cannot guarantee successful certificate issuance where validation requirements are not satisfied.

51. Certificate Renewal

Automated SSL renewal, where available, depends on continued satisfaction of technical validation requirements.

Changes to:

  • DNS.
  • nameservers.
  • domain status.
  • hosting configuration; or
  • certificate authority requirements

may cause automated renewal to fail.

52. SNI

Hostwover may support Server Name Indication ("SNI") functionality on applicable Hosting Services.

The availability and behavior of SSL functionality depend on the hosting environment and client compatibility.

53. IP Addresses

A Hosting Account may use:

  • a shared IP address.
  • an assigned IP address; or
  • a dedicated IP where expressly included or purchased.

Unless expressly agreed otherwise, IP addresses remain part of Hostwover's or the applicable infrastructure's technical resources and are not owned by the Customer.

54. IP Address Changes

Hostwover may change an assigned hosting IP address where reasonably necessary for:

  • infrastructure migration.
  • security.
  • network changes.
  • maintenance.
  • technical upgrades.
  • provider changes; or
  • Service continuity.

Where the Customer must take action because of a material IP change, Hostwover may provide appropriate information where reasonably practicable.

55. Email Functionality

Some Hosting Plans may include limited email-related functionality.

Any such functionality is distinct from Hostwover's dedicated Professional Email Service unless expressly stated otherwise.

Plan-specific limits and technical requirements apply.

56. Email Abuse

Any email functionality associated with Web Hosting must not be used for:

  • unsolicited bulk messaging.
  • phishing.
  • credential theft.
  • malware distribution.
  • email bombing.
  • deceptive sender impersonation; or
  • another activity prohibited by the Acceptable Use Policy.

57. Email Deliverability

Hostwover does not guarantee delivery of every email message.

Delivery may be affected by:

  • recipient filtering.
  • sender reputation.
  • DNS.
  • SPF.
  • DKIM.
  • DMARC.
  • message Content.
  • third-party blocklists.
  • recipient policies.
  • network issues; or
  • other factors.

58. Backups

Backups are included only where the applicable Hosting Plan or Service description expressly provides them.

The existence of a backup feature does not remove the Customer's responsibility to maintain independent copies of important data.

59. Customer Backup Responsibility

Customers should maintain independent backups of important:

  • website files.
  • databases.
  • configuration.
  • uploaded media.
  • application data.
  • source code; and
  • other critical information.

A backup stored only within the same Hosting Account should not be considered the Customer's only disaster-recovery copy.

60. Backup Frequency

Where Hostwover provides backups, the applicable:

  • frequency.
  • retention period.
  • scope.
  • restoration capability; and
  • exclusions

depend on the Hosting Plan or backup Service description.

Hostwover does not promise a specific backup schedule unless expressly stated for the purchased Service.

61. Backup Exclusions

Backups may exclude certain data because of:

  • technical restrictions.
  • file size.
  • storage limits.
  • unsupported data.
  • corrupted files.
  • policy violations; or
  • another documented technical limitation.

Customers must not assume that every file is present in every backup.

62. Backup Integrity

Hostwover seeks to operate backup functionality reliably where provided, but no backup system can guarantee recovery from every:

  • corruption event.
  • deletion.
  • software error.
  • attack.
  • hardware failure.
  • configuration issue; or
  • catastrophic event.

63. Restoration

Where restoration functionality is available, Customers may be able to restore:

  • selected files.
  • databases.
  • Account data; or
  • a broader Hosting Account state.

The exact restoration options depend on the applicable backup system.

64. Restoration May Overwrite Current Data

Restoring an older backup may replace or conflict with newer Customer Content.

Customers are responsible for understanding the effect of a requested restoration.

Hostwover is not responsible for Customer-requested restoration consequences that were reasonably inherent in restoring an older state.

65. Malware in Backups

Backups may contain malware or vulnerable code that existed when the backup was created.

Restoring a backup does not guarantee removal of the original security problem.

The Customer remains responsible for securing the restored application.

66. Website Migration

Hostwover may offer website migration assistance.

Migration availability may depend on:

  • Hosting Plan.
  • source hosting environment.
  • website technology.
  • access credentials.
  • data size.
  • application compatibility.
  • source-provider restrictions; and
  • technical feasibility.

67. Migration Authorization

By requesting migration, you represent that you are authorized to provide access to the source website and data.

You authorize Hostwover to access and copy the information reasonably necessary to perform the requested migration.

68. Migration Credentials

Hostwover may require temporary credentials to perform a migration.

Customers should:

  • provide only credentials necessary for the migration.
  • use secure submission methods where provided; and
  • rotate temporary credentials after migration where appropriate.

69. Migration Scope

Unless expressly agreed otherwise, a migration may focus on supported website data such as:

  • website files.
  • databases; and
  • relevant configuration.

Migration does not necessarily include every:

  • mailbox.
  • DNS record.
  • SSL configuration.
  • scheduled task.
  • external integration.
  • proprietary platform feature; or
  • unsupported application.

70. Migration Compatibility

Hostwover cannot guarantee that every website can be migrated without modification.

Differences may exist in:

  • PHP versions.
  • database versions.
  • server modules.
  • control panels.
  • filesystem paths.
  • permissions.
  • proprietary software.
  • extensions; and
  • configuration.

71. Migration Testing

Customers should test migrated websites before:

  • changing production DNS.
  • cancelling the previous hosting account; or
  • deleting the source environment.

The Customer is responsible for confirming that the migrated website operates as expected.

72. Migration Downtime

Hostwover may seek to minimize migration-related downtime, but zero downtime cannot be guaranteed.

DNS propagation and application behavior may create temporary differences between the source and destination environments.

73. Free Migration Offers

Where Hostwover advertises a migration as "free", the offer applies according to the disclosed eligibility and scope of that migration Service.

Free migration does not mean that every website, platform, or unlimited quantity of migration work is automatically included.

74. Website Development Is Separate

Web Hosting does not include:

  • website design.
  • application development.
  • debugging custom code.
  • SEO services.
  • Content creation.
  • application maintenance; or
  • software development

unless Hostwover expressly sells those Services separately.

75. Technical Support

Hostwover provides support for matters within the supported scope of Web Hosting.

Support may include assistance concerning:

  • Hosting Account access.
  • Service provisioning.
  • control-panel availability.
  • DNS guidance.
  • server-side Service issues.
  • supported hosting functionality.
  • billing.
  • SSL functionality.
  • Account security; and
  • Service status.

76. Unsupported Customer Code

Hostwover is not required to debug or maintain arbitrary Customer code.

We may provide reasonable guidance, but Customers remain responsible for:

  • custom PHP.
  • JavaScript.
  • application logic.
  • plugins.
  • themes.
  • third-party APIs.
  • custom databases; and
  • other Customer-developed software.

77. Root Access

Shared Web Hosting generally does not provide unrestricted root-level access.

Customers requiring root access or custom operating-system control should use an appropriate VPS or VDS Service.

78. Server Configuration

Hostwover controls server-level configuration required to operate the shared Hosting environment.

Customers may only modify configuration options made available through supported interfaces or configuration mechanisms.

79. Unauthorized Configuration Changes

Customers must not attempt to:

  • bypass hosting isolation.
  • obtain unauthorized root access.
  • alter other customers' environments.
  • modify protected server configuration.
  • exploit kernel or platform vulnerabilities.
  • disable infrastructure security controls; or
  • otherwise obtain access beyond their authorized Hosting Account.

80. Security

Hostwover applies security measures designed to protect the Hosting environment.

These may include:

  • access controls.
  • isolation.
  • monitoring.
  • malware controls.
  • network protections.
  • updates.
  • logging.
  • authentication.
  • abuse detection; and
  • other appropriate security controls.

See the Information Security Policy for additional information.

81. Shared Security Responsibility

Hostwover is responsible for security controls relating to infrastructure under Hostwover's control.

The Customer remains responsible for security of matters under Customer control, including:

  • website passwords.
  • CMS users.
  • plugins.
  • themes.
  • application code.
  • database credentials.
  • Customer devices.
  • uploaded files; and
  • Customer-created accounts.

82. Malware

Customers must not knowingly upload, distribute, or operate malicious software.

If malware is detected, Hostwover may:

  • notify the Customer.
  • restrict the affected website.
  • quarantine files where appropriate.
  • suspend harmful functionality.
  • request remediation; or
  • take emergency action

where reasonably necessary to protect infrastructure or third parties.

83. Compromised Websites

If a website becomes compromised, the Customer is responsible for cooperating with reasonable remediation requirements.

Actions may include:

  • changing passwords.
  • updating applications.
  • removing malware.
  • removing vulnerable plugins.
  • restoring clean Content.
  • reviewing users.
  • updating code; or
  • taking another reasonable security action.

84. Security Suspension

Hostwover may temporarily suspend or isolate an affected Hosting Account where it creates an urgent security risk.

Examples include:

  • active phishing.
  • malware distribution.
  • ongoing attacks.
  • credential theft.
  • a compromised website attacking other systems.
  • large-scale spam; or
  • another material threat.

Immediate protective action may occur without advance notice where necessary.

85. Vulnerability Reports

Security researchers must follow Hostwover's Responsible Disclosure Policy when testing Hostwover systems.

Customers must not use their Hosting Account to conduct unauthorized testing against other systems.

86. Logs and Monitoring

Hostwover may collect technical logs reasonably necessary for:

  • Service operation.
  • troubleshooting.
  • security.
  • abuse detection.
  • fraud prevention.
  • performance.
  • legal compliance; and
  • infrastructure protection.

Processing of Personal Data in logs is governed by the Privacy Policy.

87. Privacy

Hostwover processes Personal Data relating to the Hosting Service according to its Privacy Policy and applicable data-protection requirements.

This may include:

  • Account information.
  • Service configuration.
  • IP information.
  • billing information.
  • support records.
  • usage information.
  • security logs; and
  • technical information.

88. Customer Personal Data

Customers may process Personal Data belonging to their own:

  • website visitors.
  • customers.
  • employees.
  • users; or
  • other individuals

through the Hosting Service.

The Customer is responsible for determining the lawful basis and obligations applicable to its own processing.

89. Hostwover as Processor

Where Hostwover processes Customer-controlled Personal Data solely to provide the Hosting Service on behalf of the Customer, Hostwover may act as a data processor or equivalent service provider under applicable data-protection law.

Additional data-processing terms may apply where required.

90. Production Data

Customers should avoid unnecessarily exposing sensitive production data through:

  • public directories.
  • test websites.
  • logs.
  • debugging output.
  • source-code repositories; or
  • insecure backups.

The Customer is responsible for application-level data exposure under its control.

91. Intellectual Property

Customers must not knowingly use Web Hosting to infringe:

  • copyrights.
  • trademarks.
  • trade secrets.
  • software licenses; or
  • other protected rights.

Hostwover may process appropriate intellectual-property complaints according to the Trademark & Copyright Policy.

92. Abuse Reports

Hostwover may investigate credible reports relating to websites hosted through the Service.

Hostwover may request:

  • Customer explanation.
  • removal of prohibited Content.
  • remediation.
  • security action; or
  • additional information.

Procedures are further described in the Abuse Handling Policy.

93. Suspension for Abuse

Hostwover may suspend all or part of a Hosting Service where there is a reasonable contractual, security, legal, or policy basis.

Where circumstances permit, Hostwover may provide an opportunity to resolve the issue before suspension.

Immediate suspension may occur where delay would create material harm.

94. Suspension for Non-Payment

A Hosting Service may be restricted or suspended where payment remains unpaid after the applicable billing deadline.

The timing and consequences depend on:

  • billing status.
  • Service status.
  • applicable notices.
  • applicable Service terms; and
  • mandatory law.

95. Effect of Suspension

During suspension:

  • websites may become unavailable.
  • control-panel access may be limited.
  • databases may become unavailable.
  • email functionality may be affected.
  • applications may stop operating; and
  • Customer Content may remain stored temporarily.

Suspension does not necessarily mean the Service has been terminated.

96. Charges During Suspension

Charges may continue during a suspension where the Hosting environment and resources remain allocated to the Customer.

A suspension does not automatically cancel the subscription.

97. Reactivation

Where a suspension is remediable, Hostwover may restore the Service after the relevant issue is resolved.

Reactivation may require:

  • payment.
  • security remediation.
  • removal of prohibited Content.
  • verification.
  • resource optimization; or
  • another corrective action.

98. Service Renewal

Web Hosting subscriptions may operate on recurring billing periods.

Where Auto-Renew is enabled, Hostwover may attempt to renew the Service using an authorized payment method.

Auto-Renew does not guarantee successful renewal.

99. Renewal Pricing

Renewal pricing may differ from:

  • introductory pricing.
  • promotional pricing.
  • previous renewal pricing; or
  • initial purchase pricing.

The applicable renewal price is determined according to the Service pricing applicable to the upcoming renewal.

100. Failed Renewal

A failed renewal may result from:

  • payment rejection.
  • insufficient funds.
  • expired payment method.
  • Account restrictions.
  • payment-provider issues; or
  • another processing problem.

Customers should address failed payments promptly to reduce the risk of Service interruption.

101. Service Expiration

If a Hosting Service is not renewed, it may expire.

Following expiration, Hostwover may:

  • suspend access.
  • stop serving websites.
  • disable associated functionality.
  • retain data temporarily.
  • terminate the Hosting Account; and
  • eventually delete Customer Content

according to applicable Service procedures.

102. Data Retention After Expiration

Hostwover does not guarantee indefinite retention of Hosting Account data after expiration, cancellation, or termination.

Customers must maintain their own copies of important data.

Any temporary post-expiration retention should be treated as a recovery opportunity, not as a guaranteed backup Service.

103. Data Deletion

After the applicable termination or retention period, Hostwover may permanently delete:

  • website files.
  • databases.
  • hosting configuration.
  • mail data associated with the Hosting Account where applicable.
  • logs where no longer required; and
  • other Customer Content

subject to applicable law, backup lifecycle, and legitimate retention requirements.

104. Data Recovery After Termination

Hostwover does not guarantee that data can be recovered after a Hosting Account has been terminated.

Where recovery remains technically possible, Hostwover may provide a recovery option subject to:

  • data availability.
  • technical feasibility.
  • applicable charges; and
  • security verification.

105. Cancellation by the Customer

Customers may cancel eligible Web Hosting according to available Account functionality or other supported cancellation procedures.

Depending on the selected cancellation option, cancellation may:

  • disable future renewal; or
  • terminate the Service.

Customers should export important data before termination.

106. Cancellation Does Not Cancel Domains

Cancelling Web Hosting does not automatically cancel:

  • domain registrations.
  • domain renewals.
  • Professional Email.
  • Google Workspace.
  • VPS.
  • VDS; or
  • another independent Service.

Each Service must be managed separately.

107. Refunds

Refund eligibility is governed by Hostwover's Refund Policy and mandatory law.

Refund eligibility may depend on:

  • Service.
  • billing term.
  • promotional conditions.
  • previous refunds.
  • Service usage.
  • included third-party products; and
  • timing of the cancellation request.

108. Non-Refundable Components

Certain components associated with a Hosting order may be non-refundable after successful provisioning or use where permitted by applicable law.

Examples may include separately completed:

  • domain registrations.
  • domain renewals.
  • domain transfers.
  • third-party licenses.
  • customized Services; or
  • other irreversible transactions.

Any mandatory consumer right remains unaffected.

109. Upgrade

Hostwover may allow Customers to upgrade to a higher Hosting Plan.

An upgrade may involve:

  • higher resource allocations.
  • additional websites.
  • additional storage.
  • additional functionality; or
  • another Service enhancement.

Applicable pricing will be disclosed during the upgrade process.

110. Downgrade

Downgrades may be available where the Customer's current usage fits within the lower plan's specifications.

Before downgrading, the Customer may need to:

  • reduce storage.
  • remove websites.
  • reduce databases.
  • remove accounts.
  • reduce resource usage; or
  • otherwise meet the lower plan's limits.

111. Upgrade and Downgrade Effects

Changing plans may affect:

  • available resources.
  • features.
  • software.
  • backups.
  • website limits.
  • email functionality.
  • SSH.
  • databases; or
  • other functionality.

Customers should review the destination plan before confirming the change.

112. Infrastructure Migration

Hostwover may migrate Hosting Accounts between infrastructure where reasonably necessary for:

  • maintenance.
  • capacity.
  • security.
  • hardware replacement.
  • performance.
  • provider changes.
  • technical upgrades.
  • disaster recovery; or
  • Service continuity.

113. Migration by Hostwover

Where Hostwover initiates an infrastructure migration, we will seek to preserve Customer Content and minimize unnecessary Service interruption.

Technical changes may nevertheless affect:

  • IP addresses.
  • DNS.
  • temporary availability.
  • paths.
  • caching; or
  • application behavior.

114. Maintenance

Hostwover may perform scheduled or emergency maintenance.

Maintenance may involve:

  • security updates.
  • operating-system updates.
  • control-panel updates.
  • web-server updates.
  • database updates.
  • network changes.
  • hardware maintenance.
  • storage maintenance; or
  • infrastructure migration.

115. Emergency Maintenance

Emergency maintenance may occur without advance notice where necessary to address:

  • critical vulnerabilities.
  • active attacks.
  • infrastructure failure.
  • data-integrity risk.
  • network emergencies; or
  • another urgent technical issue.

116. Availability

Hostwover seeks to provide reliable Web Hosting.

However, no hosting environment is guaranteed to operate without interruption unless an applicable Service Level Agreement expressly provides a specific commitment.

117. Service Level Agreement

Where a Service Level Agreement applies, it governs any:

  • uptime commitment.
  • measurement method.
  • exclusions.
  • Service-credit procedure; and
  • associated remedy.

Marketing language alone should not be interpreted as creating an SLA different from the published Service Level Agreement.

118. Scheduled Maintenance and SLA

Scheduled or emergency maintenance may be treated according to the exclusions and calculation rules of the applicable Service Level Agreement.

Customers should refer to the SLA for the exact availability calculation.

119. DDoS and External Attacks

Websites may experience disruption from:

  • DDoS attacks.
  • bot traffic.
  • Internet routing issues.
  • malicious requests.
  • application-layer attacks; or
  • other external events.

Hostwover may use protective measures where available but does not guarantee immunity from every attack.

120. Force Majeure

The force-majeure provisions of the Terms of Service apply to this Agreement.

Events outside reasonable control may affect Web Hosting availability.

121. Service Changes

Hostwover may make reasonable changes to the technical environment to:

  • maintain security.
  • improve reliability.
  • improve performance.
  • replace obsolete technology.
  • comply with law.
  • maintain compatibility; or
  • improve the Service.

122. Material Reduction of Paid Service

Hostwover will seek not to materially reduce the core specifications of a paid Hosting Plan during its current paid term without an appropriate operational reason, migration, substitute, remedy, or other treatment consistent with applicable law.

123. Discontinued Features

A feature may be discontinued where:

  • its underlying technology is discontinued.
  • it creates a security risk.
  • licensing changes.
  • compatibility ends.
  • law requires discontinuation; or
  • the feature is replaced by a reasonable alternative.

Material changes will be handled according to the Terms of Service and applicable law.

124. Third-Party Infrastructure

Hostwover may rely on third-party infrastructure, software, networks, data centers, security services, or other technology to provide Web Hosting.

The use of third-party technology does not transfer ownership of Customer Content to those providers.

Relevant processing is also subject to Hostwover's Privacy Policy.

125. Data Center and Location

Hosting infrastructure may be located in the region or location associated with the purchased Service where such a location is expressly offered.

The selected hosting location does not necessarily mean that every:

  • Account record.
  • billing record.
  • support record.
  • backup.
  • monitoring record; or
  • administrative record

is processed exclusively within that location.

See the Privacy Policy for additional information.

126. Customer Access to Infrastructure

The Customer receives access only to the portion of infrastructure authorized under the Hosting Plan.

The Customer receives no right to access:

  • other customer accounts.
  • Hostwover internal systems.
  • host operating systems.
  • hypervisors.
  • private networks.
  • security systems; or
  • other unauthorized infrastructure.

127. Attempts to Circumvent Isolation

Attempting to circumvent hosting-account isolation is a serious violation of this Agreement.

Hostwover may immediately suspend an Account involved in unauthorized attempts to access another customer or protected infrastructure.

128. Account Sharing

The Customer is responsible for persons to whom the Customer grants Hosting Account access.

The Customer should use individual or limited-access credentials where supported instead of unnecessarily sharing a primary password.

129. Developers and Contractors

If you grant a developer, agency, employee, or contractor access to your Hosting Account, you are responsible for ensuring that the person is authorized.

You should revoke access when it is no longer required.

130. Account Ownership Disputes

Where multiple parties claim control over a Hosting Account, Hostwover may require evidence such as:

  • identity information.
  • organization documents.
  • Account records.
  • invoices.
  • authorization.
  • historical information; or
  • other appropriate evidence.

Hostwover may restrict sensitive changes while the dispute is investigated.

131. Customer-Controlled Credentials

Hostwover is not responsible for unauthorized actions caused solely by Customer disclosure of valid credentials where Hostwover has otherwise complied with its applicable security obligations.

This does not limit liability that cannot legally be excluded.

132. Payment and Billing

The payment and billing provisions of the Terms of Service apply to Web Hosting.

Customers agree to pay properly disclosed charges associated with the Hosting Plan.

133. Chargebacks

Fraudulent or knowingly false chargebacks are prohibited.

Where a payment for an active Hosting Service is reversed, Hostwover may investigate and may restrict the affected unpaid Service where legally and contractually permitted.

Legitimate payment disputes will be handled according to applicable law.

134. Taxes

Applicable taxes and government charges may be added or included as required by law.

The applicable amount should be displayed or otherwise disclosed during the relevant transaction.

135. Customer Communications

Hostwover may send operational communications concerning:

  • provisioning.
  • renewals.
  • payments.
  • suspension.
  • resource issues.
  • security.
  • malware.
  • abuse.
  • maintenance.
  • migration.
  • Service changes.
  • cancellation; and
  • termination.

These communications are distinct from optional marketing.

136. Current Contact Information

Customers are responsible for maintaining an accessible Account email address and accurate contact information.

Important Service notices may be sent to the contact information associated with the Account.

137. Support Communications

Customers must not send unnecessary sensitive credentials through ordinary support messages.

Do not send:

  • passwords.
  • private SSH keys.
  • complete payment-card information.
  • CVV.
  • recovery codes.
  • unrelated API secrets; or
  • other unnecessary credentials.

Hostwover may provide an appropriate secure method where temporary access is legitimately required.

138. Customer Cooperation

Customers must reasonably cooperate with Hostwover when necessary to investigate:

  • Service outages.
  • security incidents.
  • malware.
  • abuse.
  • Account compromise.
  • payment disputes.
  • migration problems; or
  • ownership disputes.

139. Termination by Hostwover

Hostwover may terminate Web Hosting where permitted by applicable law and justified by circumstances including:

  • material breach.
  • repeated prohibited use.
  • fraud.
  • serious abuse.
  • persistent non-payment.
  • unlawful activity.
  • severe security risk.
  • false Account information.
  • mandatory legal action; or
  • another basis permitted under the Terms of Service.

140. Notice Before Termination

Where reasonably possible and appropriate, Hostwover may provide notice or an opportunity to remedy an issue before terminating the Service.

Immediate termination or suspension may occur where continued operation creates material:

  • security.
  • legal.
  • infrastructure; or
  • third-party harm.

141. Export Before Termination

Customers should export important Customer Content before:

  • voluntary cancellation.
  • expiration.
  • planned migration.
  • Account closure; or
  • known termination.

Hostwover does not guarantee continued access after termination.

142. Effect of Termination

Following termination:

  • hosted websites may stop operating.
  • databases may become unavailable.
  • control-panel access may stop.
  • FTP/SSH access may stop.
  • associated email functionality may stop.
  • assigned hosting resources may be released; and
  • Customer Content may eventually be deleted.

143. Domain Independence After Hosting Termination

Termination of Web Hosting does not automatically change ownership or registration of an independently registered domain.

Customers may point their domain to another hosting provider where otherwise permitted.

144. Limitation of Liability

Hostwover's liability relating to Web Hosting is subject to the limitation-of-liability provisions in the Terms of Service.

Nothing in this Agreement excludes or limits liability that cannot legally be excluded.

145. Customer-Controlled Loss

To the maximum extent permitted by applicable law, Hostwover is not responsible for loss resulting solely from Customer-controlled matters including:

  • insecure passwords.
  • vulnerable plugins.
  • outdated CMS software.
  • Customer code.
  • Customer DNS changes.
  • accidental Customer deletion.
  • unauthorized disclosure of credentials.
  • Customer database changes.
  • unsupported software; or
  • Customer-requested restoration of older data.

146. No Guarantee of Application Compatibility

Hostwover does not guarantee that every application will function on every Hosting Plan.

Customers are responsible for checking application requirements including:

  • runtime version.
  • database requirements.
  • storage.
  • extensions.
  • memory.
  • processes.
  • file permissions; and
  • other dependencies.

147. No Business-Outcome Guarantee

Hostwover does not guarantee that use of Web Hosting will produce:

  • website traffic.
  • sales.
  • search rankings.
  • conversions.
  • profitability.
  • customer acquisition; or
  • another business outcome.

148. Customer Indemnification

To the maximum extent permitted by applicable law, the Customer agrees to indemnify Hostwover against third-party claims and reasonable costs arising directly from:

  • unlawful Customer Content.
  • intellectual-property infringement by Customer Content.
  • intentional misuse of Web Hosting.
  • malware intentionally distributed by the Customer.
  • fraud by the Customer.
  • unlawful processing controlled by the Customer; or
  • material breach of this Agreement.

This does not apply to the extent a claim results from conduct for which Hostwover is legally responsible.

Mandatory consumer rights remain unaffected.

149. Consumer Rights

Nothing in this Agreement is intended to remove, reduce, or waive a mandatory consumer right that cannot legally be excluded.

Where applicable consumer-protection law provides stronger mandatory protections, those protections prevail.

150. Governing Law

Subject to mandatory consumer and other applicable protections, this Agreement is governed by the governing law specified in Hostwover's Terms of Service.

Where the Terms of Service specify the laws of the Arab Republic of Egypt, the same governing law applies to this Agreement.

151. Complaints and Disputes

Customers who believe Hostwover has incorrectly handled a Web Hosting matter should contact Hostwover Support.

Matters may also be handled according to Hostwover's Complaints & Dispute Resolution procedures.

Nothing in this Agreement prevents the exercise of mandatory regulatory or legal rights.

152. Changes to This Agreement

Hostwover may update this Agreement to reflect:

  • Service changes.
  • security requirements.
  • technical changes.
  • legal developments.
  • infrastructure changes.
  • new functionality.
  • policy updates; or
  • clarification of existing terms.

The latest published version will display an updated Last Updated date.

153. Material Changes

Where applicable law requires notice of a material contractual change, Hostwover may provide notice through:

  • email.
  • Account notification.
  • website notice; or
  • another appropriate method.

Where explicit acceptance is legally required, Hostwover will seek that acceptance.

154. Conflict With Mandatory Law

If this Agreement conflicts with a mandatory requirement of applicable law, the mandatory requirement controls to the extent of the conflict.

155. Order of Precedence

If there is a conflict relating specifically to Web Hosting, the applicable order of precedence is generally:

  1. mandatory applicable law.
  2. expressly agreed Service-specific terms.
  3. this Web Hosting Agreement.
  4. Hostwover Terms of Service.
  5. applicable Hostwover policies.

Where a specific document expressly establishes another valid priority, that express provision may apply.

156. Severability

If any provision of this Agreement is held invalid or unenforceable, the remaining provisions continue to apply to the maximum extent permitted by law.

157. No Waiver

Failure by Hostwover to immediately enforce a provision does not constitute a permanent waiver of that provision.

158. Assignment

The Customer may not transfer the Hosting Account or contractual rights to another party except through an authorized process or with appropriate Hostwover approval where required.

Valid changes of business ownership or Account control may require verification.

159. Electronic Acceptance

This Agreement may be accepted electronically.

Hostwover may maintain records including:

  • Account identifier.
  • Hosting Plan.
  • Agreement version.
  • acceptance timestamp.
  • order information.
  • IP information; and
  • relevant transaction data

where appropriate to document acceptance.

160. Entire Web Hosting Agreement

This Agreement, together with:

  • Terms of Service.
  • applicable order.
  • Hosting Plan description.
  • applicable policies; and
  • expressly incorporated Service terms

forms the agreement governing the applicable Web Hosting Service.

161. Related Hostwover Documents

Customers using Web Hosting should also review:

  • Terms of Service
  • Acceptable Use Agreement
  • Acceptable Use Policy
  • Abuse Handling Policy
  • Privacy Policy
  • Information Security Policy
  • Refund Policy
  • Service Level Agreement
  • Customer Service Policy
  • Responsible Disclosure Policy
  • Trademark & Copyright Policy
  • Complaints & Dispute Resolution

Where a domain is also managed through Hostwover:

  • Registrar Information
  • Domain Registration Agreement
  • Domain Transfer Agreement
  • Domain Renewal & Expiration Agreement
  • Domain Expiration & Recovery Policy

may also apply.

162. Contact Hostwover

For assistance concerning Web Hosting:

Hostwover Support

Website: hostwover.com

Email: [email protected]

Where appropriate, include:

  • Hostwover Account email.
  • Hosting Service identifier.
  • affected domain.
  • relevant error message.
  • approximate time of the issue; and
  • description of the problem.

Do not send passwords, private keys, payment-card security codes, or unrelated sensitive credentials through ordinary support communications.

163. Final Provision

By purchasing or using Hostwover Web Hosting, you acknowledge that website operation is a shared technical responsibility.

Hostwover is responsible for operating and protecting the Web Hosting infrastructure within Hostwover's control according to the applicable Service.

You are responsible for the websites, software, Content, credentials, configuration, and data under your control.

Hostwover will seek to provide reliable hosting, appropriate security controls, clear Service specifications, customer support, and proportionate handling of technical or abuse-related issues.

Customers are responsible for:

  • protecting their Hosting Account.
  • keeping applications updated.
  • maintaining independent backups of important data.
  • remaining within applicable Hosting Plan limits.
  • using resources responsibly.
  • complying with applicable law and Hostwover policies.
  • monitoring renewals and payments; and
  • exporting important data before cancellation or termination.