Skip to content
Legal
Legal pages
gavelTerms of Service
shieldPrivacy Policy
paymentsRefund Policy
infoLegal Notice
More
menu_bookDocumentationhomeHome
forum A question?
Ask us anything about these policies on our Discord server.
Join the Discord →
InviteForge Legal
Legal

Privacy Policy

updateLast updated November 8, 2026

Your privacy is important to us. It is InviteForge's policy to respect your privacy and comply with any applicable law and regulation regarding any personal information we may collect about you, including through our bot InviteForge operating on discord.com and our website invite-forge.com.

Information We Collect

We collect the minimum amount of information necessary to operate the service. This includes:

  • Discord Guild ID — to identify and configure your server
  • Discord User ID — to attribute invites and manage leaderboard entries
  • Dashboard Email address — collected via Discord OAuth when you sign in to the dashboard (email scope); used for account-related and optional marketing communications
  • Invite data Invite codes, usage counts, and join/leave events
  • Message count Per-user message count per server — only the count is stored, never the content of messages
  • Chat activity Daily counts per server: messages and reactions per member, messages per channel, uses of each reaction emoji, and hourly totals for the server. When a new member joins, we also record when they send their first message. Counts and timestamps only, never message content
  • Daily streaks When enabled by a server admin: each member's current and best streak, the last day validated, streak shields owned, whether they turned on streak reminders, and a log of lost and protected streaks
  • Supporter If you boost the official InviteForge Discord server: your Discord user ID, when you started boosting, and which of your servers your boost gives Supporter to. Server owners with an active Supporter server get the Supporter role in the official server
  • Billing Stripe customer and subscription IDs for premium plan management (no card data is stored by us)
  • Permanent & Lifetime For a one-time Pro purchase: your Discord user ID, the server it covers, the plan, amount, currency, status, Stripe checkout and payment IDs, and for Lifetime the history of server transfers (from, to, date, who moved it). No card data is stored by us
  • Streak shop For one-time purchases: your Discord user ID, the server and item, amount, currency, status, Stripe checkout and payment IDs, and for a Full Transfer the one-time code and the account that redeemed it (no card data is stored by us)
  • Premium gifts For a gift: your Discord user ID, the server, the duration (1 month, Permanent or Lifetime), amount, currency, status and Stripe checkout and payment IDs. The server owner is told by Discord message who sent the gift
  • Server stores When you buy from a server's store: your Discord user ID and username, the server, the perk or tip, amount, discount, currency, status, the country of your card (as reported by Stripe), Stripe checkout, payment and subscription IDs, and what you have access to (role, start and end dates, membership status). No card data is stored by us
  • Sellers When you sell on your server: the server and owner IDs, your store settings, your sales and payouts, and your Stripe account ID. Your Stripe account details (name, email, country, bank) stay at Stripe; we only read them from Stripe to show them to you in the dashboard
  • Support In the official InviteForge support server: the answers you give when opening a ticket, the ticket's messages (as a transcript), staff notes, and the rating and comment you leave after it closes
  • Removal feedback When InviteForge is removed from a server, its owner may get a DM asking why. We keep the server ID and name, the owner's Discord user ID, when the bot was added and removed, whether the dashboard was opened or settings were saved, whether the bot had the Manage Server permission, and, if the owner answers, the reason picked and the optional comment
  • Config Server settings such as channel IDs, message templates, and reward configurations
  • Verification When enabled by a server admin: verification session tokens, verification status and score, and — only if the member consents to the anti multi-account check in the Discord verification modal — hashed browser characteristics, a hashed technical cookie, hashed Discord email, hashed Discord server list, and hashed IP address

We do not collect message content from your server, voice data, or passwords. The only exception is the official InviteForge support server, where we read the messages you send to the support bot (help questions and tickets) so we can answer them. Personally identifiable information is limited to what Discord exposes through its API or OAuth, plus the optional extended verification signals you explicitly consent to, all of which are hashed and never stored in plain text.

Dashboard Login & Discord OAuth

InviteForge uses Discord OAuth2 for two distinct purposes. Each flow requests only the scopes it needs:

  • Dashboard login — scopes: identify email guilds guilds.join. Used to authenticate server administrators, display the guild picker for servers they manage, sync their email address, and (once per account, on first dashboard login) add them to the official InviteForge support Discord server via Discord's guilds.join API.
  • Member verification — scope: identify, always. Used to confirm that the person completing verification is the same Discord user who joined the server. Never requests guilds.join, so verifying never adds you to any server.

    If the server administrator has turned on advanced anti-alt signals for that server, and only after you separately consent in the Discord verification modal, the same sign-in additionally requests email guilds so we can resolve your Discord email and server list for the anti-alt score described below. If advanced signals are off, or you don't consent, verification never requests those scopes.

