Legal
Hostwover Legal Center

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

Customer Service Policy

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.

Last updated: August 14, 2026

This Customer Service Policy ("Policy") explains how Hostwover ("Hostwover", "we", "us", or "our") provides customer service, technical support, billing assistance, account assistance, and service-related support to customers using services provided, sold, resold, managed, or made available through Hostwover.

This Policy applies to customers, account holders, administrators, authorized representatives, and other persons requesting assistance regarding a Hostwover Service ("Customer", "you", or "your").

This Policy should be read together with the:

  • Hostwover Terms of Service.
  • applicable product agreement.
  • Privacy Policy.
  • Refund Policy.
  • Acceptable Use Policy.
  • Abuse Handling Policy; and
  • other applicable Hostwover policies.

1. Purpose

Hostwover aims to provide professional, helpful, secure, and practical customer support.

This Policy explains:

  • how support may be requested.
  • what support generally includes.
  • how requests are prioritized.
  • what information Customers should provide.
  • account-verification requirements.
  • support limitations.
  • escalation procedures.
  • third-party service dependencies.
  • Customer responsibilities; and
  • how support-related information is handled.

2. Services Covered

This Policy may apply to customer-service requests involving:

  • domain registration.
  • domain transfers.
  • domain renewals.
  • DNS.
  • web hosting.
  • shared hosting.
  • VPS.
  • VDS.
  • virtual servers.
  • professional email.
  • business email.
  • Google Workspace.
  • SSL-related services.
  • Hostwover accounts.
  • billing.
  • payments.
  • renewals.
  • provisioning.
  • APIs.
  • AI functionality.
  • account dashboards.
  • technical configuration; and
  • other Hostwover Services.

3. Customer Support Philosophy

Hostwover seeks to provide support that is:

  • respectful.
  • practical.
  • technically accurate.
  • security-conscious.
  • transparent.
  • proportionate to the issue; and
  • appropriate to the Customer's Service.

Hostwover will make commercially reasonable efforts to assist Customers within the scope of the applicable Service.

4. Support Availability

Support requests may generally be submitted through available electronic support channels at any time.

A statement that support is available 24/7 means that Customers may access or submit requests through the available support system at any time unless otherwise stated.

It does not mean that:

  • every support channel is continuously staffed.
  • every request receives an immediate human response.
  • every issue can be immediately resolved.
  • every upstream provider is available continuously; or
  • all support requests receive identical response times.

5. Support Channels

Depending on availability, Hostwover may provide customer service through:

  • the Hostwover account or support dashboard.
  • support tickets.
  • email.
  • website support interfaces.
  • live chat where available.
  • automated support tools.
  • AI-assisted support.
  • service notifications; or
  • other communication channels published by Hostwover.

Not every support channel is available for every Service or issue.

6. Primary Support Contact

General Customer support may be requested through:

Hostwover Support

Email: [email protected]

Website: hostwover.com

Where an authenticated support portal is available, Customers are encouraged to use it for account-specific matters.

7. Authenticated Support

Hostwover may require sensitive account or Service requests to be submitted through an authenticated Hostwover account.

This helps Hostwover verify that the requester is authorized to manage the affected Service.

8. Support Tickets

Hostwover may create a support ticket for a Customer request.

Tickets may contain:

  • Customer messages.
  • account information.
  • Service information.
  • troubleshooting information.
  • screenshots.
  • logs.
  • technical diagnostics.
  • Hostwover responses.
  • provider communications; and
  • resolution information.

9. Ticket Reference

Customers should retain the ticket or case reference associated with a support request.

When following up, providing the existing ticket reference helps avoid duplicate investigations.

10. Duplicate Requests

Submitting repeated requests concerning the same issue through multiple channels may delay handling rather than accelerate it.

Hostwover may combine duplicate requests into one support case.

11. Support Scope

General Hostwover support may include reasonable assistance with:

  • account access.
  • Hostwover account settings.
  • orders.
  • billing.
  • payments.
  • renewals.
  • provisioning.
  • domain management.
  • basic DNS configuration.
  • hosting access.
  • control-panel access.
  • VPS or VDS provisioning.
  • professional email setup.
  • Google Workspace provisioning.
  • service status.
  • basic troubleshooting; and
  • issues directly related to Hostwover Services.

12. Billing Support

Hostwover may provide assistance concerning:

  • invoices.
  • payments.
  • failed payments.
  • renewal charges.
  • billing cycles.
  • order status.
  • service pricing.
  • account balance.
  • applicable discounts.
  • taxes.
  • refunds where applicable; and
  • billing-related errors.

13. Domain Support

