What Bardo collects
Bardo keeps the hosted website surface intentionally small. The hosted layer may process account, authentication, subscription, billing, connection, and session status information needed to operate sign-in, protected dashboard routes, cloud campaign access, external AI platform connections, and related account workflows.
That hosted data exists for account operation only. Armando A. Calderon does not use the website to collect or host your local campaign canon as a normal part of the product.
How Bardo uses data
Bardo uses hosted data to run the website, authenticate users, show dashboard state, support subscription handling, meter usage workflows, and support cloud campaign access, external AI platform connections, or status checks.
Bardo has no sale of user data, and it does not use your hosted account data to turn the service into a hosted copy of your local campaign workspace. External clients, model providers, and other tools you connect have their own separate privacy practices.
What stays local
Bardo is built around a local by default product boundary. Campaign files, notes, and workspace content remain on your machine unless you choose to send them somewhere else through a separate client or model provider.
The Bardo website does not need your local campaign files in order to run account access, billing, connection workflows, or cloud campaign status checks. Hosted integrations may use cloud campaign data that you deliberately create or connect.
Retention and requests
Bardo retains hosted data only as needed to operate the service, support accounts and subscriptions, comply with legal obligations, and troubleshoot issues. Retention can vary by workflow and dependency.
Privacy, access, correction, deletion, billing, or account requests can be sent to bard.stdio@gmail.com. Bardo will review requests under applicable Puerto Rico, United States, and other mandatory law. This page is a product disclosure, not legal advice.