Data boundary

Discovery and graph inspection are local. Pairing enables a narrow, allow-listed structured sync for the project and confirmation workflow.

Stays local

• Graph JSON and graph filenames
• Prompts and node IDs
• Local source keys, filenames, and paths
• Images, video, models, LoRAs, character sheets, storyboards, and renders
• The private mapping from local keys to opaque Pluribus references

Sent to Pluribus after pairing

• Workspace and project fields you enter
• People and contact fields you enter
• Random workflow and source references
• Workflow and source kinds, source classifications, and linked person IDs
• Normalized operation classes from supported graph paths
• Structured intended-use fields
• Confirmation recipient, message, expected role, delivery choice, and stable request ID
• A SHA-256 fingerprint of the canonical API graph for audit comparison, not the graph itself
• The pairing device label ComfyUI plugin, never your hostname

What the claim covers

The plugin constructs allow-listed structured payloads and does not include raw graph or media material in those payloads. It does not inspect image pixels or perform face recognition.

This boundary does not certify every unsupported custom node or every tool in your wider production stack. Review custom-node behavior and network traffic before using confidential material in an untested environment.

Operational safeguards

• Protect the private data directory that stores the device credential and local-to-opaque bindings.
• Keep ComfyUI on loopback or behind trusted authentication.
• Do not paste tokens, graph JSON, private paths, or client material into support requests.
• Review each release's current limits before moving into production or final workflows.

See Current limits for the product boundary and Recover state and disconnect safely for credential revocation behavior.