Audit logs

Audit history is Landing Zone's tamper-resistant record of what happened in your workspace. Entries are immutable — written once and not editable — so they can serve as evidence of process when questions come up later.

What gets recorded#

Audit entries are written across compliance, messaging, calls, billing, and outreach activity, and they are retained. Compliance events are the ones that matter most here: for example, when a contact replies STOP, the opt-out is handled and an audit entry is written alongside the suppression and consent change.

One honest nuance: not every product control produces a per-contact audit entry. The 30-day SMS cooldown, for instance, surfaces as an exclusion tally in the batch pre-send preview rather than as individual audit entries. See Repeat-contact cooldowns.

Access today#

There is no dedicated audit-history viewer screen in the app yet. The entries are recorded and retained on the platform side. If you need audit records — for example, to respond to a dispute — contact support@landingzone.co.

How audit history supports compliance work#

• Dispute response. When someone claims they were contacted after opting out, the timeline matters: when the STOP arrived, when suppression was applied, what was sent and when. Immutable entries let you reconstruct that sequence instead of arguing from memory.
• Recordkeeping. Audit history complements your consent records and the records you keep outside the platform, giving you a durable account of what your workspace did and when it did it.

What it does not do#

An audit trail demonstrates process — it shows what happened. It does not make what happened lawful. A complete, clean audit history of a send does not establish that the send was permitted, and the absence of a red flag in the log is not a clearance. The decisions the log records remain yours, as described in User responsibilities.