Privacy Policy
Last updated: November 14, 2026
Overview
ForgeFeed (“ForgeFeed,” “we,” “us”) is a Discord bot that streams GitHub activity into Discord as embeds. This policy explains what we collect, why, and the choices you have. We collect only what is needed to deliver the service, and we design for least privilege.
Information we collect
To operate trackers and route updates to the right place, we store:
- Discord identifiers: server, channel and role IDs for your configuration, such as the channel a tracker posts to or the roles allowed to submit issues. Member IDs for members you connect to a GitHub username with /accounts or /mygithub.
- GitHub App installation data: the installation IDs you link, the repositories you register with their branch and display name (including public repositories followed read-only), and the repository metadata (commits, pull requests, issues, workflow runs, releases, stars) needed to build embeds.
- GitHub usernames connected to members: the account's number on GitHub when the member signed in, which keeps their mentions working if they rename the account, and whether they have asked for DMs. Removed with
/accounts unmap, or by the member under/mygithub. - Configuration you set: your trackers and their options and filters, issue and project boards with their entries, label emoji, submission channels, rate alert settings, the time zone, schedules for digests, reminders and leaderboards, and a repository's color and layout.
- Premium counts: on Premium, a weekly count per GitHub username and repository of commits, pull requests, reviews and issues closed, for
/contributors. Only the numbers, kept two years. - Premium card and CI records: on Premium, where each pull request's card and thread are, kept 90 days after it last changes, and per workflow how many runs passed and failed.
- Live issue cards: where each
/github issuecard is and which issue or pull request it follows, until nothing has changed on it for 30 days. - Post records and event counts: a record of each update posted, so nothing posts twice, kept 30 days. A daily count of GitHub events per repository, for the
/trackerssummary, kept 90 days. - Setup dates: when a new server reached each setup step: joining, starting
/setup, linking GitHub, its first repository, its first post, and hitting a plan limit. Only dates, used to see where setup gets stuck, and kept after the bot is removed so the numbers stay honest.
Website analytics
This website (not the bot) uses Google Analytics to count visits and see which pages are useful. Analytics cookies are only set after you accept them in the cookie banner. Until then, and if you reject them, Google receives only cookieless, anonymous signals with no identifiers that link your visits together. Google processes this data under Google's privacy policy. You can change your choice at any time with the “Cookie settings” link at the bottom of every page; rejecting removes the analytics cookies already set.
What we do not collect
- Discord message content. The bot has no Message Content intent and does not read your messages. The exceptions are a message a member right-clicks with Create GitHub issue, which is held in memory for up to 10 minutes to fill in the form and is not stored, and one a member right-clicks with Comment on GitHub, which only fills in the form.
- GitHub passwords or personal access tokens. Linking uses GitHub's official GitHub App flow. Credentials are never requested or stored, and a sign-in token is used once to read who someone is, then dropped. The GitHub sign-in behind a link page is held in memory for up to 15 minutes, so the page's buttons can check your access again when pressed.
- The text of commits, comments or reviews. Activity from GitHub is used to build posts, not kept as a history.
How we use information
- To authenticate to GitHub as a GitHub App and fetch the activity you track.
- To post and update embeds in the Discord channels you choose.
- To enforce plan limits and send the alerts you configure.
- To send the welcome message to whoever added the bot, identified from the server's audit log, or to the server owner if that is not available.
- To send a member a DM about their reviews and runs only when they have turned DMs on under
/mygithub, and to tell a member by DM when someone else signs in as a GitHub account they had connected. - To keep the service reliable by pausing failing trackers and catching up on missed webhook deliveries.
Data storage & security
Configuration and the minimal identifiers above are stored in our database. GitHub webhook deliveries are cryptographically verified before processing, text from GitHub is escaped before it is posted in Discord or shown on a page, and web endpoints are rate limited. All data is scoped per server, so one server can never see or affect another's data.
Data sharing
We do not sell your data. Information is exchanged only with the platforms required to provide the service: Discord (to post messages) and GitHub (to read the activity you track), under their respective terms, plus Google Analytics for visits to this website as described above.
When a member opens an issue from Discord, with /submitissue or Create GitHub issue, the GitHub issue is created with “Submitted from Discord by:” and their Discord name at the top, so it is visible to anyone who can see that repository. @mentions in it do not notify anyone on GitHub.
When a member uses Comment on GitHub, the comment is posted on the pull request by ForgeFeed's GitHub App, signed with their Discord name, so it is visible to anyone who can see that repository, and the thread in Discord says who commented.
Data retention & deletion
You control your data. Remove individual trackers from /trackers, unlink one or every GitHub account with /github unlink, or remove the bot entirely. GitHub access can also be revoked at any time from your GitHub settings. Unlinking GitHub or uninstalling the GitHub App does not delete a server's trackers; they resume if an account is linked again. When ForgeFeed is removed from a server, that server's setup is kept for 90 days, so adding the bot back restores everything, and is then deleted. The retention periods for each kind of record are listed above. To have it deleted sooner, open a ticket at dgden.com or ask in the support server.
Children's privacy
ForgeFeed is intended for users who meet Discord's minimum age requirement. It is not directed at children under that age.
Changes to this policy
We may update this policy as the service evolves. Material changes will be reflected by the “last updated” date above.
Contact
Questions about privacy? Open a ticket at dgden.com once you sign in, or ask in the Discord support server at discord.dgden.com. There is no support email address or contact form.