This Privacy Policy explains how Blender Bridge ("we", "us", or "our") handles information when you use our website, browser extension, desktop companion app, Blender add-on, or MCP server (collectively, the "Service"). "Handle" includes processing or storing information locally on your device as well as transmitting information to another service.
The Blender Bridge browser extension has one purpose: connect a browser-based AI chat selected by the user to Blender running on the same computer. It recognizes a structured Blender command in the conversation, routes it through the paired local Blender Bridge companion app, and returns execution results and optional scene previews to the same conversation.
On a fresh browser profile, before account access or page integration, the extension displays this disclosure in the selected interface language: Blender Bridge reads the selected AI-chat page content, URL, and controls to detect structured Blender commands and return results. It stores settings, configured sites, bounded history, and reliability diagnostics locally. Clipboard access is used only when you explicitly choose Paste or Copy; display geometry is used only to size previews. Sign-in, account, and subscription status are checked by the Blender Bridge account service over HTTPS. In the normal workflow, commands, results, and previews move between the current tab and your paired local app; external sharing happens only when you explicitly choose Share. Data is never sold or used for advertising.
The disclosure links to this Privacy Policy. Until the user affirmatively clicks I agree — continue, page scanning, Universal Auto Setup, Run actions, and Blender Bridge page entry points remain inactive.
The extension treats structured Blender Python as command data and routes it only to the paired local Blender Bridge and Blender runtime. It does not execute Blender Python inside Chrome or load that command as Chrome extension code. The command workflow is designed for user-requested Blender scene and production operations.
The extension handles the email address, display name, account identifier, access and refresh session tokens, signed entitlement and execution-lease data, and the local Pairing Key required to connect the browser, companion app, and Blender add-on. Payment-card, bank-account, and crypto-wallet credentials are not handled by the extension.
To provide its visible features, the extension processes the selected page's hostname and URL, relevant page structure and short UI descriptors, model response, structured Blender command, chat composer, attachment state, send controls, and the destination where a Blender result should be returned. This processing occurs in the browser tab. Blender Bridge does not use it to build a general browsing profile.
Structured Blender commands, operation metadata, scene state, execution status, logs, Undo metadata, and user-requested viewport previews are transmitted between the extension and the companion app on the same computer. The extension may insert the result and preview into the same AI conversation selected by the user.
The extension reads the clipboard only after the user clicks Paste & Save in the Pairing Key settings. It writes to the clipboard when the user chooses a Copy or sharing action, and as a visible fallback if a user-requested Blender result cannot be inserted or sent by the configured chat interface. Clipboard contents are not continuously monitored or uploaded to Blender Bridge account servers.
When preparing a Blender scene preview or social-share image at the correct physical pixel dimensions, the extension can process display identifiers and names, primary-display status, scale, display/work-area geometry, and current browser-window geometry. This metadata is used by the extension and paired local Bridge for image sizing. The extension does not capture desktop screen pixels and does not upload this metadata to Blender Bridge account servers.
Blender Bridge keeps bounded local reliability records for Universal Auto Setup and the configured attachment, text, and send pipeline. A record may contain a timestamp, hostname, workflow event and outcome, and a bounded descriptor of a nearby UI element, such as its tag, selected class or test identifier, ARIA label, short visible-text excerpt, and size. These records support reliable operation as AI-chat interfaces change. They are not advertising analytics, behavioral profiling, or automatically uploaded telemetry.
bb_privacy_consent_v1) until extension storage is cleared or the extension is removed. A material change to the disclosed practices requires a new versioned consent record.Reliability diagnostics leave the browser only if the user explicitly copies or exports a report and chooses to share it. Removing the extension normally removes its extension-local data under Chrome's storage lifecycle. Information already delivered to a user-selected AI or sharing destination is retained according to that destination's policy.
The current browser extension contains no advertising or analytics SDK. Local Desktop, Bridge, Blender add-on, and MCP operational logs remain on the user's device unless the user explicitly provides them for support.
We do not sell personal data. We share information only as described below:
We do not transfer user data to advertising platforms, data brokers, or information resellers, and we do not use it for personalized advertising, creditworthiness, or lending.
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Extension user data is used only to provide or improve Blender Bridge's disclosed single purpose. Humans do not read extension user data except when the user gives explicit consent for a specific support case, when necessary for security or abuse investigation, to comply with law, or where permitted in aggregated and anonymized form for internal operations.
If you are in the European Economic Area, we rely on:
Blender Bridge uses HTTPS for account-service communications, signed entitlement and execution-lease verification, local Pairing Key checks, extension Content Security Policy, bounded local storage, and packaged Manifest V3 code. The extension-to-native workflow uses a loopback connection on the same computer. No security measure can eliminate every risk, and users should protect access to their browser profile, account, computer, Blender files, and Pairing Key.
Blender Bridge web and account pages use essential session/authentication cookies where needed for the Service to function. We do not use advertising or third-party tracking cookies in the browser extension. Cookies used by a user-selected AI or sharing site are controlled by that site.
We retain account data while an account is active. Following a valid account-deletion request, we delete or anonymize personal data within 30 days unless a longer period is required by law; financial records may be retained for up to seven years where legally required. Security and operational records are kept only for the period reasonably necessary for their stated purpose and legal obligations.
Depending on applicable law, you may have the right to:
Extension settings and site configurations can be changed or removed from the extension UI; signing out clears the active account session through its lifecycle; the Pairing Key can be replaced or cleared; and uninstalling the extension removes its extension-local storage under Chrome's lifecycle. To exercise account-level rights, contact blenderbridgemcp@gmail.com.
The applicable global Blender Bridge account service is hosted in Amsterdam, the Netherlands. If information is transferred across borders, we use the safeguards required by applicable data-protection law.
The Service is not directed to children under 16, and we do not knowingly collect personal data from children under 16.
We may update this policy when the Service or its data practices change. We will post the updated policy on this page with a new effective date and provide additional notice or request renewed consent where required.
For privacy questions or requests:
blenderbridgemcp@gmail.com