Uptime checksHTTP, keyword and TLS checks on your addresses, with the evidence of every failure kept.
Cron heartbeatsOne curl line at the end of a job. Silence past the grace window is the alert.
Status pagesA page your customers read, on your own domain, with the incident in plain words.
ExplanationsA written reason with the alert: what failed, what the checks saw, what to look at first.
on every plan Alerts to six channelsImportTeams
APIRead, pause, acknowledge and post updates from your own scripts.
MCP serverAsk your AI assistant what is down, then acknowledge or post an update.
WebhooksSigned JSON when an incident opens, is acknowledged or recovers.
Heartbeat guidescrontab, GitHub Actions, Railway, Node, Go, WordPress and Kubernetes.
DocsShort guides, each one task, with the lines to copy.
GuidesWhy monitors send false alarms, why cron jobs stop, and the fix.
ChangelogThe big things we shipped, newest first.
Trust and securityWhere your data lives, who processes it, how long we keep it.
Referral program soonRecommend Upglory to another team. In the works.
Contact

What we do with your data.

We hold no certification and will not imply one. What we can do is say exactly what we store, where it sits and who else touches it.

the app, the database and the backup
in the order you will ask

Six answers you can check.

Each one is written so it can be checked against the product or a document we will send you.

  1. Where your data lives

    Monitor configuration, check results, incidents and the notes you write are kept by our cloud hosting provider. The privacy notice says where personal data is processed and lists the kinds of provider that process it.

    kept by our cloud hosting provider
  2. What we store about you

    Your email address, the name you typed, your time zone, the workspaces you belong to, and a record of your sign-ins. No payment card ever reaches us: payments and invoices are handled for us, by a company that holds your billing details and issues your invoice.

    no card data · sign-in log 30 days
  3. What the evidence keeps

    A check that passes keeps its figures: the status code, the timings, and whether the keyword was found. A check that fails keeps more, because that is what an explanation is written from: the response headers we allow, a short excerpt of a failing response, the DNS answer and the TLS state. It is shown on your incident page and is never published to a status page.

    figures always · an excerpt only when it fails
  4. Who can see it

    The people who run Upglory, and only to answer a support request or fix a fault. We do not read your data to build features, and nothing is used to train a model.

    support and faults only
  5. Export and deletion

    Deleting a workspace or an account offers you an export of what it holds first. Everything stops at once. A workspace's data is removed after seven days and an account's at once, and both are out of our backups within six weeks, as the privacy notice states. The one exception is invoices, which are kept by our payment provider, as the seller, for as long as Bulgarian law requires.

    export offered before deletion
  6. How we are told when we break

    Every error on our side is reported to us the moment it happens, with a reference you can quote to support so we find the request. Every incident of ours gets three sentences: what broke, what was unaffected, what changed so it does not happen the same way.

    errors reported as they happen
who else touches it

Processors, by kind.

Each kind is described on the privacy notice; the data processing agreement says how we process your data, and workspace owners find the names, with dates, in Settings.

  • Hosting servers and backups
  • Email delivery the emails we send
  • Payments card data never reaches us
  • Error reporting request id and path only
  • Analytics cookieless, public pages and one count per new workspace
  • AI explanations one incident per request
check locations listed by the product
  • Frankfurt Germany, on every plan
  • Stockholm Sweden, on every plan
  • Ohio United States, on every plan

A check location holds no data; every result is written back to the database. The signed agreement comes from [email protected], and anything you find goes to [email protected].

Read the notice, then start.

The privacy notice says who else touches your data, and why. Free needs no card.

Start free
the app, the database and the backup