Privacy-first community cleanup that stays fair.
The default CleanerBot configuration. Keep communities active with transparent inactivity tracking. No message content reading. No privileged intents.
"Does the bot read messages?"
What you’re optimizing for
- A clean user list that reflects actual activity.
- Minimal setup time with sensible defaults.
Common pain points
- Lurkers who never participate.
- Difficulty managing roles for inactive members.
Quick Start (Standard)
Select Quick Start (Standard) during /start.
Core Behavior
- Operating Mode
- Standard (Public warnings enabled)
- Timeline
-
Warning 21 days (~3w)Mark Inactive 42 days (~6w)Kick Eligible 89 days (~3mo)
- Auto-kick
- Off
Signals & Actions
- Activity Signals (ON)
- Messages, reactions, voice, interactions, typing, threads, rsvps, cta_button.
- Engagement
- Polls OFF (Quizzes ON), CTA Button ON.
- Streaks are enabled for highscores, but no reward roles are configured by default.
Suggested Channels & Roles
Why CleanerBot fits this use case
This is our most balanced preset. It keeps members engaged with occasional nudges and "I'm active" buttons, but doesn't spam. It respects privacy by design and requires no special permissions.
How to run the standard preset well
This privacy-first path is built for balanced communities: clear nudges, manual review, and no surprises. Treat it as a steady default and only tighten it once you see consistent review habits.
These default thresholds are long enough to be fair across most community rhythms. They work especially well when you publicly explain the timeline and point people to one simple “I am here” action.
Keep removals human. The standard preset assumes auto-kick is off and that staff decides. That fits the fairness positioning in the target group analysis: people accept cleanup policies when they can see how to recover and when the decision path is predictable.
For a weekly pulse on community drift, add the Activity Health Score.
Good operational pattern
- Post warnings in one visible channel.
- Use a single status role for “needs attention”.
- Process the review queue on a fixed weekday.
When to adjust
- Shorten only after two full review cycles.
- Expand signals before tightening timelines.
- Announce changes with a clear reason.
Related reading: Auto-kick guardrails, inactivity policy template.
Common Questions
Can I customize this later?
Yes. This is just a starting point. You can change every single threshold and setting via /config after the initial setup. A good pattern is to run the defaults for a few weeks, then adjust based on what staff repeatedly agrees on during reviews.
Does it track voice?
Yes, voice activity is enabled by default in the Standard preset. This helps avoid penalizing communities where people mostly hang out in voice instead of typing.
Will it auto-kick people?
No. Auto-kick is disabled by default in all presets. You must manually enable it or use the manual review channel to kick users. This keeps the Standard preset aligned with a fairness-first approach where staff decisions come before automation.
What counts as activity in the Standard preset?
CleanerBot focuses on signals that are easy to explain: recent participation and, in this preset, voice presence. The goal is not to score people perfectly, but to identify members who have gone quiet long enough that a gentle nudge or review is reasonable. If you want the exact definition your staff will see, open /config and review the activity signals section before you announce the policy.
How often should staff review the inactive list?
A steady weekly review rhythm works well for most servers using the Standard preset. It keeps the process predictable without turning it into daily moderation work. If your community runs seasonal events or breaks, consider pausing automated actions during those periods and restarting reviews once activity patterns normalize.
How do I explain this policy without causing drama?
Keep the message short and procedural: explain the timeline, where nudges appear, and how members can signal they are still around. The most important piece is clarity about what happens next: staff review comes first, and any removal decision is human. If you need a starting point, adapt the inactivity policy template and link it in your rules or onboarding channel.
When should we tighten or loosen the defaults?
Wait until you have a few weeks of consistent reviews. Tighten the timeline only if staff repeatedly agrees that the review list contains members who have clearly disengaged. Loosen it if you see too many edge cases or frequent appeals. If you ever consider enabling automatic removals, read it carefully first and align on safeguards in auto-kick guardrails before turning anything on.
Invite CleanerBot, run /start, and publish a short, transparent inactivity policy in your rules channel.
Quick Actions
Invite CleanerBot Join Support Server Ask CopilotCopilot opens in ChatGPT (external).