Legal & Operational Boundaries
Terms of Service (Scope Isolation)
Operational governance, service boundaries, and liability constraints governing autonomous WordPress maintenance delivered by WPSmooth LLC.
Entity: WPSmooth LLC
Effective: September 2026
Model: Autonomous Managed Services (AMS)
Support: Asynchronous Only
🛡️
Scope Isolation Summary
WPSmooth LLC operates strictly as an autonomous maintenance, security, and edge-proxy provider. Operations require zero SSH or root server access. Front-end development, bespoke code creation, and SEO work are strictly excluded to maintain 100% operational velocity and reliability.
01
Service Scope & Execution Protocol
-
✓Included Operations: Autonomous daily backups streamed directly to Cloudflare R2, preventative edge security via custom WAF rules, APO caching, and API-triggered updates orchestrated via the WPSmooth Client App.
-
✗Excluded Operations: The service strictly prohibits and excludes front-end custom development, content creation, and SEO optimization from the operational scope.
-
ℹCommunication Protocol: All operational support and client communication is conducted on a strictly asynchronous basis.
02
Onboarding & Pre-Existing Technical Debt
-
•API Handshake Requirement: Target sites must successfully connect via the WPSmooth Client App and map to the Cloudflare proxy infrastructure.
-
•Tech Debt Remediation: If the initial API connection fails due to existing malware, structural database corruption, or critical incompatibilities, standard onboarding is immediately suspended.
-
•Remediation Protocol: The client is routed to a mandatory Custom Remediation Agreement, billed at a flat rate of $499, to restore the site to a deployable, zero-friction baseline.
03
Infrastructure & Agentic Intervention
-
•Zero-Friction Access: Operations function strictly through Cloudflare for SaaS proxy routing and the WPSmooth API Bridge, deliberately excluding any requirement for SSH or server root access.
-
•Autonomous Remediation: In the event of a catastrophic update, a custom MU-plugin drop-in (
fatal-error-handler.php) automatically intercepts PHP fatal errors (WSOD), deactivates the offending plugin, and triggers an autonomous Cloudflare R2 backup rollback via the API.
04
Limitation of Liability & Financial Caps
-
•Liability Constraint: Due to the autonomous nature of the API-driven remediation, WPSmooth LLC's maximum aggregate financial liability for any anomalous downtime, data loss, or service interruption is strictly capped at one month of the client's current service fees.
-
•Indirect Damages: Complete exclusion of liability for indirect, consequential, or special damages, including lost revenue, lost profit, or business interruption.
05
Termination & Offboarding Procedures
-
•Notice Period: A 30-day advance notice is required for the termination of the service agreement.
-
•Offboarding Protocol: Upon termination, WPSmooth LLC will execute the severing of the WPSmooth Client App API connection and purge the Cloudflare proxy routing (CNAME/A-record mapping), returning standard routing control to the client.
Questions regarding our Terms or Scope Isolation?
Speak with our engineering team to review infrastructure compatibility before onboarding.