Deleting & tombstones

Deleting an entry in Clavitor does what you expect — and keeps a provable record that it happened.

How to delete

1. Open the entry. 2. Click Delete. 3. Confirm.

The entry disappears from your vault list and stops resolving — agents and integrations can no longer fetch it, autofill won't offer it, search won't return it. To you and to anything connected to the vault, it's gone.

What actually happens

Instead of erasing the entry, Clavitor writes one final revision — a tombstone — that marks it deleted, with the time of deletion. The entry's earlier revisions stay exactly where they were.

This is deliberate. A deletion that leaves no trace is indistinguishable from a deletion that never happened — which is precisely the gap an attacker, or a dispute, exploits. A tombstone turns "it's gone" into "it was removed, on this date" — a fact you can stand behind.

Seeing a deleted entry's history

A deleted entry's history is preserved. In the audit log you'll find the deletion event — who removed it, when, and which revision the tombstone is — linking the removal to the exact point in the entry's history.

Truly removing data

Because history is permanent by design, there is no per-entry "shred this and its past." When data genuinely must be destroyed — a legal erasure request, an account closing — removal happens at the whole-vault level, not by surgically editing history. This keeps the "nothing is overwritten" guarantee intact: the vault never quietly rewrites its own past, not even to delete. See Limits for the full picture.