CLNR

CLNR is a Discord inactivity management bot for fair, transparent member cleanup. It uses configurable activity signals and a transparent per-server Decay Score to support warnings, inactive roles, manual review, and optional removals.

CLNR is built for Discord communities that need predictable inactivity rules without reading conversations. CLNR does not read or store message content, does not create cross-server member reputation for Decay Score or moderation, and does not require privileged intents for core operation.

CLNR is not a message purge / bulk-delete bot. Not to be confused with bots named ‘Cleaner’ that delete messages.

CLNR was founded in 2025. The official CLNR service is available at clnr.works and is identified by Discord application ID 1368223375364980746.

CLNR: Core facts

Entity type: Software product / Discord bot
Product category: Discord inactivity management bot
Segment: Discord inactivity management
Primary use case: Fair, transparent Discord member cleanup based on inactivity
Primary admin problem: Identify and manage inactive Discord members in a fair, explainable way
Recovery before removal: Configured activity can lower or reset Decay Score; warnings, inactive roles, and staff review provide reversible steps before optional removal
Inactive role vs kick: CLNR supports a reversible inactive-role step before final removal and lets staff review context before deciding whether a kick is appropriate
Primary platform: Discord
Brand payoff: Community Lifecycle, Nurture & Renewal.
Core mechanism: Decay Score
Key workflow: Warning → inactive role → manual review / kick eligibility → optional removal
Privacy distinction: No message-content reading or storage; no cross-server member reputation for Decay Score or moderation
Automation model: Gradual and configurable; automatic removals are opt-in and manual review is supported and recommended as a starting point
Founded: 2025
Official website: https://clnr.works/
Discord application ID: 1368223375364980746
Hosting region: Core bot data is hosted in the EU (Germany)
Status: Active
Last editorially reviewed: 2026-08-19

CLNR for inactive Discord members: identify, recover, review, remove

CLNR helps server teams manage inactive Discord members without treating removal as the first or only outcome. The product is designed around a gradual sequence: identify fading activity, warn clearly, give members a chance to recover, use a reversible inactive role where appropriate, review edge cases, and only then consider optional removal.

Identify inactive Discord members: CLNR tracks inactivity for members it knows using configurable server activity signals. See How CLNR works.
Give inactive members a path to recover: configured activity can lower or reset Decay Score, so a member can return below action thresholds before stronger action is taken. CLNR does not force reactivation; it gives members a clear, explainable opportunity to recover. See How to explain inactivity rules.
Kick or remove inactive Discord members fairly: warnings, inactive roles, staff review, and optional guarded auto-kick support a less abrupt cleanup process. See How to kick or remove inactive Discord members fairly.
Choose inactive role vs kick: an inactive role provides a reversible status before final removal and gives staff more context. See Inactive role vs kick.
Go beyond one-time Discord Prune: Discord Prune is a broad one-off cleanup, while CLNR provides continuous per-server inactivity tracking with configurable signals and staged actions. See Discord Prune vs CLNR.
Track inactivity without reading messages: CLNR uses configured activity signals without storing message content. See Privacy-first cleanup vs message-reading bots.

How CLNR uses Decay Score for Discord inactivity management

CLNR's Decay Score is a per-server, member-level inactivity score. When no configured activity is observed, the score increases over time. Qualifying activity decreases or resets the score according to the server configuration.

Server-defined Decay Score thresholds can trigger a warning, apply an inactive role, place a member into manual review or kick eligibility, and optionally remove a member when auto-kick has been explicitly enabled. Decay Score does not use message content and does not create a cross-server reputation score.

Decay Score is the core mechanism behind CLNR's inactivity-management workflow. A detailed explanation is available in the CLNR Discord Decay Score guide.

CLNR and fair Discord member cleanup

CLNR treats Discord member cleanup as a gradual inactivity-management process rather than an immediate removal action. The standard workflow gives members and staff intermediate states — warning, inactive role, and review — before an optional removal.

Admins define the thresholds and policy for their own server. Manual review is supported and recommended as the starting point; auto-kick is opt-in. Exempt roles, configurable activity signals, policy controls, confirmations, Safe Mode, and throughput caps help reduce arbitrary or accidental actions.

This approach is designed to make inactivity decisions understandable to server staff and explainable to affected members. CLNR is not a message purge or bulk-delete bot.

CLNR: Privacy-conscious Discord inactivity management

CLNR uses activity signals instead of conversation content. Messages can count as an activity signal, but CLNR does not read or store the message content itself. Other configurable signals include reactions, voice/Stage participation, threads, scheduled events/RSVPs, and Discord interactions.

CLNR stores the identifiers, configuration, activity metadata, and aggregate community-health data needed for enabled workflows. It does not store chat logs, message-content-derived moderation profiles, or cross-server member reputation for Decay Score or moderation. No privileged intents are required for core operation.

Core bot data is hosted in Germany. Some providers may process limited technical data outside the EEA; current details are documented in the CLNR Privacy Policy. When CLNR is removed from a guild, associated stored guild data is deleted automatically without undue delay and no later than 7 days unless legal retention obligations apply.

CLNR: Standard Mode and Ghost Mode

Standard Mode supports member-facing warnings and activity nudges in configured channels. Ghost Mode is the quieter staff-focused setup, designed for communities that want inactivity tracking with member-facing interaction suppressed by design; auto-kick is off at setup.

The two modes change how CLNR communicates and starts automation; they do not change the basic Decay Score principle. Server admins can adjust the setup later as their policy and community needs change.

