Two API calls around your own deletion, and a verification record anyone can check without trusting us. Everything here is public — no account needed to read, and none needed to verify.
BurnLedger never touches your data. You connect a read-only credential, attest that a record exists, delete it with your own tools, and BurnLedger verifies that it is gone and issues a signed verification record. The docs are split by what you are trying to do: get a first verification record issued, look up an exact field or endpoint, wire up a specific database or object store, or understand what deletion evidence means before you build anything.
If you were handed a verification record and only want to check it, skip straight to Verify a record — it works in the browser, offline with the CLI, or against the public transparency log, and none of those need an account.
