Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(risk): note throttle keys and chat purges resetting pacing

Yudhi Armyndharisb1f5e1c5fefc
diff --git a/docs/16-risk-management.md b/docs/16-risk-management.md
index c5cd88b85..6125b108e 100644
--- a/docs/16-risk-management.md
+++ b/docs/16-risk-management.md
@@ -130,7 +130,8 @@ session's age (`SEND_PACING_WARMUP_SCHEDULE`), a separate cap on new conversatio
(`SEND_PACING_COLD_DAILY_CAP`) and a consecutive-failure breaker — see
[06 §Send pacing](./06-api-specification.md). It is **off by default**, and it counts only sends that
write a `messages` row, so status posts and message edits are checked against the cap without
-counting into it.
+counting into it. Clearing or deleting a chat removes its stored rows, so that chat's sends today
+stop counting toward either cap, and the next send to it counts as a new conversation.
Still not implemented: there are no per-minute or per-hour caps and no media-specific delay. With
pacing off — the default — the guidelines below are operator discipline, not something the gateway
@@ -533,7 +534,7 @@ WhatsApp has undocumented internal rate limits. Sending too many messages can tr
**Built-in Safeguards:**
The gateway enforces HTTP request throttling (`@nestjs/throttler`, registered globally as
-`ProxyAwareThrottlerGuard` and tracked per client IP) plus the bulk-send pacing described in R002:
+`ProxyAwareThrottlerGuard` and tracked per route handler and client IP) plus the bulk-send pacing described in R002:
| Control | Default | Scope |
| ----------------------------------------------------- | -------------------------- | ------------------------------------------------------------- |