Effective date: May 2026
Last updated: May 2026
This page describes support channels, response expectations, maintenance notices, and service limitations.
Use the support or account contact information available in the service. BuildPod may provide different support paths by plan, agreement, or rollout stage.
Billing questions, cancellation questions, and refund or account-credit requests are reviewed through support or billing contact paths.
BuildPod aims to respond reasonably. Response times may vary by plan, severity, business hours, and support channel. No guaranteed response time applies unless a separate written SLA applies.
P0 means app unavailable, security incident, data-loss concern, or cross-tenant exposure risk. P1 means a critical workflow is blocked. P2 means an important workflow is degraded. P3 means visual, copy, minor usability, or noncritical behavior.
Severity assessment may consider plan, customer impact, reproducibility, security impact, data integrity, and available workaround.
BuildPod aims to provide reliable service. No specific uptime guarantee applies unless a separate SLA applies.
BuildPod will provide planned maintenance notice when practical. Emergency maintenance may occur without advance notice to protect reliability, security, or data integrity.
Support and service expectations may not cover third-party outages, customer network/device/browser issues, misuse, unsupported integrations, force majeure, or customer data entry mistakes.
Report suspected security issues through the support or contact path. Do not publicly disclose vulnerabilities before coordinated review.