skip to main content

Trademark and Logo Usage Policy

OpenText (and its affiliates) owns registered and unregistered product names, trade names, trademarks, service names, service marks, and logos (the “Marks”) in Canada, the United States, and in other countries. You may not use, reproduce, advertise, display, publish, or transmit any of the Marks without OpenText's prior written consent and/or absent a written agreement (written agreement hereinafter referred to as “Agreements and Programs”) between you and OpenText. All other trademarks and logos listed on OpenText materials are the property of their respective owners.

You must comply with this usage policy to refer to OpenText Marks. For branding requirements of OpenText Marks, taglines, colors, typography, and other materials, please refer to OpenText Brand Central. Usage of OpenText Marks may further be governed by Agreements and Programs between you and OpenText and/or prior written consent of OpenText.

General Requirements for Usage of OpenText Marks

For a listing of OpenText trademarks that apply to this usage policy, please refer to the OpenText Trademarks. This list may be updated from time-to-time and may not include all applicable OpenText trademarks, whether registered or unregistered. For questions and to inquire further about OpenText trademarks, please contact ipadmin@opentext.com.

You may use OpenText Marks, subject to restrictions set forth in Agreements and Programs between you and OpenText and/or prior written consent of OpenText, to identify OpenText products, services, and programs on packaging, promotional, and advertising materials, provided you meet the following requirements:

  1. You may not include any OpenText Mark in your company name, product or service name, or domain name.
  2. You may not include any OpenText Mark in your social media account name, assets, page(s) or community (collectively, “Social Media”), without written authorization from OpenText. Upon written authorization, you may use OpenText Marks to describe the purpose by referring to the OpenText product (“Forum for Magellan™ Users,” for example). List of Social Media includes, but is not limited to Twitter, Facebook, Instagram.
  3. You may not include any OpenText logo or product icon design, whole or in part, in your company logo, your product logo, your app launch tile image, in your software product or service or in your Social Media without prior written consent from OpenText.
  4. You should use an appropriate generic term after an OpenText trademark the first time it appears in a publication and as often as possible after that, such as product, software, cloud services, etc. For example, OpenText Magellan product; OpenText CORE cloud services.
  5. Your product name may not be confusingly similar to any OpenText trademark.
  6. You may not use any OpenText Mark on or in connection with any obscene materials, and your use of any OpenText Mark may not be disparaging, defamatory, or libelous to OpenText, any of its products, or any person or entity.
  7. You may not use OpenText Marks in any manner that directly or indirectly expresses or implies OpenText sponsorship, affiliation, certification, approval, or endorsement in relation to your product or service, except as permitted by Agreements and Programs between you and OpenText.
  8. An OpenText Mark may not be the most prominent visual element on packaging, a download page, app store marketing, or other marketing materials for your product or service. Your company name or logo, your product or service name, and your graphic identity should be significantly larger than any OpenText Mark.
  9. If you refer to an OpenText product, you should use the full name of the product in the first and most prominent reference (OpenText Magellan, OpenText AppWorks, for example). When using an OpenText trademark, mark it with a ™ or ® in accordance to that described in the OpenText Trademark list.
  10. You may not shorten, abbreviate, or modify any OpenText Mark. Always spell out OpenText’s trademarks exactly as they appear in the OpenText Trademarks and do not modify OpenText logos.
  11. You should include the following trademark attribution statement in your literature and materials (replace everything in brackets [ ] appropriately): “[List of trademarks used, with ‘OpenText’ first, if used, followed by other OpenText marks used, in alphabetical order] are either registered trademarks or trademarks of OpenText.”
  12. You should follow the basic requirements and guidelines for proper Mark usage, as exemplified in the following examples:
    • Trademarks are not verbs.
      Correct: For the trademark AppWorks – The app was enhanced using OpenText AppWorks software.
      Incorrect: The app was AppWorked.
    • Trademarks are not nouns.
      Correct: The AppWorks app pokes fun at politics
      Incorrect: The AppWorks pokes fun at the politics.
    • Always capitalize and use trademarks in their correct form.
      Correct: The app was enhanced with OpenText AppWorks software.
      Incorrect: The app was appworked.
    • Trademarks must never be used as slang terms.
      Correct: Developers use OpenText AppWorks software to manipulate apps.
      Incorrect: An appworker generates a multi-platform app.
    • Trademarks must never be used in possessive form.
      Correct: The new features in OpenText Magellan software import more formats. [The goods and services, here software, are included.]
      Incorrect: Magellan’s new features import more formats.
    • Trademarks are proper adjectives and should be followed by the generic terms they describe.
      Correct: The algorithm was generated using OpenText Magellan software.
      Incorrect: The algorithm was generated using AppWorks.
    • Trademarks must never be abbreviated.
      Correct: Take a look at the new features in OpenText AppWorks software.
      Incorrect: Take a look at the new features in AW.
    • The trademark owner should be identified whenever possible.
      OpenText and AppWorks are either registered trademarks or trademarks of OpenText.
    • The goods and services associated with the trademark should be mentioned with the trademark, where appropriate. The use of the trademark should not be descriptive.
      Correct: OpenText Magellan software enables powerful predictive analytics capabilities. [The goods and services, here software, are clearly attached to the trademark.]
      Incorrect: Magellan is a multi-step process for predictive analytics. [Here, Magellan is descriptively called out to define a technical process. This is incorrect because Magellan is not a process, but a product and service name.]
  13. Branding requirements for OpenText Marks, taglines, colors, typography, and other materials must comply with OpenText Brand Central.

