Frequently Asked Questions

Yes — 100% free. There's no paid tier and no feature locked behind payment.

Invite it to your server and grant three permissions: View Channels, Send Messages, and Use Slash Commands. That's it — nothing more is requested.

No. All configuration happens inside Discord through the /config command.

LastSeen records a "last seen" time by watching a member go offline while the bot is online. It can't know when someone was last active before it arrived. So if a member has been offline the whole time since the bot joined — and hasn't come online and gone offline again since — there's no timestamp to show yet. Once the bot sees them go offline at least once, their last-seen time starts working. Members who are currently online show as "Currently online" rather than a timestamp.

Same reason as above. A member only appears in /inactive after the bot has observed them go offline at least once and recorded a timestamp. Anyone who was already offline when the bot joined — and hasn't been online since — won't appear yet, even though they're clearly inactive. The list fills in naturally as members cycle online/offline.

Expect the first day or two to look sparse. As members go online and offline throughout the day, last-seen times, inactivity, and activity stats all fill in. Message activity is also written in short batches, so brand-new messages may take up to ~30 seconds to show in counts.

No. It does not store or read message content. It only counts message activity (how many messages, and when) as metadata for stats — nothing about what you said is kept or even seen.

Two common reasons. First, the member may have opted out with /forgetme — opted-out members aren't tracked at all until they run /optin. Second, check whether Track Only Roles is set (/config): when it's configured, only members holding one of those roles appear in /inactive, reports, and leave notifications. Role names are case-sensitive and must match exactly — leave it empty to include everyone.

No. Only a true offline status counts as offline. Idle and Do Not Disturb are treated as still being around, so they don't set your last-seen time or mark you inactive.

Discord reports Invisible as offline, so the bot treats it exactly like going offline — it will show you as offline and record a last-seen time.

Yes, LastSeen needs to be online 24/7 to observe status changes. Any online/offline changes that happen while the bot itself is offline are missed and can't be recovered.

No. Other bots are ignored — only real members are tracked.

Admin commands (/config, /inactive, /user-stats, /search, /watch, /role-history) require either the configured Bot Admin Role or Discord's Administrator permission. Set which role counts under /config → Set Bot Admin Role. Server administrators always have access.

If User Role Required is turned ON in /config, only members with the configured User Role can use the basic commands. Turn it off to let everyone use them, or give the member the required role.

That's the Allowed Channels setting. If it's set, LastSeen commands only work in the listed channels. Clear it in /config to allow commands everywhere.

LastSeen defaults to UTC. Set your server's timezone in /config → Set Timezone using an IANA name like America/New_York, Europe/London, or Asia/Tokyo. All timestamps and report scheduling then follow that timezone.

Yes — /config → Set Language. It applies to every command, embed, and report for the whole server. Built-in languages: English, Spanish, French, Dutch, and Polish. Defaults to English.

A few common causes: the target opted out with /forgetme (opted-out members can't be watched), the bot can't send messages in the channel where you created the watch, or — for online alerts — the 1-hour per-member cooldown was still active.

Yes. Both /watch online and /watch offline accept a user or a role — for example, /watch offline @Moderator 30d alerts you when a Moderator hasn't been seen in 30 days. Each alert posts to the channel where you created the watch. There's a limit of 50 watches per server — use /watch list and /watch remove <id> to manage them.

Check that the report channel still exists and the bot can send messages there, and that the timezone is set as you expect (reports fire on your server's local schedule). Reports won't send the same report twice on the same day.

For as long as the bot is a member of the server. It isn't aged out or deleted on a timer while the bot is present.

Run /forgetme. It deletes your tracked data (last seen, join info, nicknames, role history, and message counts) across every server using this bot and stops all future tracking of your account. This can't be undone. You can re-enable tracking later with /optin, but previously deleted data isn't restored — your stats start fresh.

Your record is marked inactive rather than deleted, so your history is still there if you rejoin later and pick up where you left off.

All of that server's user data is removed.

You can use /forgetme at any time, or get in touch through our community server for data requests or removal.

Locally, in the bot's own database. No data is sent to external services. Each server keeps its own separate records — the same person in two servers has two independent records.

Yes. Rejoining updates your existing record rather than creating a duplicate; your username, nickname, and roles are refreshed and you're marked active again (unless you'd opted out with /forgetme).

Join our community server — it's the official place for support, bug reports, and suggestions.