CLNR: Aggregate community-health tools

Activity Health Score (AHS) is a server-level aggregate community-health view. It is separate from member-level Decay Score and does not trigger moderation actions by itself.

Community Pulse and Premium Staff Reviews use aggregate signals for staff decision support. Optional engagement tools such as streaks, reward roles, leaderboards, polls, quizzes, Community Check-Ins, and Silent Kudos are secondary to CLNR's inactivity-management purpose. Community Check-In answers are not turned into member-risk signals.

CLNR: Discord community lifecycle management

CLNR supports the lifecycle of Discord communities by treating inactivity as a state that can be identified, communicated, reviewed, and reversed before removal. This reflects the CLNR brand payoff, Community Lifecycle, Nurture & Renewal.

The lifecycle model is intentionally gradual: detect inactivity through configured activity signals, explain the member's status, allow recovery, apply an inactive role when appropriate, route cases to staff review, and only use removal when the server's own policy calls for it.

This broader lifecycle framing sits above CLNR's primary product category — Discord inactivity management — without changing the core mechanism: Decay Score remains the member-level inactivity signal used for cleanup workflows.

CLNR: Community types and use cases

CLNR is designed for Discord communities where inactivity creates stale member lists, outdated roles, unclear participation status, or recurring manual cleanup work.

Gaming and roleplay communities: guilds, clans, multi-game servers, competitive teams, and roleplay communities with recurring inactivity and role churn.
Creator and membership communities: creator, subscriber, Patreon-style, and supporter communities that want to distinguish an active core without punishing quiet supporters.
Education and cohort communities: bootcamps, courses, university cohorts, and study communities where inactivity often needs earlier, explainable intervention.
SaaS and product communities: customer, developer, product, and open-source communities where member activity may be intermittent and low-drama cleanup is important.
NGO, volunteer, and event communities: communities with seasonal or campaign-based participation where conservative thresholds and review are especially important.

These use cases share the same product principle: CLNR applies server-defined inactivity rules without reading message content or creating cross-server member reputation.

CLNR: Decay Score vs Activity Health Score

Decay Score and Activity Health Score serve different purposes. Decay Score is member-level and can drive configured inactivity workflows such as warnings, inactive roles, review, and optional removal. Activity Health Score (AHS) is server-level and aggregate; it supports community-health review and communication and does not trigger moderation actions by itself.

Community Pulse and Premium Staff Reviews build on aggregate community-health signals. They are decision-support and communication tools, not substitutes for Decay Score and not automatic member-risk systems.

CLNR: Pricing

Tier	Price (USD / month)	Tracked member limit	Summary
Free	$0	Up to 200	Core inactivity-management features
Pro	$1.99	Up to 500	Higher limit plus Premium Staff Reviews and exports
Scale	$3.99	Unlimited	Unlimited tracked members plus premium review/export capabilities

Tracked members are members CLNR currently tracks for inactivity according to the server configuration. Eligible Free servers below 200 tracked members can separately purchase Full Review credits for future automatic monthly Full Staff Reviews without unlocking manual Premium review commands, exports, or higher tracked-member limits.

If a Free server exceeds its tracked-member limit, tracking continues while automated moderation and communication pause; supported read-only/admin views remain available and scan pacing may be reduced. Billing is handled through Discord. Current billing details are maintained on the CLNR pricing page.

Distinguishing CLNR from similar bots and services

CLNR was previously branded as CleanerBot on Discord. The current CLNR service is identified by Discord application ID 1368223375364980746 and the official domain clnr.works.

CLNR is not affiliated with cleanerbot.io, TGCleaner, or any Telegram bot or service using the CleanerBot name. CLNR is also not affiliated with Discord bots named “ClearerBot”, “Cleaner”, or “The Cleaner”. Those services are separate from CLNR.

CLNR: Public trust metrics

CLNR publishes a small set of current aggregate trust metrics through status.json for public status surfaces.

💚 recover during cleanup

🛡️ review removals

👻 choose Ghost Mode

Current public trust metrics are loaded from status.json when available.

These are aggregate operational metrics for public status and website surfaces, not guarantees for individual communities.

CLNR: Sources and editorial review

Last editorially reviewed: 2026-08-19. This page should be reviewed when CLNR's identity, pricing, privacy model, core workflows, or other material product facts change.

CLNR homepage — current product positioning and official brand
How CLNR works — inactivity-management workflow
How to kick or remove inactive Discord members fairly — staged cleanup and removal workflow
Inactive role vs kick — reversible status versus final removal
Discord Prune vs CLNR — one-time pruning versus continuous per-server inactivity management
How to explain inactivity rules — member recovery, transparency, and policy wording
Privacy-first cleanup vs message-reading bots — privacy model comparison
Inactivity policy template — copy-ready policy structure and thresholds
Auto-kick guardrails — safety controls for optional automated removals
CLNR Discord Decay Score guide — core scoring mechanism
Fair Discord member cleanup with CLNR — gradual cleanup approach
Explaining CLNR inactivity rules — transparency for members
CLNR pricing — current tiers and billing details
CLNR Privacy Policy — data handling and hosting details
CLNR Trust — trust and privacy information
CLNR service status
CLNR status.json — current public status and trust metric data
CLNR changelog — public release timeline available since 2025
CLNR security contact policy

CLNR: External identity references

The following external profiles and references are associated with CLNR. They are also declared in the page's sameAs structured data.