Breeze RMM — Sub-Processor List
Effective Date: April 8, 2026
Last Updated: April 8, 2026
This page lists the Sub-Processors that Lantern Ops, LLC (“Breeze,” “we,” “us”) engages to process Customer Data and Personal Data in connection with the Breeze RMM platform. This list is maintained pursuant to Section 9.6 of the Terms of Service and Section 7.2 of the Data Processing Addendum.
Current Sub-Processors
| Sub-Processor | Purpose | Data Processed | Location |
|---|---|---|---|
| DigitalOcean, LLC | Cloud infrastructure — compute, storage, and networking for the Breeze RMM platform, including self-hosted databases and application servers | Customer Data, device telemetry, user account data, and all data stored within the platform | United States (US Region tenant) and Frankfurt, Germany — DigitalOcean FRA1 (EU Region tenant). See Regional Hosting below. |
| Cloudflare, Inc. | CDN, DDoS protection, DNS, Web Application Firewall (WAF), and mTLS certificate management | Network traffic metadata, IP addresses, request headers; mTLS certificates for enrolled devices | Global edge network (US-headquartered) |
| Anthropic, PBC | AI model provider (Claude) powering AI-assisted device management, diagnostics, and chat features within the platform | Device metadata, system information, diagnostic data, and user queries submitted to AI features | United States |
| GitHub, Inc. (Microsoft) | Source code hosting, CI/CD pipeline (GitHub Actions), and container image registry (GHCR) for building and deploying platform releases | Deployment artifacts and container images; GitHub does not process Customer Data directly | United States |
| Stripe, Inc. | Payment processing, subscription billing, and tax calculation for Breeze RMM subscriptions | Customer billing contact (name, email, address), payment method metadata (card brand, last 4, expiry), and transaction history. Does not process Customer Data collected from Managed Devices. | United States (with global regions) |
Changes to This List
In accordance with our Terms of Service (Section 9.6) and DPA (Section 7.3), Breeze will notify Customers at least thirty (30) days before engaging a new Sub-Processor or replacing an existing Sub-Processor.
How to Subscribe to Sub-Processor Change Notifications
To receive advance notice of Sub-Processor changes, contact us at [email protected] with the subject line “Sub-Processor Notifications” and include your organization name and account email. Notifications will be sent to the account owner email address on file or through the Platform’s notification system.
Objection Process
If you have a data-protection-related objection to a new Sub-Processor, you may notify us in writing within thirty (30) days of receiving the change notification. We will work with you in good faith to resolve the concern. If no resolution is reached within thirty (30) days, you may terminate the affected services without penalty, as described in the Terms of Service and DPA.
Regional Hosting
Breeze operates two independent tenants of the Platform on DigitalOcean infrastructure:
- US Region (us.2breeze.app) — primary Customer Data stored in DigitalOcean datacenters in the United States.
- EU Region (eu.2breeze.app) — primary Customer Data stored in DigitalOcean’s Frankfurt, Germany datacenter (FRA1).
Customers select their region at account creation. The two tenants are fully isolated at the infrastructure and data layers, and Customer Data is not replicated between them. Anthropic (AI features), Stripe (payments), and GitHub (deployment infrastructure) remain US-based for both regions; Cloudflare serves both tenants from its global edge network. See our Data Processing Addendum (Section 8.5) for a full description of regional hosting and residual cross-border processing.
Infrastructure Note
Breeze RMM’s databases (PostgreSQL) and caching layer (Redis) are self-hosted on DigitalOcean infrastructure and are not provided by separate managed-service Sub-Processors.
Lantern Ops, LLC — a Colorado limited liability company
breezermm.com | [email protected]