Skip to content

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

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

[P0] Lock down developer commands and privacy handling#111
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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant