Privacy Policy for code-server Discord Presence

Effective date: August 27, 2026

code-server Discord Presence processes data only to display the user's code-server editing activity as a Discord Rich Presence.

Data accessed:
- Editor status, including filename, file extension, detected language, workspace name, and cursor line/column.
- The origin of code-server websites explicitly authorized by the user.
- Discord OAuth credentials, Discord user ID and username, and Discord headless-session tokens.
- Extension settings, including the Discord Application ID and custom activity text.

The extension does not read or transmit source-code contents.

Privacy Mode is enabled by default. While Privacy Mode is enabled, raw filenames and workspace names are removed before data leaves the code-server page. If the user disables Privacy Mode, filenames and workspace names may be included in the activity sent to Discord.

Data transmission:
Activity information and OAuth credentials are sent directly from the user's browser to Discord through Discord's HTTPS API. Public image URLs used for language and program icons may also be included in the Discord activity payload.

The developer does not operate a data-collection server and does not receive, sell, rent, analyze, or share user data. The extension contains no advertising or analytics.

Local storage:
OAuth tokens, headless-session tokens, settings, approved code-server origins, and basic Discord account information are stored locally using the browser extension storage API.

User control and deletion:
Users can disconnect Discord from the extension, which deletes locally stored OAuth credentials and requests deletion of active Discord headless sessions. Site access can be revoked through the extension or browser permission settings. Uninstalling the extension removes its locally stored data.

Data processed by Discord is subject to Discord's own privacy policy.