---
title: "Subprocessors"
description: "These providers process customer data for LogBrew. LogBrew gives notice when this list changes."
canonical: "https://logbrew.co/en/subprocessors"
last_updated: "2026-11-02"
---

# Subprocessors

These providers process customer data for LogBrew. LogBrew gives notice when this list changes.

Updated November 2, 2026

Canonical: https://logbrew.co/en/subprocessors
HTML: https://logbrew.co/en/subprocessors
See also: https://logbrew.co/en/security

| Provider | What it does for LogBrew | Data it processes | Where |
| --- | --- | --- | --- |
| Hetzner Online GmbH | Hosting and storage, including backups | All account data, project data, telemetry, uploaded source maps and native symbol files, and backups | Germany |
| Cloudflare, Inc. | DNS, content delivery, attack protection, and HTTPS at the edge for logbrew.co, api.logbrew.co, and mcp.logbrew.co | Every request in transit: IP address, headers, cookies, and request bodies, including telemetry sent to the API | Cloudflare's global network, at the location nearest the visitor |
| Resend, Inc. | Sends product email, such as invitations and alert digests, and receives mail sent to logbrew.co addresses | Recipient email addresses, teammate names in invitations, alert text (issue titles, project names, rule names, services), and the content of mail you send to support | Sending from the United States, receiving in Ireland |
| Stripe | Checkout, subscriptions, invoices, and the billing portal for paid plans | LogBrew account reference and plan. The payment card, billing email, and address that you enter in Stripe Checkout go to Stripe directly and never reach LogBrew. | United States and Ireland |
| Apple Inc. | Push notifications to the iOS app, only for users who turn them on | Device push token and notification text (alert type, issue title, project name, service) | United States |

LogBrew uses no third-party error tracker or product analytics service. LogBrew's own errors go to LogBrew. The website sets no advertising or analytics cookies.

## Services you connect

These services are not subprocessors. They process data only because you choose to connect them.

| Service | What LogBrew exchanges with it |
| --- | --- |
| Sign-in with GitHub, GitLab, Bitbucket, or Google | LogBrew receives the profile the provider shares: name, email address, avatar, and your user number at that provider. There is no password sign-in. |
| Repositories on GitHub, GitLab, or Bitbucket | When you connect a repository, LogBrew uses your access token to read repository metadata, commits, and the files it needs for source context. |
| Webhooks, including Slack, Discord, and Microsoft Teams | LogBrew sends alert messages only to the URLs you add. |
| Your AI agent | An MCP client or the CLI reads project data only with your consent or key. LogBrew sends no customer data to an AI provider of its own. |