What Observer captures
Observer captures what you configure it to — nothing implicit. Per server, on the Ingestion tab:
Discord
| Switch | Controls | Default |
|---|---|---|
| Channel monitoring | Which channels' messages are read at all | All channels on |
| Messages | Message create / edit / delete events | On |
| Member events | Joins and leaves | On |
| Mod actions | The audit-log firehose: bans, kicks, timeouts | On |
| Voice | Voice-channel presence — who joined or left which voice channel, and when. Never audio; Observer records no voice content. | On |
| Trusted roles | Roles whose messages skip AI screening (still logged) | None |
Custom platforms (REST)
You send events; capture policy is your integration. Whatever you POST is what Observer has — see Send your game's chat. Events carry your channel labels, so per-channel monitoring works there too.
What's screened vs. what's stored
- Events with message text are screened; events without (joins, presence, mod actions) are stored as context only.
- Messages from whitelisted actors or trusted roles are stored in your logs but skip screening.
- Everything captured is visible to your team in Logs — Observer holds no data about your community that your own dashboard can't see.
For how long it's all kept, see Retention & erasure.