Subprocessors & Service Providers
Trusted third-party services we use to deliver StatusPage.me
Start Free TrialWe maintain this inventory of external providers and first-party services used to deliver StatusPage.me. Last updated: 5 October 2026
About This List
We review service providers for their role in delivering the service and publish the data flows we can verify. Contractual and data-protection terms are applied as appropriate to the provider and processing relationship.
Payment / Merchant of Record
DodoPayments
Purpose: Payment processing, subscription management, and billing
Data Processed: Payment card information, billing details, transaction records, customer email
Location: Processing locations are determined by DodoPayments and its payment partners
Note: DodoPayments acts as the Merchant of Record. Payment card data is sent directly to DodoPayments and never touches our servers.
External Infrastructure & Service Providers
Telegram Bot API
Purpose: Internal operational, support, registration, plan-limit, and billing-event notifications
Data Processed: Depending on the event, account name, email, account ID, plan or billing-event details, support context, and request or error metadata
Location: Processing locations are determined by Telegram and its infrastructure providers
Note: Used for internal notifications through a configured StatusPage.me bot and chat.
Threema AG (Threema Gateway)
Purpose: Optional delivery of incident, maintenance, monitoring and other status notifications through Threema when a customer explicitly enables and configures the Threema notification channel. Nothing is sent to Threema for customers who do not use the integration.
Data Processed: The recipient Threema ID entered for the channel and the notification text: the event subject, relevant fields such as the monitor, component, incident or status-page name, status or severity, description or details text where applicable, and a link to the relevant details page
Location: Switzerland 🇨🇭
Note: Threema AG, Churerstrasse 82, 8808 Pfäffikon SZ, Switzerland. Messages are sent through StatusPage.me's own Threema Gateway account in Basic mode, where Threema encrypts the message on its servers; it is not end-to-end encrypted between StatusPage.me and the recipient.
IP Guide
Purpose: Approximate geolocation used to suggest a nearby monitoring region
Data Processed: Public IP address resolved from a customer-configured monitor target
Location: Processing locations are determined by IP Guide and its infrastructure providers
Note: Results are cached in process for one hour. Private and loopback IP addresses are not sent.
Brevo
Purpose: Additional email delivery, including delivery-problem routing and delivery to Microsoft-hosted recipient domains where configured
Data Processed: Recipient email address, message content, and delivery metadata
Location: Processing locations are determined by Brevo and its infrastructure providers
Note: Brevo supplements the primary StatusPage.me-operated mail path; it is not the platform's sole mail system.
Contabo
Purpose: First-party email infrastructure, encrypted off-site backups, an asynchronous read-only standby of the production database for disaster recovery, a retained rollback environment, and distributed monitoring infrastructure
Data Processed: Email addresses and message content and delivery logs on the mail server; encrypted database backups; a continuously replicated, read-only physical copy of the production database (the disaster-recovery standby, which holds the same personal data as the primary); a retained copy of the previous primary database, kept for rollback purposes; monitor configuration and telemetry at monitoring nodes (see below)
Location: Germany 🇩🇪 (European Union) for mail.statuspage.me, off-site backups, the disaster-recovery standby and the rollback environment; monitoring nodes in Germany 🇩🇪, the United Kingdom 🇬🇧 and the United States 🇺🇸
Note: Until 28 September 2026 Contabo hosted the primary application and database. Contabo now hosts StatusPage.me-operated email delivery (mail.statuspage.me), receives encrypted off-site backups, hosts the asynchronous disaster-recovery standby of the production database (a different provider and city from the netcup primary, with manual promotion and no automatic failover), and holds the retained previous primary environment. Contabo also hosts monitoring nodes in Germany, the United Kingdom and the United States (see Monitoring network for the current locations). The retained previous primary environment will be listed here until it is removed.
netcup GmbH
Purpose: Primary application, PostgreSQL database, Redis cache and scheduler hosting, and a regional monitoring node
Data Processed: Primary platform data, customer accounts, databases, status pages, subscription data, monitor configuration and results, and operational metadata; at the monitoring node, the monitor configuration and telemetry needed to execute checks (see below)
Location: Germany 🇩🇪 (European Union), including the monitoring node in Nuremberg
Note: Announced on 28 August 2026. netcup began processing personal data on 28 September 2026, when it became the primary infrastructure provider.
OVHcloud
Purpose: Regional uptime monitoring infrastructure
Data Processed: Monitor configuration and telemetry required to execute customer-configured availability checks: the monitor target, check type and interval, expected-result and DNS conditions, and any HTTP method, headers or query parameters configured for the monitor (which can include credentials a customer places there); response data needed to evaluate the check; results, timings, errors, and operational metadata
Location: Germany 🇩🇪 (European Union)
Note: The node caches monitor configuration and may queue unsent results locally. It does not host the primary customer-account database.
Vultr
Purpose: Regional uptime monitoring infrastructure
Data Processed: Monitor configuration and telemetry required to execute customer-configured availability checks: the monitor target, check type and interval, expected-result and DNS conditions, and any HTTP method, headers or query parameters configured for the monitor (which can include credentials a customer places there); response data needed to evaluate the check; results, timings, errors, and operational metadata
Location: Spain 🇪🇸 and Sweden 🇸🇪 (European Union); South Africa 🇿🇦; Brazil 🇧🇷
Note: The node caches monitor configuration and may queue unsent results locally. It does not host the primary customer-account database.
Kamatera Cloud
Purpose: Regional uptime monitoring infrastructure
Data Processed: Monitor configuration and telemetry required to execute customer-configured availability checks: the monitor target, check type and interval, expected-result and DNS conditions, and any HTTP method, headers or query parameters configured for the monitor (which can include credentials a customer places there); response data needed to evaluate the check; results, timings, errors, and operational metadata
Location: Italy 🇮🇹 (European Union); Japan 🇯🇵
Note: The node caches monitor configuration and may queue unsent results locally. It does not host the primary customer-account database.
DigitalOcean
Purpose: Regional uptime monitoring infrastructure
Data Processed: Monitor configuration and telemetry required to execute customer-configured availability checks: the monitor target, check type and interval, expected-result and DNS conditions, and any HTTP method, headers or query parameters configured for the monitor (which can include credentials a customer places there); response data needed to evaluate the check; results, timings, errors, and operational metadata
Location: Singapore 🇸🇬; Australia 🇦🇺
Note: The node caches monitor configuration and may queue unsent results locally. It does not host the primary customer-account database.
AlphaVPS
Purpose: Regional uptime monitoring infrastructure
Data Processed: Monitor configuration and telemetry required to execute customer-configured availability checks: the monitor target, check type and interval, expected-result and DNS conditions, and any HTTP method, headers or query parameters configured for the monitor (which can include credentials a customer places there); response data needed to evaluate the check; results, timings, errors, and operational metadata
Location: Bulgaria 🇧🇬 (European Union)
Note: The node caches monitor configuration and may queue unsent results locally. It does not host the primary customer-account database.
Self-Hosted First-Party Software
This software is operated by StatusPage.me rather than supplied as a third-party processing service.
Stalwart
Purpose: Primary transactional and notification email service at mail.statuspage.me
Data Processed: Recipient email address, message content, and delivery logs
Operation: Operated by StatusPage.me on Contabo infrastructure in Germany 🇩🇪 (European Union)
Note: Stalwart is first-party operated software, not an external subprocessor. Contabo is the underlying infrastructure provider. Migrated from a United States-hosted iRedMail instance in September 2026.
Sapat.chat
Purpose: Customer support, help desk, and knowledge base
Data Processed: Support messages, account ID, name, email, and conversation history
Operation: Operated by the same owner as StatusPage.me on the same Contabo infrastructure
Note: Sapat.chat is first-party software, not an external processor. Its underlying hosting is covered by the Contabo entry.
Plausible Community Edition
Purpose: Cookie-free analytics for the StatusPage.me public website
Data Processed: Page views and events generated on the StatusPage.me public website, plus referrer and browser or device context. Customer-configured analytics on customer status pages are separate and send data to the endpoint the customer configures.
Operation: Self-hosted by StatusPage.me at stats.brka.io
Note: Plausible Community Edition is not a third-party subprocessor. View our public stats at stats.brka.io/statuspage.me (source: community edition)
Optional User-Directed Services
These services receive data only when a user or customer selects or configures the relevant integration:
- Google OAuth, GitHub OAuth, and Stack Overflow OAuth for user-selected account sign-in when the provider is enabled
- Customer-configured OIDC providers for dashboard SSO
- Customer-configured analytics endpoints for customer status pages
- Customer-configured notification destinations and providers, including Slack, Discord, Microsoft Teams, Telegram, Threema, Google Chat, Mattermost, Rocket.Chat, Pushover, PagerDuty, ntfy, Matrix, ServiceNow, Twilio, Vonage, MessageBird, Esendex, and webhooks
- Customer-directed import providers used to import monitoring or status-page configuration when the customer supplies credentials and starts an import
EU Monitoring Stack
StatusPage.me operates monitoring infrastructure in seven EU locations across six infrastructure providers. These locations form our EU Monitoring Stack and are intended to support EU-only monitoring policies.
| Location | Provider | Region ID |
|---|---|---|
| Frankfurt, Germany | OVHcloud | eu-central-de |
| Madrid, Spain | Vultr | eu-west-es |
| Milan, Italy | Kamatera | eu-south-it |
| Munich, Germany | Contabo | eu-south-de |
| Nuremberg, Germany | netcup | eu-nuremberg |
| Sofia, Bulgaria | AlphaVPS | eu-east-bg |
| Stockholm, Sweden | Vultr | eu-north-se |
This designation applies specifically to where monitoring checks execute. Other subprocessors and optional integrations may process data separately, as disclosed on this page. It is not a statement that all customer data, email delivery, notifications or other processing stays in the EU, and a provider that hosts one EU node is not thereby an EU-only provider.
An EU-only monitoring policy is not described here as a current guarantee; these locations are the basis on which one can be offered. The Monitoring network page remains the canonical, current list of all monitoring locations.
Data Protection & Security
How We Protect Your Data
Provider Terms
We review applicable provider terms and data-protection documentation for the processing relationship.
Encryption in Transit
Public service traffic uses TLS. Provider-specific storage protections are not represented here as a blanket StatusPage.me encryption-at-rest guarantee.
Provider Review
We review providers' published security information and the technical data flow used by StatusPage.me.
International Transfers
When data is transferred outside the EU/EEA, we ensure appropriate safeguards are in place (Standard Contractual Clauses, adequacy decisions).
Changes to This List
We may update this list as we add or remove service providers. Before a new or replacement subprocessor processes personal data, we will give at least 30 days' notice through:
- An update to this page with the effective date
- Email notification to the registered account email address
You may object in writing to a proposed subprocessor before the change takes effect by contacting hey@statuspage.me. We will consider the objection in good faith. If we cannot reasonably accommodate it, you may terminate the affected service before the new subprocessor begins processing your data.
Questions About Our Subprocessors?
If you have questions about our data processing practices or need additional information about our subprocessors, please contact us.