Domain-related customer service may include reasonable assistance with:

  • registration status.
  • transfers.
  • renewal.
  • expiration.
  • nameservers.
  • DNS.
  • domain verification.
  • contact verification.
  • transfer authorization procedures.
  • registrar-related status information; and
  • escalation to the upstream registrar where appropriate.

14. Registrar Limitations

Hostwover may provide domain services through an upstream registrar or other domain provider.

Some domain operations therefore require action by:

  • the sponsoring registrar.
  • domain registry.
  • registry operator.
  • ICANN-related process; or
  • another provider.

Hostwover cannot guarantee immediate completion of actions controlled by those parties.

15. DNS Support

Hostwover may assist with basic DNS configuration for Services it supports.

This may include guidance concerning:

  • A records.
  • AAAA records.
  • CNAME records.
  • MX records.
  • TXT records.
  • SPF.
  • DKIM.
  • DMARC.
  • nameservers; and
  • verification records.

Hostwover does not guarantee immediate DNS propagation.

16. DNS Propagation

DNS changes may take time to become visible across internet resolvers.

Hostwover support cannot force third-party DNS caches, recursive resolvers, internet providers, registries, or external DNS systems to update immediately.

17. Web Hosting Support

Web Hosting support may include reasonable assistance with:

  • hosting account provisioning.
  • control-panel access.
  • domain connection.
  • DNS.
  • SSL activation.
  • hosting configuration.
  • service availability.
  • supported runtime settings.
  • email configuration where included; and
  • Hostwover-controlled infrastructure issues.

18. Website Development

Unless expressly included in the purchased Service, general hosting support does not include unlimited:

  • website development.
  • website redesign.
  • custom programming.
  • application development.
  • bug fixing in Customer code.
  • theme customization.
  • plugin development.
  • database development; or
  • business-specific software development.

Hostwover may offer such services separately where available.

19. Third-Party Website Software

Hostwover may provide reasonable guidance concerning commonly used website software.

However, Hostwover does not guarantee support for every:

  • CMS.
  • plugin.
  • theme.
  • framework.
  • application.
  • script.
  • library; or
  • third-party integration.

The developer or vendor of the third-party software may need to provide specialized assistance.

20. VPS Support

VPS support generally covers the Hostwover-provided Service and infrastructure according to the applicable VPS Agreement.

Depending on the plan, this may include assistance concerning:

  • provisioning.
  • power state.
  • network allocation.
  • server access information.
  • reinstall functionality.
  • service availability.
  • snapshots or recovery features where included.
  • billing; and
  • infrastructure-related issues.

21. VPS Administration

Unless a managed-service feature expressly states otherwise, VPS Customers are responsible for administration of their operating system and installed software.

General VPS support does not automatically include unlimited:

  • Linux administration.
  • Windows administration.
  • server hardening.
  • application deployment.
  • database administration.
  • web-server optimization.
  • firewall design.
  • debugging Customer software.
  • DevOps implementation; or
  • ongoing server management.

22. VDS Support

VDS support generally covers Hostwover-provided infrastructure and Service functionality according to the applicable VDS Agreement.

Customers remain responsible for administration of their own operating environment unless management services are specifically included.

23. Root Access

Where the Customer has root, administrator, or equivalent access, the Customer is responsible for changes made using that access.

Hostwover cannot guarantee recovery from configuration changes made by the Customer.

24. Professional Email Support

Professional Email support may include reasonable assistance with:

  • mailbox provisioning.
  • mailbox status.
  • password-reset procedures.
  • storage allocation.
  • DNS requirements.
  • MX configuration.
  • SPF.
  • DKIM.
  • supported mail-client settings.
  • billing; and
  • provider-side issues.

25. Email Deliverability

Hostwover may assist with troubleshooting email delivery.

However, Hostwover cannot guarantee that every message will:

  • reach the recipient inbox.
  • avoid spam filtering.
  • be accepted by the recipient mail server.
  • avoid third-party reputation filtering; or
  • be delivered within a specific period.

Email delivery depends partly on external systems beyond Hostwover's control.

26. Google Workspace Support

For Google Workspace purchased through Hostwover, support may include reasonable assistance with:

  • subscription provisioning.
  • licensing.
  • billing.
  • domain verification.
  • reseller-related matters.
  • basic DNS setup.
  • subscription status; and
  • escalation of qualifying provider-side issues.

27. Google-Controlled Issues

Google operates the Google Workspace platform.

Some issues may require action from Google or the applicable upstream provider.

Hostwover cannot directly modify or override all:

  • Google security controls.
  • account enforcement decisions.
  • Google outages.
  • Google product functionality.
  • Google administrative restrictions; or
  • Google infrastructure behavior.

28. Migration Assistance

Where Hostwover offers migration assistance, the exact scope may depend on the Service and migration type.

