Branding Requirements Clause Samples

Branding Requirements. Partner will include the JumpCloud Marks in a prominent location on Partner’s website, platform, and/or other channels as mutually agreed upon by the parties.

Branding Requirements. API User may develop, display or distribute API Applications that interact with the API. API User agrees that it is solely responsible for the API Applications that it develops and that its API Applications must comply with the Branding Requirements, incorporated herein by this reference, which can be found here: ▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇.▇▇▇/legal-docs/brand-requirements/.

Branding Requirements. Supplier will not use any trademarks, logos, service marks, trade names, copyrighted material, and domain names owned by Snap-on, its parent company or its affiliates (collectively, “Snap-on Marks”) without Snap-on’s prior written approval or direction, which may be withheld or withdrawn at any time in the sole and absolute discretion of Snap-on. If use of the Snap-on ▇▇▇▇ is approved or directed, Supplier will comply with the directions given by Snap-on, including, without limitation, the Snap-on brandmark guidelines, as may be amended by Snap-on from time to time. The most current brandmark guidelines will be provided to Supplier upon written request and Supplier will make written request before using any Snap-on Marks. Supplier shall obtain Snap-on’s written approval before changing the design, materials or specifications of the Products branded with Snap-on Marks. Supplier will not sell, distribute or transfer Products with Snap-on Marks to any other person or entity other than Snap-on. Snap-on reserves all rights and ownership in and to the Snap-on Marks. Supplier shall not authorize the use of the Snap-on Marks by any third-parties. Supplier shall not use Sub-Suppliers to make parts with Snap-on Marks or Products or components of Products that are privately labeled or otherwise exclusively provided to Snap-on without first obtaining Snap-on’s written approval. Supplier shall ensure that any approved Sub-Suppliers comply with this section and the Supplier’s subcontract shall, at a minimum, restrict Sub-Supplier from: (1) selling, distributing or transferring such Products or Product components (or substantially similar Products and Product components) to persons or entities other than Supplier or Snap-on and (2) using any packaging and labeling, Product design or similar designs, or business methods, technical data and other information and materials related to such Products or Product components for any purpose other than the supply of Product to Snap-on.

Branding Requirements. The Service shall initially be branded by Client as “Adelphia Music.” * CERTAIN INFORMATION IN THIS EXHIBIT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE COMMISSION. CONFIDENTIAL TREATMENT HAS BEEN REQUESTED WITH RESPECT TO THE OMITTED PORTIONS.

Branding Requirements. The Parties shall mutually agree on the branding for the exterior of each Product. Sharp shall affix or cause to be affixed the ▇▇▇▇▇ ▇▇▇▇ on such Products and on all related packaging, promotional and advertising materials as mutually agreed to by Sharp and the Carrier. In addition, Sharp shall provide appropriate branding opportunities to Danger, as mutually agreed to by Danger and Sharp, in the marketing and distribution of any Product. Notwithstanding the foregoing, Sharp shall affix or cause to be affixed the “hiptop® Technology by Danger, Inc.” logo (or other logo designated by Danger) on all Products distributed hereunder in a location and of a size to be determined by the Parties.

Branding Requirements. At CompuServe's discretion, The Knot will co-brand each of its pages and host them on the following domain: thek▇▇▇.▇▇▇▇▇▇▇▇▇▇.▇▇▇

Branding Requirements. There are certain generic operations and user interactions that are required to be implemented in all Solutions, regardless of the content creator: · Dragging a Solution from place to place. A small “envoii” cursor text appears (this may be replaced with something else in the future); · Interacting with a Solution on the desktop to minimize, maximize, destroy, clone, or stow it; · Interacting with Solutions on the desktop tray; and · Indicating state of a Solution on mouse-over (i.e.“you can drop a Solution on me,” “you can copy me,” “you can drag me to desktop.”). Envoii may prescribe by written notice the appearance, design, colors, etc. of text, icons, highlight techniques associated with these activities. The overall objective is to develop a universal and consistent visual vocabulary associated with Solutions.

Branding Requirements. The Knot must co-brand each of its pages and host them on the following domain: thek▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇ The code for the co-branding guidelines can be found at: http://▇▇▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇:▇▇▇▇/mega/index.html ID=partner, password=c0nt3nt Implementing the code will require minor changes to the parts of the code that apply specifically to The Knot.

Branding Requirements. 4.2.1 Where technically feasible and/or available, SBC-13STATE will brand Operator Services (OS) and/or Directory Assistance (DA) in CLEC's name as outlined below: 4.2.1.1 Provide its brand at the beginning of each telephone call and before the consumer incurs any charge for the call; and 4.2.1.2 Disclose immediately to the consumer, upon request, a quote of its rates or charges for the call. 4.2.2 Where SBC-13STATE provides CLEC OS and DA services via the same trunk, both OS and DA calls will be branded with the same brand. Since SBC-13STATE's DA and OS utilize the same trunk group, CLEC will receive the same brand for both DA and OS. 4.2.3 CLEC agrees and warrants that it will provide to SBC-13STATE a name to be used for branding covered by this Agreement that matches the name in which CLEC is certified to provide local Telecommunications Services by the applicable state Commission.