The guilds scope lets us show which Discord servers you can configure in the dashboard (dashboard login) or, for verification with advanced signals on, resolve which servers you're a member of so we can hash and compare that list. The guilds.join scope is used only to add you to our official support server on your first dashboard login so we can share product updates and provide help. You are not added again on later logins, and leaving that server does not affect dashboard access.

Email Addresses & Marketing Communications

When you sign in to the InviteForge dashboard, Discord may share the email address linked to your Discord account (via the email OAuth scope). We store this email alongside your Discord user ID to manage your dashboard account (receipts, license recovery, security messages) and, only if you opt in, to send setup tips, product updates and Premium offers about InviteForge. The same applies when you add the bot from our website: Discord shares your email with us, and we ask before sending you anything promotional.

  • Opt-in — marketing emails are off until you explicitly turn them on: the "Email me" option on the dashboard or after adding the bot, or "Setup tips & Premium offers" on your profile page. Nothing is pre-checked, and we record when and where you said yes
  • Unsubscribe — use the unsubscribe link included in every marketing email, or sign in to the dashboard and turn off "Setup tips & Premium offers" on your profile page at invite-forge.com/dashboard/profile. Either way, the change applies to future marketing emails right away
  • After opt-out — your email remains stored for account purposes unless you request deletion
  • Delivery — marketing emails are sent through Brevo (see Third-Party Services). We do not sell your email address
  • Verification — members completing server verification are never asked for their email address

Member Verification

Servers may enable InviteForge's optional verification gate. A single verification message is posted in the server's verification channel; clicking its Verify me button opens a Discord form (a native Discord modal) asking for your consent before anything is collected. Only after you submit that form is your personal one-time link generated, valid for 10 minutes. Opening that link asks you to sign in with Discord via OAuth2 — this confirms your Discord user ID matches the join event. It is not a bot invite and does not install InviteForge on your account.

  • Always collected — Discord user ID, verification status and score, expiry, and failure reason per session; linked invite event when counting is enabled
  • Advanced anti-alt signals (PRO, optional, off by default) — if the server administrator turns this on, and only after you consent in the Discord verification modal, we collect: browser characteristics (a hashed fingerprint), a technical cookie (a hashed random identifier stored in your browser), your Discord email (hashed), your Discord server list (each server ID hashed individually), and your IP address (hashed). Every one of these is hashed with a server-specific salt immediately on receipt — we never store any of them in plain text, and a hash cannot be reversed back to the original value
  • Why — each signal is compared, as a hash, against other verified members on the same server to catch the same person verifying multiple accounts. Matches add points to a weighted score set by the server administrator
  • Outcome — the score decides one of three outcomes: passed (you get the server's verified role), flagged (held for a moderator's manual review, with an Approve/Reject decision), or blocked. You are sent a plain-language Discord DM telling you the outcome; the score and the matched signals are not shown to you
  • What moderators see — when a verification is held for review, the server's moderators see a review card in their private log channel with the score and thresholds, which signals matched (for example "same IP address"), and the Discord user ID and username of the other verified members of that server it matched. The signal values themselves (your IP address, email, browser fingerprint, cookie and server list) are never shown to anyone
  • Review decisions — if a moderator rejects your verification, you can't request a new verification link on that server until a moderator lets you in. If you leave the server while a verification is open, it is closed and you verify again if you come back
  • Captcha (PRO, optional) — if enabled, members may be asked to complete an invisible captcha challenge before verification completes
  • Retention — verification signal hashes are purged after 90 days by default

Server administrators control whether verification is enabled, whether advanced signals are on, the point value of each signal, and the review/block thresholds. InviteForge processes verification on their behalf according to their configuration.

Chat Activity & Daily Streaks

On servers where chat activity statistics are active, InviteForge counts activity so server admins can see how their community is doing. The bot sees that a message was sent (its author and channel) or that a reaction was added, adds one to a counter, and never reads or stores what was written.

  • Who sees it — admins of that server, in the InviteForge dashboard (for example the most active members and channels, or how many new members sent a first message). The full statistics are shown on PRO servers. Counts are never shared with other servers
  • Retention — daily counts are deleted after 62 days and hourly totals after 3 days
  • Daily streaks — only on servers where an admin turned streaks on. Your streak is based on whether you sent enough messages that day. Streak reminders are sent by DM only if you turn them on with /streak remind, and you can turn them off the same way. The log of lost and protected streaks is deleted after 35 days
  • Public leaderboards — if a server makes its leaderboard public, its invite and streak rankings, including members' Discord usernames and avatars, can be seen by anyone with the link. Server admins can turn this off at any time

