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
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
- In Databrush, choose Connect Supabase.
- Supabase opens its own approval page for Databrush. Choose your organization and approve.
- Supabase gives Databrush authorization tokens. Databrush stores them encrypted with its credential-management provider and renews them when they expire.
- Back in Databrush, choose your production database, then the schemas that hold your customers and their activity.
- 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
authschema 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:
| Call | What Databrush uses it for |
|---|---|
GET /v1/oauth/authorize | Opens Supabase’s approval page in your browser. |
POST /v1/oauth/token | Exchanges your approval for tokens, and renews them. |
GET /v1/projects | Lists the databases you can choose from. |
POST /v1/projects/{ref}/database/query/read-only | Runs Databrush’s read-only queries on the database you chose. |
POST /v1/oauth/revoke | Ends 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.
| What | How long |
|---|---|
| Customer history | Daily 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 account | Deleted |
| After Databrush loses access to the database | Deleted 30 days later if access isn’t restored |
| A customer who leaves your database | Removed from the history after about 30 days, or on request |
| Analysis results, warning history and run records | About 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.