Contact the right Commentary team.
Use the support, privacy, copyright, security, and public feedback paths below so requests reach the right queue without exposing private repository or customer data.
Legal pages use the policy dates from the current configuration: effective March 18, 2026, last updated April 22, 2026.
- Support
- Privacy
- Security disclosure
- Public feedback
Direct contact paths.
These destinations preserve the existing legal and support contacts while making the public route easier to scan.
Billing and account support
General product, account, and billing support for Commentary.
support@commentary.devPrivacy requests
Data rights and privacy requests for account or review data.
privacy@commentary.devCopyright and DMCA
Copyright or DMCA notices related to commentary.dev.
dmca@commentary.devSecurity disclosure
Security concerns with reproduction details and expected impact.
security@commentary.devPublic feedback belongs in the feedback repository.
Use public issues for bugs, feature requests, rendering issues, GitHub integration issues, and UX feedback.
Do not include private data in public issues.
This opens a public GitHub issue. Do not include private repository names, private PR URLs, confidential markdown, tokens, customer data, sensitive screenshots, or private project metadata.
Need product context first?
Start with documentation or the security overview, then use the relevant contact path when a request needs follow-up.