Account and workspace information
Name, email address, organization membership, authentication identifiers, and app settings used to sign you in and keep hosted workspaces separated.
Privacy Policy
This policy explains how Builder.io collects, uses, shares, and retains data when it operates Agent-Native hosted applications, hosted apps, demos, and official browser extensions.
Last updated: June 23, 2026
Covered when Builder.io operates the Agent-Native service or hosted app for you.
Not covered for your use of the MIT-licensed source code itself.
Not covered for forks, customizations, or deployments operated by someone else.
Agent-Native is open source, and the source code is available under the MIT license. This policy applies only to hosted applications and services operated by Builder.io for Agent-Native users. It does not apply to someone else's use of the code, including forks, customized apps, private deployments, or self-hosted versions. If you operate your own deployment, you are responsible for your own data practices and privacy policy.
This policy is intended to supplement Builder.io's broader Privacy Policy for Agent-Native hosted application behavior.
Name, email address, organization membership, authentication identifiers, and app settings used to sign you in and keep hosted workspaces separated.
Content you create or upload in hosted Agent-Native apps, such as recordings, transcripts, documents, comments, tasks, prompts, agent responses, files, and configuration.
Data from services you choose to connect, such as calendar, Slack, email, storage, or developer tools, limited to the scopes and workflows shown in the hosted app.
Device, browser, IP address, diagnostic logs, page and feature usage, errors, and security events used to operate, secure, and improve hosted services.
The Agent-Native Clips Chrome extension helps you start browser-based recordings and, when enabled, attach browser diagnostics to a clip. It may collect the selected capture source, camera and microphone media you choose to include, the active tab title and URL, and authentication state needed to connect the extension to hosted Clips.
Developer logs are optional. When enabled, the extension may collect redacted console messages, JavaScript exceptions, and fetch/XHR metadata such as method, URL, status, timing, and failure details from the selected tab while a recording is active. The extension is not designed to collect request bodies, response bodies, cookies, or authorization headers.
For Chrome Web Store disclosures, use this section as the extension privacy-policy anchor: https://www.agent-native.com/privacy#clips-chrome-extension.
We do not sell Agent-Native hosted application data or use it for third-party advertising. We share data with service providers that help operate the hosted service, such as cloud infrastructure, storage, authentication, email, observability, AI, and transcription providers, when those services are needed for the feature you use.
When you connect an integration, the hosted app may send data to or receive data from that provider according to your configuration and the provider's own terms. We may also disclose information when required for security, abuse prevention, legal compliance, or to protect users and the service.
For the Agent-Native Clips Chrome extension, our use of information received from Chrome extension APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Browser activity collected by the extension is used to provide the user-facing recording and diagnostics workflow, not for advertising, resale, credit-worthiness, or unrelated profiling.
We retain hosted application data for as long as needed to provide the service, maintain workspace history, comply with obligations, resolve disputes, or improve reliability and security. Users can delete clips, documents, resources, and other hosted app content through the relevant application controls where available.
Deleted content may remain in backups, logs, or audit records for a limited period before it is removed according to operational retention schedules.
We use reasonable administrative, technical, and organizational safeguards designed to protect hosted application data, including access controls, transport encryption, monitoring, and operational security practices. No online service can guarantee perfect security, so users should avoid including secrets or sensitive information in recordings or prompts unless they intend to share that information with the hosted application.
We may update this policy as Agent-Native hosted applications change. The updated date at the top of the page shows when the policy was last revised.
For privacy requests or questions, contact Builder.io through the support and privacy channels listed in the Builder.io Privacy Policy.