demotest installation

Delete account

Last updated 30 September 2026.

This page explains what deleting an account means on Kaudata Monitoring, which KAUDATA d.o.o. runs, and how to ask for it.

If you read the status page

You have no account. The status page needs no sign-in and the application stores nothing that identifies you, so there is nothing to delete. The servers that pass requests to the application keep access logs, which include IP addresses, for 30 days, as the privacy page describes.

Status page subscriptions

Email subscriptions to the status page are not built yet, so the service holds no subscriber addresses.

If you have an account

You ask for your account to be deleted from inside the console or the app:

  1. Sign in, open Settings, and choose Request deletion under Delete this account. In the app, open Account and choose Request deletion.
  2. Another operator completes or rejects the request by hand. Until then your account works as usual, and you can withdraw the request in Settings or in the app.
  3. While your account exists, Settings and the app show where the request stands, including the reason if it was rejected. When the request is completed, each phone with alerts on gets one last notification saying the account has been deleted, and a phone that asked shows the outcome on its sign-in screen. We do not send email about it.

If you are the only operator, nobody else can process the request, so you complete it yourself on the console’s Deletion requests page, after typing your account’s address to confirm.

If you can no longer sign in, for example because you lost your password or your second factor, write to [email protected] from the address on the account, and we handle the request by hand.

We act on a request without undue delay and in any event within one month of receiving it. That period may be extended by two further months where necessary, taking into account the complexity and number of requests. If it is, we tell you within one month of receiving the request, with the reasons for the delay.

What is deleted

Completing a request deletes your account together with its password, every session it holds, its two-factor enrolment and its backup codes, all in one step, and every phone registered to it, once that last notification has been sent, at the latest 24 hours after completion. A browser or phone still signed in to the account loses access at its next request.

What deletion does not remove

  • The audit record of what the account did in the console, including asking to be deleted. Each entry keeps the email address the account had at the time and a shortened browser user agent, and no IP address. It is not deleted with the account, because an audit trail that the person it describes can erase no longer shows who changed what.
  • The record of the deletion request itself: the account’s identifier and email address, when the request was made and closed, who processed it, and the reason if it was rejected. It is the evidence that the request was handled.
  • Incidents, incident updates, maintenance windows and paused monitors that were linked to the account. They stay, with the link removed.
  • Your address on the console’s allowlist, which is part of the service’s configuration. It stays there until an operator removes it from the configuration. Without an account, the address alone cannot be used to sign in.

There is no automatic deletion for audit records or deletion requests yet, so at present they are kept without a time limit. Apart from these, the service holds nothing else about an operator. It watches machines, so there is no profile, usage history or other content to keep.