Migration may involve:

  • websites.
  • databases.
  • email.
  • DNS.
  • files; or
  • other supported content.

29. Migration Limitations

Migration may be affected by:

  • source-provider restrictions.
  • source credentials.
  • data size.
  • unsupported formats.
  • corrupted data.
  • API limits.
  • application compatibility.
  • third-party restrictions.
  • source-server availability; or
  • Customer configuration.

Successful migration is not guaranteed unless expressly stated in a separate agreement.

30. Backups and Recovery

Support may assist with backup or recovery functionality where included with the purchased Service.

Customers remain responsible for maintaining appropriate independent backups unless the applicable Service expressly provides otherwise.

31. No Guarantee of Data Recovery

Hostwover does not guarantee that deleted, corrupted, overwritten, or lost Customer data can always be recovered.

The availability of recovery depends on:

  • the Service.
  • available backups.
  • snapshot status.
  • retention periods.
  • provider systems; and
  • the nature of the incident.

32. Support Priority

Hostwover may prioritize requests based on their impact and urgency.

A higher priority generally means Hostwover may review the issue before lower-impact requests.

Priority does not itself guarantee a specific resolution time.

33. Critical Priority

A request may be treated as critical where there is evidence of a serious active issue such as:

  • widespread Service unavailability.
  • significant Hostwover infrastructure failure.
  • major security compromise.
  • inability of many users to access a production Service.
  • serious data-security event; or
  • another comparable high-impact incident.

34. High Priority

A request may be treated as high priority where:

  • a production Service is substantially impaired.
  • a major feature is unavailable.
  • email service is materially disrupted.
  • a domain-related problem significantly affects an active Service; or
  • another serious issue substantially affects the Customer's use of a Service.

35. Normal Priority

Normal-priority requests may include:

  • configuration questions.
  • ordinary technical troubleshooting.
  • billing inquiries.
  • minor Service issues.
  • DNS assistance.
  • general account assistance; and
  • other issues that do not cause substantial Service failure.

36. Low Priority

Lower-priority requests may include:

  • general information.
  • feature questions.
  • non-urgent configuration advice.
  • suggestions.
  • documentation questions; or
  • other requests that do not materially affect Service operation.

37. Priority Reclassification

Hostwover may change a ticket's priority after reviewing the actual technical impact.

A Customer's description of an issue as "urgent" does not automatically make the issue a critical incident.

38. Response Time

Hostwover seeks to respond to support requests within a commercially reasonable period based on:

  • severity.
  • ticket volume.
  • complexity.
  • required verification.
  • Service type.
  • staffing.
  • upstream-provider involvement; and
  • other relevant circumstances.

Unless expressly stated in an applicable Service Level Agreement, Hostwover does not guarantee a specific initial-response time.

39. Resolution Time

Initial response and final resolution are different.

A support agent may acknowledge or begin investigating an issue before the issue can be fully resolved.

Resolution may depend on:

  • troubleshooting.
  • Customer cooperation.
  • reproduction of the issue.
  • third-party providers.
  • DNS propagation.
  • software vendors.
  • registrars.
  • registries.
  • data centers.
  • cloud providers.
  • email providers.
  • payment providers; or
  • other external factors.

40. No Universal Resolution Guarantee

Hostwover does not promise that all support issues will be resolved within a fixed period.

Some issues can be resolved quickly, while others may require extended investigation or third-party action.

41. Service Level Agreements

Where a specific Service includes a formal Service Level Agreement ("SLA"), the applicable SLA governs qualifying service-availability commitments and service credits.

General customer-support statements do not create an SLA unless expressly identified as such.

42. Status Updates

For issues requiring extended investigation, Hostwover may provide updates when:

  • meaningful progress occurs.
  • additional information is required.
  • a provider responds.
  • the issue changes materially; or
  • a resolution becomes available.

Hostwover is not required to send repetitive updates where no meaningful new information is available.

43. Customer Information Required

Customers should provide enough information for Hostwover to understand and investigate the issue.

Useful information may include:

  • affected Service.
  • domain.
  • server identifier.
  • order number.
  • invoice number.
  • relevant URL.
  • error message.
  • time of occurrence.
  • steps to reproduce.
  • screenshots.
  • logs.
  • browser or device information; and
  • recent configuration changes.

44. Accurate Information

Customers should provide accurate and complete information when requesting support.

Incorrect or incomplete information may delay investigation or cause incorrect troubleshooting.

45. Reproduction Steps

For technical problems, Customers should provide clear steps showing how the issue can be reproduced where possible.

This may significantly improve Hostwover's ability to diagnose the problem.

46. Screenshots

Screenshots may be useful for identifying interface errors or unexpected behavior.

