Privacy Policy

1. Data Modex stores

When a moderation case is recorded, Modex can store the following information in its database:

• Server ID: the Discord server where the action was taken.
• User ID: the target member’s Discord ID when the action has a target. Some server-level actions, such as purge or slowmode, do not have a target user.
• Moderator ID: the Discord ID of the moderator who invoked the command.
• Action and reason: the moderation action and the reason supplied by the moderator. A default “No reason provided” is used where a reason is optional and omitted.
• Case ID and timestamps: a sequential case identifier (for example, MODEX-0001), the case timestamp, and, for timed actions, duration and expiration time where applicable.
• Case status: whether the action is pending, completed, or failed.

For warnings, Modex also stores the warning’s server and target IDs, reason, creation time, and whether it is active. When a warning is removed, it records the removal time, the removing moderator’s ID, and the related removal case ID. Removing a warning marks it inactive; it does not erase its history.

2. Why it is stored

This information supports persistent moderation records, sequential case IDs, and warning history, including tracking when a warning is removed. Discord IDs are stored as identifiers; Modex does not need to store member display names in the case tables.

Modex does not store message content as a moderation archive, and it does not automatically scan conversations. The bot’s purge command asks Discord to delete recent messages; those message contents are not stored in Modex’s case database.

3. Storage and retention

Case and warning records are stored in a local SQLite database file in the bot deployment, normally database/modex.db (an existing legacy database file may be used instead). The database is managed by the operator hosting that bot instance; it is not a hosted Modex web account or a website database.

The project does not define an automatic expiration period for case history. Records remain in the SQLite database until the operator removes them or deletes the database. Removing a warning changes its active status and adds removal details but retains the warning record. Hosting operators may separately make backups, which Modex itself does not manage.

4. Data security

The database is stored on the filesystem of the environment running the bot. Modex does not implement database encryption or a separate web-based access-control layer. The bot operator is responsible for securing the host, limiting access to the database and backups, and protecting the Discord bot token and deployment credentials.

Moderation reasons may be visible to people with access to the bot’s database. Enter only information appropriate for a server’s moderation record; avoid sensitive personal information.

5. Access and deletion

Modex does not currently provide a command or dashboard for users to export or delete stored case records. To ask about records for a server, contact the owner or administrator who operates that server’s Modex deployment. That operator controls the SQLite file and can review or remove records directly.

Deleting a case may affect related warning history because warning records refer to case records. Database changes should be made by the operator with care to preserve related records and database integrity. If the deployment has backups, removing a record from the active database does not automatically remove it from those backups; the operator must handle backup retention separately.

6. Changes and questions

This policy may be updated if Modex’s data handling changes. For questions about a particular server’s stored records, contact that server’s bot operator.