Server Statistics
The Statistics tab is rebuilt from scratch and served by your own bot. Over forty views of what happens on your server, stored in your bot's own database. It counts what happens, and never stores what anyone wrote.
Illustration only - actual interface and behavior may differ
What you get
The Statistics tab was rebuilt from scratch. It covers activity, channels, people and the modules you run.
Activity
- Messages sent over time
- Voice time across your server
- Joins and leaves
Channels
- Which channels are busy
- Which channels have gone quiet
People
- Activity by role
- Your most active members
Modules
- Moderation
- Tickets
- Giveaways
- Levels
What it records, and what it never touches
Everything analytics stores is a number or a date. Until you switch it on, none of it exists: the database tables are never created, your bot attaches no listeners, and it does not ask Discord for the events involved.
What gets recorded
- Server totals per day and per hour: messages, slash commands, reactions, voice seconds, threads, joins and leaves, first-time posters, and a daily member snapshot
- How often each kind of automatic moderation fired, by trigger type. Who triggered it is not stored
- Message counts per channel and per role, per day
- Per member: messages, reactions and voice seconds per day, a lifetime message total, and the dates of the first message and the last activity
- A capped list of recent events, each holding an event type, a member ID, a channel ID and a timestamp
What is never recorded
- The text of a message
- Attachments, images, files or links, neither their contents nor how many there were
- Message edits or deletions
- Direct messages. Only activity inside the server counts
- Channels your bot cannot see
- Other bots. Their messages and commands are ignored
Analytics stores no message text, and asks for no permission to read one
Counting a message needs no text. Discord tells your bot that a message happened without including what it said, and analytics never requests the permission that would add it. Some other modules do need that permission and ask for it when you switch them on. Even then nothing in analytics reads message text, and there is no field in the analytics data that could hold one.
It runs on your bot
Your bot collects the data and writes it to its own database, on the Bot-Host you picked. SCNX does not pool it with other servers, and the dashboard keeps no copy: it asks your bot for the figures each time you open the tab.
Activity in your server
Messages, voice, joins, module events
Your own bot
Collects and writes the numbers itself
Your bot's own database
Never pooled with other servers
SCNX dashboard
Asks your bot on each visit. Stores no copy.
Your bot runs on the Bot-Host you picked. Hosts sit in different regions, so that choice decides which country the data is physically in. If your bot is stopped, the dashboard has nothing to ask, and the tab tells you so.
Privacy and control
You decide what happens to the data. Export it, delete it, or let members take themselves out of it.
Download a copy
Under Privacy on the Statistics tab, for the server owner. The file is built in your browser from your bot's answers, and nothing is stored at ScootKit along the way. It covers your whole history whatever range is on screen, includes cards you have hidden, and always lists anything that could not be exported.
Delete all of it
You tick a confirmation first, and it cannot be undone. The deletion runs as one database transaction, so it either completes in full or changes nothing, and you get a report table by table with a row count for each.
Member opt-out
Off by default. Switch the Let members opt out of analytics setting on and a member can run /analytics-privacy. Their per-day records are anonymised, their totals and dates cleared, and their recent activity deleted. Server totals stay intact, only the link to the person disappears.
How long it is kept
Daily and hourly totals, and the figures per channel, per role and per member, are kept until you delete them. The list of recent individual events has a fixed size cap and the oldest fall off: a few days back on a busy server, a few months on a quiet one.
Two things a delete leaves behind
Your members' opt-out choices, so deleting the data does not quietly re-enrol anyone who opted out. And disaster-recovery backups, where a copy can persist for up to 90 days.
The data is your responsibility
As the server operator you are responsible for your members' activity data, not SCNX. Check what applies to your server and decide whether you want to offer members the opt-out. What is recorded and how long it is kept is documented in full.
For your members
Your members do not need dashboard access to see how the server is doing. Two slash commands cover it, and you can switch either one off.
Illustration only - actual interface and behavior may differ
Arrange the tab your way
Every server watches different numbers. Set the Statistics tab up the way you use it.
Drag cards into order
Put the cards you check every day at the top and the rest below.
Hide what you do not need
Hidden cards disappear from the tab and are never calculated.
Frequently Asked Questions
In your own bot's database, on the Bot-Host you picked. Bot-Hosts sit in different regions, so that choice decides which country the data is physically in. It is never pooled with other servers, and the SCNX dashboard keeps no copy: it asks your bot for the figures each time you open the tab.
No. Analytics records counts and timestamps only, and it never asks Discord for the permission that would let it read message text. Some other modules do need that permission and request it when you switch them on. Even then nothing in analytics reads message text, and there is no field in the analytics data that could hold one.
Daily and hourly totals, and the figures per channel, per role and per member, are kept until you delete them. The list of recent individual events has a fixed size cap and the oldest entries fall off, which reaches back a few days on a busy server and a few months on a quiet one.
If your server already had statistics, the history was carried across automatically and the old copy was removed. The old system never recorded joins, leaves or first-time posters, so for dates before the transfer those figures show as not recorded, and the handover point is marked. Servers still on the old source keep seeing their existing figures until they switch over, and SCNX-Bot analytics features will be suspended later this year.
Yes, once you switch the member opt-out on, which is off by default. A member then runs /analytics-privacy: their per-day records are anonymised, their lifetime total and their first-message and last-active dates are cleared, and their recent activity records are deleted. Their future activity still counts in the server totals with no link back to them. It applies immediately and they can opt back in later, but removed data stays gone.
Once. Switching statistics on under the Statistics tab restarts your bot, and it starts collecting from then on.
You are, as the server operator. In data-protection terms you are the controller and ScootKit is the processor, under the Data Processing Agreement that comes with your SCNX contract. Whether analytics runs, what the figures are used for and when they are deleted are your decisions. What is recorded and how long it is kept is documented in full at docs.scnx.xyz.
Statistics that stay on your bot
Switch the Statistics tab on, let your bot restart once, and it starts collecting into its own database.
Get started