CrowBots - Faire vérifier son bot (formulaire Discord)

Depuis la mise à jour de la politique de Discord (juin 2026), l'accès aux intents privilégiés (informations sur les membres, présence, et contenu des messages) dépend désormais du nombre d'utilisateurs de votre bot, et non plus du nombre de serveurs. Tant que votre bot reste accessible à moins de 10 000 utilisateurs, vous n'avez aucune démarche à faire : il suffit d'activer les intents dans l'onglet Bot du Portail Développeur. L'ancien seuil de 100 serveurs n'est plus utilisé.

Ce n'est qu'à partir de 10 000 utilisateurs que Discord demande de remplir un formulaire pour conserver l'accès à ces intents. Vous recevez alors une notification (par e-mail et/ou message privé système) ainsi qu'une alerte dans le Portail Développeur, et vous disposez de 90 jours pour soumettre votre demande. Bonne nouvelle : pendant tout l'examen, votre bot continue de fonctionner normalement et peut toujours rejoindre de nouveaux serveurs. En revanche, si le formulaire n'est pas envoyé dans ce délai, l'accès aux intents sera retiré (vous pourrez toujours en refaire la demande plus tard).

Comme votre Gestion V2 utilise ces trois intents (modération, onboarding, logs, rôles supporters, annonces Twitch...), vous devrez tôt ou tard remplir cette demande. Pour vous éviter d'avoir à rédiger les justifications vous-même, nous avons préparé ci-dessous l'intégralité du formulaire déjà rempli : il vous suffit de recopier chaque champ.

Comment procéder

1. Rendez-vous sur le Portail Développeur Discord et sélectionnez l'application de votre bot.
2. Ouvrez le formulaire de demande d'intents privilégiés (« Request Intents »), accessible via l'alerte affichée sur votre application une fois le seuil de 10 000 utilisateurs atteint (ou le lien reçu dans la notification).
3. Recopiez chaque champ ci-dessous dans le champ correspondant (un bouton Copier est disponible pour les textes longs).
4. Cochez les trois intents, acceptez les conditions, puis cliquez sur Submit.

⚠️ Astuce : les valeurs ci-dessous décrivent fidèlement le fonctionnement standard d'un Gestion V2. Si une fonctionnalité ne s'applique pas à votre serveur, adaptez le texte avant de l'envoyer.

ℹ️ Bon à savoir : une fois l'accès accordé, Discord demande de renouveler la demande une fois par an pour le conserver (vous serez prévenu à l'approche de l'échéance). La « App Verification » et la demande d'intents privilégiés sont par ailleurs désormais deux procédures distinctes.

Reproduction du formulaire Discord ci-dessous, prêts à copier :

Request Intents

Application Details

What does your application do? Please be as detailed as possible, and feel free to include links to image or video examples.

This application is a private server-management and moderation bot for a single large community. Its core features are: automated moderation (anti-invite/link filtering, configurable banned-word filtering, strike/sanction system, raid protection, blacklist enforcement), member onboarding (captcha/verification gating, welcome & leave messages, automatic role assignment), message audit logging (edit/delete logs to a staff channel), role menus and reaction roles, a supporter-recognition system, Twitch go-live announcements, and various community utility commands. The app operates only in the server(s) it has been explicitly added to by me and acts solely on configuration set by that server's administrators.

Do you have a public Privacy Policy telling your users about their data usage?

Privileged Gateway Intents

Which intents are you applying for, if any? (Leave blank if you do not need any of these)

Server Members Intent

Presence Intent

Message Content Intent

You have the following limited intents and may apply for their full intents: Server Members Intent, Message Content Intent, Presence Intent.

Server Members Intent

Why do you need the Guild Members intent?

Member onboarding and moderation. Specifically: welcome and leave messages, captcha/verification gating of new members with automatic kick on timeout, automatic role assignment on join, blacklist enforcement (auto-banning known bad actors on join), raid/anti-spam protection, role menus, the supporter-role system, and the moderation toolkit (strikes, mutes, kicks, bans), all of which require resolving and tracking member objects and reacting to member join/leave/update events in real time.

Member events trigger immediate actions (send a welcome message, assign a role, run verification, enforce a blacklist, apply a sanction). Member objects are read to evaluate roles and join dates for moderation logic. The bot does not build profiles of members or use the data for any purpose beyond the server-management features the server's admins have configured.

No member personal data is stored in bulk. The app persists only minimal moderation metadata keyed by user ID, e.g. sanction/strike counts and blacklist entries (which exist to enforce moderation rules and are removable by server staff). No member lists, profiles, or message history are retained.

Please provide links to screenshots and/or videos that demonstrate your use case

https://imgur.com/C3Yjc9o
https://imgur.com/yek8XaG

Are you storing any API Data off-platform (outside of Discord)?

Presence Intent

Why do you need the Guild Presences intent?

There are several features driven by presence updates such as a supporter-recognition role that is granted/removed when a member adds (or removes) the server's configured tag/keyword in their status or activity; Twitch go-live announcements, which detect when a member begins a Streaming activity and post an announcement; online-member counting for server statistics, and so on...

Presence updates are evaluated the moment they arrive and acted on immediately (add/remove a role, post a live announcement, update a counter). The activity/status text is only checked against the server-configured keyword; the streaming activity is only read to obtain the stream link/name for the announcement.

Presence and activity data is processed transiently in the event handler and is never written to persistent storage. Only the resulting role assignment (a normal Discord role) persists, as managed by the server.

Please provide links to screenshots and/or videos that demonstrate your use case

https://imgur.com/Epxlvkk
https://imgur.com/4uO2SFP

Can users opt-out of having their Presence data tracked?

Yes

Are you storing user activity data off-platform (outside of Discord)?

Message Content Intent

Can users opt-out of having their message content data tracked?

Yes

Are you storing message content data off-platform (outside of Discord)?

Will the message content data be used to train machine learning or AI Models? If yes, please explain how in the text box below, including how such models would be used.

Why do you need the Message Content intent?

Moderation and audit logging such as anti-invite/anti-link filtering that scans messages for Discord invites and external links and removes violations; a configurable banned-word filter that regex-matches message text and removes violations with a strike; message edit and delete audit logs that record content to a staff-only log channel; parsing of the server's configured customizable key-word trigger events.

Message content is inspected at receipt for moderation rules and, where logging is enabled by the server, forwarded to the staff-configured audit-log channel. It is used solely for the moderation, logging, and command features the server admins have enabled, never for analytics, training, profiling, advertising, or sharing with third parties.

Persistent storage of message bodies is not performed. Moderation records persisted by the app contain only the violation type and user ID, not message text.

Please provide links to screenshots and/or videos that demonstrate your use case

https://imgur.com/yRjh8Bz

Acknowledgement

By clicking Submit, you certify that the information provided above is accurate and complete, and that you and your app are in compliance with Discord's Developer Terms of Service and Developer Policy. If this app is owned or operated by an entity, you confirm that you have the authority to certify on its behalf.

Submit