Customers should remove or conceal unnecessary sensitive information before submitting screenshots.

47. Logs

Hostwover may request relevant logs where necessary to diagnose:

  • application errors.
  • network problems.
  • server issues.
  • email problems.
  • authentication problems; or
  • security incidents.

Customers should provide only information reasonably relevant to the support request.

48. Passwords

Customers must not send passwords by email or support ticket unless an authorized Hostwover support workflow specifically and securely requires temporary credentials.

Hostwover personnel should not require Customers to disclose the password to their Hostwover account.

49. Private Keys and Secrets

Customers should not send unnecessary:

  • SSH private keys.
  • API secrets.
  • payment-card numbers.
  • recovery codes.
  • authentication tokens.
  • database passwords; or
  • other sensitive credentials.

Where temporary access is necessary, a safer temporary or restricted credential should be used where technically possible.

50. Temporary Credentials

Where troubleshooting genuinely requires access to a Customer-controlled system, Hostwover may ask the Customer to create temporary credentials.

Customers should revoke or change temporary credentials after the support work is completed.

51. Identity Verification

Hostwover may require verification before performing security-sensitive actions.

Verification may be required for:

  • account recovery.
  • email-address changes.
  • billing changes.
  • domain transfers.
  • administrator recovery.
  • ownership disputes.
  • disclosure of account information.
  • cancellation of sensitive Services; or
  • other high-risk actions.

52. Verification Methods

Verification may involve one or more reasonable methods, including:

  • authenticated account access.
  • confirmation through the registered email address.
  • order information.
  • billing information.
  • domain verification.
  • account-security checks; or
  • additional evidence appropriate to the request.

53. Failed Verification

Hostwover may refuse or delay a requested account action if the requester cannot sufficiently demonstrate authorization.

Protecting the account from unauthorized access takes priority over convenience.

54. Authorized Representatives

Customers may authorize employees, developers, administrators, or other representatives to communicate with Hostwover where supported.

The Customer remains responsible for access granted to those persons.

55. Authorization Verification

Hostwover may require confirmation from the account owner before allowing an additional person to make security-sensitive or billing-sensitive changes.

56. Former Employees and Contractors

Customers are responsible for removing access from employees, contractors, or administrators who are no longer authorized.

Hostwover is not responsible for actions performed by a person who retained valid Customer-issued credentials unless Hostwover caused the unauthorized access.

57. Account Recovery

Hostwover may assist with account recovery when appropriate verification requirements are satisfied.

Recovery procedures are designed to protect against unauthorized account takeover.

58. Security Takes Priority

Hostwover may decline a support request if fulfilling it would create an unreasonable:

  • security risk.
  • privacy risk.
  • fraud risk.
  • account-takeover risk; or
  • legal risk.

59. Support Access to Customer Systems

Hostwover personnel may need limited access to relevant technical systems or information in order to provide support.

Such access should be limited to what is reasonably necessary for the support purpose.

60. Customer Authorization

By requesting troubleshooting that reasonably requires examination of Customer-controlled data or configuration, the Customer authorizes Hostwover to access the information necessary to perform that requested support activity, subject to applicable privacy and security requirements.

61. Data Privacy

Support communications may contain personal information.

Hostwover processes such information in accordance with the Hostwover Privacy Policy and applicable law.

62. Support Records

Hostwover may retain support tickets and related records for purposes including:

  • providing support.
  • maintaining service history.
  • security.
  • quality assurance.
  • training.
  • dispute resolution.
  • fraud prevention.
  • legal compliance; and
  • improving Services.

63. Sensitive Data

Customers should avoid providing personal or confidential information that is not necessary for the support request.

64. Payment Card Information

Customers must not send complete payment-card numbers, card security codes, or other prohibited cardholder data through ordinary support communications.

65. Upstream Providers

Some Hostwover Services depend on third-party providers.

Hostwover may need to communicate with an upstream provider when investigating a Customer issue.

66. Provider Escalation

Where appropriate, Hostwover may escalate a case to:

  • a registrar.
  • registry.
  • infrastructure provider.
  • cloud provider.
  • data center.
  • email provider.
  • software provider.
  • Google.
  • payment provider; or
  • another relevant service provider.

67. Information Shared During Escalation

Hostwover may share information reasonably necessary for an upstream provider to investigate the issue.

Hostwover will handle such information in accordance with applicable privacy requirements.

68. Provider Response Times

Hostwover cannot guarantee the response or resolution time of an external provider.

An upstream provider's delay does not necessarily mean Hostwover has stopped working on the issue.

69. Provider Decisions

Hostwover cannot always override decisions made independently by third-party providers.

