Audit logging & integrity

Operational security events are recorded for forensics and governance.

Logs support investigations; they do not by themselves prove legal compliance. Tamper evidence reduces undetected alteration of new rows — it does not replace WORM hardware or court-grade evidence procedures unless paired with broader controls.

What we log (examples)

API abuse signals (rate limits, CORS rejects).
Key lifecycle events (rotation/revocation).
Capture accept/reject and billing sync milestones.

Tamper evidence

Every new audit record is cryptographically sealed against the records that came before it, so any later edit, deletion, or reordering becomes detectable. The result is independently verifiable: a reviewer can confirm that a run of records is intact without having to take our word for it.

At extreme write volumes, the strict ordering of simultaneous records is not guaranteed. Where sequence itself has to survive a contested proceeding, pair the audit trail with serialized ingestion or an external immutable log.