diff --git a/.gitlab/issue_templates/Bug.md b/.gitlab/issue_templates/Bug.md
index 60bab3f6ce..f47bed0095 100644
--- a/.gitlab/issue_templates/Bug.md
+++ b/.gitlab/issue_templates/Bug.md
@@ -5,6 +5,17 @@ triggered repeatedly - then please make sure that you make the new issue
 confidential by clicking the checkbox at the bottom!
 -->
 
+<!--
+If you found the problem in BIND 9 using generative AI tools and you have verified it
+yourself to be true: write the report yourself and explain the problem as you
+have learned it. This makes sure the AI-generated inaccuracies and invented
+issues are filtered out early before they waste more people's time.  Even if you
+write the report yourself, you must make sure to reveal the fact that
+generative AI was used in your report.
+
+We ban users immediately who submit fake reports to the project.
+-->
+
 ### Summary
 
 <!-- Concisely summarize the bug encountered. -->
diff --git a/.gitlab/issue_templates/Default.md b/.gitlab/issue_templates/Default.md
index c0079fa2a8..347ecdaf10 100644
--- a/.gitlab/issue_templates/Default.md
+++ b/.gitlab/issue_templates/Default.md
@@ -4,5 +4,6 @@ It would be a tremendous help if you could follow these steps first:
 - [ ] Search the existing issues in GitLab (both open and closed) to see if your report might be a duplicate. We have a large database here and many issues have already been fixed in the latest versions!
 - [ ] Make sure this is **not** a support question. If you have specific trouble configuring or debugging your setup, please use the bind-users mailing list: https://lists.isc.org/mailman/listinfo/bind-users
 - [ ] You have read and understood the "out in the open" support policy: https://blog.powerdns.com/2016/01/18/open-source-support-out-in-the-open/ . Even though it was written by the PowerDNS folks, we follow it as well!
+- [ ] The content you are submitting was not generated by a Generative AI!
 
 Before continuing, **please select the appropriate issue template in the drop-down menu above, under the heading _Description_**.
diff --git a/.gitlab/issue_templates/Feature_Request.md b/.gitlab/issue_templates/Feature_Request.md
index 72d2cb4931..b7fdcb257b 100644
--- a/.gitlab/issue_templates/Feature_Request.md
+++ b/.gitlab/issue_templates/Feature_Request.md
@@ -1,3 +1,11 @@
+<!--
+If you plan to submit a merge request for the feature that you are requesting,
+please note that we do not doc accept contributions generated by large language
+models or other probabilistic tools. Code, documentation, pull requests, issues,
+comments, and any other contributions to the BIND 9 project are all covered by
+this policy.
+-->
+
 ### Description
 
 (Describe the problem, use cases, benefits, and/or goals.)
diff --git a/.gitlab/issue_templates/Security_issue.md b/.gitlab/issue_templates/Security_issue.md
index 2789c45e24..c272f63d74 100644
--- a/.gitlab/issue_templates/Security_issue.md
+++ b/.gitlab/issue_templates/Security_issue.md
@@ -1,3 +1,20 @@
+<!--
+If you found the problem using generative AI tools and you have verified it
+yourself to be true: write the report yourself and explain the problem as you
+have learned it. This makes sure the AI-generated inaccuracies and invented
+issues are filtered out early before they waste more people's time.  Even if you
+write the report yourself, you must make sure to reveal the fact that the
+generative AI was used in your report.
+
+As we take security reports seriously, we investigate each report with
+priority. This work is both time- and energy-consuming and pulls us away from
+doing other meaningful work. Fake and otherwise made-up security problems
+effectively prevent us from doing real project work and make us waste time and
+resources.
+
+We ban users immediately who submit fake reports to the project.
+-->
+
 ### Summary
 <!--
 Concisely summarize the bug encountered,