Examples may include:

  • domain registry actions.
  • registrar restrictions.
  • Google account enforcement.
  • payment-provider decisions.
  • IP blocklists.
  • external mail filtering; or
  • third-party application policies.

70. Third-Party Services

Hostwover support does not automatically include troubleshooting every third-party service used by a Customer.

Where an issue originates solely from a third party, Hostwover may advise the Customer to contact that provider directly.

71. Customer-Controlled Software

The Customer is responsible for software, applications, scripts, and code installed or deployed by the Customer unless the applicable Service expressly includes management of that software.

72. Unsupported Software

Hostwover may decline deep troubleshooting of:

  • obsolete software.
  • end-of-life operating systems.
  • unsupported plugins.
  • unauthorized software.
  • pirated software.
  • unsupported custom applications; or
  • systems whose configuration prevents reasonable diagnosis.

73. Development Assistance

Hostwover support may provide limited guidance related to Service configuration.

Support does not automatically include writing, reviewing, debugging, or maintaining Customer application code.

74. Database Administration

Unless expressly included, Hostwover support does not provide ongoing administration of Customer-managed databases.

Customers remain responsible for:

  • queries.
  • schema design.
  • application data.
  • indexes.
  • access permissions.
  • backups; and
  • optimization

within Customer-managed environments.

75. Security Hardening

Hostwover may provide general security guidance.

Unless expressly included in a managed service, comprehensive security hardening of a Customer-controlled VPS, VDS, application, or website remains the Customer's responsibility.

76. Malware Cleanup

Hostwover may assist in identifying an infected Service where practical.

Full malware investigation, forensic analysis, website cleanup, or server remediation is not automatically included unless specifically offered as part of the Service.

77. DDoS and Security Incidents

Customers experiencing attacks should provide relevant information where available.

Hostwover may apply available protections or coordinate with infrastructure providers, but no security measure can guarantee protection against every attack.

78. Service Outages

When Hostwover becomes aware of a significant Service incident, Hostwover may communicate through:

  • support tickets.
  • account notifications.
  • email.
  • status pages.
  • website notices; or
  • other appropriate channels.

79. Known Incidents

Where a Customer's issue is part of a known platform-wide incident, Hostwover may associate the ticket with that incident rather than independently reproducing the same investigation for every Customer.

80. Planned Maintenance

Hostwover or its providers may perform planned maintenance.

Where appropriate and reasonably practicable, Customers may receive advance notice of maintenance expected to materially affect a Service.

81. Emergency Maintenance

Emergency maintenance may sometimes be necessary without advance notice to:

  • address security vulnerabilities.
  • prevent infrastructure failure.
  • mitigate abuse.
  • restore service; or
  • protect Customers.

82. Customer Responsibilities

Customers are responsible for reasonably cooperating with troubleshooting.

This may include:

  • responding to questions.
  • providing requested logs.
  • performing recommended tests.
  • confirming configuration.
  • maintaining valid contact information.
  • securing credentials.
  • applying necessary updates; and
  • providing appropriate system access where required.

83. Failure to Cooperate

Hostwover may be unable to continue an investigation where the Customer does not provide information reasonably necessary to diagnose the issue.

A ticket may be placed on hold or closed if required information is not supplied.

84. Customer Configuration Changes

Customers should inform Hostwover of relevant configuration changes made shortly before an issue occurred.

Changes may include:

  • DNS modifications.
  • application deployments.
  • firewall changes.
  • password changes.
  • software updates.
  • server configuration changes.
  • plugin installations; or
  • account-permission changes.

85. Changes During Investigation

Customers should avoid making unnecessary major configuration changes during troubleshooting unless requested or clearly documented.

Untracked changes can make technical diagnosis more difficult.

86. Customer Backups Before Changes

Before performing significant Customer-controlled changes, Customers should maintain appropriate backups where possible.

87. Hostwover-Performed Changes

Where Hostwover is authorized to make configuration changes during support, Hostwover will use reasonable care.

However, technical intervention may involve inherent risks, particularly in Customer-managed systems.

Customers should maintain suitable backups.

88. Professional Conduct

Hostwover expects respectful communication between Customers and support personnel.

Disagreement, complaints, and criticism are permitted.

However, Customers must not use support channels for:

  • credible threats.
  • unlawful harassment.
  • abusive flooding.
  • discriminatory abuse.
  • malicious impersonation; or
  • other conduct prohibited by Hostwover policies.

89. Support Abuse

Hostwover may restrict access to a particular support channel where a person repeatedly:

  • floods tickets.
  • sends automated spam.
  • submits knowingly false information.
  • threatens personnel.
  • attempts social engineering.
  • abuses support systems; or
  • materially interferes with Hostwover's ability to assist other Customers.

Where practical, Hostwover may preserve another reasonable communication method for legitimate account matters.

