diff --git a/src/hmnurl/hmnurl_test.go b/src/hmnurl/hmnurl_test.go
index 4540c5f9..1cdab20e 100644
--- a/src/hmnurl/hmnurl_test.go
+++ b/src/hmnurl/hmnurl_test.go
@@ -86,7 +86,7 @@ func TestStaticPages(t *testing.T) {
 	AssertRegexMatch(t, BuildManifesto(), RegexManifesto, nil)
 	AssertRegexMatch(t, BuildValues(), RegexValues, nil)
 	AssertRegexMatch(t, BuildAbout(), RegexAbout, nil)
-	AssertRegexMatch(t, BuildCommunicationGuidelines(), RegexCommunicationGuidelines, nil)
+	AssertRegexMatch(t, BuildCommunicationGuidelines(), RegexOldCommunicationGuidelines, nil)
 	AssertRegexMatch(t, BuildContactPage(), RegexContactPage, nil)
 }
 
diff --git a/src/hmnurl/urls.go b/src/hmnurl/urls.go
index 5f1ae547..06e2c0c7 100644
--- a/src/hmnurl/urls.go
+++ b/src/hmnurl/urls.go
@@ -344,7 +344,25 @@ func BuildAbout() string {
 	return Url("/about", nil)
 }
 
-var RegexCommunicationGuidelines = regexp.MustCompile("^/communication-guidelines$")
+var RegexRules = regexp.MustCompile("^/rules$")
+
+func BuildRules() string {
+	return Url("/rules", nil)
+}
+
+var RegexPrivacyPolicy = regexp.MustCompile("^/privacy$")
+
+func BuildPrivacyPolicy() string {
+	return Url("/privacy", nil)
+}
+
+var RegexAIPolicy = regexp.MustCompile("^/ai-policy$")
+
+func BuildAIPolicy() string {
+	return Url("/ai-policy", nil)
+}
+
+var RegexOldCommunicationGuidelines = regexp.MustCompile("^/communication-guidelines$")
 
 func BuildCommunicationGuidelines() string {
 	return Url("/communication-guidelines", nil)
diff --git a/src/templates/src/about.html b/src/templates/src/about.html
index 1966a4e3..4e7053d8 100644
--- a/src/templates/src/about.html
+++ b/src/templates/src/about.html
@@ -13,7 +13,7 @@ <h2>
 			The Handmade Network was founded by Abner Coimbre as a community for fans of <a href="https://handmadehero.org/">Handmade Hero</a>, a Twitch series where games industry veteran Casey Muratori teaches you how to make a game and engine from scratch. Since then, the community has grown massively, launched many careers, and spawned amazing projects that thousands of people use every day. Handmade Hero is no longer active, but Casey is still producing high-quality programming education through <a href="https://www.computerenhance.com/">Computer, Enhance!</a>
 		</p>
 		<p>
-			The Handmade Network is an initiative of the <a href="https://handmade.foundation/">Handmade Software Foundation</a>, a (soon-to-be) 501(c)(6) nonprofit corporation.
+			The Handmade Network is an initiative of the <a href="https://handmade.foundation/">Handmade Software Foundation</a>, a 501(c)(6) nonprofit corporation.
 		</p>
 	</div>
 
@@ -30,7 +30,7 @@ <h4>Lead, Foundation President</h4>
 					As lead and foundation president, Ben sets the vision and direction for the Handmade community and writes a lot of web pages like this one. His goal is to foster the development of Handmade software and Handmade programmers, and to move the software industry toward a new future where our "high-level" tools are built on solid low-level foundations.
 				</p>
 				<p>
-					On the professional side, Ben works on WebAssembly at Mozilla within the <a href="https://spidermonkey.dev/">SpiderMonkey</a> team. Before this, he spent many years as a web developer building apps and backend services, with a focus on performance. He also acts as lead mentor of a <a href="https://www.msarobotics.org/"><i>FIRST</i> Robotics team</a>.
+					On the professional side, Ben works on WebAssembly at Mozilla within the <a href="https://spidermonkey.dev/">SpiderMonkey</a> team. Before this, he spent many years as a web developer building apps and backend services. He also mentors a <a href="https://www.msarobotics.org/"><i>FIRST</i> Robotics team</a>.
 				</p>
 				<!-- <p>
 					Twitter: <a target="_blank" href="https://twitter.com/its_bvisness">its_bvisness</a>
diff --git a/src/templates/src/ai_policy.html b/src/templates/src/ai_policy.html
new file mode 100644
index 00000000..467cbc9f
--- /dev/null
+++ b/src/templates/src/ai_policy.html
@@ -0,0 +1,96 @@
+{{ template "base-2024.html" . }}
+
+{{ define "extrahead" }}
+<script type="module" src="{{ static "js/hilbert.js" }}"></script>
+{{ end }}
+
+{{ define "content" }}
+<div class="h3 hilbert hilbert-color" style="--hue: 340deg"></div>
+<div class="flex justify-center tc">
+	<div class="w-100 mw-site-narrow">
+		<h1 class="pv4 pv5-ns f3 f2-ns">AI Policy</h1>
+	</div>
+</div>
+<div class="mw-site-narrow ph3 post-content center">
+  <hr class="mb4">
+
+  <p>The Handmade Network exists to promote the development of high-quality software and foster a community of programmers who enjoy and deeply understand programming. We recognize that AI tools are powerful, but because they make it easy to produce code without understanding, AI tends to go against the values of this community in practice.</p>
+
+  <p>Our goal with this policy is not to forbid the responsible use of AI. Instead, our AI policy is designed to put boundaries on AI use that preserve the community’s values and provide guidance on how to use AI in ways we consider responsible.</p>
+
+  <p><b>Please remember:</b> We do NOT believe that it is impossible to create useful (or even high-quality) software using the tools and practices forbidden here. If we forbid a practice, that ONLY means that it goes against our community values.</p>
+
+
+  <h3>No vibe-coding</h3>
+
+  <p>We are firmly against “vibe-coding”, by which we mean “producing software without looking at the code”. Vibe-coded projects are not allowed to be shared under any circumstances. For discussion purposes, vibe-coding should be considered off-topic for the community.</p>
+
+  <p>The Handmade community has always encouraged its members to build things for themselves, whether for self-sufficiency, education, or simply the joy of programming. We care about what the computer is actually doing, and the best way to understand this will always be to write the code yourself, but reading the code is the bare minimum.</p>
+
+
+  <h3>No AI prose</h3>
+
+  <p>It is never acceptable for any of your communication within the community to be generated by AI. This includes messages on the website and Discord, blog posts, READMEs, and any other text authored by you and intended to be read by members of the community.</p>
+
+  <p>It is rude to expect others to put more effort into reading than you put into writing. Furthermore, in an online community, you <em>are</em> the words you write. Your words reveal your personality, your background, your experience, and your understanding. Writing is also thinking; by writing about a subject, you clarify your own understanding of it, and become a better community member and a better engineer.</p>
+
+  <p>We would always rather read broken English or a half-finished blog post instead of sanitized AI prose.</p>
+
+
+  <h3>All projects require AI disclosure</h3>
+
+  <p>All projects on the website must disclose how they use generative AI, including for prototypes, secondary artifacts like tests and build scripts, and purposes other than code generation. This gives the community and its leadership the information they need to judge whether a project is a good fit for Handmade values.</p>
+
+  <p>We understand that many community members are using AI in ways they feel are responsible and in line with the Handmade ethos, and we wish to respect that, while recognizing that opinions vary widely within the community on which kinds of AI use are acceptable. Disclosure is the most practical way for us to navigate this tension.</p>
+
+
+  <h3>Restrictions on Discord</h3>
+
+  <p>Some channels on the Handmade Network Discord server have additional restrictions on AI content:</p>
+
+  <ul>
+    <li><b>Discussion of generative AI is forbidden in #general.</b> This ensures that community members always have a space they can visit for AI-free programming discussion. General discussion of generative AI is permitted in other channels such as #undefined-behavior.</li>
+    <li><b>All #project-showcase posts must be Zero AI<sup>*</sup>.</b> The showcase channel is our community’s greatest source of inspiration, and should be the clearest expression of our values. Projects that use some amount of AI may still be discussed in other channels like #workspace.</li>
+  </ul>
+
+  <p>By “Zero AI<sup>*</sup>” we mean that the material being showcased has zero AI generated code, in all respects (including build scripts and tests, if applicable), with two exceptions:</p>
+
+  <ol>
+    <li>Using AI as a search tool is acceptable. For the purposes of this policy, we do not consider copy-paste of AI search results to be “AI codegen”, although you really ought to read and understand it carefully.</li>
+    <li>Using AI for entirely mechanical and deterministic purposes is acceptable, e.g. generating bindings or data tables. In such cases, the end result is indistinguishable from handwritten code.</li>
+  </ol>
+
+  <p>The #project-showcase restriction applies only to the material being showcased, not the entire project. The author of a project that has disclosed AI use may therefore still share updates in #project-showcase as long as AI was not involved in the material being showcased.</p>
+
+
+  <h3>FAQ</h3>
+
+  <h4>Can I use AI to find bugs or do security analysis?</h4>
+
+  <p>Yes. Just don’t be too eager to apply an AI-suggested fix :)</p>
+
+  <h4>I have no sense of aesthetics. Can I use AI to help my projects look more appealing?</h4>
+
+  <p>We do not draw a distinction between AI-generated styles and AI-generated code. As with prose, we would rather see programmer UI than artificially polished UI. If you want to make your project look better, the community is full of people who would be happy to help!</p>
+
+  <p>As for assets, while we have no specific rules against AI-generated media, you are strongly discouraged from using AI assets in your projects. We like programmer art!</p>
+
+  <h4>I am a beginner. Is it ok to use AI to find my way around?</h4>
+
+  <p>We understand that AI can be very helpful as a beginner tool, but please don’t take shortcuts! We pride ourselves on being welcoming to beginners and willing to answer stupid questions, and are happy to provide guidance. We also love when beginners share their work, so don’t be afraid to engage with the community. We were all once beginners.</p>
+
+  <h4>What’s wrong with using AI for tests?</h4>
+
+  <p>Testing is a serious and important skill in programming that needs to be developed like any other. Programmers who are good at testing their code have developed their instincts through experience, and often employ a variety of techniques to make their tests more coherent, maintainable, and effective.</p>
+
+  <h4>What’s wrong with using AI for build scripts?</h4>
+
+  <p>Your build script is a critical part of your project that also deserves care and attention. If your build script is so complicated that you need an AI to write it for you, perhaps you just need to simplify your builds. Your future self, and future coworkers, will thank you for taking your build seriously!</p>
+
+
+  <hr>
+
+
+  <p><i>Last updated on September 6, 2026.</i></p>
+</div>
+{{ end }}
diff --git a/src/templates/src/communication_guidelines.html b/src/templates/src/communication_guidelines.html
deleted file mode 100644
index 17ddc362..00000000
--- a/src/templates/src/communication_guidelines.html
+++ /dev/null
@@ -1,54 +0,0 @@
-{{ template "base-2024.html" . }}
-
-{{ define "content" }}
-<div class="mw-site pa3 post-content center">
-	<h1>Handmade Network Communication Guidelines</h1>
-
-	<h2>Our philosophy</h2>
-	<p>
-		The Handmade community strives to create an environment conducive to innovation, education, and constructive discussion. To that end, we expect members of the community to respect the following set of principles to maintain civil discourse and create an inclusive environment.
-	</p>
-	
-	<h2>Discourse</h2>
-	<ul>
-		<li>The community is mostly business, with a bit of fun. Discussion should primarily be about software development, and in particular about the relevant project or topic at hand.</li>
-		<li>Support arguments with evidence and respectful discussion. Don't resort to ad hominem attacks or personality judgments. Don't try to get the last word; please be willing to disengage if a conversation gets heated.</li>
-		<li>Differing opinions are valuable and should be respected. Not everyone sees eye-to-eye on every matter, but we're all trying to write useful software.</li>
-		<li>Be aware of differences in English comprehension and culture. What you say may be misinterpreted through no fault of your own or the listener. Please be patient and kind when misunderstandings occur.</li>
-	</ul>
-
-	<h2>Professional & respectful conduct</h2>
-	<p>
-		A Handmade community member shall not:
-	</p>
-	<ul>
-		<li>Sexualize or objectify others, even if they think it's a compliment.</li>
-		<li>Dismiss other people's contributions, opinions, or concerns based on their personal attributes.</li>
-		<li>Use pejoratives or excessively rely on foul language, especially if used to attack an individual.</li>
-		<li>Disparage a person instead of criticizing their work. Handmade community members should acknowledge and respect high-quality work even if they dislike the author.</li>
-		<li>Antagonize others, particularly if a disagreement has occurred.</li>
-		<li>Assume a motive for uncharacteristic behavior. Everyone has a bad day.</li>
-		<li>Dwell excessively on a topic or argument when the other parties involved have made it clear they are no longer interested or comfortable discussing it.</li>
-		<li>Continue to ask a person to disclose information, particularly about their personal lives, when that person has declined to do so.</li>
-	</ul>
-
-	<h2>Integrity</h2>
-	<p>
-		The Handmade community values integrity, the honest pursuit of knowledge, and working hard to build effective, uncomplicated software.
-	</p>
-	<p>
-		In particular, we strive to:
-	</p>
-	<ul>
-		<li>Be honest with others about the state of our work.</li>
-		<li>Foster an environment where dedicated learners of any skill level may ask questions and receive detailed, useful answers.</li>
-		<li>Advertise projects for what they are and what their authors reasonably hope they might become.</li>
-	</ul>
-	<p>
-		It is up to the discretion of the moderators to determine when these guidelines are being met, and they are permitted to act accordingly.
-	</p>
-	<p>
-		If you feel an action has been made against you unreasonably, please contact the <a href="/contact">Handmade Network Team</a> privately with your grievance and we will review the decision.
-	</p>
-</div>
-{{ end }}
diff --git a/src/templates/src/include/header-2024.html b/src/templates/src/include/header-2024.html
index b4b5c54e..65c30729 100644
--- a/src/templates/src/include/header-2024.html
+++ b/src/templates/src/include/header-2024.html
@@ -22,7 +22,8 @@
       </a>
       <div class="submenu" id="about-submenu">
         <a href="{{ .Header.ManifestoUrl }}">Manifesto</a>
