templates/pages/about/policies/trademarks.html

   1 {%extends "base/page.html"%}
   2 {%load pgfilters%}
   3 '{%block title%}Trademark Policy{%endblock%}
   4 {%block contents%}
   5
   6 <h1>Trademark Policy <i class="fas fa-gavel"></i></h1>
   7
   8 <p><em>Last updated: November 20, 2024. {%git_changes_link%}</em></p>
   9
  10 <p>
  11   This policy pertains to our trademarks. Specifically, the terms
  12   <em>Postgres</em> and <em>PostgreSQL</em> and the Elephant Logo (Slonik) are
  13   all registered trademarks of the
  14   <a href="https://www.postgres.ca/">PostgreSQL Community Association of Canada</a>.
  15   If you wish to use these marks, you must comply with this policy.
  16 </p>
  17
  18 <h3>Why This Matters</h3>
  19
  20 <p>
  21   We have implemented this Trademark Policy because it is important to the
  22   Community that our trademarks are not used in ways that confuse people. For
  23   example, we do not want people to use our trademarks:
  24 </p>
  25
  26 <ul>
  27   <li>
  28     with software that is not related to PostgreSQL, does not run on it or work
  29     with it,
  30   </li>
  31   <li>to suggest (falsely) that PostgreSQL is not open source software,</li>
  32   <li>
  33     to suggest that they are somehow sponsored by, affiliated with, endorsed by
  34     or approved by the PostgreSQL Project when they are not,
  35   </li>
  36   <li>
  37     on competitive products (i.e. databases that are not PostgreSQL, or built on
  38     or derived from PostgreSQL), or to use them with unrelated goods and
  39     services.
  40   </li>
  41 </ul>
  42
  43 <p>
  44   If these things happen, over time, our marks will lose their meaning. As the
  45   Community grows, the best way to ensure that this does not happen is by
  46   setting and enforcing standards for how our marks are used.
  47 </p>
  48
  49 <h3>Fair Uses That Don’t Require Prior Approval</h3>
  50
  51 <p>
  52   You may make fair use of <em>Postgres</em> or <em>PostgreSQL</em> to refer to
  53   the software in true factual statements. For example:
  54 </p>
  55
  56 <ul>
  57   <li>
  58     If it’s true, you can say in your software or documentation that certain
  59     software runs on, with, or is derived from <em>PostgreSQL</em>&reg;
  60     software.
  61   </li>
  62   <li>
  63     You can use the trademarks to accurately advertise <em>PostgreSQL</em>&reg;
  64     software-related content in a public event.
  65   </li>
  66   <li>
  67     You can use the names <em>Postgres</em>&reg; or <em>PostgreSQL</em>&reg; in
  68     articles and blogs and forums to reference the database system.
  69   </li>
  70   <li>
  71     You may use <em>Postgres</em>&reg; or <em>PostgreSQL</em>&reg; in the title
  72     of a book about the software.
  73   </li>
  74   <li>
  75     You may (if accurate) identify yourself as an individual or corporate
  76     contributor to the <em>Postgres</em>&reg; or <em>PostgreSQL</em>&reg;
  77     database project.
  78   </li>
  79   <li>
  80     You may use <em>Postgres</em> or <em>PostgreSQL</em> on your website as
  81     links to our website at: <a href="/">https://www.postgresql.org</a>.
  82   </li>
  83 </ul>
  84
  85 <p>
  86   As long as you do not state or imply that that you or your business are
  87   affiliated with, endorsed, sponsored or approved by the PostgreSQL Community
  88   Association of Canada, PostgreSQL Global Development Group, PostgreSQL
  89   Project, PostgreSQL Core Team, or PostgreSQL Community, these kinds of uses of
  90   the words Postgres and PostgreSQL are generally fine.
  91 </p>
  92
  93 <h3>Other Approved Uses</h3>
  94
  95 <ul>
  96   <li>
  97     If your event or conference satisfies the
  98     <a href="/about/policies/conferences/">Community Recognition Guidelines</a>,
  99     you may use the marks to promote the event, including in the event name.
 100   </li>
 101   <li>
 102     <a href="/about/policies/user-groups/">Recognized PostgreSQL User Groups</a>
 103     may use the marks to promote their events, activities and groups.
 104   </li>
 105   <li>
 106     <a href="/about/policies/npos/">Recognized PostgreSQL nonprofit organizations</a>
 107     may use the marks in their materials in support of the project.
 108   </li>
 109 </ul>
 110
 111 <h3>How To Use Our Marks</h3>
 112
 113 <p>
 114   Please adhere to the following guidelines when using the marks as permitted
 115   under this <a href="">Trademark Policy</a>. If you fail to do so, we may
 116   revoke your permission to use them.
 117 </p>
 118
 119 <ul>
 120   <li>
 121     The marks should not be modified in any way without prior approval. They
 122     should not be presented with other trademarks or logos.
 123   </li>
 124   <li>
 125     <p>The Elephant Logo (Slonik) must appear in one of the forms below:</p>
 126     <p>
 127       <img class="img-fluid logo-preview" src="/media/img/about/press/elephant.png" alt="PostgreSQL Logo" />
 128       <img class="img-fluid logo-preview" src="/media/img/about/press/elephant-bw.png" alt="PostgreSQL Logo" />
 129     </p>
 130   </li>
 131   <li>
 132     Particularly if these uses are commercial in nature, we encourage you to
 133     present the marks with <em>Postgres</em>, <em>PostgreSQL</em> or the
 134     Elephant Logo (Slonik) followed by the &reg; symbol wherever practicable. If
 135     you use the outline version of Slonik, this should be followed by the
 136     &trade; symbol.
 137   </li>
 138   <li>
 139     Wherever possible, include the line:
 140     <em>
 141       Postgres, PostgreSQL and the Slonik Logo are trademarks or registered
 142       trademarks of the PostgreSQL Community Association of Canada, and used
 143       with their permission.
 144     </em>
 145   </li>
 146   <li>
 147     Do not seek to register any trademark containing one of our marks or a
 148     variant thereof.
 149   </li>
 150   <li>Do not use the marks in a business name or trade name.</li>
 151   <li>
 152     Do not use the marks in a way that would disparage the software, the
 153     PostgreSQL Community Association of Canada, PostgreSQL Global Development
 154     Group, PostgreSQL Project, PostgreSQL Core Team, or PostgreSQL Community.
 155   </li>
 156 </ul>
 157
 158 <h3>Uses That Require Approval</h3>
 159
 160 <p>
 161   For pretty much any use not discussed above, you must contact us for
 162   permission before you use our marks. For example, if you want to use our marks
 163   (or some variant of them) in your company name, product name or domain name,
 164   you must obtain prior approval. We will try to work with you to permit uses
 165   that support the <em>PostgreSQL</em>&reg; project and our Community. Please
 166   note, however, that we will approve uses in our sole discretion, and that we
 167   will not be able to approve uses if we believe that they will cause confusion
 168   about your relationship with the PostgreSQL Community Association of Canada,
 169   PostgreSQL Global Development Group, PostgreSQL Project, PostgreSQL Core Team,
 170   or PostgreSQL Community.
 171 </p>
 172
 173 <h3>Additional Information</h3>
 174
 175 <p>
 176   The
 177   <a href="https://www.postgres.ca">PostgreSQL Community Association of Canada</a>
 178   does NOT make any express or implied warranties, including but not limited to
 179   the warranties of non-infringement of any third-party intellectual property
 180   rights. We reserve the right to update this Trademark Policy from time to time
 181   without notice. Uses that predate this version of the Trademark Policy (i.e.
 182   uses prior to December 8, 2020) do not require permission from us so long as
 183   the use is consistent with this Policy. However, if you think you may have
 184   used the trademarks in the past in ways that would violate this Policy, we
 185   suggest seeking permission. Our aim is to work with you to support uses that
 186   support the project, however PostgreSQL Community Association of Canada
 187   reserves the right to deny trademark use that violates this Policy. Past use
 188   in violation of this policy does not confer a right to continue that use.
 189 </p>
 190
 191 <p>
 192   Please feel free to reach out to us by emailing
 193   <a href="mailto:board@lists.postgres.ca">board@lists.postgres.ca</a> with any
 194   questions or requests for approval.
 195 </p>
 196 {%endblock%}