90. Social Engineering

Customers must not attempt to manipulate Hostwover personnel into bypassing:

  • authentication.
  • identity verification.
  • security procedures.
  • payment protections.
  • account ownership requirements; or
  • other security controls.

91. Support Agent Authority

A support agent may assist within the authority granted to that role.

Certain actions may require escalation to:

  • billing personnel.
  • technical specialists.
  • security teams.
  • administrators.
  • management.
  • legal or compliance personnel; or
  • upstream providers.

92. Escalation

A support request may be escalated where:

  • specialized technical expertise is required.
  • the issue remains unresolved after reasonable troubleshooting.
  • provider involvement is required.
  • security risk exists.
  • billing investigation is required.
  • policy interpretation is necessary; or
  • another higher-level review is appropriate.

93. Escalation Is Not Automatic Priority

Escalating a request does not necessarily mean the issue is critical.

Escalation may simply mean that a different team or provider has the necessary capability to continue the investigation.

94. Management Review

Customers may request reasonable review of a support matter where they believe:

  • a material issue remains unresolved.
  • support procedures were incorrectly applied; or
  • an important factual issue was overlooked.

A request for management review does not guarantee a different outcome.

95. Complaints

Customer-service complaints may be submitted to Hostwover Support.

Customers should identify:

  • the relevant ticket.
  • Service.
  • issue.
  • previous response.
  • reason for dissatisfaction; and
  • desired resolution.

96. Complaint Review

Hostwover may review:

  • prior communications.
  • technical records.
  • Customer statements.
  • account activity.
  • provider information.
  • applicable policies; and
  • available remedies.

97. Billing Complaints

Billing disputes should be reported promptly.

The Customer should identify the affected:

  • invoice.
  • order.
  • transaction.
  • Service; and
  • disputed amount.

98. Refund Requests

Refund requests are handled under the applicable Hostwover Refund Policy, Terms of Service, product agreement, and applicable law.

A support agent's attempt to troubleshoot an issue does not itself create or remove a refund entitlement.

99. Chargebacks

Customers are encouraged to contact Hostwover regarding disputed charges before initiating a payment chargeback where practical.

A chargeback does not automatically determine whether the underlying Service charge was valid.

100. Cancellation Requests

Support may assist with cancellation where the relevant Service permits it.

Customers remain responsible for understanding the difference between:

  • disabling automatic renewal.
  • cancelling future renewal.
  • terminating an active Service; and
  • ending an existing commitment.

101. Renewal Assistance

Hostwover may assist Customers with:

  • renewal dates.
  • automatic renewal.
  • failed renewal.
  • payment methods.
  • renewal status; and
  • applicable renewal pricing.

102. Expired Services

Recovery of expired Services may depend on the product.

For example:

  • domains may enter renewal or redemption stages.
  • hosting may be suspended.
  • email may become inaccessible.
  • Workspace services may be suspended; or
  • server data may eventually be deleted.

Support cannot guarantee recovery after expiration.

103. Account Notifications

Customers are responsible for maintaining an accurate, monitored contact email address.

Hostwover may send important notifications concerning:

  • renewal.
  • payment.
  • security.
  • service status.
  • domain verification.
  • account access.
  • abuse.
  • suspension; or
  • support cases.

104. Language of Support

Hostwover may provide support in one or more languages depending on staff and channel availability.

Availability of translated website content does not guarantee real-time support in every language at all times.

105. Translation

Where a complex technical or legal issue is handled in more than one language, terminology may differ slightly.

Hostwover may use the English version of applicable legal terms where necessary to avoid ambiguity.

106. AI-Assisted Support

Hostwover may use artificial intelligence or automated systems to:

  • answer common questions.
  • classify requests.
  • suggest troubleshooting.
  • retrieve relevant documentation.
  • summarize tickets.
  • route requests; or
  • assist support personnel.

107. AI Limitations

Automated or AI-generated support may contain errors or incomplete information.

Customers should not rely solely on automated guidance for actions that may materially affect:

  • data.
  • production infrastructure.
  • billing.
  • security.
  • domain ownership; or
  • legal rights.

Hostwover may provide human review where appropriate and available.

108. Automated Ticket Routing

Hostwover may automatically categorize or prioritize support requests.

Automated classification may be corrected after human review where appropriate.

109. Service Documentation

Hostwover may publish:

  • tutorials.
  • documentation.
  • FAQs.
  • knowledge-base articles.
  • setup guides.
  • troubleshooting guides; and
  • status information.

Customers may be directed to relevant documentation where it adequately addresses the issue.

110. Self-Service Tools

Certain actions may be designed for Customer self-service through the Hostwover dashboard.

