Beta / Early Access Terms

This page applies to beta, pilot, preview, experimental, and early-access features or programs.

Beta features may be incomplete, changed, removed, contain errors, or have limited support. Beta features may receive lower support priority than generally available production functionality unless a written agreement says otherwise.

Beta access may be invite-only. If an offer states that the beta timer starts when an account is created, the beta period begins when the invited user completes account creation.

Do not rely on beta features for production-critical, safety-critical, legal, financial, or customer-facing commitments unless separately agreed. Validate outputs and workflows before relying on them.

If customer relies on beta workflows during a pilot or early-access rollout, customer should report material bugs, incorrect behavior, and operational blockers promptly.

Customer may provide feedback. BuildPod may use feedback to improve the service without obligation unless separately agreed.

Data remains governed by the Privacy Policy and Data & Processing policy. Beta features may create logs and diagnostics. In non-production beta or preview environments, beta data may be reset, changed, limited, or removed as part of testing, support, or release preparation.

Beta access may expire after the stated access period. Beta access does not auto-charge unless the customer separately converts to a paid subscription with explicit confirmation. A saved payment method, if requested later, does not authorize automatic beta-to-paid conversion by itself.

Providing a payment method during beta does not authorize BuildPod to charge you automatically. Paid access begins only after you explicitly confirm conversion to a paid subscription.

Trial offers may have different terms. A trial may auto-convert only when separate explicit auto-billing consent is requested and recorded. Continued use after beta or trial expiration may require a paid subscription.

BuildPod may end beta access, change beta feature access, or revoke beta participation at any time, including for safety, security, reliability, misuse, support burden, or product-readiness reasons.

Expiration does not intentionally delete workspace data. Access may be limited after expiration until the customer renews, converts, or otherwise resolves the access state.