This privacy policy explains what nox (“we”, “our”, or “us”) stores about you when you use it on Discord and on this website, why, for how long, and how to have it removed.
Message Content
nox does not request Discord's message content intent. Unlike prefix bots that need to read messages to find commands, nox uses Discord application commands and interaction components.
Necessary Data Only
nox stores what it needs to run the features your community has enabled: the server's configuration, the ids of the channels, roles and emojis it should use, scheduled feature records, and per-member feature progress. Every kind of record is listed below.
nox is operated under Discord's Developer Policy. Discord's policy explains the platform rules that apply to apps and bots.
Discord's Developer PolicyNothing here is collected by scraping. Every record below is written by an action you or your community's admins take: signing in, running a command, reacting, submitting a form, or saving a setting.
When you sign in with Discord we create a website account holding your Discord id, display name, avatar URL and the email address on your Discord account. The email is only the account identifier; we do not send mail to it.
Each website session stores a session token, its expiry, and the IP address and browser user agent it was created from. Expired sessions are deleted by a daily purge.
The Discord OAuth access and refresh tokens from sign-in are stored encrypted at rest. They are used only to list the servers you belong to and to check your membership and permissions when you open a dashboard. Membership is read from Discord at request time; we do not keep a copy of it.
For each server the bot is in we store the server id, the owner's user id, and the configuration saved on this website: which features are on and the channel, role and emoji ids they use. Custom command replies, posts, ticket panels and form definitions are stored as your admins wrote them.
When a feature such as levelling, economy, birthdays or achievements is used, the bot keeps a per-server member profile: your user id, username and avatar URL, experience, reputation, currency, streaks, lifetime message, voice and reaction counts, an optional birthday month and day (no year), and the styling you chose for your profile card. The profile and its economy data are deleted when you leave the server.
Insights keeps monthly message and voice-time counts per member, plus server-wide daily, monthly and hour-of-week totals and per-command usage counts (counts only, not who ran them). The community feed and the admin log record who did what, for example who created an event or changed a setting, with your user id and username at the time.
Warnings store the warned member's user id and username, the reason, the strike number, any evidence links the moderator attached, and who issued and executed the warning. Tickets store who opened, claimed, resolved and closed them, the thread ids, and the notes staff write inside the ticket. Form submissions store the answers as displayed, the submitter's user id unless the form is anonymised, and where the submission was posted.
Responding to an event, entering a giveaway or voting in a poll stores your user id against that run (for events, together with the role you picked) so the message can be kept up to date and winners can be drawn.
Retention is fixed in code and enforced by a nightly purge job. The windows below apply to every community; there is no paid tier that changes them.
Community feed and admin log entries are deleted 365 days after they are written.
Health-check incidents are deleted 90 days after they are resolved; unresolved incidents are kept until they are resolved.
Ended events, giveaways, polls and House Cup runs, including responses, entries and draws, are deleted 180 days after they end.
Per-member monthly message and voice counts are deleted after 25 months. Achievement daily counters are kept for 35 days.
Expired website sessions and sign-in verification tokens are deleted as soon as they expire.
Leaving a server deletes your member profile and economy data for that server. Warnings, tickets, form submissions, feed entries and activity counts about you stay until their own window or the server's reset, unless your community's warning settings delete strikes on leave.
Warnings, tickets and their notes, form submissions, and server-wide insights totals have no age limit. They are kept for the life of the installation as moderation records and year-over-year comparisons, and are removed by a server reset (warnings and insights are optional there) or when the bot is removed.
When nox is removed from a server, that server's data enters a 7-day grace period in case the bot is re-added and is then deleted in full, including uploaded images. Your website account is not tied to any single server and is unaffected.
Data lives in a PostgreSQL database and a Redis cache reachable only from the application's own servers; Redis holds short-lived caches and cooldowns, never the only copy of anything. Discord OAuth tokens are encrypted at rest. The bot token used to act on Discord is held in server configuration and is never sent to the browser. Only the developers operating the service have access to production data.
Website sign-in is handled by Better Auth, an open-source library that runs inside our own application. It is not a third-party service: your account, session and token rows live in our database and nothing is sent to Better Auth.
We do not sell data and do not share it with anyone except the services listed below, each of which receives only what its job needs. Data is used solely to run the bot, this website, and the features your community has turned on.
nox is a Discord application. Everything it does on Discord, such as posting messages, managing roles and channels and reading who is in a server, goes through Discord's API under Discord's own terms and policies.
Discord's Privacy PolicyError reports and a small sample of performance traces are sent to Sentry. A report can include the Discord user id of the signed-in user, the server id, the request path and the error itself; it never includes message content or the request body.
Sentry's Privacy PolicyImages your admins upload for posts, embeds and messages are stored in an S3 bucket under a per-server prefix. An image is deleted when it is replaced or removed, and the whole prefix is deleted when the server is reset or the bot is removed.
AWS Privacy NoticeOnly if your community sets up stream announcements: we store the configured streamer's public Twitch id, login, display name and current stream title and category, fetched from Twitch's API. No viewer or member data is sent to Twitch.
Twitch's Privacy NoticeServer admins can reset their server from the dashboard, which deletes its feature data and optionally its warnings, insights and community history, or remove the bot, which deletes everything after the grace period. As an individual, leaving a server removes your profile there; to have anything else about you deleted, including your website account, which has no self-service delete yet, contact us and we will remove it by hand.
If you do not want nox storing data about you, do not sign in to this website and do not use its commands. A server you are in may still count your messages and voice time if its admins have enabled insights or levelling; to stop that, ask the server's admins or contact us.
If you'd like to talk to us regarding any of the points in this document, please contact one of the @Developers in our support Discord.
