Data access transparency

Message Content Access

Why LSK may require Discord's Message Content privileged intent

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, security, or explicitly requested functionality.

Deleted-message moderation

Deleted-message events occur asynchronously. Moderation teams may require the relevant content in order to understand and respond to those events.

An interaction can request moderation information, but it cannot recreate the content of a message after that message has already been deleted.

Ticket transcripts

An authorized interaction can request a ticket transcript, but the interaction itself does not contain the historical conversation that must be read in order to generate it.

Explicit channel extraction

An authorized user may explicitly request a bounded extraction of accessible server channel history.

Relevant Discord permissions are checked before access.

Interaction-first design

LSK uses slash commands, context commands, buttons, select menus, modals, and other Discord interactions whenever those tools can replace direct Message Content access.

Message Content is not requested merely to preserve a legacy text-command interface.

Deleted messages and /snipe

LSK includes moderation functionality that can allow authorized staff to retrieve recent deleted-message context through /snipe when Message Content access is available.

Temporary Message Content used by the supported /snipe moderation feature is retained for approximately 15 minutes and automatically expires.

Where temporary Message Content is persistently stored for this moderation functionality, the stored content is encrypted at rest.

Ticket transcript handling

Authorized users may request ticket reports or transcripts through LSK's ticket system.

Message Content access is required to retrieve the historical messages that make up the ticket conversation.

Ticket transcript content generated by LSK is created in memory for processing and delivery and is not persistently written to LSK's local disk storage.

Explicit channel-history extraction

LSK may allow an authorized user to explicitly request a bounded export of message history from an accessible Discord server channel.

The operation is user-initiated and relevant Discord permissions are checked before access.

The interaction starts the operation, but Message Content access is still required to retrieve the historical messages explicitly requested by the authorized user.

User Message Content privacy controls

LSK provides users with an explicit Message Content privacy preference.

Users may opt out of supported Message Content processing using /privacy optout, localized in French as /confidentialite optout.

When enabled, LSK withholds that user's Message Content from supported:

Users may check their current privacy preference through LSK's privacy status command.

Users may restore normal processing at any time using /privacy optin, localized in French as /confidentialite optin.

Automated server safety and moderation rules may still inspect a message temporarily in memory when necessary to perform a configured moderation action.

The privacy preference prevents LSK from copying the user's Message Content into the supported logs, archives, exports, and temporary storage covered by the preference.

LSK Personal

LSK Personal does not passively retrieve a user's complete Discord DM or conversation history.

Personal features are initiated explicitly by the user through supported Discord interactions or content they intentionally select or provide.

Production safety behavior

Message Content-dependent functionality remains restricted when Discord has not granted LSK access to the privileged Message Content Intent.

LSK does not attempt to bypass Discord's Message Content restrictions.

Features that require historical Message Content, including complete ticket transcripts and explicit channel-history extraction, may remain unavailable until Discord grants the required access.

What LSK does not use Message Content for

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.

Data retention and security

LSK aims to retain Message Content only for as long as reasonably necessary to provide the feature for which it was processed.

Temporary Message Content used by the supported /snipe feature is retained for approximately 15 minutes and automatically expires.

Where that temporary Message Content is persistently stored, it is encrypted at rest.

Ticket transcripts generated by LSK are created in memory for processing and delivery and are not persistently written to local disk.

Privacy and deletion requests

Users may use /privacy optout to control future Message Content processing covered by LSK's privacy preference.

Users may also request deletion of eligible previously stored LSK data through the official support server: https://discord.gg/lsk .

Privacy requests are reviewed and verified before eligible stored data associated with the requesting user is deleted.

Privacy Policy

For more 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 .