-        <a href="{{ .Header.ValuesUrl }}">Our values</a>
+        <a href="{{ .Header.ValuesUrl }}">Our Values</a>
+        <a href="{{ .Header.RulesUrl }}">Rules &amp; Policies</a>
         <a href="{{ .Header.AboutUrl }}">About</a>
       </div>
     </div>
diff --git a/src/templates/src/manifesto.html b/src/templates/src/manifesto.html
index b3f2e321..39abfae6 100644
--- a/src/templates/src/manifesto.html
+++ b/src/templates/src/manifesto.html
@@ -14,24 +14,37 @@ <h1 class="pv4 pv5-ns f3 f2-ns">The Handmade Manifesto</h1>
 <div class="mw-site-narrow ph3 post-content center">
 	<hr class="mv4">
 
+	<div class="serif tc i flex justify-center mv4 mv5-ns">
+		<div>
+			<div class="f4">
+				“What I cannot create,<span class="dn-ns"><br>&nbsp;</span> I do not understand.”
+      </div>
+      <div class="tr">
+				- Richard Feynman
+      </div>
+    </div>
+  </div>
+
+	<hr class="mv4">
+
 	<h3>Computers are amazing.</h3>
-	<p>Computing has changed our lives for the better. Computers allow us to learn, connect with each other, and express ourselves in amazing new ways. And every year our devices get more powerful, less expensive, and more accessible - computers today can do things we hardly dreamed of twenty years ago.</p>
+	<p>Computing has changed our lives for the better. Computers allow us to learn, connect with each other, and express ourselves in amazing new ways. And every year our devices get more powerful, less expensive, and more accessible – computers today can do things we hardly dreamed of just twenty years ago.</p>
 
 	<h3>So why is software so terrible?</h3>
