Support

No. Uptime Guard has no accounts, no sign-up and no cloud backend. All of your monitors, history and settings live only on your device, in a database encrypted with SQLCipher whose key is held in platform secure storage (Apple Keychain / Android Keystore).

Work through these steps:

• Confirm notifications are allowed for Uptime Guard in your device settings.
• Make sure a Focus or Do Not Disturb mode isn’t silencing the app.
• Open the app once — it runs a catch-up check on launch and will alert you if a site is currently down.
• On Android, exclude the app from battery optimization so background checks aren’t deferred.

Because Uptime Guard runs entirely on your device with no server, background checks happen only when the operating system lets the app wake up:

• Android uses WorkManager with a ~15-minute minimum; it is reliable but can be delayed by Doze mode and battery optimization.
• iOS uses BGTaskScheduler, which is opportunistic — the system decides when to run the task based on your usage patterns and battery. It is not guaranteed to run hourly when the app is closed.

The app always runs a catch-up check when you open it and shows an honest “last checked X ago” timestamp so you know how fresh the data is. For near-real-time checks on Android, enable Real-time mode (below). Guaranteed 24/7 monitoring while the app is closed would require a server.

Real-time mode (Android, opt-in) runs a foreground service that re-checks every monitor every 1–5 minutes with a persistent status notification. It trades some battery for genuinely near-real-time alerts. iOS does not permit this kind of long-running background service for a monitoring app, so the feature is Android-only.

Domain registration expiry is fetched via RDAP — a keyless, public registration-data service — about once a day per site. SSL/TLS certificate expiry is read directly from the site. Both send you escalating alerts at 30, 14, 7 and 1 days before expiry so a domain or certificate never lapses unnoticed.

Yes. You can import a Postman collection (.json) or paste a cURL command (from browser DevTools, docs, or Postman’s “Copy as cURL”). Fill in your variables and credentials — which are stored encrypted on device — and the app runs the requests on a schedule, alerting you when a request starts failing. You can mark one request as a login call and inject the returned token into later requests for auto-login.

Domain Health is a professional, MxToolbox-style report covering DNS (A record, name servers, SOA), Email (MX, SPF, DMARC, DKIM), blacklist screening (Spamhaus, Barracuda, SpamCop, SORBS, Abuseat CBL), and web/SSL reachability and certificate validity. A few SMTP-level checks (PTR, banner, open-relay, TLS) are honestly marked “not available on device” because they require outbound port 25, which mobile networks block.

The app contacts only (1) the sites and endpoints you add, for checks and diagnostics, (2) Google Public DNS and the public RDAP service when you use the DNS Lookup or Domain Health tools, and (3) any alert channel you set up yourself. There are no analytics, ads, tracking or crash-reporting SDKs. Full details are in our Privacy Policy.

Yes. In Settings you can enable a biometric or device-credential lock (Face ID, fingerprint or device PIN) so only you can open the app.

The app can export your data to a file, which you can save or share via your device’s share sheet. Because there is no cloud sync, this export is how you move data to a new device. Keep exported files safe — they contain your monitoring data.

You are always in control: delete an individual monitor, incident or history entry from within the app at any time. Uninstalling the app removes its encrypted database and the encryption key from your device, permanently deleting everything the app stored.