Some Guildify features process additional data. They are never a condition of using the Service: a community administrator decides whether to enable a feature for the community, and you can switch each purpose off for yourself at any time with the /privacy command in Discord or under Settings → Data & Privacy on the website. Withdrawing consent stops all further processing for that purpose and does not affect processing carried out before withdrawal.
Live Raid Radar (presence data). When you are signed up to a guild event, Guildify can read your Discord online status (online, idle, do-not-disturb, offline) and the name of the game you are currently playing, in order to show raid leads who is actually in game and in voice. This requires your explicit consent, only runs while an event window is active, is sampled at most once every five minutes, is never shared with third parties, and is deleted after 30 days.
Game catalogue (anonymous presence shapes). Independently of any event, while the bot is installed in a server it records the shape of the Discord Rich Presence activities it can see: the activity or game name, the activity type, the application identifier, and a truncated, link-stripped copy of the presence fields the game itself publishes (which can include a character name, zone or lobby). These rows are aggregated across members per game and activity type, are never linked to a person, and do not contain your Discord user ID, username, avatar or any per-person timestamp. They are used to keep an accurate list of real games and applications and to build game-specific parsing for the presence features described above. If you switch presence processing off with /privacy disable presence_radar, your presence is excluded from this catalogue as well.
Engagement, XP and attendance. When you use the bot or the website, we record which commands, buttons, selects and reactions you used, how long you were in event voice channels, and which events you attended. This is used to calculate guild XP, contribution scores, leaderboards and reward or loot priority. We never read or store your message content for this purpose. The lawful basis is our legitimate interest in operating community management features; you may object at any time with /privacy disable xp_system or /privacy disable engagement_index, and voice-join timestamps are kept for 365 days.
Message-based features. Some features read message content, but only when you are explicitly addressing the bot or writing inside a surface the bot itself created for that purpose: mentioning the bot, an AI thread opened by a bot command, or the bid thread of an auction. Message content is never used to train machine-learning models, is never used for advertising, and is never scanned across channels.
A full, per-purpose list with the exact data categories, legal basis and retention period for your account is available under Settings → Data & Privacy, and you can request a copy or deletion of your data there or with /privacy data.