The audit trail and integrity seal

Everything that happens to a request is written to the audit trail: submission, verification, every task created and completed, every message, sign-off, delivery, refusal, appeal, and closure, each with who did it and when. Actions by your team, by the requester, by data source contacts, and by the system itself are all recorded.

Why it matters

When a regulator or complainant asks "show me how this request was handled", the audit trail is the answer. It reconstructs the request end to end without relying on anyone's memory or inbox.

The integrity seal

Audit records are cryptographically chained: each entry is linked to the one before it, and the chain is sealed automatically every night. The result is tamper-evident. If any historical entry were altered or deleted, the chain would no longer verify.

Under Settings, then Audit integrity you can run a verification at any time. It recomputes the chain and confirms the trail is intact, and you can run it in front of an auditor.

What you should do

Nothing, day to day. The trail writes itself. The two habits worth building:

• Record reasoning in case notes at judgement moments (why you refused, why you kept some data back on an erasure, why you were satisfied with identity). The trail proves what happened. Your notes prove why.
• Run the integrity check as part of any periodic compliance review, so "verified regularly" is itself on the record.