Skip to content

[P0] Lock down developer commands and privacy handling - #111

Closed
apple050620312 wants to merge 1 commit into
Kyrela:mainfrom
apple050620312:p0-security-privacy
Closed

apple050620312 wants to merge 1 commit into
Kyrela:mainfrom
apple050620312:p0-security-privacy

Conversation

@apple050620312

Copy link
Copy Markdown
Contributor

Summary

  • Disable developer commands by default and require both an allowlisted developer guild and user ID when enabled.
  • Enforce caller validation at runtime and terminate timed-out subprocesses.
  • Remove message content, URLs, and upstream response bodies from telemetry and error logs.
  • Align the privacy policy with Discord and EmbedEZ data flows and actual retention behavior.

Priority

P0 — closes direct host-command exposure and sensitive-data logging/privacy gaps.

Validation

  • Runtime imports succeed with developer commands disabled by default.
  • Developer commands are absent from the default command surface.
  • All Python files pass AST parsing.

@Kyrela

Kyrela commented Oct 25, 2026

Copy link
Copy Markdown
Owner

Disable developer commands by default and require both an allowlisted developer guild and user ID when enabled.

Developer commands are already disabled by default, if no dev guild is provided. An allowlist is nice, but I didn't put any because the command will still appear for every users.

Enforce caller validation at runtime and terminate timed-out subprocesses.

That's a good one actually

Remove message content, URLs, and upstream response bodies from telemetry and error logs.

Nah I need to see urls that caused the errors to properly find error causes actually

Align the privacy policy with Discord and EmbedEZ data flows and actual retention behavior.

See above

@Kyrela Kyrela closed this Oct 25, 2026
@github-actions github-actions Bot locked and limited conversation to collaborators Oct 25, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants