Privacy Policy for Blender Workflows and Blender ChatGPT MCP

1. Products covered by this policy

This policy describes how data is processed when using Blender Workflows, a package of instructions for working in Blender, and the separately installed local Blender ChatGPT MCP version 0.3.1.

Blender Workflows contains rules for performing tasks. The package itself does not install Blender or MCP, connect the user to the developer’s server, or create a user account with the developer. Controlling a scene requires an MCP client with a separately connected local Blender ChatGPT MCP.

In the current local configuration, the MCP server, bridge, and Blender add-on run on the user’s computer. The developer’s own cloud service is not involved in transmitting commands or results. This policy applies to the products listed above; data processing when visiting the website or using third-party services is subject to separate terms.

2. Data that is processed

Task and scene data. To carry out actions selected by the user, the local MCP processes commands, operation parameters, requested information about the scene and objects, geometry, materials, render settings, file names and paths, operation results, error messages, and preview images. If Python execution is enabled, the submitted code and its output are also processed. This data may contain personal or confidential information if it is included in the materials selected by the user.

Local operational data. Connection settings, local access keys, and pairing information are stored on the device. Operations that make changes may save receipts containing the operation identifier, time, a cryptographic fingerprint of the request, status, and result. Local diagnostic logs, scene recovery files, renders, and exports may also be created.

Support inquiries. If a user writes to support@505.cx, the developer receives the sender’s email address, their name if provided, the contents of the message, and any materials attached voluntarily. These may include an error description, the software version, a screenshot, or a log excerpt selected by the user. Sending this information to the developer is not required for normal operation of the local MCP.

The standard local product does not send telemetry, usage analytics, full chat contents, or automatic crash reports to the developer. The Blender Workflows package itself also does not send messages, scenes, files, or images to the developer.

3. How data is used

Local processing is necessary to perform requested actions in Blender, check results, manage access, diagnose errors, recover from failures, and prevent the same operation from being executed more than once.

Support inquiry data is used to respond to the user and investigate the reported issue. Contacting support does not subscribe the user to marketing emails.

In the current local release, the developer does not receive scene data for advertising, profiling, or training their own models.

4. Who may receive data

The selected MCP client. The local MCP returns the results of invoked tools, requested scene information, and previews to the client. If the client is ChatGPT or Codex, these results may be transmitted to OpenAI systems. Running commands locally in Blender does not, by itself, make data processing in that client entirely local.

Data processing by the client and its operator, as well as access by administrators of a work account, is governed by their terms, settings, and applicable policies. For OpenAI products, see the OpenAI Privacy Policy.

The developer and the support email provider. When a user contacts support@505.cx, the message and attachments are processed by the developer and the email services that deliver and store the correspondence. The standard local configuration does not automatically send project files to the developer.

Services contacted by executed code. When permitted, Python runs with the permissions of the Blender process and can read files or access the network. If the executed code calls an external service or sends data to it, that service becomes a recipient. Such transfers depend on the task and the code being executed; the local MCP is not an isolated environment for arbitrary Python code.

5. Where data is stored and for how long

• Projects and created files. .blend files, assets, recovery files, saved previews, renders, and exports remain on the device. They are retained until deleted by the user or by their software and backup system.
• Settings and pairing. Local configuration, access keys, and connection information are retained until changed or deleted by the user. Disabling the plugin in the client does not, by itself, delete these files.
• Operation receipts in local MCP 0.3.1. The substantive result data of a completed operation that makes changes is cleared after 24 hours, or earlier if the journal exceeds its 64 MiB limit. The operational record, including the identifier and outcome information, is retained for 30 days to prevent duplicate execution. Cleanup takes place during the next maintenance of the active journal and is not guaranteed to occur exactly when the retention period expires. Records of operations with an uncertain outcome are retained until the result is established or the user deliberately performs journal maintenance.
• Local diagnostic logs. Version 0.3.1 does not provide a general guaranteed period for automatically deleting all text logs. These files remain on the device until the user deletes or clears them. Local backups may retain earlier data.
• Support correspondence and attachments. Support correspondence and attachments are retained while the inquiry is being handled and, if needed to investigate follow-up inquiries about the same issue, for no more than 12 months after it is closed. Materials that are no longer needed are deleted earlier. Longer retention is permitted if required by law or necessary to resolve a specific dispute.
• Data held by the MCP client. Retention periods for requests, chats, received results, and uploaded materials are determined by the selected client, plan, account settings, and its policies. The local MCP journal’s retention periods do not determine retention periods at OpenAI or another client operator.

6. Options available to the user

The user can disable Blender Workflows in the client, stop the local MCP or disable the Blender add-on, change the permitted folders and tool access, and disable Python execution. The MCP should be stopped before deleting local operational files. Projects and recovery files are deleted separately at the user’s discretion.

The user can manage chat history and account data through the selected MCP client. Disabling Blender Workflows or the local MCP does not delete results already transmitted to the client.

To request access to, correction of, or deletion of information from a support inquiry, write to support@505.cx. The developer considers requests concerning data they hold, taking into account applicable requirements and technical capabilities. Requests to delete data held by OpenAI or another client operator must be addressed through the relevant service. The developer does not have automatic remote access to the user’s local files.

7. Access and security

The standard local configuration uses the address of the user’s computer and local authorization. Settings, connection keys, and operational records are stored on the device. The security of this installation also depends on access to the computer, operating system settings, and the permissions of the Blender process.

When contacting support, send only the materials needed to investigate the issue. Do not include passwords, access keys, verification codes, passport details, or other people’s personal information. Personal information in file paths, images, and logs can be redacted before sending.

8. Policy changes and future services

Updates to this policy are published on the same page with a new revision date. If a cloud MCP service is introduced or data processing changes, its recipients, purposes, retention periods, and user options will be disclosed before use of that service begins. This policy does not describe a cloud product that has not yet been launched.

9. Contact

Support and privacy inquiries: support@505.cx.