Server Stores (Monetization)

Servers using Monetization can sell roles, time passes and monthly memberships, and accept tips, through a store on invite-forge.com. Payments are processed by Stripe and made to the seller's own Stripe account.

  • Signing in — to buy, you sign in with Discord. We only ask for your Discord identity (the identify scope), to know who to give the role to and to check that you're a member of the server
  • What the seller sees — the server's admins see their sales and members in the InviteForge dashboard: your Discord username and ID, what you bought, the amount, your card's country, and your membership status. They never see your full card number. As the merchant, the seller also sees the payment in their own Stripe Dashboard, with the name and email you entered and your card's brand, country and last four digits
  • What Stripe receives — your payment details and the email you enter at checkout, under Stripe's own Privacy Policy. Stripe sends your receipt on behalf of the seller. For sellers, Stripe also collects the identity and bank details it needs to verify your account and pay you out
  • Messages — if the server turned them on, a thank-you message mentioning you may be posted in one of its channels after a purchase, and InviteForge may send you a Discord DM when a time pass is about to end or a membership payment fails
  • Public store — the store can show how many members have each perk (a number only, never who)

InviteForge Ads

Some servers show InviteForge Ads in one of their channels. Ads are not targeted at you: a server only chooses which kinds, categories and languages of ads it accepts. What we collect is used to tell real clicks from fake ones, to bill advertisers and pay publishers correctly, and to handle reports.

  • When you click an ad — your Discord user ID, the ad and the server, the time, when you joined that server, whether you have staff permissions there, and your account's creation date (which Discord IDs contain)
  • On the check page — before the link opens, a short check collects your IP address, characteristics of your browser and device (a fingerprint), a random identifier kept in a technical cookie set only by this page (if_ads_cid, kept 1 year), and, if enabled, the result of an invisible captcha. These are hashed with a secret key as soon as we receive them, the original values are never stored, and the hashes are only compared with other clicks on the same ad
  • Server ads — if you join the advertised server shortly after clicking, we note that you joined and whether you're still a member 1, 7 and 30 days later. When InviteForge is also in that server, we count how many messages you send there in your first 7 days (a number, never the content). This measures the quality of the ad and of the server that showed it
  • Reports — when you report an ad, we keep your Discord user ID with the report so each member counts once
  • Who sees what — advertisers and publishers only see totals (clicks, blocked clicks and why, joins). They never see who clicked or reported. Our team can look at click records to review fraud and reports
  • Advertisers and publishers — we keep the server's ads, campaigns, ad wallet and its history, and review decisions, and InviteForge may DM the server owner about reviews. Top-ups are paid through Stripe, which receives your payment details. For withdrawals, Stripe collects the identity and bank details it needs to verify your account and pay you out
  • First top-up bonus — to offer the bonus once per advertiser, we keep, with each top-up, the Discord user ID of the person who paid and what Stripe tells us about the card: its fingerprint (an identifier of the card), its brand and its last 4 digits, never the full card number, which we never receive. When you open the payment, we also keep your IP address, characteristics of your browser (a fingerprint) and the random identifier of the if_ads_cid technical cookie, hashed with a secret key as soon as we receive them; these hashes are deleted after 12 months. If InviteForge verification linked your Discord account to another one, that link is checked too. We compare all of this, the server's owner, the server or website it advertises and the text of its ads with those of servers that already got the bonus. This is only used to decide on the bonus and to prevent fraud; our team sees what matched, other servers never do
  • Waitlist — before Ads opens, you can join its waitlist from the dashboard or from invite-forge.com/ads (there, signing in with Discord only asks for your username and email: scopes identify and email). We keep your Discord user ID, the email address you enter, what you want to do (earn, advertise or become an affiliate), the server you joined from and the date, only to give you access before everyone else and tell you when it is ready (by email or Discord DM). You can leave the waitlist from the same page at any time, and it is deleted once Ads has opened to everyone
  • Retention — the hashes from the check page are deleted after 30 days. Click records and wallet history are kept as billing records
  • Legal basis — our legitimate interest in preventing fraud (including bonus fraud) and billing correctly, and, for advertisers and publishers, the performance of our agreement with you

