Privacy Policy

This policy explains what information InviteCount collects when you use the InviteCount Discord bot, its dashboard and the website invite-count.xyz, why we need it, how long we keep it and what you can do about it.

Who we are

InviteCount is run by Alexandre RODRIGUES MOREIRA, who decides how the personal data described in this policy is used (the data controller). Contact: [email protected]. Our servers and database are hosted by Contabo GmbH in Germany.

The short version

• We store Discord IDs, counters and server settings. Outside ticket channels and honeypot (trap) channels, the bot does not read or store the content of your messages: it only counts them.
• In a ticket channel, the bot can save the conversation as a transcript if the server turns this on. In a trap channel, it shows the message that triggered the trap in the report posted on Discord, without storing it.
• Server administrators choose which features run on their server. The public web leaderboard of a server is on by default, and its administrators can take it off the web at any time.
• We do not sell or rent your data, and we do not use it for advertising.
• Anyone can ask us to access or delete their data.

What we collect

When the bot is in a server

To track invites and run the features a server turns on, the bot stores, linked to the server ID and to members' Discord user IDs:

• Invite tracking: who invited whom, the invite code used, when a member joined or left, whether the join was detected as fake, the members the server has already seen (to recognize members who come back), and each member's invite counters (regular, bonus, fake and left).
• Growth analytics: each join and departure with its source (invite code and inviter, vanity link, bot added, or unknown) and whether it was counted as fake. These events feed the charts, the analytics of the dashboard and the growth reports.
• Messages and levels: how many messages each member has sent, in total and per day, and their XP and level, if the server uses these features.
• Giveaways: the prize, the host, the members who entered and the winners. When a giveaway has entry conditions, the bot checks the member's roles, account age, time on the server or message count when they enter.
• Tickets, honeypot, raid protection and website verification: see the sections below.
• Badges shown on a member's profile, and members a server has hidden from its leaderboards or blacklisted from its invites.
• Server settings: welcome, leave and join messages, roles and channels, verification, logs (including the webhook the bot posts logs with), leaderboards, invite labels (names and roles given to invite links), growth reports, ticket types and panels, honeypot and raid protection settings, card designs, the bot's profile on the server, the public leaderboard settings and the other options the administrators choose.

Some features read information from Discord when they run without storing it, for example the age of a member's account for fake invite and raid detection, or a member's avatar when the bot draws a level card or a welcome banner.

Message content

Discord only gives bots the text of members' messages through its "Message Content" permission, which the bot uses only once Discord has granted it to us. Even then:

• the bot reads the content of messages only in ticket channels (to keep it in transcripts) and in honeypot channels (to show the message that triggered the trap in the report posted on Discord, without storing it);
• everywhere else, it only counts messages (who sent a message, in which channel and when) for message counting and levels. It does not read or keep what they say, and it does not keep messages in memory;
• the only other message it looks at is a message made only of a mention of the bot, to answer with a help message (Discord always shows bots the messages that mention them). Nothing is stored.

Without this permission, transcripts only contain the bot's own messages and the form answers, and honeypot reports say that the content is not available.

Tickets

When a server uses tickets, the bot stores for each ticket: the member who opened it, the staff member who claimed it, the ticket type and panel used, the channel name, the dates of opening, first answer and closing, how it was closed, its events (claimed, renamed, members added, automations...) and the answers given to the opening form. If the server turns on the satisfaction survey (Premium), the member who opened the ticket receives a rating request by direct message after closing, and their rating from 1 to 5 is stored with the ticket.

