How we handle your project data.
The information BranchSlate stores to provide your workspace and AI connections.
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
BranchSlate 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. Repository access follows the permissions you approve. Checks run through authenticated runners on your execution infrastructure; BranchSlate does not provide AI inference.
Beta service and privacy requests
Your workspace is private to its authorized users and agents. Use the support page for account, export or deletion requests. Service operation uses OVH hosting and Cloudflare; payment details are handled by Stripe when paid billing is enabled. Do not include passwords or API keys in a support request.