Last updated: August 2026
This page applies specifically to the ScripForge Discord bot and is intentionally not listed in the main navigation. It is only accessible through the main Privacy Policy.
The bot may process Discord account identifiers, usernames, and tags, server IDs, moderation records, support ticket metadata, and support transcript text files. When a user links their Discord account to a ScripForge account, we store the Discord ID and tag alongside the site account reference so the bot can verify ownership and sync a Verified Customer role.
Moderation actions such as warn, timeout, kick, ban, and unban are logged locally with the target member ID/tag and moderator ID/tag. Support tickets capture the opener's Discord ID/tag, ticket thread ID, and optional order context. Transcript files may be saved locally for staff review.
We use the Discord account data to verify customers, assign access roles, maintain moderation history, and operate customer support threads. The bot does not sell user data and does not use Discord data for advertising or unrelated profiling.
Temporary AI support conversation memory is kept in memory only while the bot is running. It is not persisted to disk and is not treated as a permanent record. Ticket transcripts are stored locally as plain text files so staff can review the conversation and close tickets.
For website-driven Discord linking, the app requests only the Discord `identify` scope and uses the returned user data to create the account link. The OAuth access token is not stored for later reuse. The bot does not collect or retain broad profile data beyond the Discord user ID and tag needed for verification and role syncing.
We keep moderation logs and support records for as long as they remain necessary for operation, moderation, or support. Support transcript files are retained locally until they are no longer needed for the ticket workflow or are manually removed by the operator. Account links may be removed when a user unlinks their Discord account.
Only authorized staff or bot operators with the required server access should be able to view moderation data, transcript files, or account-link records. We do not share this data with unrelated third parties. The bot uses Discord and, where relevant, the local ScripForge store data to support the features it provides.
For privacy questions about the bot or its data handling, contact the operator of the ScripForge installation or the staff contact for the Discord server running the bot.