Analytics allowed. Analytics declined. No choice saved.
Your choice applies to our website analytics. Active external services are listed below.
Google Analytics 4 (Google)
Яндекс Метрика (Yandex)
Webvisor (Yandex)
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.
We apply the data protection rules applicable to you, including the GDPR where it applies. The basis depends on the purpose:
Blender Bridge uses HTTPS for account-service communications, verifies signed access data before granting entitlement, and keeps local storage bounded. No security measure can eliminate every risk, and users should protect access to their browser profile, account, computer and Blender files.
Account pages use cookies for sign-in, form security, connecting devices, and remembering the language and account region. Access cookies last 15 minutes; sign-in renewal cookies last 30 days. Temporary security and navigation cookies last from 10 minutes to 24 hours, depending on their purpose. Language, region and browser-identifier cookies last up to one year. The website stores its language in local storage until it is changed or browser data is cleared, and its sound preference in tab session storage. The extension uses no advertising or tracking cookies. Cookies on an AI or sharing site you choose are governed by that site.
With your permission, we analyse website use to improve it and measure which sources lead to registration, a trial or a purchase. Our own analytics is stored on our regional servers: .ru in Russia, .com in the Netherlands. We do not sell these records or use them for personalised advertising.
Our own analytics: After consent, we record a random browser identifier, visits, referral host and campaign labels, language, country derived from IP, window size, device category, viewed sections and button actions. Diagnostics include browser family, graphics adapter, loading time, frame-rate band and site version. IP is not stored in our analytics tables. Forms, conversations, code and scene contents are not collected. Registration and payment facts may be linked to the browser identifier.
Without consent, this analytics and external counters stay off. Separate server totals count public-page requests and response errors by day, without visitor identifiers, IP, referral addresses or precise request times. Requests include bots and reloads; they are not unique people. Necessary authentication and security processing is separate.
Our own analytics: Detailed events are kept for 90 days; identified visitor history for 12 months after the last visit. Anonymous totals are kept without a time limit. The browser identifier lasts 30 days after the last visit, and the choice is remembered for up to 180 days. A temporary account-site arrival cookie lasts up to 30 minutes. A minimal withdrawal marker may remain for 90 days to block delayed events.
Google Analytics 4 is used only on .com and Yandex Metrica only on .ru, when enabled and with your consent. Active services are listed above. On the public .ru homepage, Webvisor and interaction maps may record the displayed page, clicks, pointer movements and scrolling. Field contents and login and payment pages are excluded. Yandex keeps recordings for 15 days. Personalised advertising is disabled. Adding a service or session recording requires renewed consent. Search Console and Yandex Webmaster provide separate search reports without installing counters.
You can decline or withdraw consent using the controls at the top of this policy. The site remains fully available. Withdrawal stops further analytics and removes links to your visitor history; anonymous totals remain. Operational account and payment records follow their separate purposes and retention rules.
We retain account data to provide and manage your account for as long as it is maintained. You may request deletion using the contact details below. Ordinary support correspondence is retained for one year after the last message once the case is closed. Relevant records may be retained longer where necessary for an ongoing dispute or a legal obligation; this does not extend retention of all account data. Security and operational records are retained only as long as needed for their stated purposes. Expiry of a cookie or email link does not itself delete the account. Specific retention periods and deletion procedures apply separately to these different records.
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 support@blenderbridge.com.
Your data may be processed outside your country of residence. We apply reasonable organisational and technical safeguards. Email, sign-in, AI and sharing providers you choose yourself may process data in other countries according to their own policies.
The account service is intended for adults aged 18 or over. If you believe that a minor has provided us with personal data, please contact support@blenderbridge.com.
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.
Service operator: Danil Anufriev, a sole proprietor registered in the Russian Federation.
City: Kazan.
Registration number (OGRNIP): 322890100007421.
Phone: +7 922 057 18 20.
For privacy questions or requests:
support@blenderbridge.com