AI-BDR Trust Centre

Security & Data

Last updated: 18 October 2026

Hosting and connections

AI-BDR’s primary application and database are hosted on DigitalOcean in London, United Kingdom. Public application connections use HTTPS. Connected providers may process information in other locations, as explained in our Privacy Policy.

Account and workspace access

Authenticated application requests are checked against account and workspace permissions. Access controls are tested as part of our release process. Keep your credentials private and review access to shared workspaces.

Connected services

AI-BDR uses an integration credential vault to protect supported stored credentials. Disconnecting an integration removes its saved connection from AI-BDR; some providers also require you to revoke permission in their own account settings. Never send passwords, API keys or access tokens to Support.

Outreach preferences

Recipient opt-outs are recorded independently of contact cards. Quick Send, Campaigns and Interpreter check the workspace’s email preference before handing an outreach message to the provider. Deleting and importing a contact again does not clear an existing block. Restoring outreach requires recorded evidence of renewed permission.

Backups and recovery

Local backups are maintained, and recent deployment records include successful backup restoration checks. An operational offsite backup and recovery process has not yet been verified. We do not currently promise a fixed recovery time or maximum data-loss window.

Updates and verification

Application releases undergo automated build, regression and isolated database checks before deployment. These checks help detect problems but do not guarantee that every vulnerability or failure will be prevented.

Data retention and deletion

Retention depends on the type and purpose of the information. Financial, security and account-closure records may need to be retained after an account closes. See our Privacy Policy and Data Deletion page for details.

Report a security concern

Contact [email protected] with a brief description and steps to reproduce the issue. Do not include credentials or unnecessary personal information.