Last Updated: January 05, 2026
These Terms of Service govern the standard WordPress Health managed WordPress hosting, maintenance, security, monitoring, backup, support, optimization, migration, and related services.
1. Acceptance and Scope
These Terms of Service (“Terms”) govern access to and use of the WordPress hosting, maintenance, security, monitoring, backup, support, optimization, migration, and related services offered under the WordPress Health brand (“WordPress Health,” “we,” “us,” or “our”).
WordPress Health is operated by the legal entity identified on your Order, invoice, or account records (the “Provider”).
These Terms form a legally binding agreement between the Provider and the individual or entity purchasing, receiving, accessing, renewing, or using the Services (“Customer,” “you,” or “your”). By purchasing, receiving, accessing, renewing, or using the Services, you agree to these Terms.
If you accept these Terms on behalf of a company or other organization, you represent that you have authority to bind that organization.
2. Agreement Structure
Your agreement with WordPress Health may include these Terms, the service plan or Order applicable to your account, an applicable Service Level Agreement (SLA), Business Associate Agreement (BAA), Data Processing Addendum (DPA), Privacy Policy, Acceptable Use Policy, and any mutually executed Order Form, proposal, or service-specific addendum.
If there is a conflict, the following order of precedence applies unless a document expressly states otherwise:
An executed BAA, but only with respect to PHI and HIPAA obligations.
A mutually executed Order Form, SOW, or service-specific addendum.
An applicable DPA.
These Terms.
An applicable SLA.
Other incorporated policies and published service documentation.
A negotiated agreement applies only to the Customer and Services identified in that agreement and does not modify WordPress Health’s standard terms for other customers.
3. Description of Services
Depending on the plan or Order, WordPress Health Services may include:
Managed WordPress hosting.
WordPress core, plugin, theme, PHP, and related maintenance.
Malware scanning and malware remediation.
Security, file-integrity, uptime, and SSL monitoring.
Website backups and restoration assistance.
WAF, CDN, DDoS, bot, or rate-limiting protections where included in the hosting stack.
Staging environments and update testing.
Performance monitoring, caching, and optimization.
Content updates and routine site maintenance.
Migration assistance.
WordPress technical support.
Other services expressly included in the applicable plan or Order.
Features differ by plan. A feature is included only if it is identified in your purchased plan, Order, proposal, or written service description.
4. Managed Service; Not Unlimited Development
WordPress Health is a managed hosting, maintenance, security, and support service. Unless expressly included in your plan or Order, the Services do not include custom application development, complete redesigns, new website builds, major new functionality, extensive copywriting, custom graphic design, complex integrations, digital advertising management, full forensic cybersecurity investigations, legal or regulatory consulting, or work on systems unrelated to the managed WordPress website.
Work outside the plan may be separately quoted.
5. Unlimited Services and Fair Use
If a plan is described as “unlimited,” that means WordPress Health does not impose a predetermined numerical monthly limit on qualifying requests. It does not mean unlimited labor, unlimited simultaneous work, unlimited infrastructure usage, or unlimited development resources.
Qualifying routine requests may include replacing text, updating images, modifying existing page content, uploading Customer-supplied media, and similar maintenance tasks.
Unlimited services do not include major redesigns, extensive page creation, bulk data entry, large migrations, custom programming, custom graphics, video production, complex third-party integrations, or other projects that would ordinarily require a separate development engagement.
WordPress Health may reasonably schedule, prioritize, batch, or limit requests to prevent abuse and preserve service quality.
6. Customer Ownership
Customer retains ownership of Customer Content, including website content, Customer-provided code, trademarks, branding, media, databases, domain names, and other materials owned by Customer.
Customer grants WordPress Health and its authorized service providers a limited, non-exclusive right to access, copy, process, modify, transmit, back up, restore, and otherwise use Customer Content solely as reasonably necessary to provide, secure, maintain, support, migrate, troubleshoot, or improve the Services.
This license ends when no longer reasonably necessary to provide the Services, subject to backup-retention, legal, security, and regulatory requirements.
7. Customer Responsibilities
Maintain accurate account, billing, and authorized-contact information.
Use reasonable security practices, including unique credentials and multi-factor authentication where available.
Protect privileged credentials and not knowingly share them with unauthorized persons.
Ensure the legality, accuracy, and licensing of Customer Content.
Maintain appropriate privacy notices, terms, consents, and regulatory disclosures for Customer’s business.
Secure systems, devices, email accounts, DNS, registrar accounts, and third-party platforms outside WordPress Health’s control.
Notify WordPress Health promptly of known or suspected unauthorized access affecting the Services.
Not intentionally disable or circumvent security, backup, update, monitoring, access-control, or resource-protection mechanisms required to provide the Services.
8. WordPress, Plugin, Theme, PHP, and Software Maintenance
Customer authorizes WordPress Health to perform reasonable maintenance and updates within the scope of the selected plan. WordPress Health may delay an update when reasonably necessary to evaluate compatibility, stability, or security risks.
Where appropriate, WordPress Health may test material changes in staging or create a recovery point before updating production.
Third-party software may become abandoned, insecure, incompatible, unsupported, or unavailable. If WordPress Health reasonably determines that a component creates a material security or operational risk, it may disable, quarantine, replace, or recommend removal of that component. Where practicable, Customer will be notified.
Customer is responsible for third-party license fees unless the applicable plan or Order expressly states that a license is included.
9. Security Services
WordPress Health employs commercially reasonable measures intended to reduce security risk. Depending on the plan and infrastructure, these measures may include malware scanning, file-integrity monitoring, firewall/WAF controls, CDN/DDoS protections, restricted administrative access, authentication controls, vulnerability monitoring, software updates, malware remediation, backups, and uptime/security monitoring.
Security services reduce risk but cannot eliminate it. WordPress Health does not warrant that a website, server, network, plugin, application, account, or backup will be completely immune from attack, malware, compromise, unauthorized access, vulnerability, data loss, or service interruption.
10. Malware Cleanup
Where malware cleanup is included, WordPress Health will use commercially reasonable efforts to identify, quarantine, remove, or remediate malicious code affecting the managed WordPress website.
Remediation may include restoring a known recovery point, replacing compromised WordPress files, removing malicious database entries, disabling vulnerable components, recommending credential rotation, or other appropriate measures.
Malware cleanup is not a digital-forensics investigation. Unless separately agreed, it does not include investigation or remediation of Customer computers, employee devices, email systems, unrelated servers, payment systems, registrar compromise, or third-party SaaS platforms.
WordPress Health is not responsible for repeated reinfection to the extent caused by compromised credentials, Customer-controlled systems, unsupported software, unauthorized modifications, or vulnerabilities outside WordPress Health’s reasonable control.
11. Security Incidents and Emergency Protective Action
WordPress Health may take immediate protective action when it reasonably believes a site, account, plugin, user, workload, or configuration poses a material security or stability risk; contains malware; is actively compromised; attacks another system; violates law; exposes information; or materially threatens other customers or infrastructure.
Protective action may include restricting access, disabling a plugin, rotating or disabling credentials, blocking traffic, isolating or suspending a site, restoring a backup, disabling administrative access, quarantining files, or taking other reasonable actions.
Where practicable, WordPress Health will notify Customer. Emergency action taken in good faith to protect systems, data, customers, or third parties does not constitute a service breach.
12. Backups
Where backups are included, WordPress Health will create and retain backups according to the applicable plan or Order. Backup frequency and retention differ by plan. A plan or Order may provide weekly backups, daily backups, monthly retention, pre-update recovery points, off-site copies, or restoration testing.
WordPress Health will use commercially reasonable efforts to maintain usable backups, but no backup system can guarantee that every recovery point will be complete, uncorrupted, or restorable.
Customer should maintain an independent copy of business-critical information where appropriate. Where an Order includes restoration testing, WordPress Health will perform such testing at the intervals stated in the Order.
13. Website Restoration
Customer may request restoration to an available recovery point. Restoration may overwrite or remove changes made after the selected recovery point.
WordPress Health is not responsible for data intentionally or automatically overwritten through a Customer-authorized restore. Where a security incident is involved, WordPress Health may determine that restoration to an earlier clean recovery point is reasonably necessary.
14. Availability and Uptime
WordPress Health uses proactive monitoring and commercially reasonable efforts to maintain reliable service.
Any specific uptime commitment applies only where stated in an applicable SLA or Order. Unless an SLA expressly states otherwise, downtime calculations exclude scheduled maintenance, emergency maintenance, Customer code or configuration, plugin/theme failures, DNS/domain failures outside WordPress Health’s control, Customer actions, security or nonpayment suspension, third-party systems outside our reasonable control, upstream-provider failures, attacks beyond commercially reasonable mitigation, and Force Majeure events.
15. Support
Support requests must be submitted through approved WordPress Health support channels.
Where a plan advertises “24/7 WordPress Support,” eligible Customers may submit qualifying support requests at any time and applicable monitoring may operate continuously. This does not create a guaranteed response or resolution time unless an SLA or Order expressly provides one.
WordPress Health may prioritize support based on severity, security impact, plan level, and operational impact. Requests sent to personal email accounts, text messages, social media, or unofficial channels may not be monitored.
16. Third-Party Services and Subprocessors
WordPress Health may use third-party hosting platforms, data centers, CDNs, security providers, backup providers, monitoring systems, software vendors, payment processors, plugins, APIs, or other service providers to deliver the Services.
Customer acknowledges that portions of the Services depend on those providers. WordPress Health may replace a provider when reasonably necessary. WordPress Health is not responsible for failures caused solely by third parties outside its reasonable control, but will use commercially reasonable efforts to manage providers and assist with service-impacting issues.
Use of third-party software may be subject to the applicable provider’s license terms.
17. HIPAA and Protected Health Information
WordPress Health Services are not automatically HIPAA-eligible merely because a Customer purchases a hosting, maintenance, or security plan.
Customer may store, transmit, provide access to, or otherwise use the Services for Protected Health Information (PHI) only when all of the following apply:
WordPress Health has expressly approved the Customer for a HIPAA-eligible configuration.
WordPress Health and Customer have executed an appropriate Business Associate Agreement.
Customer uses only approved hosting, backup, monitoring, support, and related components for PHI.
Customer follows applicable configuration, access, security, data-residency, and operational requirements associated with the HIPAA-eligible service.
Unless those conditions are satisfied, Customer must not intentionally submit, store, or transmit PHI using the Services.
Where an executed BAA applies, the BAA controls with respect to PHI in the event of a conflict with these Terms. Customer remains responsible for determining whether HIPAA applies to Customer and for Customer’s own compliance obligations. WordPress Health does not provide legal advice.
18. Other Regulated Data
Unless expressly agreed in writing, WordPress Health does not represent that the standard Services independently satisfy Customer obligations under PCI DSS, GLBA, FERPA, CJIS, ITAR, export-controlled-data requirements, or other specialized regulatory frameworks.
Using WordPress Health does not itself make a Customer compliant with a regulatory standard.
19. Payment Card Data
Customers should use established third-party payment processors and should not intentionally store full payment-card data directly within WordPress unless expressly approved and appropriately configured. WordPress Health is not a payment processor. Customer is responsible for its own PCI obligations.
20. Acceptable Use
Customer may not use the Services to:
Violate applicable law or facilitate unlawful activity.
Infringe intellectual property, privacy, publicity, or other rights.
Distribute malware, ransomware, phishing tools, credential-harvesting systems, or malicious code.
Send spam or unsolicited bulk messaging.
Conduct unauthorized vulnerability scanning, exploitation, penetration testing, or attacks.
Operate command-and-control infrastructure, botnets, malicious proxies, or cryptocurrency-mining workloads.
Interfere with or degrade WordPress Health systems or the systems of others.
Host child sexual abuse material or content facilitating terrorism, trafficking, or other serious illegal conduct.
Circumvent access, security, resource, rate, or platform restrictions.
High-risk or heavily regulated uses may require prior written approval. WordPress Health may refuse or discontinue a use case it reasonably determines cannot be safely or lawfully supported.
21. Resource Usage
Hosting plans may have practical limits relating to storage, bandwidth, CPU, memory, database size, file counts, concurrent processes, traffic, backup storage, or other infrastructure resources.
A plan described as “unlimited” does not mean unlimited infrastructure consumption. If a workload materially degrades platform performance, threatens stability, or negatively affects other customers, WordPress Health may optimize or rate-limit the workload, require configuration changes, recommend or require a plan upgrade, restrict the resource-intensive functionality, or suspend the affected site where reasonably necessary.
WordPress Health will use reasonable efforts to provide notice before non-emergency action.
22. Customer Content and Legal Compliance
Customer represents that it has the rights and permissions necessary for Customer Content and that Customer’s use of the Services complies with applicable law.
WordPress Health has no obligation to proactively review Customer Content for legal compliance. It may remove, restrict, or disable content when reasonably necessary to comply with law, valid legal process, the Acceptable Use provisions, or a material security risk.
23. Domain Names, DNS, and SSL
Where domain registration, DNS, or SSL services are included or facilitated by WordPress Health, those services may be provided through third parties. Customer remains the beneficial owner of Customer domain names, subject to registrar rules and payment requirements.
WordPress Health does not guarantee continued availability of a particular domain name. Customer is responsible for keeping domain-registration information current.
24. Email Services
WordPress Health hosting does not include business-email hosting unless expressly stated in the applicable plan or Order. WordPress Health is not responsible for third-party mailbox security, spam filtering, or email delivery where those services are not provided by WordPress Health.
25. Migrations
Where migration is included, WordPress Health will use commercially reasonable efforts to migrate the agreed WordPress website. Migration may depend on access to the existing host, source-site condition, plugins, DNS, database size, third-party systems, and cooperation from other providers.
A migration does not guarantee that unsupported or incompatible functionality will operate identically after transfer.
26. Customer-Requested Changes
WordPress Health may act on instructions received from an authorized account contact. Customer is responsible for ensuring its authorized contacts have appropriate authority.
WordPress Health may request additional verification before performing high-risk changes such as DNS/domain modification, production restoration, deletion, creation of privileged users, release of backups, transfer of ownership, or security-control changes.
27. Fees and Billing
Fees are charged according to the selected plan or Order. Unless otherwise stated, subscriptions are billed in advance, applicable taxes are additional, Customer must maintain a valid payment method, and Customer authorizes WordPress Health or its payment processor to charge applicable subscription and renewal fees.
28. Automatic Renewal
Unless an Order states otherwise, recurring subscriptions automatically renew for the same billing period until canceled. Customer must cancel before the renewal date to avoid renewal.
WordPress Health will provide at least 30 days’ notice of a material increase in the recurring subscription price where reasonably practicable.
29. Nonpayment
If an invoice or subscription payment is overdue, WordPress Health may restrict support, suspend service, or ultimately terminate the affected account after reasonable notice.
WordPress Health may act immediately where a payment is reversed, fraudulent, disputed in bad faith, or associated with abuse. Customer remains responsible for fees incurred before termination.
30. 30-Day Money-Back Guarantee
Where advertised, a new Customer may request cancellation and a refund of eligible WordPress Health subscription fees within 30 days of the initial paid subscription date.
The guarantee applies only to the first qualifying subscription purchase unless expressly stated otherwise and does not apply to renewals, domain fees, software licenses, third-party charges, custom development, migrations or project work separately quoted, compliance services, usage fees, or Services terminated for abuse or violation of these Terms.
A Service provided at no additional charge or as part of a promotional or bundled package does not generate a cash refund.
31. Suspension
WordPress Health may temporarily suspend all or part of the Services where reasonably necessary because of a material security threat, malicious activity, nonpayment, unlawful use, abuse of resources, material violation of these Terms, unauthorized third-party access, legal or regulatory requirements, or circumstances creating a material risk to WordPress Health, Customer, other customers, or third parties.
Where appropriate, WordPress Health will use commercially reasonable efforts to notify Customer and restore Services after the issue is resolved.
32. Customer Cancellation
Customer may cancel a subscription through the designated account or support process. Unless a refund right expressly applies, cancellation takes effect at the end of the current paid term and previously paid fees are non-refundable.
Customer should request any necessary website export or migration assistance before termination becomes effective.
33. Termination by WordPress Health
WordPress Health may terminate Services for material breach not cured after reasonable notice; immediately for malicious or unlawful activity, serious security threats, fraud, or abuse; where continued service would violate law; where Customer materially threatens platform stability; or upon discontinuation of a Service.
If WordPress Health terminates a prepaid recurring Service solely for its convenience and Customer is not in breach, WordPress Health will provide a prorated refund of unused prepaid recurring hosting fees.
34. Data After Termination
Customer is responsible for exporting Customer Content before termination.
Unless law, an applicable BAA, or an Order requires a different period, WordPress Health may retain terminated-account backups for a limited operational period, generally no more than 30 days, and may permanently delete them thereafter. WordPress Health does not guarantee that terminated-account data will remain recoverable.
Where a BAA applies, return, destruction, and retention of PHI are governed by the BAA.
35. Portability
Customer is not required to remain with WordPress Health. Subject to payment of amounts properly due and reasonable security verification, Customer may migrate its WordPress website to another qualified provider.
WordPress Health will not intentionally lock a Customer website to the WordPress Health platform. Standard migration assistance may be included in the plan or separately quoted.
36. Service Changes
WordPress Health may improve, modify, replace, or discontinue features. It will use commercially reasonable efforts to provide advance notice of a material change that significantly reduces a paid recurring Service during an active prepaid term.
Security updates, emergency changes, legal-compliance changes, and third-party platform changes may be implemented without advance notice where reasonably necessary.
37. Changes to These Terms
WordPress Health may update these Terms from time to time. Material changes will become effective no earlier than 30 days after publication or notice, unless an earlier effective date is reasonably required by law, security, fraud prevention, or a third-party platform requirement.
Continued use after the effective date constitutes acceptance. If Customer does not agree with a material change, Customer may discontinue the affected Service before the change becomes effective, subject to any separately negotiated agreement.
38. WordPress Health Intellectual Property
WordPress Health retains all rights in its trademarks, branding, documentation, software, internal tools, methods, templates, workflows, monitoring systems, processes, and other proprietary materials.
“WordPress” is a trademark of the WordPress Foundation. WordPress Health is not the WordPress Foundation unless expressly stated otherwise.
39. Confidentiality
WordPress Health will use non-public Customer information only as reasonably necessary to provide the Services, operate its business, comply with law, prevent fraud or abuse, or as otherwise permitted by the Privacy Policy or an applicable agreement.
WordPress Health will use reasonable safeguards to protect credentials and other sensitive Customer information. Customer must likewise protect WordPress Health confidential or security-sensitive information provided to Customer.
40. Privacy
WordPress Health’s collection and use of personal information is governed by its separate Privacy Policy. An applicable BAA or DPA may impose additional requirements.
41. Warranty Disclaimer
EXCEPT FOR EXPRESS COMMITMENTS CONTAINED IN AN APPLICABLE SLA, ORDER, OR BAA, THE SERVICES ARE PROVIDED ON AN ‘AS IS’ AND ‘AS AVAILABLE’ BASIS TO THE MAXIMUM EXTENT PERMITTED BY LAW.
WORDPRESS HEALTH DOES NOT WARRANT THAT THE SERVICES WILL BE UNINTERRUPTED OR ERROR-FREE; THAT EVERY SECURITY THREAT WILL BE DETECTED OR PREVENTED; THAT EVERY BACKUP WILL BE FREE FROM CORRUPTION; THAT EVERY RESTORATION WILL SUCCEED; THAT ALL THIRD-PARTY SOFTWARE WILL REMAIN COMPATIBLE; THAT THE SERVICES WILL SATISFY EVERY CUSTOMER REQUIREMENT; OR THAT A WEBSITE WILL NEVER BE HACKED, COMPROMISED, SUSPENDED, OR UNAVAILABLE.
TO THE MAXIMUM EXTENT PERMITTED BY LAW, WORDPRESS HEALTH DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT.
42. Limitation of Liability
TO THE MAXIMUM EXTENT PERMITTED BY LAW, WORDPRESS HEALTH AND ITS OWNERS, OFFICERS, EMPLOYEES, CONTRACTORS, AFFILIATES, AND SERVICE PROVIDERS WILL NOT BE LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, PUNITIVE, OR CONSEQUENTIAL DAMAGES, LOSS OF PROFITS, LOSS OF REVENUE, LOSS OF GOODWILL, BUSINESS INTERRUPTION, OR LOSS OF DATA ARISING OUT OF OR RELATING TO THE SERVICES.
EXCEPT FOR LIABILITY THAT CANNOT LAWFULLY BE LIMITED AND EXCEPT AS EXPRESSLY PROVIDED IN AN APPLICABLE BAA OR NEGOTIATED WRITTEN AGREEMENT, WORDPRESS HEALTH’S TOTAL AGGREGATE MONETARY LIABILITY ARISING OUT OF OR RELATING TO THE AFFECTED SERVICE WILL NOT EXCEED THE GREATER OF (A) $500 OR (B) THE RECURRING FEES ACTUALLY PAID TO WORDPRESS HEALTH FOR THE AFFECTED SERVICE DURING THE SIX MONTHS IMMEDIATELY PRECEDING THE EVENT GIVING RISE TO THE CLAIM.
Multiple claims do not increase this limit. Any SLA service credit is Customer’s exclusive monetary remedy for an SLA failure unless otherwise expressly agreed.
43. Customer Indemnification
Customer will defend, indemnify, and hold harmless WordPress Health and its owners, officers, employees, affiliates, contractors, and service providers from third-party claims, liabilities, damages, fines, penalties, costs, and reasonable attorneys’ fees arising from Customer Content, Customer’s unlawful use of the Services, Customer’s infringement of third-party rights, Customer’s violation of these Terms, or Customer’s violation of applicable law.
WordPress Health will provide reasonable notice and cooperation. Customer may not settle a claim in a manner that admits liability by WordPress Health or imposes non-monetary obligations on WordPress Health without written approval.
44. Force Majeure
WordPress Health is not responsible for delays or failures caused by circumstances beyond its reasonable control, including natural disasters, war, terrorism, civil unrest, widespread internet or telecommunications outages, utility failures, labor disputes, governmental action, changes in law, upstream cloud or data-center outages, large-scale cyberattacks, DDoS attacks beyond commercially reasonable mitigation, domain-registry failures, or similar events.
45. Export Controls and Sanctions
Customer may not use the Services in violation of applicable U.S. sanctions, export-control laws, or trade restrictions. WordPress Health may deny, suspend, or terminate access where reasonably necessary to comply with those laws.
46. Legal Requests
WordPress Health may respond to subpoenas, warrants, court orders, regulatory demands, or other valid legal process. Where legally permitted and reasonably practicable, WordPress Health may notify Customer before disclosing Customer information.
Customer may be responsible for reasonable costs arising from unusually burdensome legal requests relating specifically to Customer where permitted by law.
47. Copyright / DMCA
WordPress Health may remove or restrict content in response to a valid copyright or intellectual-property complaint. Repeat infringement may result in account termination.
48. Assignment
Customer may not assign these Terms or transfer an account without WordPress Health’s prior written consent, except as part of a bona fide merger or sale of substantially all of Customer’s business where the successor agrees to these Terms.
WordPress Health may assign these Terms to an affiliate or successor in connection with a merger, restructuring, acquisition, or sale of substantially all relevant assets.
49. No Agency or Partnership
Nothing in these Terms creates a partnership, joint venture, employment, fiduciary, or agency relationship between Customer and WordPress Health.
50. Waiver and Severability
Failure to enforce a provision does not waive the right to enforce it later. If any provision is held unenforceable, the remaining provisions remain in effect and the invalid provision will be enforced to the maximum extent legally permitted.
51. Governing Law
Unless an Order or other written agreement states otherwise, these Terms are governed by the laws of the state in which the Provider’s principal place of business is located, without regard to conflict-of-law principles.
52. Dispute Resolution; Binding Arbitration
EXCEPT FOR ELIGIBLE SMALL-CLAIMS MATTERS AND REQUESTS FOR TEMPORARY OR INJUNCTIVE RELIEF RELATING TO INTELLECTUAL PROPERTY, UNAUTHORIZED SYSTEM ACCESS, SECURITY, FRAUD, OR MISUSE OF THE SERVICES, DISPUTES ARISING FROM THESE TERMS OR THE SERVICES WILL BE RESOLVED BY BINDING INDIVIDUAL ARBITRATION ADMINISTERED BY THE AMERICAN ARBITRATION ASSOCIATION UNDER ITS APPLICABLE COMMERCIAL RULES.
Unless the parties agree otherwise, arbitration will take place in the county and state of the Provider’s principal place of business or by remote proceeding. The arbitrator may award any individual remedy available under applicable law but may not consolidate claims of different customers without the parties’ consent.
53. Class Action and Jury-Trial Waiver
TO THE MAXIMUM EXTENT PERMITTED BY LAW, CUSTOMER AND WORDPRESS HEALTH AGREE THAT CLAIMS WILL BE BROUGHT ONLY IN AN INDIVIDUAL CAPACITY AND NOT AS A PLAINTIFF OR CLASS MEMBER IN A CLASS, COLLECTIVE, CONSOLIDATED, OR REPRESENTATIVE ACTION.
TO THE MAXIMUM EXTENT PERMITTED BY LAW, EACH PARTY WAIVES THE RIGHT TO A JURY TRIAL.
54. Electronic Communications
Customer consents to receive notices, invoices, account messages, security notices, and contractual communications electronically at the contact information associated with the account. Electronic acceptance of these Terms has the same effect as a physical signature to the extent permitted by law.
55. Notices
Operational and account notices may be sent to the primary account email.
Formal notices to WordPress Health may be sent using the legal contact information identified on the Customer’s Order, invoice, or account, or by email to help@wordpresshealth.com.
56. Entire Agreement
These Terms and all documents expressly incorporated into them constitute the agreement governing the standard WordPress Health Services. They supersede prior general representations regarding those Services except for a separately executed Order, SOW, BAA, DPA, SLA, or other written agreement that expressly modifies these Terms.
57. Contact
Questions regarding these Terms may be directed to help@wordpresshealth.com.