Your project. Reusable building blocks.
Builder saves your code and project memory privately. You can use and export licensed Vibed components in your projects. Sharing eligible new helpers with other creators is optional and separate from publishing.
Version 2026-11-07-builder-reuse-1 · Effective November 7, 2026
Your rights and Vibed components
You retain any ownership rights you hold in your projects and materials. Vibed grants you a non-exclusive, worldwide, royalty-free license to use, modify and distribute Vibed-provided Builder components within your own projects, including commercial projects and source exports. This does not license Vibed branding or unrelated platform source code.
Optional sharing permission
Sharing reusable helpers is optional and separate from publishing. If you explicitly enable sharing for a project, you grant RRG Figueroa, LLC a non-exclusive, worldwide, royalty-free license to store, reproduce, test, modify, combine, distribute and sublicense eligible reusable functional components newly generated while sharing is enabled, within Vibed services and other Builder projects. You confirm you have the rights needed for this permission and will not include confidential or unauthorized third-party material in a contribution.
Eligible code and exclusions
Eligible contributions are separately identified, bounded functional components that pass the supported provenance and automated checks. A generated project is not automatically a shared component. Existing private versions, source borrowed from another project, uploaded or pre-existing proprietary code, personal or customer data, credentials, confidential business information, brand identity and media assets are excluded unless separately authorized. Third-party material remains subject to its own licenses.
Non-exclusive components and stopping sharing
Shared components are non-exclusive. Other creators may use them in different projects and may export the licensed components with those projects. Turning off sharing stops new contributions; components already distributed under this license remain usable and licensed if the originating project is removed. Keeping a project private does not undo a separate component license you have granted.
Private memory and provider processing
Private project memory, source, build history and notes remain account-scoped unless you publish a version or separately authorize a permitted contribution. Sharing a helper does not publish your project or customer data. This permission does not itself authorize third-party AI model training. Builder requests and relevant private context are processed by the configured build provider as described in the Privacy Policy.
Review and limitations
Copyright protection and ownership depend on applicable law and any human contribution; model generation alone is not proof of ownership or clearance. Automated checks do not guarantee that code is error-free, secure or free of third-party claims. You remain responsible for reviewing your project before use or publication.
What can be shared today?
The initial shared library admits only small, self-contained clamp,interpolation and distance helpers with supported provenance and automated function checks. Whole apps, unknown dependencies, existing private source and media assets are excluded. Passing checks is evidence about tested behavior, not a legal-clearance guarantee.
Enable sharing before the first build of a new empty project.Projects using a private reference cannot contribute helpers. A new private source version breaks sharing eligibility until you start a new eligible project. You can still use Builder, private memory, components and marketplace publishing without contributing.
