diff --git a/.github/ISSUE_TEMPLATE/5-docs-bug.md b/.github/ISSUE_TEMPLATE/5-docs-bug.md
index 7693d543..1169ff15 100644
--- a/.github/ISSUE_TEMPLATE/5-docs-bug.md
+++ b/.github/ISSUE_TEMPLATE/5-docs-bug.md
@@ -8,6 +8,10 @@ assignees: ""
 ---
 # **📚 Documentation Issue Report**
 
+**Security vulnerability?** Do not use this form — report privately via [SECURITY.md](https://github.com/plastic-labs/honcho/blob/main/SECURITY.md).
+
+GitHub issues are public. Redact secrets, JWTs, and production user content.
+
 ## **Describe the bug**
 <!-- A clear and concise description of what the bug is. -->
 
@@ -33,8 +37,8 @@ assignees: ""
 
 ---
 
-### **Media prove**
-<!-- If applicable, add screenshots or videos to help explain your problem. -->
+### **Screenshots and videos**
+<!-- If applicable, add screenshots or videos to help explain your problem. Redact secrets and production content. -->
 
 ---
 
@@ -46,7 +50,7 @@ assignees: ""
 ---
 
 ### **Additional context**
-<!-- Add any other context or additional information about the problem here.-->
+<!-- Add any other context about the problem. Redact secrets and production user content. -->
 
 *
 
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index eed3d7c8..23eb7c58 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -196,7 +196,7 @@ We welcome various types of contributions:
 When reporting bugs or requesting features:
 
 1. Check if the issue already exists
-2. Use the appropriate [issue template](https://github.com/plastic-labs/honcho/issues/new/choose) (bug, memory/recall quality, feature, or integration)
+2. Use the appropriate [issue template](https://github.com/plastic-labs/honcho/issues/new/choose) (bug, memory/recall quality, feature, integration, or documentation)
 3. Provide clear reproduction steps for bugs
 4. Include relevant environment information (managed vs self-hosted, server version, SDK)
 5. Be specific about expected vs actual behavior
@@ -209,6 +209,7 @@ When reporting bugs or requesting features:
 - **Memory / recall quality** - GitHub issues → Memory / recall quality template
 - **Feature requests** - GitHub issues → Feature request template
 - **Integrations / plugins / app-store listings** - GitHub issues → Integration request template
+- **Documentation issues** - GitHub issues → Documentation issue template
 - **Security issues** - Report **privately** only — see [`SECURITY.md`](./SECURITY.md) (GitHub Private Vulnerability Reporting or email). Do not open a public issue.
 
 ## License
diff --git a/SECURITY.md b/SECURITY.md
index 64f7e2a0..172758d3 100644
--- a/SECURITY.md
+++ b/SECURITY.md
@@ -7,7 +7,7 @@
 Please report security issues privately using one of:
 
 1. **[GitHub Private Vulnerability Reporting](https://github.com/plastic-labs/honcho/security/advisories/new)** (preferred)
-2. Email **<hello@plasticlabs.ai>** with subject line `[SECURITY] …`
+2. Email **<support@honcho.dev>** with subject line `[SECURITY] …`
 
 Include as much of the following as you can:
 
diff --git a/docs/v2/contributing/guidelines.mdx b/docs/v2/contributing/guidelines.mdx
index 80f9ad8b..12f44179 100644
--- a/docs/v2/contributing/guidelines.mdx
+++ b/docs/v2/contributing/guidelines.mdx
@@ -153,7 +153,7 @@ We welcome various types of contributions:
 When reporting bugs or requesting features:
 
 1. Check if the issue already exists
-2. Use the appropriate [issue template](https://github.com/plastic-labs/honcho/issues/new/choose) (bug, memory/recall quality, feature, or integration)
+2. Use the appropriate [issue template](https://github.com/plastic-labs/honcho/issues/new/choose) (bug, memory/recall quality, feature, integration, or documentation)
 3. Provide clear reproduction steps for bugs
 4. Include relevant environment information (managed vs self-hosted, server version, SDK)
 5. Be specific about expected vs actual behavior
@@ -166,6 +166,7 @@ When reporting bugs or requesting features:
 - **Memory / recall quality** - GitHub issues → Memory / recall quality template
 - **Feature requests** - GitHub issues → Feature request template
 - **Integrations / plugins / app-store listings** - GitHub issues → Integration request template
+- **Documentation issues** - GitHub issues → Documentation issue template
 - **Security issues** - Report **privately** only — see [`SECURITY.md`](https://github.com/plastic-labs/honcho/blob/main/SECURITY.md) (GitHub Private Vulnerability Reporting or email). Do not open a public issue.
 
 ## License
diff --git a/docs/v3/contributing/guidelines.mdx b/docs/v3/contributing/guidelines.mdx
index 80f9ad8b..12f44179 100644
--- a/docs/v3/contributing/guidelines.mdx
+++ b/docs/v3/contributing/guidelines.mdx
@@ -153,7 +153,7 @@ We welcome various types of contributions:
 When reporting bugs or requesting features:
 
 1. Check if the issue already exists
-2. Use the appropriate [issue template](https://github.com/plastic-labs/honcho/issues/new/choose) (bug, memory/recall quality, feature, or integration)
+2. Use the appropriate [issue template](https://github.com/plastic-labs/honcho/issues/new/choose) (bug, memory/recall quality, feature, integration, or documentation)
 3. Provide clear reproduction steps for bugs
 4. Include relevant environment information (managed vs self-hosted, server version, SDK)
 5. Be specific about expected vs actual behavior
@@ -166,6 +166,7 @@ When reporting bugs or requesting features:
 - **Memory / recall quality** - GitHub issues → Memory / recall quality template
 - **Feature requests** - GitHub issues → Feature request template
 - **Integrations / plugins / app-store listings** - GitHub issues → Integration request template
+- **Documentation issues** - GitHub issues → Documentation issue template
 - **Security issues** - Report **privately** only — see [`SECURITY.md`](https://github.com/plastic-labs/honcho/blob/main/SECURITY.md) (GitHub Private Vulnerability Reporting or email). Do not open a public issue.
 
 ## License