Barua privacy policy

Connecting Google reporting

Optional connection notice, version 2026-10-26.1.

When you choose “I agree and connect Google” in your workspace, you accept this notice for that workspace and sending domain. Google then asks you to allow read-only Postmaster access. You can keep using Barua without connecting.

What Barua reads

Barua reads Google Postmaster's aggregate reports for your configured sending domain: spam rates, authentication results, delivery errors and compliance results. Some compliance results describe the parent domain. Reports may include email sent through other services using the same domain. Low sending volumes can leave Google with no report to share.

This permission does not give Barua access to your Gmail messages or contacts. It does not allow Barua to send email through your Google account or change your Postmaster domain settings.

How the reports are used

Barua displays the reports in Delivery health and uses them to warn your workspace owner about delivery problems. Workspace members and agents with access to the workspace's deliverability read can see these reports. An agent you authorize receives them under your arrangement with that agent.

These reports leave your existing sending controls unchanged. Their warnings do not pause email or enable automatic holds.

Google data is used only for this reporting feature. Barua does not use it for advertising or sell it. It is never supplied to models to train them. Barua's use and transfer of Google API data follows the Google API Services User Data Policy, including its Limited Use requirements.

Storage and removal

Barua keeps daily aggregates for 90 days. Scheduled, bounded cleanup removes older reports; an outage or backlog can delay physical removal. Connection consent and warning records remain as workspace operational records until workspace deletion. The existing privacy policy describes hosting and account deletion.

Barua encrypts the Google refresh credential needed to obtain fresh reports. It does not include that credential in workspace exports or agent responses. Disconnecting removes the credential and stops collection. Replacing the sender invalidates the connection. Removing the connecting owner's authority or closing the workspace invalidates it too. Retained reports remain subject to the retention period and workspace deletion.

Disconnecting one workspace does not revoke the Google account's grant for your other workspaces. You can separately remove Barua's access in your Google account. If this notice changes, Barua will ask for your acceptance before resuming Google reporting under the new version.

Questions or removal requests: chris@barua.ai.