What Gets Sent Online
Understand provider requests, file storage, update checks, and local agent access.
Your canvas and generated files live in your Obsidian vault. Generation uses the provider you choose, which has its own pricing and data policies.
When you click Run
Bragi sends your selected prompt and connected upstream text to the chosen provider. It also sends the selected references supported by that model, such as images, video, audio, PDFs, or note content.
Provider keys are stored in your plugin settings. They are sent to the relevant provider to authorize requests. Vault backup or sync tools may also copy your plugin settings, depending on your configuration. Do not publish your settings file or put keys in canvas nodes.
Seedance draft finalization
Draft Mode stores the provider, task ID, original model ID, output format, and submission time with the video node in your canvas. It does not store credentials in the node. Clicking Generate 1080p sends the saved task/model identity and output controls to the provider that created the draft, using your current key for that provider. BytePlus drafts go to your configured BytePlus endpoint; SVRouter drafts go to SVRouter. It does not upload the prompt or reference files again. BytePlus's seven-day draft-finalization window is not a promise that the provider deletes all stored data after seven days.
Temporary transfers with Bragi Relay
Some providers need a reachable URL to fetch a reference. Bragi can upload the reference to Bragi Relay for that transfer; other providers use their own file or asset service.
Temporary Relay files under the bragi/ and temp/ paths are scheduled to expire after one day. Expiration runs asynchronously, so deletion is not guaranteed at exactly 24 hours. Persistent voice assets use a separate path and are not covered by that temporary-file policy.
Anyone with a temporary public file URL may be able to fetch it while it exists. Relay is a transfer service, not a private backup. Final generation outputs are saved in your vault.
Local agent access
The optional MCP server is off by default. When enabled, it listens on 127.0.0.1, normally port 17775. Agents connected to it can read or change canvas content and start generations.
A token is optional. Without one, other processes on your computer can also call the server. A configured token is required on every client request. Host and browser-origin checks reject unexpected web origins; they do not isolate trusted and untrusted local processes.
See Agents and MCP for setup and connection limits.
Update checks
Opening or activating a canvas can check GitHub for the latest public plugin release. That check does not send your vault content, prompts, or provider keys. Bragi Canvas does not include client-side analytics.