These may include:

  • password resets.
  • DNS changes.
  • renewals.
  • server actions.
  • billing settings.
  • account preferences; or
  • service configuration.

Support may direct the Customer to use the relevant self-service function.

111. Experimental or Beta Features

Support for experimental, preview, beta, or early-access functionality may be limited.

Such functionality may change without the same support commitments applicable to generally available Services.

112. Unsupported Requests

Hostwover may decline requests that would require Hostwover to:

  • violate applicable law.
  • violate a provider agreement.
  • bypass security controls.
  • access another Customer's information.
  • perform unauthorized system access.
  • disclose confidential information.
  • circumvent licensing restrictions.
  • assist abuse; or
  • perform an action outside Hostwover's technical authority.

113. Legal Advice

Customer service does not provide legal advice.

Support personnel may explain Hostwover policies and product procedures but cannot provide professional legal advice concerning a Customer's individual circumstances.

114. Tax Advice

Hostwover support may explain taxes charged on a Hostwover order.

Hostwover does not provide tax advice regarding a Customer's independent tax obligations.

115. Financial Advice

Customer service does not provide financial or investment advice.

116. Compliance Advice

Hostwover may provide information about Service features or available documentation.

Customers remain responsible for determining whether a Service satisfies their specific:

  • regulatory.
  • privacy.
  • security.
  • industry.
  • contractual; or
  • compliance requirements.

117. Support Quality

Hostwover may review support interactions for:

  • quality assurance.
  • technical accuracy.
  • security.
  • training.
  • process improvement; and
  • Customer experience.

118. Feedback

Hostwover may invite Customers to provide feedback about support experiences.

Feedback may be used to improve:

  • documentation.
  • products.
  • support workflows.
  • training; and
  • customer-service quality.

119. No Guarantee of Requested Outcome

Hostwover will consider reasonable Customer requests but cannot guarantee that the specific outcome requested by the Customer will always be technically, contractually, legally, or commercially available.

120. Good-Faith Troubleshooting

Hostwover may recommend troubleshooting steps based on the information reasonably available at the time.

Technical troubleshooting can involve uncertainty, and a suggested step does not guarantee resolution.

121. Changes to Services

Support may provide information concerning current Hostwover features.

Services, interfaces, providers, and functionality may change over time in accordance with applicable agreements.

122. Support During Suspension

A Customer whose Service is suspended may still contact Hostwover regarding:

  • billing.
  • account verification.
  • remediation.
  • abuse.
  • restoration requirements; or
  • another appropriate administrative matter.

Suspension does not guarantee that every Service feature remains accessible.

123. Abuse Cases

Reports of prohibited activity are handled primarily under the Hostwover Abuse Handling Policy and Acceptable Use Policy rather than as ordinary Customer-service tickets.

Support may route such cases to the appropriate abuse or security process.

124. Security Incidents

Security incidents may be handled separately from ordinary technical support due to their sensitivity and urgency.

Hostwover may restrict the information disclosed while an investigation is active.

125. Privacy Requests

Formal requests involving privacy rights may be handled under the Hostwover Privacy Policy and applicable privacy procedures.

Ordinary customer-support personnel may route such requests to the appropriate process.

126. Domain Ownership Disputes

Customer support does not decide complex disputes concerning legal ownership of a domain.

Such disputes may need to be handled through:

  • the sponsoring registrar.
  • registry procedures.
  • UDRP or another applicable domain dispute process.
  • court proceedings; or
  • another legally recognized process.

127. Intellectual Property Disputes

Support personnel do not ordinarily adjudicate complex copyright or trademark disputes.

Such matters may be routed through the applicable abuse, legal, or provider process.

128. Provider Outages

When an upstream provider experiences an outage, Hostwover may:

  • investigate.
  • confirm the impact.
  • communicate available information.
  • escalate where appropriate; and
  • monitor restoration.

Hostwover cannot directly repair infrastructure controlled entirely by another provider.

129. Force Majeure

Customer-support availability or response may be affected by events beyond Hostwover's reasonable control, including:

  • telecommunications outages.
  • internet outages.
  • provider failures.
  • major cyberattacks.
  • natural disasters.
  • governmental actions.
  • power failures.
  • war.
  • civil disturbance; or
  • similar events.

130. No Modification of Contract by Informal Support

Unless expressly authorized, an informal statement by a support representative does not modify:

  • the Terms of Service.
  • product agreements.
  • pricing commitments.
  • refund rules.
  • Service Level Agreements; or
  • other contractual terms.

Contract modifications must follow an authorized Hostwover process.

131. Pricing Quotes

A support representative may provide pricing information based on information available at the time.

The price displayed and confirmed through the applicable order or checkout process controls unless Hostwover expressly agrees otherwise.

