Privacy Policy

Account and server data

Forge stores a Discord user ID, display name, avatar, owned-server list and a short-lived OAuth access token in its server-side session. Sessions expire after 24 hours without activity or when Forge is updated. Background status checks do not count as activity. Server configuration, module settings, channel/role IDs and permission metadata are stored in Postgres. Forge does not archive Discord message history in its database.

Module data

Tickets store server, channel and user IDs and open/closed status. Ticket conversation content lives in Discord. Counting reads message text to validate numbers, then stores the count and last user ID. QOTD stores posting history; temporary voice rooms store ownership/channel IDs. Suggestions and reaction roles use Discord messages and events.

Forge Studios announcements

Developer announcements start enabled. Forge creates a public, read-only #forge-announcements channel and posts a one-time setup message. This also applies to existing servers. Owners can change the channel, choose product updates, maintenance notices and service issues separately, or turn all announcements off in Studio under Modules. Forge stores the server ID, selected channel ID, those three preferences and the account ID that last updated them. Published announcements keep per-server delivery state so Forge can retry safely without intentionally sending the same announcement twice. Announcement messages disable Discord allowed mentions, so Forge does not use this system for @everyone, role or member pings, and it does not send announcement DMs.

Message logs

If a server owner enables message logs, Forge posts edit and deletion events in the selected private staff channel. Logs contain message, channel and author IDs when available. Including cached message text is a separate option, off by default. Message text is not saved to the Forge database. Discord messages temporarily cached by the running bot are lost on eviction or restart. Log messages remain in Discord until server staff remove them; deleting Forge data does not delete those Discord messages. Forge cannot recover uncached deleted text or reliably identify who deleted a message.

AI and browser storage

AI requests send your prompt, recent conversation and relevant server structure to the configured Gemini provider. AI prepares a draft only. Drafts, versions and AI conversation history also remain in your browser local storage until cleared.

Retention

Aggregate service availability checks and Forge Studios announcement campaigns/delivery records are retained for up to 180 days. Availability checks contain no server or user IDs; announcement delivery records contain the server and destination channel needed to track delivery. Build jobs and structural backups are retained for seven days. Audit events and closed ticket metadata are retained for 30 days; QOTD history for 90 days. Cleanup runs while the service is running. Guild settings, announcement subscriptions and active module state remain until deletion. This includes the server ID and most recent invite timestamp used to prevent duplicate onboarding messages. Infrastructure logs and provider backups follow the operator-configured retention schedule; this application does not control their expiry.

Delete guild data

The current server owner can use the authenticated deletion endpoint documented on the setup and operations page. Deletion drains module work and removes configuration, module state, tickets, QOTD history, jobs/backups, audit history, usage records, announcement subscriptions and that server’s announcement delivery records. The global announcement text itself is not tied to one guild and may remain until its normal retention period. A server-ID-only suppression record remains to prevent modules recreating erased data. A new owner-approved build re-enables the server. Clear site storage and downloaded backup files separately. Data already in provider backups expires under their retention schedule.

Service providers and security

Discord, Railway/Postgres and the configured AI provider process data needed for their services. Forge does not sell user data. Owner checks, CSRF protection, request limits and redacted operational logging protect management APIs. Never put credentials or sensitive personal information in AI prompts or drafts.