Subprocessors
Last updated: November 13, 2026.
1. About this list
Subprocessors are third parties that process personal data on our behalf to provide Bilge. This list applies together with our Data Processing Agreement and Privacy Policy.
2. Hosting, database and network
- dply: Runs the application containers, queue workers, managed PostgreSQL database, Redis-compatible cache and database backups. Processes all data stored in the Service, including ingested error, trace and log payloads.
- Cloudflare, Inc.: DNS, TLS termination, content delivery and protection against abuse for all traffic to the Service, including ingest requests. Also delivers transactional email (verification, invitations, alerts, digests and billing notices) through Cloudflare Email Service.
3. Payments
- Stripe, Inc.: Processes payment details, subscriptions, invoices, tax calculation and related fraud signals for paid plans. We do not store full card numbers.
4. Sign-in
- GitHub, Inc. and Google LLC: Only when you choose to sign in with GitHub or Google: they process the authentication request and share your name, email address and account identifier with us.
5. Optional features
- OpenAI, L.L.C.: Only for organizations that turn on AI fix suggestions: the error message, exception class, file and line, release, environment, request URL and stack trace of the issue are sent to generate a suggestion.
- Integrations you connect: When you connect GitHub, GitLab, Jira, Linear, Slack or another destination, we send the data you configure (for example issue titles, links and alert messages) to that service. Those services act under your own agreement with them.
6. Changes
We may update this list when we add or replace subprocessors. We will post the revised page with a new “Last updated” date and, where our customer terms require it, notify affected customers in advance or offer a mechanism to object.