Local files and workspace context
Bardo is designed so your campaign files, notes, and other workspace context can stay local. If a question depends on your local files, the source of truth should remain your machine rather than the public website.
This product boundary is intentional: Bardo's hosted layer exists to support access and account workflows, not to turn the website into a copy of your local campaign data.
Hosted service data
The hosted Bardo surface may receive and process account details, session state, approval requests, subscription state, metering-related data, and runtime status information needed to operate the service.
That hosted data supports the website and dashboard experience, but it is not the same thing as your local campaign or workspace files.
Third-party clients and models
Bardo can be used alongside external MCP-capable clients and model providers. Those tools may send prompts, outputs, or other data to their own services under their own policies.
Before using any third-party client or model provider, review that provider's own terms, privacy practices, and data-use policy.
Policy boundary
This page explains how Bardo handles its own hosted surface. It does not replace the policies of the AI client, model provider, operating system, or cloud platform you may choose to use alongside Bardo.
If you need a simpler rule, use this one: local files stay local to Bardo unless you deliberately connect them to another tool or service.