A record an auditor can check
Every step of every DROP cycle is an entry in an append-only log. Each entry stores a SHA-256 hash of its content and of the entry before it, so editing or removing one breaks the chain. Export it with each batch's statuses as one evidence packet.
Evidence log · chain intact
- #000410
batch.downloaded3 lists, 3,066 work itemsa41c…07e2 - #000411
batch.matched404 single, 2 multiple (browser)9f3a…c118 - #000412
batch.confirmeddeletions confirmed by M. Ortiz2be7…5d90 - #000413
drop.upload3 files accepted, 0 rejectede06d…41ab
What is logged
Downloads with the ZIP's own SHA-256, matches, exemptions with their legal basis, deletion confirmations with who and when, every upload and DROP's reply.
Checked on export
Each export re-computes every hash. The README in the packet says whether the chain is intact or names the first entry where it breaks.
Six years
The Delete Act asks for audit records to be kept at least six years. Keep the packets in your own archive too, so the record never depends on one vendor.
Plans: every plan. See pricing
What is in an evidence packet
| File | What it holds |
|---|---|
README.txt | Workspace, registered broker name, when it was made, and whether the audit chain is intact |
audit_log.csv | Every event: sequence, time, person, action, detail, previous hash, hash |
work_items.csv | For a batch: each work item, its list, match count, status, exemption basis and when it was sent |
submissions.json | Each upload to DROP and DROP's reply |
batch.json | The batch: file name, download time, report-by date, the ZIP's SHA-256 and a status summary |
The first independent audits start on 1 January 2028. The audit guide sets out what an auditor is likely to test.
Questions
Something else? Write to us and a person answers within one working day.
Is the log tamper-proof?
Who can see the log?
Can we export everything at once?
The rest of the product
Answer your next DROP batch on time
14-day trial on every plan. Run the practice batch first if you like.