The following sections list more specific usages and contexts for OpenText Marks.

Logos

You may not use, reproduce, advertise, display, publish, or transmit any OpenText logo without OpenText’s prior written consent. Your use must comply with Agreements and Programs between you and OpenText, as well as requirements described here. Absent such agreement with OpenText, you do not have permission to use OpenText logos.

You may qualify for use of certain logos under the programs offered through the OpenText Partner Program, as well as other programs OpenText offers. The OpenText Partner program may refer to additional specific partner program logo guidelines.

Use of OpenText Marks in titles of publications, conferences, and seminars

Upon prior written consent of OpenText and/or Agreements and Programs between you and OpenText, you may use OpenText Marks in the titles of publications, conferences and seminars that provide in-depth training on OpenText products or services beyond that available from OpenText product tutorials, training and reference materials. Usage of OpenText Marks must comply with all of the following requirements:

  1. The subject of the publication, conference or seminar should be the specific OpenText product, service or technology to which the title refers.
  2. The OpenText Marks may not appear larger or more prominent than the rest of the full publication, conference or seminar title, and your name or logo should be displayed more prominently on the cover of the publication and in all materials related to the conference or seminar.
  3. The OpenText Marks may not be used in the stylized form other than that used by OpenText, and no OpenText logos, taglines, or OpenText product imagery may be used on your publication’s cover or your publication, conference or seminar’s website, advertising, or promotional material, without express written permission from OpenText.
  4. You may not use an OpenText trademark in the domain name of your publication, conference or seminar website, or Social Media associated therewith, without prior written consent or equivalent authorization from OpenText.
  5. You may not shorten or abbreviate any of OpenText’s trademarks. Always spell and capitalize OpenText’s trademarks exactly as they appear in the OpenText Trademarks.
  6. You must include the following trademark attribution statement: "[List of trademarks used, with 'OpenText' first, if used, followed by other OpenText marks used, in alphabetical order] are either registered trademarks or trademarks of Open Text."
  7. You must otherwise comply with the requirements of OpenText Brand Central.
  8. There should be nothing else in the use of OpenText Marks or in the circumstances that would lead consumers to believe there is an association with, or endorsement by, OpenText that does not exist, and the OpenText Marks should be used only to refer to the OpenText products that are the subject of the publication, conference or seminar.

Additional Requirements for Third-Party Developers

If you are a developer (including system integrator and/or services providers) of apps, plug-ins, tools, scripts, application programing interfaces (APIs) or extensions for an OpenText product or service, you may use, with prior written consent and/or subject to Agreements and Programs between you and OpenText, OpenText Marks in a referential manner on packaging, websites, promotional, and advertising materials to give notice that your product is compatible with the referenced OpenText product or service, provided you meet the following requirements:

  1. You may not incorporate or include any OpenText Mark in your company name, trade name, product name, domain name, name of your service, and/or a Social Media associated therewith.
  2. You may not include any OpenText Mark, product icon design, or product imagery, in whole or in part, in your company logo, your product logo, your app launch icon or launcher tile image or otherwise in your software product or service without a prior written license or equivalent authorization from OpenText.
  3. Your product or service name may not be confusingly similar to any OpenText Mark.
  4. If you state that your product is compatible with an OpenText product or service, the product must in fact be compatible with that OpenText product or service and otherwise work with that OpenText product as intended and described in the documentation of your product.
  5. Any notice that your product is compatible with an OpenText product or service must be made in a referential manner such as “for use with,” “for,” “powered by,” or “compatible with.” Example: “[Your product name] app for OpenText AppWorks”, “[Your product name], powered by OpenText Magellan”, or “ABC extension for OpenText Content Server.”
  6. Branding requirements for OpenText Marks, taglines, colors, typography, and other materials must comply with OpenText Brand Central.