Subprocessors

Last updated: September 17, 2026

Uptimeify (Zaskoku & Haupt GbR) uses certain third-party subprocessors to assist in providing our services. A subprocessor is a third-party data processor who may have access to personal data of our customers or their end-users in order to provide services to Uptimeify.

This page provides information about the identity, location, and role of each subprocessor we use. We will update this page from time to time to reflect changes in our subprocessors.

Where we watch them

Most of the providers on this page publish their own availability, and we read it: they appear on our dependency status page alongside the other services we track. Four do not appear there, and the reason is the same in each case: there is nothing machine-readable to read. easybell publishes a plain web page and nothing else; LOX24's status address does not resolve at all. fastmon and Tuta publish data, but through undocumented, single-purpose endpoints that could change without notice. Tuta's even carries a report ID in its path, and the page shows no incident history at all. We would rather show nothing than show something we cannot stand behind.

Service Subprocessors

These providers are involved in operating the Uptimeify platform itself. Monitoring Data indicates whether customer account data or monitoring data (e.g. monitored URLs, check results, alert contents, notification recipients) is processed by this subprocessor to deliver our services.

Business Operations

These providers support our internal business operations. They do not process monitoring data.

Mobile Apps (optional)

Our iOS and Android incident management apps are optional. You do not need them to use Uptimeify: alerts still reach you by email, SMS, voice call, webhook and through the integrations you configure.

If you install an app and enable push notifications, delivery necessarily runs through your operating system vendor's push service. There is no other route to an iOS or Android lock screen. For that case, these providers act as subprocessors of Uptimeify.

What we transmit: the push carries a wake signal, an alert identifier, the severity, a signed acknowledgement token and the alert text in encrypted form. Your device generates a key pair when it registers and tells us only the public half; the private half never leaves the device. Apple and Google therefore carry a block they cannot open, and receive no monitoring data from us. Decryption happens on the device before the notification appears; with no key registered, the lock screen shows a generic line.

This section takes effect on 30 September 2026, together with the release of the apps. Until then Uptimeify sends no push notifications and no data reaches either provider.

If you do not install an app, or if you disable push notifications, no data is transmitted to these providers.

Downloads from the App Store or Google Play happen outside our reach. Apple and Google process the resulting data such as store account, downloads and device model under their own responsibility. For that they are not subprocessors of ours but controllers in their own right. See our privacy policy for details.

Optional Integrations

Uptimeify lets you connect third-party services to receive alert notifications. These integrations are optional and only become active when you configure them yourself. When you connect an integration, alert data (e.g. monitor name, status, error details) is transmitted to the provider you chose, under your own agreement with that provider. They are therefore not subprocessors of Uptimeify.

Slack

Discord

Telegram

PagerDuty

Pushover

Opsgenie

All Quiet

Matrix

Jira

Google Chat

Mattermost

Rocket.Chat

ntfy

Gotify

ilert

Grafana OnCall

incident.io

Squadcast

GitHub

GitLab

Linear

ServiceNow

Lark

DingTalk

WeCom

Custom Webhooks

International Data Transfers

Our core infrastructure is hosted exclusively in the European Union. For any transfers of personal data outside the European Economic Area (EEA), we ensure appropriate safeguards are in place through:

• Adequacy decisions (where the European Commission has determined that a third country ensures an adequate level of protection)
• The EU-US Data Privacy Framework (DPF) for certified US providers
• Standard Contractual Clauses (SCCs) approved by the European Commission
• Additional technical and organizational measures to protect personal data

Updates to Subprocessors

We may update our list of subprocessors from time to time. We will notify customers of any new subprocessors in accordance with the terms of our Data Processing Agreement.

All changes to our infrastructure and subprocessors are also published in our infrastructure changelog. Subscribe to its RSS feed to be notified automatically.

Objecting to Subprocessors

If you are a customer of Uptimeify and wish to object to a new subprocessor, please contact us promptly at hello@uptimeify.io. If we determine that your objection is reasonable, we will work with you to find a mutually acceptable resolution. If we cannot reach a resolution, you may terminate your agreement with us in accordance with the terms of your contract.

If you have questions or concerns about any of our subprocessors, please contact us at hello@uptimeify.io.