-	<p>Why do high-end gaming PCs struggle to browse the web at 60 frames per second? Why does a simple calculator need a splash screen? Why does your phone's battery still die so quickly? And why does each update make the problem worse?</p>
-	<p>And why do we all use huge frameworks that no one understands? Why do our projects take minutes to compile? Why do we have to restart our language servers every twenty minutes? And why does everyone think this is fine?</p>
+	<p>Why do high-end gaming PCs struggle to browse the web at 60 frames per second? Why do simple applications need splash screens? Why does your phone's battery still die so quickly? And why does each update make the problem worse?</p>
+	<p>And why do we all use huge frameworks that no one understands? Why do our projects still take minutes to compile? Why do we have to restart our language servers every twenty minutes? And why does everyone think this is fine?</p>
 
 	<h3>We made it terrible.</h3>
-	<p>We, programmers, have made it terrible through our thoughtless behavior. We rewrite our apps in new languages, and rather than measure anything, we just assume it will be better. We ship thousands of dependencies to our users to save ourselves a few minutes of effort. We build towers of abstractions, forget how they work, and then build new ones on top.</p>
-	<p>This isn't engineering. We're building Rube Goldberg machines, and users are paying the cost.</p>
-	<p>You may have learned that programming is about classes, monads, or type systems. You may have been taught to make your code clean, abstract, and future-proof. None of that matters when the end result is garbage.</p>
+	<p>We, programmers, have made it terrible through our thoughtless behavior. We rewrite our apps in new languages without measuring a thing. We buy faster computers rather than make our software faster. We ship thousands of dependencies to our users to save a few minutes of effort. We build towers of abstractions, forget how they work, and then build new ones on top.</p>
+	<p>This isn't engineering. We're building Rube Goldberg machines, and everyone else is paying the cost.</p>
+	<p>You may have learned that programming is about classes, monads, or type systems. You may have been taught to make your code clean, abstract, and future-proof. But none of that matters when the end result is garbage.</p>
 
 	<h3>But there is another way.</h3>
