Skip to content
DoerbayBook a call

Security and your data

What the agents can reach, what they can’t, and who decides when something changes in your accounts.

Your data is kept apart by the databases

Every row of your data carries your company. The databases themselves only return a company’s own rows: row-level security where Doerbay keeps your accounts and settings, and row policies in the warehouse where your synced data lives. A query can’t see another company’s rows, even if our code forgot to filter them.

Connections run over encrypted links. The keys and sign-ins for your tools are stored encrypted, with a key kept outside the database.

Agents reach your data only through Doerbay

Each agent is a separate service. It talks to Doerbay only through a fixed set of operations, and Doerbay knows which company and which agent is calling from the agent’s own key, never from what the agent says.

Nothing changes until you tap Apply

Most workflows only read. When an agent wants to change your Google Ads, it proposes a batch: each change with its reason and expected effect. Doerbay checks the batch with Google before you see it. Nothing changes until someone at your company taps Apply. Afterwards you can undo the batch; Doerbay puts back what it changed and tells you anything it can’t, such as a budget someone has moved since.

Agents that act in other tools ask first too: Outbound adds people to HubSpot or an Instantly campaign only after you say yes.

What agents can’t do

Who we are

Doerbay is made by Duenders GmbH, a company in Zug, Switzerland, under Swiss law. Error reports from the app go to an error-monitoring service in the EU.

Data from Google, such as Search Console, Google Analytics and Google Ads, is used under Google’s Limited Use requirements: only to run the features you use, never sold, never used for advertising and never used to train general AI models. The details are in our Privacy Policy.

Book a callQuestions and answers