Inactivity policy template

Inactivity Policy Template for Discord (Copy/Paste)

CLNR helps you keep your member list healthy and active with fair, transparent inactivity cleanup without reading messages.

Want a setup that fits your community? Browse the Use Case Guides.

Tip: Start in Ghost Mode for a quiet, staff-only trial - no public warnings, no role changes.

Why servers use an inactivity policy

Big member counts can look great, but ghost members make it harder to build real conversation and events. A clear policy keeps things fair - everyone knows the rules.

How CLNR keeps it fair

CLNR uses an Inactivity Score (Decay Score). It goes up when someone is inactive and goes down when they show up. Members get a heads-up before anything happens.

Need the full concept first? Read Discord Decay Score explained before publishing your policy.

Decay is not a penalty - it is a gentle reminder that activity fades with time.

What counts as activity (you choose)

Admins decide what showing up means. CLNR can count multiple activity signals without storing message content.

Text chat

Sending messages in allowed channels counts as activity.

Metadata only
Reactions

Adding emoji reactions helps keep your streak alive.

/toggle reactions_as_activity
Voice & stage

Joining voice channels or stages counts as activity.

/toggle voice_activity
Typing

Typing indicators can register as lightweight activity.

/toggle typing_activity
Commands & components

Slash commands, buttons, and other components add activity.

/toggle interactions_activity
Threads

Posting inside public threads counts too.

/toggle thread_activity
Event RSVPs

Participating in scheduled events contributes to activity.

/toggle scheduled_events_activity
Member joins

New joins can count as activity (useful as an onboarding cushion).

/toggle member_join_activity
Message pins

Pinning a message can count as activity (rarely needed).

/toggle message_pin_activity
Emoji adds

Adding new emojis can count as activity (usually off).

/toggle emoji_add_activity
I'm Active CTA button

A button members can click to record an activity moment (if enabled).

Configurable
Answer Hint ๐Ÿ’ก

Optional interactions in quizzes/polls tracked as activity (if enabled).

/polls_wizard
ON = counts toward activity (default) OFF = ignored
Admins can change this anytime via /config - no policy rewrite needed.
Make it stricter or quieter

Strict policy

Enable voice + interactions + threads; keep typing off.

Quiet policy

Keep most signals on, but run Ghost Mode so member-facing messages stay staff-only.

Your server's checkpoints (thresholds)

Thresholds are simple checkpoints. People get an early heads-up first. Later, an inactivity role can be applied. Removals should be reviewed (and can be automated only if you want).

Check 1
Early heads-up
Score {WARNING}+
→ Friendly warning
Check 2
Inactivity status
Score {INACTIVE_ROLE}+
→ Inactive role
Check 3
Final limit
Score {KICK}+
→ Staff review (auto-kick optional)

Admins can tweak these anytime in /config when your community changes.

If you enable auto-kick, review the Auto-Kick Guardrails.

Not sure whether to use an inactive role or removal? Start with Inactive role vs kick.

Copy/Paste Template

If you want shorter announcement wording, use the copy blocks in How to explain inactivity rules to your members.

Fill these variables first:

{WARNING} {INACTIVE_ROLE} {KICK} {DECAY_BEHAVIOR} {ALLOWED_SIGNALS}
Hey everyone ๐Ÿ‘‹
Quick update from the staff team.

We use CLNR to manage inactivity fairly and transparently - without reading messages or storing chat logs.

Instead of counting days inactive, CLNR uses an Inactivity Score (Decay Score):

- Everyone starts at 0
- The score goes up when someone is inactive
- The score goes down when they show up (activity counts immediately)

โœ… What counts as activity here:
{ALLOWED_SIGNALS}

๐Ÿงญ What happens at certain checkpoints:
- โš ๏ธ Score {WARNING}+: friendly warning (early heads-up)
- ๐ŸŽญ Score {INACTIVE_ROLE}+: inactivity role may be applied
- ๐Ÿšช Score {KICK}+: staff review for removal (auto-kick is optional)

๐Ÿ”„ How activity reduces your score:
{DECAY_BEHAVIOR}

๐Ÿ“Œ Check your own status anytime:
Use `/my_score` to see your score, streak, and last active date.

This policy is here to keep the server fresh and fair for everyone. If something feels off, tell staff - we can adjust thresholds when the community changes.

{ALLOWED_SIGNALS} example: ๐Ÿ’ฌ messages, โค๏ธ reactions, ๐Ÿ–ฑ๏ธ commands & buttons, ๐Ÿงต threads, ๐Ÿ“… event RSVPs

{DECAY_BEHAVIOR} option A: Any tracked activity instantly resets your score back to zero.

{DECAY_BEHAVIOR} option B: Each tracked activity lowers your score by {X} points, so steady engagement pays off.

Before you publish this policy

  • Your warning, inactive-role, and review thresholds are set.
  • Staff agrees whether auto-kick is off or enabled.
  • Exempt roles are configured.
  • CLNR has access to the channels you expect it to observe.
  • Your policy says CLNR does not read or store message content.
  • Members know how to check their own status with /my_score.

Privacy & trust (what we do and don't do)

We don't store chat logs or message content.
Decay scoring is computed per server (no cross-server activity profiling for moderation). Limited account-level metadata may be processed for entitlements/voting where enabled.
We use no ads, trackers, or pixels.
Cleanup decisions are traceable - scores and reasons stay visible to staff.

More details: CLNR privacy and the Privacy vs Message-Reading Bots Comparison.

Start in Ghost Mode if you want a staff-only trial first.

Want a setup that fits your community? Browse the Use Case Guides.