diff --git a/templates/pages/about/policies.html b/templates/pages/about/policies.html
index 1f89f1e7..79c39170 100644
--- a/templates/pages/about/policies.html
+++ b/templates/pages/about/policies.html
@@ -48,6 +48,7 @@
PostgreSQL Sponsorship
Conferences
Non-Profit Organisations
+ User Groups
{%endblock%}
diff --git a/templates/pages/about/policies/user-groups.html b/templates/pages/about/policies/user-groups.html
new file mode 100644
index 00000000..25a81995
--- /dev/null
+++ b/templates/pages/about/policies/user-groups.html
@@ -0,0 +1,127 @@
+{%extends "base/page.html"%}
+{%load pgfilters%}
+{%block title%}Recognised PostgreSQL User Groups{%endblock%}
+{%block contents%}
+
+Recognised PostgreSQL User Groups
+
+Last updated: November 19, 2020 {%git_changes_link%}
+
+
+ Recognised PostgreSQL User Groups, aka "PUGs", may
+ be listed on the PostgreSQL Website as
+ such. To become recognised as PostgreSQL User Group, the user group must
+ self-certify that they meet the criteria below, aimed at ensuring they meet
+ the standards of openness expected in the PostgreSQL Community.
+
+
+
+ Use of the terms "MAY", "MUST", "MUST NOT", "SHOULD" and "SHOULD NOT" in the
+ criteria below should be interpreted per
+ RFC2119,
+ where:
+
+
+
+ - MUST and MUST NOT are requirements, and
+ - MAY, SHOULD, and SHOULD NOT are optional, recommended guidelines.
+
+
+General
+
+
+ -
+ The PostgreSQL User Group MUST be primarily focused on PostgreSQL and
+ related technologies. PostgreSQL User Groups that target a broad range of
+ database products are not eligible as PostgreSQL User Groups.
+
+ -
+ PostgreSQL User Groups are for the entire PostgreSQL community and are
+ public in nature. There MUST NOT be any requirement of a Non-Disclosure
+ Agreement (NDA) or similar contract for an attendee to attend the Meetup.
+
+ -
+ The PostgreSQL User Group MUST adopt and follow an appropriate Code of
+ Conduct to ensure a safe and enjoyable environment for anyone who wishes to
+ participate.
+
+
+ -
+ The PostgreSQL User Group MUST have at least one event every two calendar
+ years in order to maintain its recognition as a PostgreSQL User Group.
+
+ -
+ The PostgreSQL Core Team reserves the right
+ to recognise, not recognise, or rescind a previous recognition for any
+ PostgreSQL User Group without justification.
+
+ - These criteria MAY be reviewed and potentially updated at any time.
+
+
+Organisers
+
+
+ - The PostgreSQL User Group Organizers MUST be individuals.
+ -
+ The PostgreSQL User Group Organizers MUST be listed on the membership site
+ for the PostgreSQL User Group.
+
+ -
+ The PostgreSQL User Group Organizers SHOULD NOT consist of 50% or more of
+ the same company or group of companies under the same ultimate ownership or
+ management.
+
+
+
+Events
+
+
+ -
+ Anyone MAY submit a PostgreSQL-related talk proposal. The Organizers SHOULD
+ choose to accept or reject the talk proposal based on a simple majority
+ vote.
+
+ -
+ Anyone MAY offer to host a PostgreSQL User Group. The meeting space SHOULD
+ be in the region represented by the PostgreSQL User Group. The Organizers
+ SHOULD choose to accept or reject the space based on a simple majority vote.
+
+ -
+ A Speaker MUST disclose in advance if the primary content of their talk
+ involves a closed-source product or a project that is not directly related
+ to PostgreSQL.
+
+ -
+ Organizations MAY promote their business at a PostgreSQL User Group event
+ if:
+
+ -
+ Their business SHOULD help drive further adoption of PostgreSQL AND
+
+ -
+ Any content presented at the PostgreSQL User Group MUST be technical in
+ nature.
+
+
+
+
+
+Sponsorship
+
+
+ -
+ The PostgreSQL User Group group MUST disclose on its web page any
+ organizations that provide financial or in-kind sponsorship to the Community
+ User Group.
+
+ -
+ The PostgreSQL User Group SHOULD mention any Sponsors in the introductions
+ of the user group meeting.
+
+
+{%endblock%}
diff --git a/templates/pugs/index.html b/templates/pugs/index.html
index dbbc0df3..57c8fb07 100644
--- a/templates/pugs/index.html
+++ b/templates/pugs/index.html
@@ -3,8 +3,9 @@
{%block contents%}
Local User Groups
-The PostgreSQL community is proud to have many local chapters that advocate and educate users about PostgreSQL. Below is a list of PostgreSQL User Groups (PUGs) sorted by country and local area. If you would like to start a PostgreSQL User Group, please send an email to usergroups@postgresql.org and describe the PUG that you want to create.
-If a PUG already exists in your area, follow the URLs below to find out how to attend and participate.
+The PostgreSQL community is proud to have many local chapters that advocate and educate users about PostgreSQL. Below is a list of PostgreSQL User Groups (PUGs) sorted by country and local area.
+If you would like to start a PostgreSQL User Group, please send an email to usergroups@postgresql.org and describe the PUG that you want to create. If a PUG already exists in your area, follow the URLs below to find out how to attend and participate.
+PostgreSQL User Groups must follow the Recognised PostgreSQL User Group policy.
{% for pug_group in pug_list %}
{{ pug_group.country }}