Privacy Policy

Last updated: 22 October 2026

The short version

• KumaAlert works fully without our servers. Connect to your Uptime Kuma server, watch your monitors, use widgets and the Apple Watch, and nothing is stored on KumaAlert's servers.
• You choose a privacy mode: Full, Local only, keep push, or Local only, where nothing about your device is kept on our servers. Change it any time in Settings › Privacy.
• Synced server passwords, tokens and API keys are always encrypted. By default our servers hold the key, unlocked by your Apple or Google sign-in. Turn on end-to-end encryption and only your devices hold it.
• No ads, no analytics, no tracking. Crash reports are off unless you turn them on. We never sell or share your data.

Stored only on your device

Whatever you choose below, these stay on your device:

• Server credentials (username, password), login tokens and API keys, in your device's secure keystore (iOS Keychain / Android Keystore)
• Server addresses, monitors and heartbeat data, in the app's local database
• Widget and Apple Watch data, in a container shared only between KumaAlert's own app and extensions

The app talks directly to your own Uptime Kuma server(s). Nothing passes through us to do that.

Optional: stored on KumaAlert's servers

Our servers run on Cloudflare. What they hold depends on the privacy mode you choose in setup. You can change it any time in Settings › Privacy.

• Full: push alerts, outage history, and optional account sync (sign-in is only available in this mode).
• Local only, keep push: push alerts only. No outage history and no account (you are signed out). We keep only what delivering alerts needs, listed under Push alerts below: your push token, device model, OS version and app version, alert settings, snooze and acknowledge state, Live Activity outage details while a monitor is down, and a 30-day delivery log of random IDs.
• Local only: nothing about this device is kept on our servers. If you chose to keep your account for your other devices, the account stays until you delete it, but this device is no longer part of it. There are no alerts at all in this mode; check status in the app and widgets.

Push alerts

To deliver an alert when your phone isn't open, your Uptime Kuma server sends a webhook to our push relay, which forwards it through Apple (APNs) or Google (Firebase Cloud Messaging). For this we store:

• A random device ID and the push token Apple or Google gives your device
• Your notification settings: which alerts you want, sounds, quiet hours, per-monitor overrides
• Whether you have snoozed or acknowledged an alert, so repeat alerts stop when you deal with it
• Device model, OS version and app version, used only to fix delivery problems
• A delivery log recording whether each alert arrived, identified only by random IDs (never server or monitor names, and never the alert text), deleted automatically after 30 days
• While a monitor is down, the details needed to keep its Live Activity up to date, deleted when it recovers

Outage history

Outage history is kept only in Full mode. In Full mode, we keep a record of your outages so the history survives a reinstall and matches on every device. We store:

• Monitor names and their current up/down status
• When each outage started and ended, and the error message Uptime Kuma reported (which can include the hostname or IP of the thing being monitored)
• Any notes or acknowledgements you add to an incident

Servers are identified by a random ID, never by their address. Switching to either Local only mode deletes this device's outage history from our servers and stops anything new being stored for it. If you are signed in and choose to keep your account, the account's history stays for your other devices; it is deleted when you delete the account.

Account sync

Signing in with Apple or Google is optional. It creates a free account whose only job is to sync your setup between devices. We store:

• Your account ID from Apple or Google, and the email address they share with us (Apple lets you hide it)
• Your servers, credentials and app preferences, encrypted. With Standard sync (the default) we also keep the encryption key, itself encrypted, so any device you sign in on can unlock your data. That means our servers could technically decrypt it; we never do, and nothing is ever logged or shared.
• With end-to-end sync (Settings › Account › Sync encryption) we delete our copy of the key: it lives only on your devices, and we hold ciphertext we cannot read. We store your recovery key only in encrypted form, locked by a code only you have.
• The public keys your devices use to pass the encryption key to each other in end-to-end mode
• Your notification settings and monitor order, so they follow you between devices

Diagnostics

If you tap Send diagnostics in Settings, the app uploads a bundle of app logs and settings so support can look into a problem. Passwords and tokens are stripped from the logs before they are even saved on your device. It is only ever sent when you tap the button, and it is deleted after 7 days.

Support messages

If you write to us with the contact form in Settings, your name, email address and message are sent to our support inbox so we can reply. If you choose to attach diagnostics, the bundle described above is uploaded too.

What we never store

• Your Uptime Kuma passwords, login tokens or API keys in readable form
• The addresses of your Uptime Kuma servers, unless encrypted inside account sync
• Heartbeat data, response times or anything about your monitors beyond what's listed above
• Your location, contacts or anything else on your device
• Advertising IDs, analytics or usage tracking. Crash reports, if you turn them on, contain no server addresses.

Deleting your data

• Push alerts: switch to Local only in Settings › Privacy. The app removes its webhook from the Uptime Kuma servers it can reach (and tells you about any it couldn't), then deletes everything our servers hold for this device: its registration, alert settings, outage history and delivery log. If you just delete the app, the relay deletes the device's record once Apple or Google report its push token as no longer valid.
• Outage history: switch to either Local only mode in Settings › Privacy and this device's history is deleted straight away. An account's history is deleted when you delete the account.
• Account: sign out to unlink a device. While signed in, Settings › Privacy › Delete my account removes your account, synced servers and outage history, for every device. You can also email us at help [at] kumaalert.app from any address and tell us which Apple or Google account you used.

Third-party services

• Cloudflare hosts our servers and this website
• Apple Push Notification service and Firebase Cloud Messaging deliver push alerts, only if you turn them on
• Sign in with Apple and Google Sign-In, only if you create an account

The app includes no analytics, advertising or tracking SDKs. It includes the open-source Sentry SDK for crash reports, which runs only in the Full privacy mode and never in either Local mode (Settings › Privacy), and sends only to our own self-hosted server. Before a report leaves your device, server addresses, web addresses and your device's relay ID are removed.

This website

This website counts visits using Traks, our own analytics on our own servers. It sets no cookies, records no personal data, and cannot identify you or follow you to other sites. It is not connected to the app or to your monitors.

Children's Privacy

We do not knowingly collect any information from children under 13.

Changes

We may update this policy from time to time. Changes will be reflected on this page with an updated date.

Contact

If you have questions about this privacy policy, contact us at help [at] kumaalert.app.