Affiliate Program

When you open an affiliate link (invite-forge.com/r/…), we store the affiliate's code in a cookie in your browser for 60 days and count the visit. If a server you manage then buys ad credit for the first time, the server is linked to that affiliate for a limited time.

  • What the affiliate sees The name and icon of the linked server, the number of valid clicks its ads received, what it spent on them and the resulting commission. Never who paid, payment details or anything about your members
  • Affiliates For affiliates, we store their Discord user ID, username and avatar, their link, visit counts, commissions and payouts, to run the program and pay them

Website Analytics

We measure how invite-forge.com is used with Databuddy, an open-source analytics tool that we host ourselves. The script is served from our own domain and the data stays on our servers; it is not shared with Databuddy or anyone else.

  • What is recorded — pages viewed, the referring site and campaign (UTM) tags, clicks on links to other sites (such as "Add to Discord") and on a few marked buttons, page load performance (Web Vitals), and JavaScript errors. Plus the browser, operating system, device type, language, and approximate location (country, region, city)
  • Not recorded — your IP address and full user agent are used only to work out the approximate location and device, and are not stored. Analytics doesn't set cookies: it keeps a random anonymous identifier in your browser's local storage to count unique visitors, which you can clear at any time. Member verification pages are never tracked, and server IDs in dashboard URLs are replaced with a placeholder
  • Why — to see which pages and sources bring new server owners, and to find slow pages and errors

Website Assistant & Support Tickets

The chat bubble on invite-forge.com answers questions about InviteForge with an AI model, based on our public documentation. Please don't share passwords, payment details or other sensitive information in it.

  • What is sent — your question and the last few messages of the conversation are sent from our servers to Groq's API to generate the answer
  • What we keep — we don't store assistant conversations on our servers. The conversation stays in your browser's session storage for the current tab, and is cleared when you close the tab or open a support ticket. To limit abuse, we count the questions sent from each IP address; that counter, which includes the IP address, is deleted after 10 minutes. We also keep anonymous daily totals for 40 days (number of questions, which AI model answered, response time, the page the chat was used on and the documentation sections linked in answers), never what you wrote and never your IP address
  • Groq — according to Groq's documentation, Groq doesn't keep the content of requests by default, but may log it for up to 30 days to fix errors or investigate abuse. That data is stored in the United States
  • Support tickets — you can open a ticket from the chat after signing in with Discord. We then create a private channel in the official InviteForge Discord server, visible to you and our support staff, with your Discord account, the topic and description you entered, and your conversation with the assistant. The channel is deleted one hour after the ticket is closed. A transcript, including the conversation, is posted in a staff-only channel and sent to you by Discord DM. The conversation is also kept on our servers for 30 days so it can be shown in the ticket

Legitimate Reasons for Processing Your Information

We only collect and use your personal information when we have a legitimate reason for doing so. Data is collected solely to provide, maintain, and improve the InviteForge service — including invite tracking, leaderboard ranking, reward automation, and premium subscription management.

How We Use Your Information

  • To track and attribute Discord server invites in real time
  • To generate leaderboards, analytics, and statistics for server administrators
  • To trigger auto-role rewards when invite milestones are reached
  • To send join/leave messages and join DM messages based on your server's configuration
  • To briefly mention new members in channels chosen by the server admin (the message is deleted right away), and to wait until a member has completed Discord's server onboarding before welcoming them, when the admin enables it
  • To run daily streaks, streak rewards, and opt-in streak reminders
  • To show chat activity statistics to server admins
  • To measure how our website is used and find slow pages and errors (self-hosted analytics)
  • To manage Supporter status (the "Add InviteForge" buttons option or a boost of the official server) and the matching Supporter role
  • To process streak shop purchases and refunds
  • To deliver Premium gifts, process their refunds and tell the server owner who sent them
  • To run server stores: process payments, give and remove roles, handle memberships, refunds and disputes, show sales to the server's admins, take InviteForge's fee, and pay out what's left of DonateBot-era balances through Stripe
  • To answer questions in the website chat assistant
  • To answer support questions and handle support tickets in the official InviteForge server, including tickets opened from the website
  • To manage premium subscriptions and one-time Pro purchases (Permanent, Lifetime) via Stripe, including Lifetime transfers
  • To run optional member verification and role assignment when enabled by a server administrator
  • To send optional marketing emails to dashboard users who remain opted in
  • To display your server's data on the InviteForge dashboard

Data Retention

