Vibe Construction Suite Beta Features Policy
- Version
- 1.0
- Effective Date
- August 2, 2026
- Last Updated
- August 2, 2026
See also the Terms of Service, Privacy Policy, Acceptable Use Policy, Data Retention & Account Deletion Policy, and Security Policy.
This Beta Features Policy ("Policy") establishes the terms that govern any preview, beta, early access, pilot, experimental, or pre-release functionality made available by Vibe Supply Products LLC ("Company," "we," "our," or "us") within the Vibe Construction Suite platform, including the Hub, all associated applications and modules, websites, and related services (collectively, the "Services").
This Policy applies to every individual or entity that accesses or uses such functionality, whether by invitation, self-enrollment, default availability, or otherwise ("Customer" or "you").
BETA FEATURES ARE EXPERIMENTAL AND ARE PROVIDED "AS IS" AND "AS AVAILABLE," WITHOUT WARRANTY OF ANY KIND. DO NOT RELY EXCLUSIVELY ON BETA FEATURES FOR CRITICAL BUSINESS OPERATIONS.
1. PURPOSE
The purpose of this Policy is to set clear expectations for functionality that has not yet reached general availability. Beta Features allow the Company to validate new capabilities with real construction workflows and allow Customers to preview functionality before it is finalized, in exchange for accepting that such functionality is unfinished.
This Policy is intended to be read before enabling or using any Beta Feature, so that Customers understand the risks, the level of support available, and the limits of the Company's obligations.
2. SCOPE AND RELATIONSHIP TO OTHER AGREEMENTS
This Policy applies to all current and future Beta Features across the Vibe Construction Suite, including features offered within the Hub and within any individual application or module.
This Policy is incorporated by reference into, and forms part of, the Vibe Construction Suite Terms of Service, and supplements the Privacy Policy, Subscription & Billing Policy, Refund Policy, Cookie Policy, Acceptable Use Policy, Data Retention & Account Deletion Policy, and Security Policy. Capitalized terms not defined here have the meanings given to them in the Terms of Service.
Where this Policy conflicts with another agreement with respect to Beta Features specifically, this Policy controls. In all other respects, the Terms of Service control. Any separate written beta or pilot agreement signed by the parties controls over this Policy to the extent of a direct conflict.
Beta Features involving artificial intelligence remain subject to the AI Features & Responsible Use Policy in addition to this Policy.
3. DEFINITION OF BETA FEATURES
"Beta Features" means any functionality, application, module, integration, report, tool, model, interface, or service made available by the Company that is identified or reasonably understood as preview, beta, early access, pilot, experimental, limited release, technology preview, sandbox, trial functionality, or otherwise pre-release or not generally available.
Beta Features may be labeled within the Services — for example with a Beta, Preview, or Early Access indicator — or may be described as such in release notes, in-product messaging, documentation, invitations, or other Company communications. The absence of a label does not convert pre-release functionality into a generally available feature where the Company has otherwise identified it as pre-release.
Beta Features are distinct from generally available production features and are not part of the committed feature set of any subscription plan.
4. AVAILABILITY
Beta Features are made available at the Company's sole discretion. They may be offered to all Customers, to a limited group, to specific companies, to specific roles or users, or to participants selected by the Company, and availability may vary by application, plan, region, or account.
Beta Features may be offered at no additional charge or as part of an existing subscription. Access to a Beta Feature at no charge does not entitle a Customer to continued access, to the feature at the same price upon general availability, or to any credit, discount, or refund if the feature changes or is withdrawn.
Beta Features may be subject to usage limits, capacity constraints, quotas, or reduced availability windows that do not apply to production features.
5. CUSTOMER PARTICIPATION
Participation in a Beta Feature is voluntary. By enabling, accessing, or using a Beta Feature, a Customer accepts this Policy and acknowledges the experimental nature of the functionality.
Where a Beta Feature is enabled at the company level, the company owner or administrator who enables it is responsible for that decision on behalf of the company and its users, including any effect on the company's data, workflows, or personnel. Customers should ensure that users who will encounter a Beta Feature are informed that it is pre-release.
Where a Beta Feature can be disabled, a Customer may stop participating at any time. Where a Beta Feature cannot be disabled by the Customer, the Customer may request removal from the beta by contacting the Company. Discontinuing participation may result in the loss of data, settings, or output created solely through the Beta Feature.
6. EXPECTED BEHAVIOR AND NO WARRANTY
Beta Features are experimental and are provided "AS IS" and "AS AVAILABLE," without warranties of any kind, whether express, implied, or statutory, including any implied warranties of merchantability, fitness for a particular purpose, accuracy, quality, availability, or non-infringement.
Beta Features may:
- contain bugs, defects, or errors;
- operate differently than production features;
- produce unexpected, incomplete, or inaccurate results;
- experience downtime, degraded performance, or interruption;
- change without notice; and
- be discontinued permanently.
No service level commitment, uptime target, performance standard, support response time, or roadmap commitment applies to Beta Features, whether stated elsewhere in the Company's agreements or in marketing materials.
7. KNOWN LIMITATIONS
Because Beta Features are unfinished, they commonly exhibit limitations that would not be acceptable in a production feature. These may include incomplete functionality, missing validation, absent or partial permission enforcement within the feature itself, limited or missing export capability, missing audit or activity records, incompatibility with other features, poor performance at scale, unfinished user interface elements, and untested behavior on some devices or browsers.
Documentation, help content, training material, and in-product guidance for Beta Features may be incomplete, out of date, or absent.
Customers should avoid relying exclusively upon Beta Features for critical business operations, including bidding, pricing, procurement, scheduling, contractual commitments, safety determinations, code compliance, or any decision with financial or legal consequence.
8. DATA INTEGRITY AND VERIFICATION
Customers remain responsible for independently verifying all information produced through Beta Features.
Quantities, measurements, takeoffs, estimates, pricing, reports, summaries, exports, and other output generated by a Beta Feature must be reviewed by a qualified person before being used, relied upon, transmitted to a third party, or incorporated into a bid, proposal, order, or contract.
Beta Features may create, modify, or delete data within a Customer's account. Data created solely by, or dependent upon, a Beta Feature may be lost, reset, migrated, or rendered unusable when the feature is changed, reverted, or withdrawn, and may not be recoverable. Customers should export and independently retain any Beta Feature output they need, consistent with the Data Retention & Account Deletion Policy.
Customers should not use Beta Features to process information they cannot afford to lose, or information subject to heightened confidentiality, regulatory, or contractual protection, unless expressly agreed in writing by the Company.
9. SUPPORT EXPECTATIONS
Beta Features are excluded from any standard support commitment. The Company may, at its discretion, provide informal assistance, respond to reports, or issue fixes, but is under no obligation to acknowledge, prioritize, diagnose, or resolve any issue arising from a Beta Feature.
Reports concerning Beta Features may be submitted through the in-product feedback and debug reporting tools where available, or by email. Reports are welcome and help shape the final feature, but submitting a report does not create an entitlement to a fix, a timeline, or a response.
10. FEATURE CHANGES
Beta Features are expected to change. The Company may add, alter, restrict, redesign, rename, reprice, re-scope, or replace a Beta Feature, its behavior, its data model, or its user interface at any time and without prior notice.
Changes may not be backward compatible and may affect data, settings, integrations, saved configurations, or workflows that depend on the prior behavior. Customers that build internal processes or external integrations around a Beta Feature do so at their own risk.
The Company makes no guarantee that Beta Features will become permanent production features.
Statements about possible future functionality, roadmaps, timelines, or general availability are informational only, are not commitments, and must not be relied upon in making a purchasing decision.
11. FEATURE REMOVAL
The Company may discontinue a Beta Feature permanently, in whole or in part, at any time. Where practicable, the Company will provide advance notice within the Services or by email, but notice is not guaranteed and may not be possible where removal is required for security, legal, licensing, cost, or technical reasons.
Removal of a Beta Feature does not entitle a Customer to a refund, credit, discount, extension, or substitute feature, and does not constitute a reduction in the Services purchased. Refunds and billing are governed by the Subscription & Billing Policy and the Refund Policy.
Data associated solely with a removed Beta Feature may be deleted. Customers should export anything they wish to keep before a Beta Feature is withdrawn.
12. FEEDBACK
Customers are encouraged to submit comments, suggestions, bug reports, feature requests, evaluations, usage observations, and other input regarding Beta Features ("Feedback").
Customer feedback submitted regarding Beta Features may be used by Vibe Supply Products LLC to improve the Services without compensation to the Customer.
By submitting Feedback, the Customer grants the Company a perpetual, irrevocable, worldwide, royalty-free, fully paid, sublicensable, and transferable license to use, reproduce, modify, adapt, publish, and otherwise exploit the Feedback for any purpose, including developing, improving, marketing, and commercializing the Services, without attribution, accounting, confidentiality obligation, or payment of any kind.
Customers should not submit as Feedback any confidential, proprietary, personal, or third-party information they do not wish the Company to use on these terms.
13. INTELLECTUAL PROPERTY
Participation in Beta programs does not transfer ownership of any software, feature, intellectual property, or future development.
All right, title, and interest in and to the Services, Beta Features, software, source code, models, designs, workflows, interfaces, documentation, branding, and all derivative works and improvements — including any developed in response to Customer Feedback — remain the exclusive property of Vibe Supply Products LLC and its licensors.
Access to a Beta Feature grants only a limited, revocable, non-exclusive, non-transferable right to use that feature during the beta period, subject to the Terms of Service and Acceptable Use Policy. No license, joint development interest, co-ownership, partnership, or right of first refusal is created by participation.
Customers retain ownership of their own project data as described in the Data Retention & Account Deletion Policy, including project data processed through a Beta Feature.
14. CONFIDENTIALITY
Where a Beta Feature is offered on a limited or invitation-only basis, or is designated as confidential, the feature itself and all related non-public information — including its existence, functionality, performance, screenshots, documentation, pricing, and roadmap — constitute the Company's confidential information.
Customers participating in such a program agree not to disclose that information to any third party, not to publish screenshots, recordings, benchmarks, or reviews, and not to use it for competitive analysis, without the Company's prior written consent. These obligations continue until the information becomes publicly available through no fault of the Customer.
Beta Features that are generally available to all Customers and not designated as confidential are not subject to this Section, though the restrictions in the Acceptable Use Policy continue to apply.
15. LIMITATION OF LIABILITY
TO THE MAXIMUM EXTENT PERMITTED BY LAW, THE COMPANY SHALL HAVE NO LIABILITY OF ANY KIND ARISING FROM OR RELATING TO BETA FEATURES.
This includes, without limitation, liability for lost profits, lost revenue, lost bids, lost business opportunity, cost of substitute services, rework, project delay, inaccurate quantities or estimates, corrupted, lost, or deleted data, downtime, or any indirect, incidental, special, consequential, exemplary, or punitive damages, whether based in contract, tort, negligence, strict liability, or any other theory, and whether or not the Company was advised of the possibility of such damages.
The Company may modify, suspend, remove, or restrict Beta Features, restrict beta participation, and terminate beta access at any time without liability. The limitations and disclaimers in the Terms of Service apply in full to Beta Features and are in addition to those in this Section. Where liability cannot be excluded as a matter of law, it is limited to the maximum extent permitted.
16. TERMINATION OF BETA ACCESS
The Company may terminate or restrict a Customer's or an individual user's access to any Beta Feature at any time, with or without cause and with or without notice, including where the Beta Feature is concluded, where participation criteria change, where capacity is limited, or where the Company believes access is being misused.
Termination of beta access does not affect the Customer's access to generally available features under its subscription, and does not entitle the Customer to any refund, credit, or extension.
Sections concerning Feedback, Intellectual Property, Confidentiality, and Limitation of Liability survive the termination of beta access.
17. POLICY UPDATES
The Company may revise this Policy from time to time to reflect changes in the Services, in beta program practices, or in applicable law. When material changes are made, the Company will publish the revised Policy with an updated version number and Last Updated date and, where appropriate, provide additional notice through the Services or by email.
Each published version of this Policy is retained as a distinct, versioned document. Revisions apply prospectively from the date they take effect. Continued use of a Beta Feature after a revision takes effect constitutes acceptance of the revised Policy.
18. CONTACT INFORMATION
Questions about this Policy, requests to join or leave a beta program, and reports concerning Beta Features should be directed to:
- Vibe Supply Products LLC
- Vibe Construction Suite
- Email: admin@vibeconstructionsuite.com
© Vibe Supply Products LLC. All rights reserved. Vibe Construction Suite is a product of Vibe Supply Products LLC.