Skip to content
databrushDocs
  • OverviewDatabrush’s churn and retention analysis for your Supabase database, in the app and over MCP.
  • QuickstartConnect Supabase, choose your database and confirm the setup to publish your first analysis.
  • Supabase integrationHow Databrush connects to Supabase, what it reads and keeps, and how to revoke its access.
  • Connect your agentConnect Databrush to Claude, Claude Code, ChatGPT, Codex or another agent over MCP.
  • Tool referenceEvery tool Databrush’s MCP server offers, what it does, and who can use it.
  • How it worksHow Databrush analyzes your data, what Home shows, and how sure each finding is.
  • DefinitionsCustomers, who is left out, actions, churn and the dormant window, and how to change them.
  • Security & dataHow Databrush protects your database, your customers’ details and your account.
Connect Supabase
Security & data

Account

Security & data

Databrush only reads your database, keeps as little about your customers as it can, and lets you decide what your agents see. This page summarizes how. The Privacy Policy and the Data Processing Addendum are the full terms.

On this page

Your database

Databrush connects through Supabase’s own OAuth approval and reads your database through Supabase’s read-only query endpoint: the schemas you choose, database statistics and a fixed set of reads from Supabase Auth. It never writes to your database. See Supabase integration.

Storage and encryption

  • Traffic is encrypted in transit.
  • Supabase authorization tokens and any database credentials are stored encrypted with Databrush’s credential-management provider.
  • The customer history Databrush keeps is designed not to include names, email addresses or free text.
  • Databrush limits what its logs record.

Who can see what

  • Every read of Databrush’s own data is scoped to your team and workspace.
  • Owners, admins and members can see a team’s workspaces, mark customers contacted and dismiss, snooze or restore warnings.
  • Owners and admins can also set up workspaces, change definitions, manage Retention Signals and act on product suggestions.

Agents and keys

  • An agent signs in as you and acts with your role. Every change it makes is recorded as you.
  • Agents see customer names and emails only if you turn that on. See Customer names and emails.
  • An API key for an agent that can’t sign in also acts as you, and expires after 90 days.
  • Revoke any agent sign-in or key in Settings › MCP. Access ends at once.

AI providers

Databrush uses OpenAI to propose your setup and to word product suggestions. What it sends is limited to schema details (table and column names, types and comments), database statistics, category values such as plan names, and calculated figures, and is designed not to include customers’ names, email addresses, free text or identifiers. Databrush hasn’t opted in to OpenAI using its API data to train OpenAI’s models, and doesn’t use your data to train general-purpose AI models.

Suspension

A suspended account loses its Supabase access and agent keys. See Suspended accounts.

Report a concern

Report a security concern to support@databrush.ai. Please leave out passwords, tokens and connection strings.

Questions? Email support@databrush.ai.