LSK uses Discord interactions wherever they can provide the required functionality. Message Content access is requested only for features where the message itself is necessary to provide moderation, support, archival or explicitly requested functionality.
Moderation context
Edited and deleted messages occur asynchronously. Moderation teams may need the relevant content to understand and respond to those events.
Ticket transcripts
An authorized interaction can request a transcript, but the interaction cannot contain the historical conversation that must be read to create it.
Explicit channel extraction
An authorized user may explicitly request a bounded extraction of accessible channel history. Relevant Discord permissions are checked before access.
Interaction-first design
LSK uses slash commands, context commands, buttons, select menus and modals whenever those tools can replace direct message access. Message Content is not requested merely to preserve a legacy command interface.
LSK Personal
LSK Personal does not passively retrieve a user's complete DM or conversation history. Personal features are initiated explicitly by the user through supported Discord interactions or content they intentionally select or provide.
What LSK does not use Message Content for
- Targeted advertising
- Selling user data
- Providing advertisers access to conversations
- Unrelated behavioral profiling
Administrator and permission controls
Server-side moderation, logging, ticketing and security features are controlled by server administrators. LSK can only access channels and information that Discord makes available through permissions granted to the application.
Privacy
For information about data categories, retention, sharing, privacy requests and security practices, see the LSK Privacy Policy.
Contact
Questions about LSK's use of Discord data can be sent through the official support server: https://discord.gg/lsk.