132. Promotional Offers

Support representatives cannot guarantee expired or unavailable promotions unless Hostwover expressly authorizes the offer.

133. Security Verification Cannot Be Waived Informally

A Customer cannot require a support representative to bypass required security verification merely because the Customer claims urgency.

134. Customer Satisfaction and Technical Outcome

Hostwover seeks to provide a positive Customer experience.

However, Customer dissatisfaction alone does not establish that:

  • Hostwover breached an agreement.
  • a refund is required.
  • an SLA was violated; or
  • a Service was defective.

Such questions are determined under the applicable agreement and law.

135. Customer Service and SLA Distinction

This Customer Service Policy describes support practices.

It does not, by itself, create a guaranteed:

  • response time.
  • resolution time.
  • uptime percentage.
  • compensation entitlement; or
  • service credit.

Any such guarantee must be expressly stated in an applicable Hostwover SLA, product agreement, or order.

136. Changes to This Policy

Hostwover may update this Policy to reflect:

  • new Services.
  • new support channels.
  • changes in operating procedures.
  • provider changes.
  • security requirements.
  • customer-service improvements.
  • legal requirements; or
  • changes in support capabilities.

The Last Updated date identifies the most recent version.

137. Material Changes

Where required by applicable law, Hostwover may provide notice of material changes to this Policy.

138. Continued Use

Continued use of Hostwover Services after an updated version of this Policy becomes effective constitutes acceptance of the updated Policy to the extent permitted by applicable law where this Policy forms part of the applicable contractual framework.

139. Relationship With Product Agreements

Product-specific agreements may define additional or different support responsibilities.

Where a product-specific agreement expressly conflicts with this general Policy, the more specific product provision will govern that Service to the extent of the conflict.

140. Relationship With Terms of Service

This Customer Service Policy forms part of Hostwover's customer-service and operational framework.

Where incorporated into or referenced by the Hostwover Terms of Service, it applies together with those Terms.

141. Relationship With Third-Party Terms

Third-party products supplied through Hostwover may be subject to the support processes and limitations of their underlying providers.

Hostwover cannot grant support rights exceeding those technically or contractually available through the applicable provider.

142. Severability

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

143. No Waiver

Hostwover's failure to enforce a provision of this Policy in one instance does not waive its right to enforce that provision in another instance.

144. Language

Hostwover may provide translations of this Policy.

Where permitted by applicable law and unless Hostwover expressly states otherwise, the English version will control in the event of a material inconsistency between translations.

145. Definitions

For purposes of this Policy:

"Customer" means a person or entity purchasing, controlling, administering, or using a Hostwover Service.

"Customer Support" means assistance provided by Hostwover concerning accounts, billing, provisioning, configuration, technical matters, or other Service-related matters.

"Resolution" means the point at which a support matter has been corrected, appropriately addressed, referred to the responsible provider, or otherwise reasonably concluded.

"Service" means a domain, hosting plan, server, email product, Google Workspace subscription, API, AI functionality, account feature, or other product or service supplied through Hostwover.

"Support Request" means a request submitted to Hostwover for Customer Service or technical assistance.

"Upstream Provider" means a registrar, registry, hosting provider, infrastructure provider, cloud provider, data center, email provider, software provider, payment provider, distributor, or another third party involved in supplying a Hostwover Service.

146. Customer Service Principles

Hostwover's customer-service process is guided by the following principles:

  1. Customers should be treated professionally and respectfully.
  2. security and account ownership should be verified where necessary.
  3. critical Service issues should receive appropriate priority.
  4. technical information should be communicated as accurately as reasonably possible.
  5. Customers should be told when an issue depends on an external provider.
  6. support should not make promises outside Hostwover's technical or contractual authority.
  7. Customers should reasonably cooperate with troubleshooting.
  8. sensitive credentials should be protected.
  9. tickets should be escalated when specialized assistance is reasonably required.
  10. support should distinguish initial response from final resolution.
  11. Customers should not be promised fixed resolution times unless expressly covered by an SLA; and
  12. Hostwover should make commercially reasonable efforts to assist Customers within the scope of their purchased Service.

147. Contact

For Customer Service:

Hostwover Support

Email: [email protected]

Website: hostwover.com

When contacting support, include the relevant:

  • domain.
  • Service.
  • order.
  • invoice.
  • server.
  • subscription; or
  • ticket reference

where appropriate.

Do not include passwords, private keys, full payment-card numbers, or unnecessary security credentials in ordinary support communications.

148. Effective Date

This Customer Service Policy becomes effective on the date stated above and applies to Hostwover Customer Service interactions and Services that reference or incorporate this Policy.

END OF CUSTOMER SERVICE POLICY