Sub-processors

Last Updated: October 2026

Brimble Inc. ("Brimble", "we", "our", or "us") relies on certain third-party service providers ("Sub-processors") to operate and deliver the Brimble platform.

1. Overview

These providers assist with infrastructure hosting, monitoring, analytics, email delivery, payments, content delivery, and other operational services. Sub-processors may process limited customer data only as necessary. Brimble carefully selects vendors that maintain strong security and privacy practices.

2. Infrastructure Providers

Hetzner

Purpose: Cloud infrastructure and compute hosting.

Data Processed: Application workloads, networking traffic, and infrastructure metadata.

DigitalOcean

Purpose: Hosting for Brimble's internal tooling and APIs.

Data Processed: Internal tooling and API workloads, API request data, and infrastructure metrics.

Nobus

Purpose: Local cloud infrastructure and compute hosting in Africa.

Data Processed: Application workloads, networking traffic, and infrastructure metadata.

Pantech Dynamics

Purpose: Local cloud infrastructure, compute hosting, and data centre services in Africa.

Data Processed: Application workloads, networking traffic, and infrastructure metadata.

Tailscale

Purpose: Private networking between Brimble servers across all regions.

Data Processed: Server identifiers, network addresses, and connection metadata. Traffic between servers is end-to-end encrypted.

3. Content Delivery and Networking

Cloudflare

Purpose: CDN, DNS management for domains, caching, security services including traffic filtering and DDoS mitigation, and object storage (R2) for files, assets, and user-generated storage.

Data Processed: Domain DNS records, IP addresses, request metadata, network traffic information, stored files, and associated storage metadata.

4. Domain Registration

Namecheap

Purpose: Domain registration, renewal, and transfer.

Data Processed: Domain names, registration and transfer details (including authorization codes), and DNS and nameserver settings.

Dynadot

Purpose: Domain registration, renewal, and transfer.

Data Processed: Domain names, registration and transfer details (including authorization codes), and DNS and nameserver settings.

Name.com

Purpose: Domain registration, renewal, and transfer.

Data Processed: Domain names, registration and transfer details (including authorization codes), and DNS and nameserver settings.

5. Object Storage

Tigris

Purpose: Object storage services for files, assets, and user-generated storage.

Data Processed: Stored files and associated storage metadata.

6. Monitoring and Logging

Better Stack

Purpose: Public status page and downtime alerts.

Data Processed: Service availability metrics, incident details, and status page subscriber email addresses.

Google Cloud Uptime Monitoring

Purpose: External uptime monitoring of Brimble services.

Data Processed: Service availability metrics and monitoring results.

Laravel Nightwatch

Purpose: Application monitoring for PHP-based workloads.

Data Processed: Application performance metrics and debugging information.

Sentry

Purpose: Error tracking and performance monitoring.

Data Processed: Error reports, stack traces, request metadata, and pseudonymous user identifiers.

Supabase

Purpose: Storage for deployment and build logs.

Data Processed: Build and deployment log output, and deployment metadata.

7. Analytics

PostHog

Purpose: Product analytics and platform usage insights.

Data Processed: Usage analytics, feature interaction data, pseudonymous identifiers, page and event metadata, and session replay data with masking controls.

8. Email Delivery

Resend

Purpose: Transactional email delivery including account notifications, authentication emails, and platform alerts.

Data Processed: Email addresses and email content required to deliver messages.

SendByte

Purpose: Transactional email delivery including account notifications, authentication emails, and platform alerts.

Data Processed: Email addresses and email content required to deliver messages.

9. Payment Processing

Stripe

Purpose: Global payment processing and subscription management.

Data Processed: Payment information, billing data, and transaction metadata.

Bachs

Purpose: Local payment processing in local currencies for customers in supported African markets.

Data Processed: Customer email addresses, payment details, billing data, and transaction information.

10. Development Infrastructure

GitHub

Purpose: Source code hosting, version control, and development collaboration.

Data Processed: Code repositories, commit history, and development metadata.

Docker Hub

Purpose: Container image registry used to distribute and manage application containers.

Data Processed: Container images and metadata.

Namespace

Purpose: Remote container builds and container image registry.

Data Processed: Application source code at build time, build logs, container images, and metadata.

11. Authentication Providers

WorkOS

Purpose: Authentication, identity management, and user session services.

Data Processed: User identity information, email addresses, authentication events, and session metadata.

External login providers may include: Google Login, GitHub Login, GitLab Login

These providers process authentication requests and identity verification data.

12. Sub-processor Updates

Brimble may update this list periodically as new service providers are added or removed.

13. Contact

Questions regarding sub-processors: privacy@brimble.app