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
Supabase integration

Connect

Supabase integration

Databrush connects to your Supabase organization through Supabase’s own OAuth approval. It reads your database through Supabase’s read-only query endpoint and never writes to it. You don’t share a database password, a connection string or a service key.

On this page
Approval
Supabase OAuth
Access
Read-only: your chosen schemas and fixed Auth reads
Revoke
Any time, in Supabase
Your Supabase database is read through Supabase’s read-only query endpoint into Databrush’s analysis, which feeds Home and your agent. Nothing is written back.YOUR SUPABASEChosen schemasAuth: fixed readsOther schemas: neverSUPABASE APIRead-only queryendpointUser-Agent: DatabrushDATABRUSHOngoing analysisCustomer history,no names or emailsHomeYour agentNothing is ever written back to your database.

Requirements

  • A database hosted on supabase.com. Databrush connects through Supabase’s platform API.
  • A Databrush plan. Every plan starts with a free trial. See Plans & billing.

How approval works

  1. In Databrush, choose Connect Supabase.
  2. Supabase opens its own approval page for Databrush. Choose your organization and approve.
  3. Supabase gives Databrush authorization tokens. Databrush stores them encrypted with its credential-management provider and renews them when they expire.
  4. Back in Databrush, choose your production database, then the schemas that hold your customers and their activity.
  5. Review the setup Databrush proposes and confirm it. See the Quickstart.

What Databrush reads

  • Tables in the schemas you chose at setup. Apart from the fixed Supabase Auth reads below, Databrush never reads any other schema.
  • Database statistics, used to plan its queries and describe your data.
  • From Supabase Auth: user IDs, email addresses, sign-up and last sign-in times, session times and sign-in events. These come from a fixed list of read statements and nothing else, and the auth schema is never added to your chosen schemas.

Every request Databrush sends to Supabase’s API identifies itself with this header, so you can recognize it:

User-Agent: Databrush

When you mark a customer contacted or a suggestion shipped, that is saved in Databrush, never in your database. To see exactly which tables a workspace reads, open Settings › Data, or ask your agent for the data coverage.

Supabase API calls

Databrush calls only these Supabase endpoints:

CallWhat Databrush uses it for
GET /v1/oauth/authorizeOpens Supabase’s approval page in your browser.
POST /v1/oauth/tokenExchanges your approval for tokens, and renews them.
GET /v1/projectsLists the databases you can choose from.
POST /v1/projects/{ref}/database/query/read-onlyRuns Databrush’s read-only queries on the database you chose.
POST /v1/oauth/revokeEnds Databrush’s authorization when an account is deleted or suspended.

What Databrush keeps

To measure churn and retention, Databrush keeps a history for each customer in the connected database: their identifier in that database (such as a primary key), status, plan or segment labels, billing status and amounts where your database holds them, daily activity counts, warnings, and records your team adds, such as marking a customer contacted. The history is designed not to include names, email addresses or free text. Names and emails are read only when a page, an exclusion rule or an agent request needs them.

WhatHow long
Customer historyDaily records for about 400 days, then weekly summaries for up to 3 years, while the database stays connected
After you disconnect, or delete the workspace or accountDeleted
After Databrush loses access to the databaseDeleted 30 days later if access isn’t restored
A customer who leaves your databaseRemoved from the history after about 30 days, or on request
Analysis results, warning history and run recordsAbout 400 days

Databrush and its providers process information in the United States and other countries where they operate. When Databrush proposes your setup or words a suggestion, it sends OpenAI schema details, database statistics, category values such as plan names, and calculated figures, designed not to include customers’ names, email addresses, free text or identifiers. See AI providers. The Data Processing Addendum lists every provider that processes your data, and the Privacy Policy has the details.

Revoke access

  • In Supabase: an organization owner removes Databrush’s authorization in Authorized Apps in your organization’s settings. Databrush can then no longer renew its token or read your database. Your workspace shows that Supabase needs approving again, and the history is deleted after 30 days if you don’t approve again.
  • In Databrush: disconnecting a database in Settings › Data deletes the history Databrush kept for it. Disconnecting doesn’t remove Databrush’s approval in Supabase, so remove it there too.
  • Deleting your Databrush account revokes Databrush’s authorization at Supabase and cancels any trial or plan.

Suspended accounts

If Databrush suspends an account for abuse, fraud or a breach of Databrush’s terms, every Supabase approval that person gave stops serving reads at once. Their agent keys are revoked, and Databrush revokes its authorization at Supabase within 24 hours, as Supabase’s partner terms require.

If access stops working

If Supabase refuses Databrush’s token, Home shows a notice. Owners and admins see Approve Supabase again, and members see a note to ask one of them. Approve in Supabase and Databrush picks up where it left off. For anything else, email support@databrush.ai.

Questions? Email support@databrush.ai.