Retention
What WhaBuzz stores, for how long, and how retention controls the replay window.
#What is kept
| Data | How long |
|---|---|
| Event metadata (id, type, timestamps, wamid, wa_id, number) | Forever |
Event bodies and the raw Meta payload | Your retention_days, then removed |
| Webhook delivery records and attempts | 13 months |
| Media bytes | Never stored. Streamed through. |
| Business access tokens | Until you disconnect the number; stored encrypted |
#Your setting
retention_days is one of 30, 90, 180 or 365, default 90. Change it with PATCH /v1/tenant. A shorter value removes older bodies at the next cleanup; a longer one only applies to events from now on.
Under the hood events live in monthly partitions that are dropped at 13 months.
#Replay window
An event can be replayed only while its body exists, so the replay window equals your retention. Replaying older events answers 404 not_found with details.reason: "payload_expired". See Webhooks.
Read the log yourself with GET /v1/events and GET /v1/events/{event_id}.
#Customer data
Message bodies contain your customers' personal data. Choose the shortest retention that serves you, and mirror what you need into your own system from the webhook.
This page as Markdown: /guides/retention.md. All docs in one file: /llms-full.txt.