Visual Copilot is an AI-powered design tool that assists teams in creating visual content by generating graphics, layouts, and design suggestions, streamlining the creative process.
Visual Copilot is an AI-powered design-to-code platform that transforms Figma designs into production-ready, interactive code, streamlining the workflow from concept to deployment while preserving custom components, styles, and business logic.[1][2][3][4] Key features include automatic component mapping via AI semantic matching, seamless integration with codebases like Next.js and Remix, natural language generation of interactivity for buttons, forms, and links, and one-click syncing of design updates to code without manual reconciliation.[1][2][4][5]
It targets design and development teams, enabling designers to export responsive components directly and developers to iterate rapidly within their tech stack, ideal for collaborative projects requiring pixel-perfect consistency and real API integration.[3][6] What sets Visual Copilot apart is its deep contextual understanding of design systems, existing code patterns, and enterprise CMS capabilities through Builder's Fusion platform, eliminating generic AI outputs and reducing development time by automating reuse and enforcement of brand standards.[3][4][5][6]
Sources
The documents reference AI Terms at https://builder.io/docs/ai-terms but do not provide the full text. The ToS mentions
No training opt-out mechanism was identified in the legal documents.
Moderate risk. Suitable for internal data but avoid confidential information.
The documents reference AI Terms at https://builder.io/docs/ai-terms but do not provide the full text. The ToS mentions Usage Data can be created for 'improving and enhancing the Services' but lacks explicit clarity on whether user content trains AI models. This vague language warrants a moderate concern score.
“[ToS] 'Builder may create aggregated, anonymized data based on Customer Data...for the purpose of improving and enhancing the Services.'”
Customer grants Builder a 'worldwide, royalty-free, fully-paid up, non-exclusive, transferable, sublicensable license' to use Customer Data during the Service Term. The sublicensing right and broad scope create moderate concern, though the license is limited to providing the Services.
“[ToS] 'Customer hereby grants Builder and its licensors and suppliers a worldwide, royalty-free, fully-paid up, non-exclusive, transferable, sublicensable license to use the Customer Data during the Service Term to process the Customer Data for the purpose of providing the Services.'”
The Privacy Policy mentions sharing with 'service providers,' 'affiliated companies,' and 'partners' with some controls, but lacks a comprehensive sub-processor list. Service providers are stated to be prohibited from using data for other purposes, but the definition of 'partners' is vague.
“[Privacy] 'We disclose your personal information to...Services providers...Partners...Unless otherwise expressly noted, when acting as Builder's service providers, these services providers are prohibited from using the personal information we have disclosed to them for purposes other than those requested by us.'”
The Privacy Policy states retention is based on 'nature of the information' and 'purposes outlined' but lacks specific retention periods. The ToS specifies 30 days for Customer Data retrieval post-termination, but long-term retention policies are vague.
“[Privacy] 'In general, we will retain your personal information for the length of time reasonably needed to fulfill the purposes outlined in this privacy policy...unless a longer retention period is required or permitted by law.' [ToS] 'Builder will make all Customer Data available to Customer for Customer's electronic retrieval for a period of thirty (30) days, but thereafter Builder may, but is not obligated to...delete stored Customer Data.'”
The ToS explicitly states that 'Customer owns and retains all right, title and interest in and to Customer Data' with no restrictions on commercial use. Builder claims no ownership rights over Customer Data or generated outputs.
“[ToS] 'Customer owns and retains all right, title and interest in and to Customer Data and its digital properties, including all related intellectual property rights therein. Customer reserves all rights in and to the foregoing.'”
The documents reference European data processing addenda (EDPA and USDPA) and mention compliance with data protection laws, but no specific certifications (SOC 2, ISO 27001, HIPAA) are explicitly stated. Security measures are mentioned as 'administrative, technical, and organizational' but lack formal certification documentation.
“[Privacy] 'We have implemented administrative, technical, and organizational security measures that are designed to help protect your information.' [ToS] 'the parties will comply with their respective obligations set forth in the European data processing addendum located at www.builder.io/docs/EDPA and the U.S. data processing addendum located at www.builder.io/docs/USDPA.'”
Track and measure your AI tools with Olakai's observability platform.
Explore Olakai