Copy and policy guide
Inactivity cleanup works best when members understand the policy before anything happens. Use these copy-ready blocks for rules, announcements, onboarding, or staff replies.
Keep the tone calm. Decay is not a punishment.
Without explanation, inactivity cleanup can feel personal or sudden. A good policy tells members what counts as activity, when warnings happen, what an inactive role means, whether removals are reviewed by staff, how members can recover, whether CleanerBot reads message content, and who to contact if something looks wrong.
Avoid wording that sounds punitive, invasive, or absolute.
We use CleanerBot to keep the server healthy and fair. CleanerBot uses an inactivity score called Decay Score. The score rises when a member has no configured activity and drops or resets when they participate again. Our process is: - friendly warning first - inactive role if inactivity continues - staff review before any removal CleanerBot does not read or store message content. It only uses configured activity signals such as messages, reactions, voice, threads, commands, buttons, or events. Use /my_score anytime to check your own status. If something looks wrong, contact staff.
Hey everyone, quick note from the staff team.
We use CleanerBot to manage inactivity fairly and transparently. The goal is not to punish quiet members. The goal is to keep our roster, roles, and member access accurate.
CleanerBot uses an inactivity score called Decay Score:
- Everyone starts safe.
- The score rises when there is no configured activity.
- The score drops or resets when you participate again.
- Staff uses clear checkpoints before taking action.
What counts as activity here:
{ALLOWED_SIGNALS}
Our checkpoints:
- Warning at score {WARNING}: friendly heads-up.
- Inactive role at score {INACTIVE_ROLE}: your status may be marked inactive.
- Review at score {KICK}: staff reviews whether removal makes sense.
Auto-kick:
{AUTO_KICK_POLICY}
How activity changes your score:
{DECAY_BEHAVIOR}
Privacy:
CleanerBot does not read or store message content. It only uses configured activity signals and limited metadata needed for inactivity cleanup.
You can check your own status with /my_score.
If something feels wrong, contact staff. We can adjust thresholds when the community changes.Copied!{ALLOWED_SIGNALS}
messages in allowed channels, reactions, voice or stage participation, threads, slash commands, buttons, scheduled events, and poll interactions
{AUTO_KICK_POLICY} option A
Auto-kick is off. Staff reviews final cleanup actions manually.
{AUTO_KICK_POLICY} option B
Auto-kick is enabled only after configured thresholds and CleanerBot guardrails. Staff can adjust this policy if it creates issues.
{DECAY_BEHAVIOR} option A
Any tracked activity resets your Decay Score to 0.
{DECAY_BEHAVIOR} option B
Each tracked activity lowers your Decay Score by {X} points, so steady participation helps.
Gaming / RP: We use CleanerBot so rosters, raid roles, and character or faction roles stay accurate. The inactive role is a status signal, not a ban.
Creator / supporter: We use CleanerBot to keep the community active without treating quiet supporters unfairly.
Education: We use CleanerBot as an early check-in signal so staff can help before students fall behind.
SaaS / product: We use CleanerBot staff-side to understand roster health and reduce stale access.
NGO / volunteer: We use CleanerBot to keep volunteer roles accurate while respecting seasonal participation.
Did the bot read my messages?
No. CleanerBot does not read or store message content. It only uses configured activity signals, such as whether activity happened in allowed places.
Why did I get an inactive warning?
You crossed our configured inactivity threshold. It is only a heads-up. If you participate again, your score can drop or reset depending on our setup.
Am I being punished?
No. The inactive status is not a punishment. It helps staff keep roles and access accurate.
Can I come back?
Yes. Participate again or contact staff if you need help. CleanerBot is designed around recovery before removal.
Yes, especially in Standard Mode. If you use Ghost Mode, staff can observe privately first, then announce later if member-facing actions are enabled.
Usually yes. Clear thresholds reduce confusion and make the policy easier to trust.
Use careful wording. Say staff review for possible removal unless auto-kick is actually enabled and explained.
Use clear copy for Decay Score, warnings, inactive roles, staff review, and privacy boundaries.