Last updated: March 4, 2026
Overview
Coderbuds uses a limited number of third-party sub-processors to help deliver, maintain, and improve our service. Each sub-processor has been evaluated to ensure they meet our security and privacy standards. This page lists all current sub-processors, their purpose, and data processing locations.
Infrastructure & Hosting
Laravel Forge
United StatesServer provisioning and deployment management for application hosting.
DigitalOcean
United KingdomCloud infrastructure and file storage for application hosting and assets.
AI & Machine Learning
OpenAI
United StatesAI-powered code review generation and Slack coaching responses. Only team performance metadata is processed — no source code is stored by OpenAI. API inputs are retained by OpenAI for up to 30 days for abuse monitoring only and are not used for model training.
Payments & Billing
Stripe
United StatesSubscription billing and payment processing. Coderbuds does not store credit card numbers — all payment data is handled directly by Stripe.
Communications
Loops
United StatesEmail marketing and product updates for opted-in users.
Monitoring & Error Tracking
Sentry
United StatesApplication error tracking and performance monitoring. Personally identifiable information (PII) is not sent to Sentry.
Source Code Integrations
GitHub
United StatesRepository integration for pull request data, code reviews, and deployment tracking via webhooks and OAuth.
Atlassian (BitBucket)
AustraliaRepository integration for pull request data, code reviews, and deployment tracking via webhooks and OAuth.
Changes to This List
We will update this page when sub-processors are added or removed. If you have questions about our sub-processors or data processing practices, please contact us at privacy@coderbuds.com.