Security
Last updated: September 20, 2026
A short summary of how we protect the data you share with ADBU and the Google accounts you link. If you need more detail for a procurement questionnaire, e-mail us.
Data in transit and at rest
All traffic to adbu.io and to our API is served over HTTPS (TLS). The application and its database run on Railway, the website on Vercel, both with encryption at rest and access controls managed by the provider.
Access to your Google Ads account
We never ask for your Google password. Access is granted through Google's standard manager account linking or OAuth, with the minimum scopes needed, and you can revoke it from your Google account or the dashboard at any time. Ad spend is paid by you to Google directly and never passes through ADBU.
Who at ADBU can see your data
Only the team members who work on your account. Access is protected by strong authentication, and access to production systems is limited to the people who operate them.
Sub-processors
Railway, Vercel, Google, Anthropic and Resend, each under a contract that limits use of your data to the service we ask of them. The full list and what each one does is in the Privacy Policy.
Changes to your campaigns
Every new campaign is created paused and switched on only after you approve it. Budgets are kept within the monthly cap in your order form. Changes made through the dashboard are logged.
Reporting a vulnerability
If you believe you have found a security issue, e-mail security@adbu.io. We respond promptly and appreciate responsible disclosure.
Questions? Contact us at info@adbu.io.