Trademark and Logo Usage Policy
OpenText™ (and its affiliates) owns registered and unregistered product names, trade names, trademarks, service names, service marks, trade dress, taglines logos and other source identifiers (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 (any such written agreement or consent hereinafter are collectively referred to as “Agreements and Programs”) between you and OpenText. For the avoidance of doubt, this policy is incorporated by reference into and is deemed to be a part of any Agreements and Programs between you and OpenText. As such, this policy is contractually and legally binding on you. ACCORDINGLY, IF YOU DO NOT AGREE TO THIS POLICY, YOU MUST NOT MAKE ANY USE WHATSOEVER OF ANY OF THE MARKS. Moreover, the Agreements and Programs between you and OpenText and this policy, both expressly supersede and take precedence over any right to use or refer to the Marks (whether as a “fair use” or otherwise) that you might otherwise have and YOU HEREBY EXPRESSLY AND IRREVOCABLY WAIVE ANY AND ALL SUCH RIGHTS. All other trademarks and logos listed on OpenText materials are the property of their respective owners.
You must comply with this usage policy to use or refer to the Marks. For branding requirements of the Marks, including their required colors, typography, and other materials containing the Marks, please refer to other OpenText media. Usage of the Marks may further be governed by Agreements and Programs between you and OpenText, and as stated previously, this policy is incorporated by reference into and is a part of such Agreements and Programs. .
General Requirements for Usage of the Marks
OpenText trademarks that apply to this usage policy include all applicable Marks, whether registered or unregistered. For questions and to inquire further about the Marks, please contact firstname.lastname@example.org.
You may use the Marks, subject to restrictions set forth in Agreements and Programs between you and OpenText, and this policy, to identify OpenText products, services, and programs on packaging, promotional, and advertising materials, provided you meet the following requirements:
- You may not include any Marks in your company name, product or service name, or domain name.
- You may not include any Marks 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 the Marks to describe the purpose of the Social Media forum by referring to the OpenText product (“Forum for Magellan™ Users,” for example). Social Media includes, but is not limited to Twitter, Facebook (Meta), Instagram and Linked-In.
- You may not include any Mark, including any OpenText logo or product icon design, in 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.
- You should use an appropriate generic term after a Mark the first time it appears in any usage (whether in electronic or other media, including websites, white papers, technical documentation, manuals, packaging, a download page, app store marketing and Social Media) and as often as possible after that, such as product, software, cloud services, etc. For example, “OpenText™ Magellan™ software”; “OpenText™ CORE™ cloud services”.
- Your product name may not be confusingly similar to any Mark.
- You may not use any Marks on or in connection with any obscene materials, and your use of any Marks may not be disparaging, defamatory, or libelous to OpenText, any of its products, or any person or entity.
- You may not use 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. You may not use the Marks in any other way that is deceptive, false or misleading.
- A 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 Mark.
- 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 a Mark, use it with a ™, SM or ® in accordance with the Marks in OpenText media.
- You may not shorten, abbreviate, or modify any Mark. Always spell out the Marks exactly as they appear on OpenText media and do not modify and of the Marks, including any OpenText logos.
- 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 or unregistered marks of OpenText.”
- 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 Mark 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 or unregistered 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.]
The following sections list more specific usages and contexts for the Marks.
The Marks include any OpenText logos. Accordingly, 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 Agreements and Programs with OpenText, you do not have permission to use any 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 requirements.
Use of the Marks in titles of publications, conferences, and seminars.
Only if and to the extent permitted under any Agreements and Programs between you and OpenText, you may use the 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. Such usage of the Marks must comply with all of the following requirements:
- The subject of the publication, conference or seminar should be the specific OpenText product, service or technology to which the title refers.
- 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.
- 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.
- You may not use a Mark 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.
- You may not shorten or abbreviate any of Marks. Always spell and capitalize the Marks as shown on OpenText media.
- 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 or unregistered trademarks of Open Text."
- You must otherwise comply with the requirements in accordance with OpenText media.
- There should be nothing else in the use of the Marks or in the circumstances that would lead consumers or others to believe there is an association with, or endorsement by, OpenText that does not exist, and the 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, only with the prior written consent of OpenText, as reflected in and subject to Agreements and Programs between you and OpenText, the 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:
- 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.
- You may not include any 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 written authorization from OpenText as reflected in an Agreement and Program.
- Your product or service name may not be confusingly similar to any Mark.
- 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.
- 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.”
- Branding requirements for Marks, including taglines and their colors, typography, and other materials must comply in accordance with OpenText media.