Preparation only

Secure Audit Log Readiness

Future Messenger and WhatsApp events need safe audit trails before any live reply is allowed. This page explains the preparation model for Australian property-agent teams without storing customer data.

No live audit database is active. No Supabase migration exists for this page. No token storage, no customer data stored, and no raw message logging.

Current safe state

  • No live audit database.
  • No Supabase migration.
  • No token storage.
  • No customer data stored.
  • No raw message logging.
  • AI reply OFF.
  • Outbound queue OFF.
  • Human review required.

Future safe audit categories

  • Disabled route checks.
  • Webhook fail-closed decisions.
  • Tenant mapping decisions.
  • Unknown connection quarantine decisions.
  • Disconnected or revoked connection ignores.
  • Outbound reply blocked events.
  • AI reply blocked events.
  • Owner and App Review gate reminders.

Future requirements

Owner-gated before persistence

  • Audit table owner gate.
  • Redaction before persistence.
  • Tenant/channel reference hashes.
  • Disconnect/revocation audit events.
  • Owner-visible evidence without secrets.
  • App Review/internal test evidence.

Forbidden by default

Never store sensitive values in audit evidence

  • No tokens or env values.
  • No raw phone numbers or customer names.
  • No raw Page IDs or raw phone number IDs.
  • No signatures, headers, cookies, or payload dumps.
  • No Graph or WhatsApp API response bodies.
  • No full message text.

RED / HARD STOP gates

  • Supabase schema migration.
  • Audit table creation.
  • Production database write.
  • Customer data access.
  • Token storage implementation.
  • Env insertion.
  • Real OAuth.
  • Graph API or WhatsApp Cloud API.
  • n8n live connection.
  • AI reply enablement.
  • Live Messenger or WhatsApp messages.