Skip to content

Add privacy-safe issue reporting - #41

Merged
mkaand merged 1 commit into
mainfrom
feat/report-an-issue
Oct 4, 2026
Merged

mkaand merged 1 commit into
mainfrom
feat/report-an-issue

Conversation

@mkaand

@mkaand mkaand commented Oct 4, 2026

Copy link
Copy Markdown
Owner

Summary

  • Adds a small public Report an issue dialog, including a failed-analysis launcher.
  • Sends reports synchronously to the configured reports recipient, with an admin-email fallback.

Privacy and security

  • Issue report contents are not stored in analytics or the application database.
  • Submitted URLs are sent only when the user explicitly submits an issue report.
  • Failed-analysis context uses an explicit provider/error-code/request-ID allowlist.
  • The endpoint is CSRF-protected, validated, and rate-limited to five reports per fifteen minutes.
  • Mail failures return a generic response and use sanitized server diagnostics only.

Regression guard

  • Theme, Paste, provider icons, roadmap, and Share/Save behavior are unchanged.
  • No migrations, media pipeline, Facebook, YouTube, GeoIP, or analytics changes.

Tests

  • Added backend coverage for recipient selection, escaping, validation, rate limiting, no persistence, and safe failures.
  • Added frontend coverage for context allowlisting and sacred public controls.

@mkaand
mkaand merged commit 4ca94b3 into main Oct 4, 2026
4 checks passed
@mkaand
mkaand deleted the feat/report-an-issue branch October 4, 2026 18:46
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