Beta Features Policy

This Beta Features Policy applies to any feature SparrowHawk CRM LLC labels as “beta,” “preview,” “experimental,” “alpha,” “early access,” or otherwise identifies as not generally available. It supplements the Terms of Service.

Beta features are provided on an “as is” and “as available” basis. They may contain bugs, incomplete functionality, unstable data models, or performance issues. Warranties and remedies otherwise available in the Terms of Service do not apply to beta features to the extent permitted by law.

SparrowHawk CRM LLC may modify, restrict, reset, discontinue, or promote to general availability any beta feature at any time and without prior notice. Data created inside a beta feature may be reset before general availability if data-model changes require it. When practical, SparrowHawk CRM LLC will provide reasonable notice before a disruptive reset.

Availability, uptime, performance, and support commitments — whether from the Terms of Service, a signed order form, or Billing Terms — do not apply to beta features unless expressly stated in writing. Refund entitlements do not apply to beta features unless required by law.

Data submitted to beta features is handled according to the Privacy Policy and, where applicable, the Data Processing Addendum. Some beta features may transmit data to new subprocessors that will be added to the Subprocessor List when the feature moves toward general availability.

Customers who participate in beta programs are encouraged to provide feedback. SparrowHawk CRM LLC may use feedback without restriction, compensation, or attribution to improve the platform, subject to any confidentiality obligations the Customer marks on the feedback itself.

Beta features, their documentation, roadmap discussions, and screenshots may be confidential. Customers must not publicly disclose non-public beta features or their performance characteristics without written permission from SparrowHawk CRM LLC.

When a beta feature is discontinued, SparrowHawk CRM LLC will use reasonable efforts to allow export of associated Customer Data in a documented format where feasible. Where migration to a general-availability successor is offered, migration steps will be described in-product or in release notes.