-	<p>You can break out of this cycle. You can learn how computers actually work, so you can unleash the full potential of modern systems. You can dig deep into the tech stack and learn what others take for granted. When you run into a wall, rather than stop, you can dig under it.</p>
-	<p>This is our mission. You don't have to be a genius to make your software better - you just have to be willing to learn and willing to go against conventions. We're here to teach you, to inspire you, to help you break free from the mess of modern software development and make software the Handmade way.</p>
+	<p>You can fight the trends of laziness and slop. You can learn how computers actually work, so you can unleash the full potential of modern systems. You can dig deep into the tech stack and learn what others take for granted. When you run into a wall, rather than stop, you can climb over it – or dig under it.</p>
+	<p>This is our mission. You don't have to be a genius to make your software better – you just have to be willing to learn and willing to go against conventions. You don't have to depend on libraries, StackOverflow, or AI – computers are not magic, and you can learn how they work. We're here to teach you, to inspire you, to help you break free from the mess of modern software development and make software the Handmade way.</p>
 
 	<h3>So join us.</h3>
-	<p>We <em>know</em> how much better software can be. The industry needs to change, and we're going to lead the way. Join us, and learn to build software by hand.</p>
+	<p>We <em>know</em> how much better software can be. Join us, and learn to build software by hand.</p>
 
 	<hr class="mv4">
 
