What the preview stores.
A concrete account of the current application’s data practices. Production policy is pending operator and legal review.
Account and workspace data
The self-hosted database stores account names, email addresses, password hashes, sessions, organization memberships, invitations, teams, project metadata, context, agent configuration, tasks, decisions, and audit records.
Credentials
Agent and invitation credentials are hashed. Raw values are displayed only when issued. Authentication session data is managed by Better Auth. Project exports exclude credential values and token hashes.
Acquisition and activation analytics
The preview records allowlisted funnel events, acquisition source, referral host, landing path, campaign tags, and a random analytics session ID. Campaign attribution is stored in browser storage and attached to signup when possible. Passwords, source file contents, credential values, and arbitrary query strings are not analytics fields.
Device preferences
Your browser stores appearance, selected organization, campaign attribution, and a random analytics session identifier. Account access uses HTTP-only session cookies.
No model execution
BranchSlate does not send project context to an AI model automatically. You choose the model and run the agent. No live repository synchronization, hosted inference, or runner execution occurs in V0.
Before production launch
The operator must publish contact details, applicable privacy rights, data retention and deletion procedures, subprocessors, and jurisdiction-specific notices. This page describes a local preview and is not a finalized production privacy policy.