We retain your data for as long as your server has InviteForge installed or as long as necessary to provide the service. When you remove the bot from your server or request deletion, your data will be deleted or anonymised within a reasonable period.

Some data has a fixed, shorter lifetime: chat activity counts are kept 62 days (hourly totals 3 days), the streak loss log 35 days, verification signal hashes 90 days by default, and the hashed signals from the InviteForge Ads check page 30 days. A member's streak is removed if a server admin resets it. Website assistant conversations attached to a support ticket are kept 30 days, and the assistant's per-IP counters 10 minutes.

Dashboard account data (Discord user ID, email, marketing preference) is retained while you use the dashboard or until you request deletion. Billing records may be retained longer where required by applicable accounting or legal obligations. This includes server store purchases and payouts, and InviteForge Ads clicks, top-ups, earnings and withdrawals, which are kept even if the bot is removed from the server.

Third-Party Services

We use the following third-party services to operate InviteForge:

  • Discord — the underlying platform. Subject to Discord's own Privacy Policy.
  • Stripe — payment processing for premium subscriptions, one-time Pro purchases, Premium gifts, streak shop purchases, server store purchases (made on the seller's own Stripe account, through Stripe Connect), and InviteForge Ads top-ups and publisher withdrawals (through Stripe Connect). Stripe does not share card details with us.
  • Sentry — error monitoring for our API and Discord bot, hosted in the EU. When something breaks, Sentry receives a technical error report, which can include identifiers such as a Discord server or user ID. Subject to Sentry's Privacy Policy.
  • Groq — questions asked to the website assistant on invite-forge.com, and to the support bot's AI help in the official InviteForge support server, are sent to Groq's API to generate an answer. Subject to Groq's Privacy Policy.
  • Brevo — email delivery and contact list management for opted-in dashboard users. Subject to Brevo's Privacy Policy.
  • Resend — delivery of transactional emails, such as the code to move a Lifetime license to a new Discord account or the notice that a Lifetime license was freed. It receives the recipient's email address and the message. Subject to Resend's Privacy Policy

We do not sell, rent, or trade your personal information to any third party.

Discord Gateway Intents

The InviteForge Discord bot requests the following privileged Gateway Intents. Each is used for a specific, limited purpose directly related to the bot's invite-tracking and server-management features. We do not use these intents for surveillance, advertising, or any purpose unrelated to the service described on this page and in our documentation.

  • GUILD_MEMBERS Used to detect when members join or leave a server, attribute invites to the correct inviter, update leaderboard counts, assign verification roles, deliver reward roles, and send join/leave messages configured by the server administrator. Without this intent, invite tracking and verification cannot function. This is a privileged intent.
  • GUILD_MESSAGES Used to count messages per user per server (message events only — author and channel IDs). These counts are used for the optional minimum message requirement for giveaway eligibility, daily streaks, and the chat activity statistics shown to server admins. Counting never reads message text, embeds, or attachments. Not a privileged intent.
  • MESSAGE_CONTENT Used only for text commands (for example ,if invites). When a message is posted, the bot only checks whether it starts with the command prefix; every other message is ignored right away. For a command, the text is read in memory to run it and reply. Message content is never stored, logged, shared with third parties, or used to train AI models. Server admins can turn text commands off in the dashboard (Settings → Text commands). Commands that mention the bot (@InviteForge invites) work without this intent. This is a privileged intent.
  • GUILD_MESSAGE_REACTIONS Used to count reactions per member and per emoji for the chat activity statistics. Not a privileged intent.

Security

We protect your information within commercially acceptable means to prevent unauthorised access, disclosure, copying, use, or modification. No method of electronic transmission or storage is 100% secure, and we cannot guarantee absolute security.

Your Rights

You have the right to:

  • Request access to the personal data we hold about you
  • Request correction of inaccurate data
  • Request deletion of your data (right to erasure)
  • Object to or restrict processing of your data
  • Unsubscribe from marketing emails at any time, using the link in any marketing email or from your profile page at invite-forge.com/dashboard/profile
  • Lodge a complaint with a data protection supervisory authority

To exercise any of these rights, contact us at the address below.

Changes to This Policy

We may update this Privacy Policy from time to time to reflect changes to our practices or for legal and regulatory reasons. Updates will be posted on this page with a revised "Last updated" date. Continued use of the service after changes are posted constitutes your acceptance of the updated policy.

Contact

For any questions or requests regarding this Privacy Policy, please contact us at our Discord server.

gavelTerms of Servicearrow_forwardpaymentsRefund Policyarrow_forwardinfoLegal Noticearrow_forward