Data Retention
Overview
Nox stores only the configuration and activity data your enabled features need to work. Different kinds of data have different lifetimes: some is kept while the bot is in your server, some follows individual members, and some expires automatically on a rolling window. This page explains each lifetime, and what the manual cleanup paths — a dashboard guild reset, removing the bot, and member leave — do and do not remove. For the wider policy see the privacy policy.
What Nox stores
Guild configuration
Per-server settings for each feature: channels, roles, schedules, and toggles you configure from the dashboard or bot commands.
Feature records
Data created by features as your community uses them: tickets, form responses, giveaways, events, warnings, custom commands, and similar.
Member profiles
Guild-scoped member state such as levels, currency, and birthday details, owned by each member while they are in your server.
Activity history
The event records that power the activity feed, logs, and insights, such as joins, leaves, and feature usage. These are events about what happened, not copies of conversations.
Nox never stores message content. It uses Discord's Application Command API and does not request the message content intent, so commands work without giving Nox access to what members write.
Retention windows
Activity logs and insights cover a rolling 365-day window. Older activity entries are deleted automatically.
Guild configuration and feature records are kept for as long as Nox is in your server, or until you delete the content or reset the guild.
Member profiles are kept while the member is in your server. When a member leaves, their profile is deleted, and warnings can also be removed according to your warnings leave policy.
Uploaded images for posts and embeds are stored while the content that uses them exists, and are cleaned up when that content is deleted.
Dashboard guild reset
The dashboard reset is a partial guild wipe you can run at any time. It deletes guild-scoped feature collections, resets the guild configuration back to defaults, and preserves the guild id, owner id, premium user id, and original guild creation timestamp.
Member profiles are preserved. Levels, currency, and other member-owned profile values are not deleted by the dashboard guild reset.
Feature collections such as custom commands, forms, form responses, posts, streamers, temporary voice instances, tickets, event and giveaway records, house points, house elections, and scheduled feature data are deleted.
Warnings and insights can be included or excluded according to the reset options used by the dashboard flow.
Community history activity entries are deleted only when the reset is run with community history deletion enabled.
Before the reset deletes stored feature data, Nox gathers the Discord messages, commands, and scheduled events it knows about and attempts to clean them up.
Gather tracked Discord outputs
Nox looks for stored message references, custom command ids, form command ids, and active scheduled event ids.
Delete tracked Discord outputs
Nox attempts to delete tracked messages, guild commands, and Discord scheduled events before clearing the stored feature data.
Reset configuration
After feature data is deleted, the guild configuration is reset to defaults while preserving the guild identity fields.
When Nox leaves your server
Marked as removed
When Nox leaves or is kicked, the guild is marked as removed. Nothing is wiped immediately.
Seven-day grace window
If Nox is re-invited within seven days, the removal mark is cleared and your configuration and data are still there.
Full wipe
After the grace window, a scheduled cleanup deletes the guild's saved data. Unlike the dashboard reset, the full wipe removes the guild record rather than resetting it to defaults.
When a member leaves
When an individual member leaves a guild, Nox deletes that member's profile, removing guild-scoped levels, currency, birthday details, and profile state from the dashboard and bot.
Features can have their own leave behaviour on top of that. Warnings can delete stored warnings on leave when that warning policy is enabled, and insights records the leave event for reporting.
Individual users also have the right to request deletion of all data related to them, as described in the privacy policy.
Important notes
The 365-day window applies to activity history. Configuration, feature records, and member profiles do not expire on a timer.
Dashboard reset is destructive and permanent for the guild-scoped feature data it deletes, but it preserves member profiles — it is not the same as removing every member's levels, currency, or profile data.
Rejoining within the seven-day grace window restores access to existing data; after the full wipe runs, deletion is permanent.
Discord cleanup only covers messages, commands, and scheduled events Nox stores and knows how to remove. Manually-created channels, roles, and old untracked Discord messages remain Discord-owned unless you remove them in Discord.
Member leave cleanup is not a guild reset. It affects the leaving member's profile and feature-specific leave policies.
Troubleshooting
I reset the guild but member levels stayed
That is expected for the dashboard guild reset. Member profiles are preserved while guild configuration and feature collections are reset.
A Discord message or role still exists
Reset cleanup only removes tracked Discord outputs. Review the feature that created the message or event and remove any Discord-owned channels, roles, or manually-created messages directly in Discord.
The bot was kicked and data still exists
Bot removal marks the guild as removed first. Full deletion happens later after the seven-day grace window.