diff --git a/src/templates/src/privacy.html b/src/templates/src/privacy.html
new file mode 100644
index 00000000..3f7fb8f5
--- /dev/null
+++ b/src/templates/src/privacy.html
@@ -0,0 +1,139 @@
+{{ template "base-2024.html" . }}
+
+{{ define "extrahead" }}
+<script type="module" src="{{ static "js/hilbert.js" }}"></script>
+{{ end }}
+
+{{ define "content" }}
+<div class="h3 hilbert hilbert-color" style="--hue: 180deg"></div>
+<div class="flex justify-center tc">
+	<div class="w-100 mw-site-narrow">
+		<h1 class="pv4 pv5-ns f3 f2-ns">Privacy Policy</h1>
+	</div>
+</div>
+<div class="mw-site-narrow ph3 post-content center">
+  <hr class="mb4">
+
+  <p>As programmers, we know how much programmers care about privacy. We endeavor to only store the minimum data required to operate our services on behalf of the Handmade community, and we never share or sell user data.</p>
+
+  <p>This privacy policy covers this website (<a href="https://handmade.network/">https://handmade.network/</a>) and its subdomains, as well as our Discord server (<a href="https://discord.gg/hmn">https://discord.gg/hmn</a>).</p>
+
+  <p>If you have any privacy-related questions, concerns, or requests, please contact us at <a href="mailto:team@handmade.network">team@handmade.network</a>.</p>
+
+
+  <h3>General data practices</h3>
+
+  <p>We are located in the United States and our data is hosted on US servers. Our database storage is encrypted at rest. User-created assets and media are stored in a cloud object storage service. Access to production data is restricted to site administrators.</p>
+
+  <p>We always endeavor to maintain strong security practices, and to follow industry-standard guidance by organizations such as OWASP.</p>
+
+
+  <h3>Explicitly-collected user data</h3>
+
+  <p>We store the following data provided directly by users as part of our normal operation:</p>
+
+  <ul>
+    <li><b>Authentication information,</b> including usernames, email addresses, passwords, and OAuth access tokens. Stored passwords are hashed and salted according to OWASP guidelines.</li>
+    <li><b>Profile information</b>, including public-visible data such as display names, bios, and avatars, as well as behind-the-scenes info such as email addresses and linked third-party accounts.</li>
+    <li><b>User-created content</b>, such as projects (and associated media), timeline posts, blog posts and forum posts.</li>
+    <li><b>Event-specific information</b> for ticket purchasers, such as name, email address, dietary restrictions, requests for accommodation, and Stripe transaction IDs.</li>
+    <li><b>Newsletter email addresses</b> for newsletter subscribers.</li>
+    <li><b>Other explicitly-provided user information</b> in cases such as surveys or if users contact us for support.</li>
+  </ul>
+
+  <p>We never process or store direct payment information such as credit card numbers or bank account numbers. Payments are always performed externally through our payment processor, Stripe. We use Stripe's API to get information about transactions, but Stripe never permits us to see users' payment information.</p>
+
+
+  <h3>Automatically-collected user data</h3>
+
+  <p>Some data is automatically collected as part of the normal process of operating the website:</p>
+
+  <ul>
+    <li><b>Basic request information,</b> including IP address and request headers. This data is logged on our server.</li>
+    <li><b>Information used for account creation,</b> including usernames, email addresses, and IP addresses, in order to help fight spam.</li>
+  </ul>
+
+  <p>We do not use client-side analytics or tracking, including in our emails. We only use cookies for strictly necessary purposes, such as authentication.</p>
+
+
+  <h3>Discord bot data</h3>
+
+  <p>We have a custom Discord bot as part the website codebase that provides various helpful services for the Handmade Network Discord server. The bot is special-purpose and is only used on the Handmade Network Discord. Most user interaction with the Handmade Network Discord is governed by Discord's own <a href="https://discord.com/privacy">privacy policy</a>, but as part of the bot's operation, we process and store some additional kinds of data from Discord:</p>
+
+  <ul>
+    <li><b>Message metadata,</b> such as message ID, channel ID, and author ID. This data is stored for all messages in select channels so that we can quickly fetch messages when a user enables cross-posting.</li>
+    <li>
+      <p><b>Message contents,</b> including text and attachments, may be processed and stored for various purposes:</p>
+      <ol>
+        <li>Message contents may be read (but not stored) in order to provide automatic moderation, such as the automatic deletion of messages.</li>
+        <li>Message contents may be stored in order to enable Discord messages to be cross-posted to the website. Message contents will only be stored when the message author has linked their Discord account to their website account.</li>
+      </ol>
+    </li>
+    <li><b>Profile information</b>, such as user ID, username, and avatar. This is used to provide account information for new signups and to correlate messages to authors.</li>
+  </ul>
+
+  <p>When a user unlinks their Discord account, all profile information (except the Discord user ID) and all stored message text from that Discord user are immediately deleted. Existing cross-posts are preserved.</p>
+
+
+  <h3>Twitch bot data</h3>
+
+  <p>We have a feature on our Discord server that posts in a channel when community members stream on Twitch. To enable this feature, we subscribe to webhook events from Twitch and store the following data:</p>
+
+  <ul>
+    <li><b>Basic channel info,</b> including ID and channel name.</li>
+    <li><b>Stream and VOD info,</b> including ID, title, category, tags, and start and end times.</li>
+    <li><b>Webhook events,</b> which we store in full for a limited time for debugging purposes.</li>
+  </ul>
+
+
+  <h3>Third parties</h3>
+
+  <p>We use a variety of third-party services as part of our normal operation. In some cases these third parties may require user information, but we endeavor to keep this at a minimum.</p>
+
+  <p>Third-party services that may encounter user data include:</p>
+
+  <ul>
+    <li>DigitalOcean, our web hosting service, where user content and assets are routinely stored as part of normal operation.</li>
+    <li>Postmark, for transactional emails and newsletters, where user email addresses are required.</li>
+    <li>Cloudflare, for networking and site protection.</li>
+    <li>Stripe, for payment processing.</li>
+  </ul>
+
+
+  <h3>User data controls</h3>
+
+  <p>Users can edit their own user-generated content, such as forum posts, timeline posts, and user profile contents, at any time. Most user-generated content can be deleted by users at any time; some, like projects, can only be deleted by a website administrator upon request.</p>
+
+  <p>Users with a linked Discord account can disable the cross-posting feature at any time, which will stop creating posts automatically but will not stop saving message contents. Users can unlink their account at any time, in which case all message contents will be deleted but previously created cross-posts will remain.</p>
+
+  <p>Users may request that their account be deleted by contacting us at the email address provided above. When an account is deleted, user-specific data and associated Discord data will be deleted, but user-generated content may be retained in anonymized form.</p>
+
+  <p>Users may at any time request a copy of all data associated with their user or identity. Data will be provided in a straightforward and machine-readable format.</p>
+
+
+  <h3>Data retention</h3>
+
+  <p>Generally speaking, we retain user data for as long as that user has an active account. We delete user information immediately upon account deletion, but some user data may be retained for up to 90 days in server logs and database backups.</p>
+
+  <p>Additionally, we may retain some user information indefinitely as part of responsible operation:</p>
+
+  <ul>
+    <li>As mentioned above, user-generated content may be retained in anonymized form upon account deletion.</li>
+    <li>Banned accounts may be retained for analysis, but are still subject to data deletion requests.</li>
+    <li>Bounced email addresses are always retained in order to protect our sender reputation.</li>
+  </ul>
+
+  <p>Webhook events from Twitch are retained in full for four days to facilitate debugging.</p>
+
+
+  <h3>Changes to this policy</h3>
+
+  <p>Changes to our privacy policy will be announced in a notice on this website and on our Discord server.</p>
+
+
+  <hr>
+
+
+  <p><i>Last updated on September 6, 2026. For any questions or requests, please contact us at <a href="mailto:team@handmade.network">team@handmade.network</a>.</i></p>
+</div>
+{{ end }}
diff --git a/src/templates/src/rules.html b/src/templates/src/rules.html
new file mode 100644
index 00000000..c2276972
--- /dev/null
+++ b/src/templates/src/rules.html
@@ -0,0 +1,50 @@
+{{ template "base-2024.html" . }}
+
+{{ define "extrahead" }}
+<script type="module" src="{{ static "js/hilbert.js" }}"></script>
+{{ end }}
+
+{{ define "content" }}
+<div class="h3 hilbert hilbert-color" style="--hue: 240deg"></div>
+<div class="flex justify-center tc">
+	<div class="w-100 mw-site-narrow">
+		<h1 class="pv4 pv5-ns f3 f2-ns">Rules &amp; Policies</h1>
+	</div>
+</div>
+<div class="mw-site-narrow ph3 post-content center">
+  <hr class="mb4">
+
+  <p>The Handmade Network is a community of programmers unified by a love of Handmade-style programming. We strive to maintain a community atmosphere where programmers can share their expertise, disagree productively, and be challenged to make better software.</p>
+
+  <p>We expect all community members to abide by the rules and policies listed here.</p>
+
+
+  <h3>Conduct &amp; behavior</h3>
+
+  <p>We expect community members to behave professionally and to treat each other with respect. As a rule of thumb, don't do anything that would get you fired. More specifically:</p>
+
+  <ul>
+    <li><b>Keep conversations centered around programming.</b> Even though we have off-topic channels, programming is the thing that brings the community together. Divisive topics (outside of programming) are not welcome.</li>
+    <li><b>Be willing to disagree.</b> Differing opinions are welcome as long as the participants are respectful. Don't try to get the last word; if a conversation gets heated, or comes to a conclusion you disagree with, just disengage.</li>
+    <li><b>Be principled.</b> Members of the Handmade community should acknowledge and respect high-quality work from people they dislike. Likewise, they should hold their friends accountable for poor-quality work.</li>
+    <li><b>Give others the benefit of the doubt.</b> Don't assume ill intent, and don't make assumptions about others based on their name, avatar, language preference, or other personal attributes.</li>
+    <li><b>Don't attack or police others.</b> It's fine to ask questions or criticize others' work, but personal attacks are not allowed. If you have concerns about a community member's conduct, please message an admin.</li>
+  </ul>
+
+
+  <h3>Use of generative AI</h3>
+
+  <p>Community use of AI is governed by our <a href="{{ .AIPolicyUrl }}">AI policy</a>.</p>
+
+
+  <h3>Privacy policy</h3>
+
+  <p>Use of this website and the Discord server is governed by our <a href="{{ .PrivacyPolicyUrl }}">privacy policy</a>.</p>
+
+
+  <hr>
+
+
+  <p><i>Last updated on September 6, 2026.</i></p>
+</div>
+{{ end }}
diff --git a/src/templates/src/values.html b/src/templates/src/values.html
index 0c484f69..834226ec 100644
--- a/src/templates/src/values.html
+++ b/src/templates/src/values.html
@@ -12,29 +12,16 @@ <h1 class="pv4 pv5-ns f3 f2-ns">Our Values</h1>
 	</div>
 </div>
 <div class="mw-site-narrow ph3 post-content center">
-  <hr class="mb3">
-
-	<div class="serif tc i flex justify-center mv4 mv5-ns">
-    <div>
-      <div class="f4">
-        “What I cannot create,<span class="dn-ns"><br>&nbsp;</span> I do not understand.”
-      </div>
-      <div class="tr">
-        - Richard Feynman
-      </div>
-    </div>
-  </div>
-
   <hr class="mb4">
 
   <h3>We love learning how things work.</h3>
-  <p>Many programmers are afraid of learning how computers work behind the scenes—but not us. We are driven to understand how systems work at every layer of the stack.</p>
-  <p>If someone gives us JavaScript, we’ll dig deeper into the runtime. If someone gives us C++, we’ll dig deeper into the machine code. If someone gives us machine code, we’ll dig deeper into the microarchitecture. There is a real computer behind our magic abstractions, and we want to understand what makes it tick.</p>
+  <p>Many programmers are afraid of learning how computers work behind the scenes, but not us. We are driven to understand how systems work at every layer of the stack.</p>
+  <p>If someone gives us JavaScript, we will dig deeper into the engine. If someone gives us C++, we will dig deeper into the machine code. If someone gives us machine code, we will dig deeper into the microarchitecture. There is a real computer behind our magic abstractions, and we love to learn what makes it tick.</p>
 
   <h3>We like to reinvent the wheel.</h3>
-  <p>Many programmers think that writing software from scratch is a waste of time. They will criticize you for “reinventing the wheel”. They think that the hard problems have already been solved.</p>
-  <p>But programming is a very young field. Much of the world’s software is a first draft. There is so much room to innovate, and the only way to innovate is by trying new approaches to familiar problems.</p>
-  <p>As Casey Muratori said on <a href="https://youtu.be/uxbJo5DDpWY?si=pXsiklQimQHCIZDn&t=3410">day 1 of Handmade Hero</a>, nothing we have developed in the past 30 years is a “wheel”. Our software today is like a bicycle with square wheels, awkwardly clunking along. To make better software, we <em>must</em> reinvent the wheel, and we love that challenge.</p>
+  <p>Many programmers think writing software from scratch is a waste of time. They will criticize you for “reinventing the wheel”. They think the hard problems have already been solved.</p>
+  <p>But programming is a very young field! Much of the world’s software is a first draft. There is so much room to innovate, and the only way to innovate is by trying new approaches to familiar problems.</p>
+  <p>As Casey Muratori said on <a href="https://youtu.be/uxbJo5DDpWY?si=pXsiklQimQHCIZDn&t=3410">day 1 of Handmade Hero</a>, nothing we have developed in the past 30 years is a “wheel”. Software today is like a bicycle with square wheels, awkwardly clunking along. To make better software, we <em>must</em> reinvent the wheel, and we love that challenge.</p>
 
   <h3>We don’t make excuses for bad software.</h3>
   <p>There is no excuse for bad software. If it doesn’t work, it doesn’t work. If it’s slow, it’s slow. No amount of excuses can make up for software that doesn’t work the way it should.</p>
@@ -46,15 +33,22 @@ <h3>We value competence.</h3>
   <h3>We like to be self-sufficient.</h3>
   <p>We like to build things ourselves. We don’t care if someone else has already made a library or a framework for us. We’d rather write the code that we need, when we need it, and learn from what others have built instead of using it blindly.</p>
 
+  <h3>We like to write the code ourselves.</h3>
+  <p>High-level programming wisdom is born from years of lower-level work. You don't know how to build a system until you've built it by hand a few times. It may be easy to use a library or prompt an AI, but by doing so you rob yourself of the understanding that makes it worthwhile.</p>
+
   <h3>We question “best practices”.</h3>
-  <p>We don’t contort our code in weird ways, write useless tests, or type a bunch of boilerplate unless we understand why. We strive to <em>be</em> experts, not to blindly trust those who claim to be.</p>
-  <p>After all, if the “best practices” still produce terrible software, maybe the “best practices” are wrong.</p>
+  <p>We don’t turn our code inside out, write useless tests, or type a bunch of boilerplate unless we understand why. We strive to <em>be</em> experts, not to blindly trust those who claim to be.</p>
+  <p>After all, if the “best practices” still produce terrible software, maybe it’s the “best practices” that are wrong.</p>
 
   <h3>We are not “language people”.</h3>
   <p>We are not “C programmers”, “C++ programmers”, “Rust programmers”, or “web programmers”. We are programmers, and languages are tools. What actually matters is how the software works, not how the software is created.</p>
 
-  <h3>We value the user more than the programmer.</h3>
+  <h3>We value the user above the programmer.</h3>
   <p>The user doesn’t care about the code. The user is not impressed by how elegant our programs are, or how quickly we wrote them. They only care if their software works, and works well.</p>
-  <p>We are happy when the user is happy.</p>
+  <p>Users can feel when software was made with care and craft. They can also feel when it was made without. Nothing we do as programmers matters unless it actually produces good software.</p>
+
+  <hr class="mv4">
+
+	<p class="i">Explore the best <a href="{{ .ProjectsUrl }}">Handmade projects</a> created by the community.</p>
 </div>
 {{ end }}
diff --git a/src/templates/types.go b/src/templates/types.go
index 678d83cf..a1978a1a 100644
--- a/src/templates/types.go
+++ b/src/templates/types.go
@@ -66,6 +66,7 @@ type Header struct {
 	CalendarUrl     string
 	ManifestoUrl    string
 	ValuesUrl       string
+	RulesUrl        string
 	AboutUrl        string
 
 	HSFUrl           string
diff --git a/src/website/base_data.go b/src/website/base_data.go
index 1637c2f8..04701c60 100644
--- a/src/website/base_data.go
+++ b/src/website/base_data.go
@@ -99,6 +99,7 @@ func getBaseTemplateData(c *RequestContext, title string, breadcrumbs []template
 			CalendarUrl:     hmnurl.BuildCalendarIndex(),
 			ManifestoUrl:    hmnurl.BuildManifesto(),
 			ValuesUrl:       hmnurl.BuildValues(),
+			RulesUrl:        hmnurl.BuildRules(),
 			AboutUrl:        hmnurl.BuildAbout(),
 
 			HSFUrl:           hmnurl.BuildHSFLanding(),
diff --git a/src/website/routes.go b/src/website/routes.go
index 2e778e0b..d459d52c 100644
--- a/src/website/routes.go
+++ b/src/website/routes.go
@@ -108,8 +108,13 @@ func NewWebsiteRoutes(conn *pgxpool.Pool, perfCollector *perf.PerfCollector) htt
 	hmnOnly.GET(hmnurl.RegexManifesto, Manifesto)
 	hmnOnly.GET(hmnurl.RegexValues, Values)
 	hmnOnly.GET(hmnurl.RegexAbout, About)
-	hmnOnly.GET(hmnurl.RegexCommunicationGuidelines, CommunicationGuidelines)
+	hmnOnly.GET(hmnurl.RegexRules, Rules)
+	hmnOnly.GET(hmnurl.RegexPrivacyPolicy, PrivacyPolicy)
+	hmnOnly.GET(hmnurl.RegexAIPolicy, AIPolicy)
 	hmnOnly.GET(hmnurl.RegexContactPage, ContactPage)
+	hmnOnly.GET(hmnurl.RegexOldCommunicationGuidelines, func(c *RequestContext) ResponseData {
+		return c.Redirect(hmnurl.BuildRules(), http.StatusFound)
+	})
 	hmnOnly.GET(hmnurl.RegexOldNewsletterSignup, func(c *RequestContext) ResponseData {
 		return c.Redirect(hmnurl.HMNProjectContext.BuildBlog(1), http.StatusFound)
 	})
diff --git a/src/website/staticpages.go b/src/website/staticpages.go
index 602e5516..79b14021 100644
--- a/src/website/staticpages.go
+++ b/src/website/staticpages.go
@@ -27,18 +27,14 @@ func Manifesto(c *RequestContext) ResponseData {
 func Values(c *RequestContext) ResponseData {
 	type TemplateData struct {
 		templates.BaseData
-		AboutUrl string
+		ProjectsUrl string
 	}
 	baseData := getBaseTemplateData(c, "Values", nil)
-	baseData.OpenGraphItems = append(baseData.OpenGraphItems, templates.OpenGraphItem{
-		Property: "og:description",
-		Value:    "“What I cannot create, I do not understand.”",
-	})
 
 	var res ResponseData
 	res.MustWriteTemplate("values.html", TemplateData{
-		BaseData: baseData,
-		AboutUrl: hmnurl.BuildAbout(),
+		BaseData:    baseData,
+		ProjectsUrl: hmnurl.BuildProjectIndex(),
 	}, c.Perf)
 	return res
 }
@@ -49,15 +45,30 @@ func About(c *RequestContext) ResponseData {
 	return res
 }
 
-func CommunicationGuidelines(c *RequestContext) ResponseData {
-	baseData := getBaseTemplateData(c, "Communication Guidelines", nil)
-	baseData.OpenGraphItems = append(baseData.OpenGraphItems, templates.OpenGraphItem{
-		Property: "og:description",
-		Value:    "The Handmade community strives to create an environment conducive to innovation, education, and constructive discussion. These are the principles we expect members to respect.",
-	})
+func Rules(c *RequestContext) ResponseData {
+	type tmpl struct {
+		templates.BaseData
+		AIPolicyUrl      string
+		PrivacyPolicyUrl string
+	}
+	var res ResponseData
+	res.MustWriteTemplate("rules.html", tmpl{
+		BaseData:         getBaseTemplateData(c, "Rules & Policies", nil),
+		AIPolicyUrl:      hmnurl.BuildAIPolicy(),
+		PrivacyPolicyUrl: hmnurl.BuildPrivacyPolicy(),
+	}, c.Perf)
+	return res
+}
+
+func PrivacyPolicy(c *RequestContext) ResponseData {
+	var res ResponseData
+	res.MustWriteTemplate("privacy.html", getBaseTemplateData(c, "Privacy Policy", nil), c.Perf)
+	return res
+}
 
+func AIPolicy(c *RequestContext) ResponseData {
 	var res ResponseData
-	res.MustWriteTemplate("communication_guidelines.html", baseData, c.Perf)
+	res.MustWriteTemplate("ai_policy.html", getBaseTemplateData(c, "AI Policy", nil), c.Perf)
 	return res
 }