Transcripts. If the server turns them on, the bot saves a transcript when a ticket is closed: a page containing the last 5,000 messages of the ticket channel (each author's display name and avatar, the date, the text, the embeds and the attached files) and the form answers. Attached files are copied when the transcript is made, up to 8 MiB per file and 50 MiB per transcript; above these limits, or when Discord no longer provides a file, only its name is kept. The page is compressed and stored with these files in a private storage space at Cloudflare (R2), under a random key; it is never public. Transcripts can only be opened after logging in with Discord, by the server's administrators (Administrator or Manage Server permission), by members who have a support role for that ticket type, and by the member who opened the ticket if the server allows it or sent them the link when closing. The attached files are then shown through temporary links, valid for 6 hours, created only after this access check. Transcripts made while a server is on the free plan are deleted after 30 days; those made while it has Premium (and those of a server that gets Premium) are kept with no time limit as long as the server has Premium. If the server loses Premium, they are deleted 30 days after the loss, unless Premium comes back before then. A transcript's files are deleted with it, and transcripts are in any case deleted with the server's ticket data (see "How long we keep it").

Honeypot and raid protection

Honeypot. Administrators can set up trap channels that real members are told not to use. When someone posts there, the bot applies the sanction chosen by the server: by default, the member is removed from the server and their messages of the last 24 hours are deleted; a server can also choose a ban, a timeout or a report only. The owner, administrators, members who can manage the server and the roles and members the server exempts are never sanctioned. The bot records the member's ID and username, the channel, the sanction and whether it succeeded, and the date. The text of the message is never written to our database: it is only shown in the report posted in the server's log channel on Discord, which also shows the age of the member's Discord account (worked out from their ID) and when they joined the server. These records are deleted after 3 days on free servers and after 30 days on Premium servers.

Raid protection. To detect a raid, the bot looks at how many members join per minute and at the age of their accounts. When it detects a raid, it records an incident: when it started and ended, the IDs of the members who joined during it and of those whose accounts were recent, the invites used (code, creator and number of joins), the members removed on arrival by the account age filter, the actions taken (who took them and when: invites paused, verification strengthened, recent accounts removed, raid banned) and a summary posted in the server. Depending on the settings chosen by the administrators, members can be removed or banned automatically or after a moderator's action. Incidents are deleted after 3 days on free servers and kept with no time limit on Premium servers, until the server's data is deleted.

Website verification

When a server uses the "website" verification level, the bot sends each new member a personal link, valid for 15 minutes and usable once. The verification page shows the server and your Discord name and avatar, and uses Cloudflare Turnstile to check that you are not a robot: for this check, Cloudflare processes technical signals from your browser and your IP address, under its own privacy policy. We only store a fingerprint (SHA-256) of the link, the server and member it was made for, and when it was used; these are deleted about one day after the link expires. Your IP address is used to limit abuse and is passed to Cloudflare for the check, but it is not stored with the verification. The other verification levels (button and image captcha) take place in Discord.

Bot profile, cards and banners

• Bot profile (Premium): when administrators give the bot its own nickname, bio, avatar or banner on their server, the images (PNG, JPEG or GIF, up to 10 MiB each) are sent to Discord, which displays them, and stored in a private storage space at Cloudflare (R2) so they can be applied again, for example when the bot is added back. A replaced or removed image is deleted, and all of them are deleted when an administrator restores the default profile; they are otherwise kept as server settings.
• Card designs (level card and welcome banner): the design (layers, texts, colors, fonts) is stored as a server setting. An image placed in a design is either the web address (https) of an image hosted elsewhere, in which case we store the address and not the image, or an image uploaded from the dashboard (see below). To draw a card, our server downloads these images and the avatar of the member concerned from Discord, draws the picture and the bot sends it to Discord. We do not keep the drawn picture. Drawing requests are signed, so only the bot can order one.
• Images uploaded from the dashboard: images that administrators upload for the bot's messages (embeds) or for card designs are stored at Cloudflare (R2), at a public web address made of the IDs of the server and of the uploader followed by a random name, so it cannot be guessed. Anyone who has this address can see the image, since Discord and our card drawing load it from there. These images are not deleted automatically, because saved messages and designs keep using them; you can ask us to delete them.

Public leaderboard

Every server has a public leaderboard, on by default: its invites, messages and levels leaderboards on a page of our website, at an address made of the server's ID (invite-count.xyz/leaderboard/ followed by the server ID), readable without logging in. A Premium server can also give it a custom link. The page shows the server's name, icon and member count and, for each ranked member, their display name, avatar and counter. If the administrator turns on the details, it also shows the breakdown of invites (regular, bonus, left and fake), the share of invited members still on the server and the latest member invited (display name, avatar and date). Only members still on the server are ranked: members hidden by the server and members who left are left out. User IDs and usernames are never shown, and a latest member invited who has since left is shown without their name or avatar. The page asks search engines not to index it, but anyone who has the address can see it. The server's administrators can take it off the web at any time, from the dashboard or with /leaderboard unpublish. If the server loses Premium, its custom link no longer shows the page and stays reserved for 30 days, then it is released; the address with the server's ID keeps working. If you do not want to appear on it, ask the server's administrators to hide you, or contact us.

Reports and exports

• Growth reports: if the administrators turn them on, the bot posts every month (or every week with Premium) a report in the channel they choose, with joins, leaves and the top inviters of the period.
• CSV exports (Premium): administrators can download the analytics, the leaderboards and the lists of invited members as CSV files. Files are made when requested and sent directly to the administrator; we do not keep a copy. Once downloaded, the server is responsible for them.

When you log in to the dashboard

You log in with Discord. We only ask Discord for the identify and guilds permissions: your user ID, username and avatar, and the list of servers you are in, so the dashboard can show the servers you manage. We never see your Discord password or email address.

• Your login session is kept in an encrypted cookie on your device for up to 7 days.
• For security, we record each login, logout and dashboard access with your user ID, IP address, browser (user agent) and date.

When you get Premium

Premium is bought on Patreon. To recognize your subscription, we read from Patreon your membership tier, your patron status and the Discord account you connected to Patreon. We store your Discord user ID, your tier, when your Premium started and the servers where you activated it. Payments are handled entirely by Patreon: we never see your card or payment details.

When you visit the website

• Cookies: the website only sets the cookies needed for the dashboard login (your session and a short-lived security cookie during login).
• Audience measurement: the website may use Google Analytics to count visits and pages viewed. It is only loaded after you accept it.
• Error reports: when a page or the bot crashes, Sentry receives a technical report (for example the page, the error and your browser) so we can fix it.
• Like any website, our hosting and content delivery providers process technical data such as your IP address to deliver pages and protect the service against abuse.

When you contact us

If you email us or ask for help in our support server, we receive what you send us, for example your Discord username and your message.

Why we use it

• To provide the bot and the dashboard (invites, messages and levels, giveaways, tickets, analytics, reports, cards, bot profile and each server's settings): this is necessary to provide the service that server administrators asked for when they added the bot; for the members of their servers, it relies on the legitimate interest of the server and of InviteCount in running the features the community uses.
• To protect servers (honeypot, raid protection, website verification, fake invite detection): legitimate interest in protecting communities against spam, raids and automated accounts.
• To show a public leaderboard: on by default for every server, on the basis of the server's legitimate interest in showing its community; its administrators can turn it off, and you can object as explained above.
• To provide Premium and activate it on the right servers: necessary to perform your subscription.
• To keep the service secure, detect abuse and fix errors: legitimate interest.
• To answer your support requests: legitimate interest, or the performance of your subscription when it concerns Premium.
• Audience measurement relies on your consent, which you can withdraw at any time.

We may also process information when the law requires it.

Who we share it with

We never sell your information. We only rely on the services needed to run InviteCount:

• Discord, where the bot runs, which handles the dashboard login and which receives what the bot posts and the bot profile images;
• Cloudflare, which protects and delivers our website and API, runs the Turnstile anti-robot check of website verification, and stores files with its R2 service (transcripts and their attached files, bot profile images and images uploaded from the dashboard);
• our hosting provider (Contabo GmbH), which runs our servers and our database;
• Patreon, which processes Premium payments;
• Sentry, for error reports, and Google, for audience measurement if you accept it.

Some of these providers are located outside the European Union, in particular in the United States. Transfers then rely on the safeguards these providers offer under the GDPR, such as adequacy decisions or standard contractual clauses.

Inside a server, the bot shows the stored information to the server's members and administrators, for example in leaderboards, welcome messages, logs, reports and the commands that show a member's invites. Transcripts are only shown to the people listed above, and a public leaderboard to anyone who has its link. We may also disclose information if the law requires it.

How long we keep it

• While the bot is on a server, its data is kept, except for the shorter periods below.
• When the bot is removed from a server, that server's member data (invites and invite counts, who invited whom, the history of joins and leaves, analytics events, message counts and levels, giveaway entries, tickets and their transcripts, honeypot records, raid incidents and verification links) is permanently deleted 90 days after the bot left, unless the bot is added back before then; if it comes back within 90 days, everything is still there. The server's settings (welcome and leave messages, roles, verification, logs, ticket types, card designs, bot profile and other configuration) are always kept, so the server finds its setup again if it adds the bot back.
• Ticket transcripts (with their copied files): 30 days when made on a free server; no time limit when made on a Premium server, as long as it has Premium, then 30 days from the loss of Premium (no time limit again if Premium comes back before then).
• Honeypot records: 3 days on free servers, 30 days on Premium servers.
• Raid incidents: 3 days on free servers; no time limit on Premium servers.
• Analytics events (joins and leaves with their source): 32 days on free servers; no time limit on Premium servers.
• Messages per day (leaderboards by period): 32 days.
• Day-by-day history of joins and leaves (growth charts) and records of dashboard visits: 365 days.
• Website verification links: valid for 15 minutes, deleted about one day after they expire.
• Bot profile images: until an administrator replaces or removes them, or restores the default profile.
• Images uploaded from the dashboard: not deleted automatically, since saved messages and designs use them; deleted on request.
• Public leaderboard link: kept 30 days after the server loses Premium, then released.
• Dashboard login session: up to 7 days. Login and logout records are deleted after 12 months.
• Premium information follows your Patreon membership.
• CSV exports are not kept.

When a server loses Premium, the free periods apply again 30 days after the loss, unless Premium comes back before then: analytics events, raid incidents and honeypot records older than the free periods, and transcripts kept with no time limit, are then deleted. Administrators can delete invites, message counts and levels at any time with the /delete commands, and can ask us to delete any other data of their server. You can also ask us to delete your data, or a server's data, at any time (see below).

Your rights

Under the GDPR, you can ask to access, correct or delete your information, to restrict its use or to receive it in a portable format, and you can object to its use. Email [email protected] or ask in our support server, and include your Discord user ID (or the server ID) so we can find the data. We answer within one month. If you think we have not handled your data properly, you can also complain to a data protection authority, such as the CNIL in France.

Children

InviteCount is meant for people old enough to use Discord under Discord's Terms of Service.

Security

We protect the information we keep with reasonable technical measures: encrypted connections, encrypted login sessions, restricted access to our servers, transcripts and their files kept in a private storage space and readable only by authorized people after logging in, with temporary signed links for the attached files, and signed requests between the bot and the server that draws cards. No system is perfectly secure, but we only store what the service needs, which limits the risk.

Changes

We may update this policy when the bot or the law changes. The date at the top of this page shows the latest version.

Contact

Questions about your privacy: [email protected].