Subprocessors
These vendors can receive personal data when you use Bermward. We have written agreements with each that require them to protect it. The list is part of the Data Processing Addendum. We give at least 30 days' notice before a new vendor starts receiving customer data, by updating this page and emailing workspace administrators. Questions or objections: privacy@bermward.com.
| Vendor | What they do | Personal data they can receive | Location | When used |
|---|---|---|---|---|
| Amazon Web Services | Hosting, storage, email delivery and related infrastructure services | All service data, including account data and monitoring data | United States | Always |
| Stripe | Subscription billing, invoices and card payments | Billing contact name and email, plan, payment details entered with Stripe | United States and other Stripe locations | Paid plans and alert credits |
| Twilio | SMS and voice alerts | Alert phone numbers and the alert message text | United States | When SMS or voice alerts are used |
| Cloudflare (Turnstile) | Bot protection on sign-up, free scan and privacy-request forms | IP address, browser signals and the challenge response | United States and other Cloudflare locations | On pages that show a verification challenge |
| Have I Been Pwned (Troy Hunt) | Breach lookups for monitored email addresses and domains | Email addresses and domains you monitor | Provider-operated; see vendor | Leaked-credential monitoring |
| Hudson Rock | Infostealer exposure counts for a domain | The domain being scanned | Provider-operated; see vendor | Free scans and domains with credential monitoring |
| LeakCheck and XposedOrNot | Fallback breach lookups when the primary source cannot answer | Email addresses you monitor | Provider-operated; see vendor | Only if the primary breach source is unavailable and the lookup is configured |
| Threat-intelligence and discovery sources (for example Shodan, VirusTotal, SecurityTrails, Censys, GreyNoise, AbuseIPDB, AlienVault OTX, urlscan.io, crt.sh) | Find subdomains, exposed services, reputation and certificate data for a domain | Domain names, hostnames and IP addresses being scanned; no account data | Provider-operated; see vendor | Scans, where the source is configured for the plan |
| OSV.dev (Google) | Known-vulnerability data for dependencies | Package names and versions; no personal data | United States | Dependency monitoring |
| GitHub and GitLab | Read repository manifests you connect | Repository names and dependency manifests; the OAuth token you grant, stored encrypted | United States | When you connect a repository |
| Google and Microsoft | Single sign-on and, if you connect it, directory sync of staff addresses | Name, email address and the directory entries you authorize | Provider-operated; see vendor | When you sign in with, or connect, those accounts |
Vendors that only receive domain names, package names or IP addresses of your assets, and no account data, are listed for transparency. Your workspace uses a given vendor only if the feature that needs it is enabled for your plan.
Changes to this document
- 2026-11-18: First full version.