SecDoma

Delete your account

How to request deletion of a SecDoma Cloud account and how deletion differs for organisation-managed and self-hosted accounts.

SecDoma Cloud accounts

Use the account-deletion control available in SecDoma account settings. When an in-app deletion control is unavailable in your current build, email hello@kitechsoftware.com from the address associated with the account.

Include:

  • the account email address or username;
  • whether the account is personal or organisation-managed;
  • the deployment or organisation name, if applicable; and
  • whether you are also requesting deletion of separately controlled support records.

We may require reasonable identity verification before acting on a request. Do not send passwords, recovery codes, identity documents, or message content unless specifically requested through a secure channel.

Organisation-managed accounts

Contact the organisation administrator first. The organisation may control the account, membership, messages, files, audit records, and retention requirements. Leaving an organisation or losing access is not necessarily the same as deleting the underlying account.

An organisation may need to transfer ownership of workspaces, communities, records, or administrative responsibilities before deletion can be completed.

Self-hosted accounts

Contact the operator or administrator of the self-hosted SecDoma deployment. KiTech Software normally cannot delete an account or content stored in infrastructure it does not operate.

What deletion covers

Where KiTech Software controls the relevant information, deletion normally covers:

  • the account profile and authentication relationship;
  • personal settings and device/session associations;
  • content and records that can lawfully and technically be deleted; and
  • supporting service data no longer required for another legitimate purpose.

Information that may remain

Some information may be retained or preserved where necessary for:

  • security, fraud prevention, abuse investigation, or audit integrity;
  • legal claims, court orders, regulatory requirements, or lawful holds;
  • billing, tax, and accounting obligations;
  • backup rotation and disaster recovery;
  • records controlled by an organisation or self-hosted operator; or
  • communications that other participants or organisations have an independent right or obligation to retain.

Where deletion cannot be completed immediately, access will be restricted where appropriate and the information will be removed when the applicable retention requirement ends.

Request another privacy action

Access, correction, objection, restriction, portability, and other privacy requests can be submitted through the Privacy Choices page.