Privacy controls for server managers
Configure private support access and explain data use to members.
Check access before publishing
Test ticket categories and transcript destinations using an ordinary member account. Select only the support roles that need access. Keep transcripts, staff notes and private attachments out of public channels. Review permissions after changing categories or staff roles.
Explain AI to members
Link the AI disclosure from support guidance. Explain that relevant questions and limited context go to Groq when AI support is enabled. Keep public knowledge accurate and avoid publishing personal records as support guidance. Always provide a human route.
Set and communicate retention
Review ModMail retention settings and your separate channel-ticket archive. A thirty-day ModMail setting does not erase Discord transcript messages, downloaded files or backups. Follow the data policy and review copies your server controls separately.
Handle a request privately
Ask for the relevant Discord ID and case reference, verify access proportionately and avoid disclosing other members’ information. Contact [email protected] for records under Pryn Team control. Do not collect passwords or unnecessary identity documents.