Kommit deletes the data you tell us to delete, when you tell us to delete it. There is no soft-archive layer and we do not retain customer data "for compliance reasons" beyond what's described below. This article is also honest about the one piece that is still in build: automated retention enforcement.
Per-object deletion
You can delete most objects from the Kommit dashboard directly:
- —Workflows: deleting a workflow removes its definition and configuration. Its past runs stay in the run log — see "Why the run log is different" below.
- —Documents and uploaded files: removed from the application DB and from object storage.
- —Members: removing a member revokes their session immediately and removes their membership row. Their authored actions remain in the run log, but the member's profile is no longer linked.
Whole-organization deletion
A hard org-delete from the Settings page cascades through every tenant-owned table — workflows, runs, projects, support transcripts, audit logs, and embedding stores. Nothing is archived under a different name; the rows are gone from Postgres on commit.
Backups containing the deleted data are aged out according to the backup retention policy below.
Backup retention
| Backup type | Retention | Why |
|---|---|---|
| Postgres daily snapshot | 30 days | Standard operational rollback window. |
| Postgres point-in-time WAL | 7 days | Allows recovery to any second in the last week. |
| Object storage snapshot | 30 days | Aligned with the DB snapshot retention. |
A deleted org's rows persist in the most recent snapshots for the retention window above and then age out automatically.
Automated retention: what's enforced today
You can set retention values in the product, and they are stored —
but the automated deletion job that enforces them is still in
build. Until it ships (it's on the public /roadmap and
tracked on /trust), enforcing a retention window means
deleting the data yourself from the dashboard, or asking us to do it
via security@getkommit.ai. We'd rather tell you that plainly than
let a settings screen imply enforcement that isn't running yet.
Why the run log is different
The run log is the one surface where data is not deletable entry by entry. Editing or removing individual past entries would defeat the point of a trustworthy record of what your automations did.
If you delete the organization, the run log goes with the cascade. But individual entries are not editable or removable from the dashboard or the API. See [#exporting-audit-logs] for how to pull a copy out before deletion.
GDPR / data-subject requests
If a data subject asks you to delete data Kommit holds about them,
you can perform the deletion yourself for any object except the run
log. For the run log, contact security@getkommit.ai and we will
work through the regulator-acceptable approaches with you (typically:
retain the integrity record, erase the personal content). See
[#gdpr-support] for the broader posture.