Every question, answered plainly.

Per-member stats (XP, level, message counts, invite counts, warnings), your server's configured settings, economy balances, reminders you set, and any backups you choose to create. That's the full list — there's no hidden analytics store beyond this.

No. SJW does not archive message content. Messages pass through the bot in memory to check things like XP, automod filters, or banned words, then that's it — the text itself isn't written to the database. The one exception is AI Moderation (see the Moderation & AI section below).

No. SJW only has access to servers it's added to, and only to channels its role can see there. It cannot see your direct messages with other people.

No. Nothing is sold, and nothing is shared outside of what's strictly needed to run the bot's own features (for example, sending a moderation log to your own server's log channel).

Settings and stats simply stop updating the moment the bot leaves — nothing new is recorded. If you'd like your server's existing data deleted outright, reach out on our support server and we'll take care of it.

Yes — most of it is already visible to you directly in the web dashboard (stats, settings, warnings, economy). If you want a full raw export, ask in the support server.

Sign-in uses Discord's own OAuth2 login. You authenticate directly with Discord, and Discord hands us back a token proving who you are — your password is never seen, sent to, or stored by SJW at any point.

Only accounts that hold Manage Server permission (or Administrator) in that specific Discord server can view or edit its settings — the same permission Discord itself uses to gate server management.

Only what its active features need — e.g. Send Messages, Manage Roles, Manage Channels for backups and tickets, Kick/Ban for moderation commands. You can review and revoke any of these at any time from Discord's own Server Settings → Integrations page.

It's designed to flag or reverse mass-damage actions (rapid channel deletions, mass bans, role/permission abuse) — not routine single actions by trusted staff. You control the sensitivity and the exempt-roles list from the dashboard.

Please report it on the support server or by email rather than posting details publicly — we'll patch it as a priority and credit you if you'd like.

If you enable it, a message flagged by the rules engine is sent to our AI provider in the moment purely to be scored for a policy violation. We do not keep a copy of that message text in our own database — it's a live check, not an archive.

Only if you configure it to. By default it's built to flag and log for staff review; auto-action thresholds (warn/timeout/ban) are opt-in settings you control per server.

Only your own server's staff/moderators, through the bot's moderation commands. It isn't visible to regular members or to other servers.

Yes — every moderation feature, including AI Moderation and the Advanced Rules Engine, is opt-in and can be toggled off per server from the dashboard at any time.

No. Shards, balances, and every shop item are in-game only. None of it has real-world value, can be cashed out, or is ever bought with real currency.

Server staff have no dashboard control over individual member balances beyond what standard moderation commands expose (e.g. resetting a repeat exploiter). There's no hidden 'grant myself shards' switch.

Both have built-in cooldowns, success odds, and caps designed around balance — vaults exist specifically so a portion of your balance is always protected from theft.

No. Settings, stats, and balances live in the database independently of the bot process being online. An outage pauses live features; it doesn't erase configuration or history.

Yes, the database itself is backed up on our end. Separately, the /backup command lets you snapshot your own server's channels and roles on demand.

Use the Suggestions & Bugs page — reports go straight into a tracked channel our team monitors, or drop it in the support server directly.