Blender content safety and privacy

Establish the boundary

1. Identify every supplied file, archive, URL, library, and referenced dependency. Treat unknown or third-party content as untrusted until the user confirms its origin and intended use.
2. Work on a copy in a dedicated output directory. Preserve the original bytes and record a cryptographic hash when provenance matters.
3. Keep generated files, logs, previews, and captures local by default. Share or upload them only when the user requests it and the destination is appropriate.

Inspect safely

1. Inspect filenames, types, sizes, hashes, archive listings, and dependency metadata before opening content in an authoring application.
2. Open untrusted .blend files with automatic Python execution disabled. Do not enable embedded scripts, startup handlers, scripted drivers, add-ons, or referenced executable content without explicit trust and user approval.
3. Use an isolated Blender profile or disposable process for untrusted scenes. Avoid loading unrelated user preferences, credentials, extensions, or writable project locations.
4. Treat USD layers, textures, linked libraries, fonts, archives, and other dependencies as separate inputs. Do not assume a trusted container makes all referenced content trusted.

Bound materialization