1. Who operates GuildDesk
GuildDesk is software installed and configured by a Discord server operator. That operator controls the server’s bot, admin portal, and stored GuildDesk data. For questions about a particular server’s records, contact that server’s owner or administrator.
2. Information GuildDesk stores
To provide its features, GuildDesk may store:
- Discord user IDs and usernames for requesters, members, and staff;
- event titles, proposed dates, descriptions, review decisions, and reviewer names;
- ticket subjects, status, suggested guidance, and private ticket channel IDs;
- merit and demerit reasons, the member and staff IDs involved, and whether a record was reversed;
- staff availability dates and reasons;
- timestamps of server messages and bot commands for staff activity and inactivity checks. GuildDesk does not store the text of server messages for this activity tracking.
3. How information is used
GuildDesk uses this information to show records in the admin portal, route and review requests, notify members, and run configured staff activity checks. Event and record decisions may be sent to the affected member by Discord direct message and written to a server log channel when configured.
4. Ticket guidance and optional local AI
Basic ticket guidance uses local matching rules. If the operator configures a local Ollama model, ticket text may be sent to the Ollama service at the address they configured to classify the question. That service is controlled by the operator; GuildDesk does not send ticket text to a paid AI API by default.
5. Storage, access, and retention
GuildDesk stores operational data in a local data.json file by default. The server operator and anyone with access to the host or backups may be able to access it. Data remains in that file until the operator removes it. The admin portal uses a browser session cookie when a portal password is configured; demo-mode sample data is stored in that browser’s local storage.
6. Discord and third parties
GuildDesk relies on Discord to provide the bot, server, and direct-message features. Discord processes information under its own policies. Optional local AI processing is controlled by the server operator as described above.
7. Your choices and questions
For access, correction, or removal of a server record, contact the server owner or administrator who operates GuildDesk. They control the data file and server logs. Discord account and privacy settings are managed separately through Discord.
8. Policy changes
This policy may be updated as GuildDesk changes. The current version will be published at this URL.