Trademarks subject to the guidelines Our trademarks This Policy covers: 1. Our word trademarks and service marks (the "Word Marks"): Mark Common descriptive name for the goods or services CakePHP REMOVE CakeDC REMOVE CakeSF REMOVE CakeFest REMOVE CakeTalent REMOVE CakeJobs REMOVE CakeUniversity REMOVE

2. Our logos (the "Logos"): CakePHP Horizontal Logo CakePHP Vertical Logo CakePHP Vertical Tagline Logo CakePHP Horizontal Tagline Logo CakePHP Version Number

Horizontal Logo CakePHP Version Number

Vertical Logo CakePHP Version Number

and Name Horizontal Logo CakePHP Version Number

and Name Vertical Logo 3. CakePHP sister brands’ logos: CakeDC Full Name Horizontal Signature CakeDC Initials Horizontal Signature CakeDC Full Name Vertical Signature CakeDC Initials Vertical Signature CakeSF Full Name Horizontal Signature CakeSF Initials Horizontal Signature CakeSF Full Name Vertical Signature CakeSF Initials Vertical Signature CakeFest Horizontal Signature CakeFest Vertical Signature CakeTalent Horizontal Signature CakeTalent Vertical Signature CakeJobs Horizontal Signature CakeJobs Vertical Signature CakeUniversity Horizontal Signature CakeUniversity Vertical Signature 4. Community Flags

These have been corrected to show your support for the CakePHP project. The terms of this Policy applies to the usage of these logos. 1. Group Flag: The Group Flag is used to show plural form of usage. Example, you are a company or group of developers wanting to let others know you use CakePHP.

Floating Flag Embed Code: <div style = "position:fixed; top:20%; right:0; z-index:9999;" > <a href = "http://www.cakephp.org/" > <img src = "http://www.cakephp.org/img/flags/We-bake-with-CakePHP.png" width = "100px;" > </a> </div> Image files: DOWNLOAD PNG DOWNLOAD EPS DOWNLOAD SVG 2. Application Flag: The Application Flag is used to show that your have built an application that is using CakePHP. Floating Flag Embed Code: <div style = "position:fixed; top:20%; right:0; z-index:9999;" > <a href = "http://www.cakephp.org/" > <img src = "http://www.cakephp.org/img/flags/Baked-with-CakePHP.png" width = "100px;" > </a> </div> Image files: DOWNLOAD PNG DOWNLOAD EPS DOWNLOAD SVG 3. Developer Flag: The Developer Flag is used by individuals to show their support for the project and that they are using CakePHP. Floating Flag Embed Code: <div style = "position:fixed; top:20%; right:0; z-index:9999;" > <a href = "http://www.cakephp.org/" > <img src = "http://www.cakephp.org/img/flags/I-bake-with-CakePHP.png" width = "100px;" > </a> </div> Image files: DOWNLOAD PNG DOWNLOAD EPS DOWNLOAD SVG 4. Supporter Flag: The Supporter Flag is used to spread the word about CakePHP and tell them to use CakePHP. Floating Flag Embed Code: <div style = "position:fixed; top:20%; right:0; z-index:9999;" > <a href = "http://www.cakephp.org/" > <img src = "http://www.cakephp.org/img/flags/Bake-with-CakePHP.png" width = "100px;" > </a> </div> Image files: DOWNLOAD PNG DOWNLOAD EPS DOWNLOAD SVG 5. Community Flags usage Guidelines:

Respect a margin over a forth of the flag’s hight to ensure visual effectiveness. The side margins might be disregarded while using the flag on the extreme left or right sides of a layout. 5. And the unique visual styling of our website and packaging (the "Trade Dress").

5.1. Brand colors. PANTONE 1797 C CMYK: 11, 91, 75, 2 RGB: 212, 61, 68 HEX: #D33C43 PANTONE 446 C CMYK: 0, 0, 0, 90 RGB: 65, 64, 66 HEX: #404041 5.1.1 Sister Brand Colors. - CakeDC PANTONE 7689 C CMYK: 80, 38, 18, O RGB: 47, 137, 175 HEX: #2F85AE PANTONE 446 C CMYK: 0, 0, 0, 90 RGB: 65, 64, 66 HEX: #404041 5.1.2 Sister Brand Colors. - CakeSF PANTONE 7508 C CMYK: 17, 24, 71, O RGB: 215, 185, 103 HEX: #D6B967 PANTONE 446 C CMYK: 0, 0, 0, 90 RGB: 65, 64, 66 HEX: #404041 5.1.3 Sister Brand Colors. - CakeFest PANTONE 7473 C CMYK: 79, 22, 36, 1 RGB: 32, 152, 161 HEX: #1F97A0 PANTONE 446 C CMYK: 0, 0, 0, 90 RGB: 65, 64, 66 HEX: #404041 5.1.4 Sister Brand Colors. - CakeTalent PANTONE 631 C CMYK: 65, 0, 12, 2 RGB: 52, 189, 215 HEX: #34bdd7 PANTONE 446 C CMYK: 0, 0, 0, 90 RGB: 65, 64, 66 HEX: #404041 5.1.5 Sister Brand Colors. - CakeJobs PANTONE 123 C CMYK: 0, 20, 90, 2 RGB: 248, 197, 48 HEX: #f8c530 PANTONE 7465 C CMYK: 70, 0, 40, 0 RGB: 49, 187, 172 HEX: #404041 5.1.6 Sister Brand Colors. - CakeUniversity PANTONE 7465 C CMYK: 70, 0, 40, 0 RGB: 49, 187, 172 HEX: #31bbac PANTONE 446 C CMYK: 0, 0, 0, 90 RGB: 65, 64, 66 HEX: #404041 5.2. Brand stylistic shape: the ellipse used to design the Brandmark is also a brand asset itself, and it can be used as a decorative corner on layout boxes and backgrounds. 5.3. Iconography: icons and illustrations follow the Brandmark aesthetics: flat, clean and use negative space for lighting and shading. The images are designed using the official color palette. Conceptually, the ico nography follows the baking universe. This Policy encompasses all trademarks and service marks, whether Word Marks, Logos or Trade Dress, which are collectively referred to as the “Marks.” Some Marks may not be registered, but registration does not equal ownership of trademarks. This Policy covers our Marks whether they are registered or not. The trademarks we are licensing in this Policy The following trademarks are ones that covered by the Policy, all others are reserved exclusively to our use: Community flags as shown in Section 4 Contact us as described in "Where to get further information" below if you have questions or want to ask permission to use any of our reserved trademarks.

Universal considerations for all uses Whenever you use one of the Marks, you must always do so in a way that does not mislead anyone, either directly or by omission, about exactly what they are getting and from whom. The law reflects this requirement in two major ways described in more detail below: it prohibits creating a "likelihood of confusion" but allows for "nominative use". For example, you cannot say you are distributing the CakePHP Framework when you're distributing a modified version of it, because people would be confused because they are not getting the same features and functionality they would get if they downloaded the software directly from us. You also cannot use our logo on your website in a way that suggests that your website is an official website or that we endorse your website. You can, though, say you like the CakePHP Framework, that you participate in the CakePHP community, that you are providing an unmodified version of the CakePHP Framework, or that you wrote a book describing how to use the CakePHP Framework. This fundamental requirement, that it is always clear to people what they are getting and from whom, is reflected throughout this Policy. It should also serve as your guide if you are not sure about how you are using the Marks. In addition: You may not use the Marks in association with the use or distribution of software if you are also not in compliance with the copyright license for the software. You may not use or register, in whole or in part, the Marks as part of your own trademark, service mark, domain name, company name, trade name, product name or service name. Trademark law does not allow your use of names or trademarks that are too similar to ours. You therefore may not use an obvious variation of any of our Marks or any phonetic equivalent, foreign language equivalent, takeoff, or abbreviation for a similar or compatible product or service. We would consider the following too similar to one of our Marks: Any mark ending with the letters Cake. Any mark beginning with the letters Cake. You agree that you will not acquire any rights in the Marks and that any goodwill generated by your use of the Marks inures solely to our benefit.

Use for software See Universal considerations for all uses, above, which also apply. Uses we consider non-infringing Distribution of unmodified source code or unmodified executable code we have compiled

When you redistribute an unmodified copy of our software, you are not changing the quality or nature of it. Therefore, you may retain the Word Marks and the Logos we have placed on the software, to identify your redistribution -- whether that redistribution is made by optical media, memory stick or download of unmodified source and executable code. This kind of use only applied if you are redistributing an official distribution from this Project that has not been changed in any way. Distribution of executable code that you have compiled, or modified code

You may use the Word Marks, but not the Logos, to truthfully describe the origin of the software that you are providing, that is, that the code you are distributing is a modification of our software. You may say, for example, that "this software is derived from the source code for CakePHP Framework." Of course, you can place your own trademarks or logos on versions of the software to which you have made substantive modifications, because by modifying the software, you have become the origin of that exact version. In that case, you should not use our Logos. Our source code version therefore does not contain our Logo data files. Statements about compatibility, interoperability or derivation

You may use the Word Marks, but not the Logos, to truthfully describe the relationship between your software and ours. Our Mark should be used after a verb or preposition that describes the relationship between your software and ours. So you may say, for example, "Bob's software for the CakePHP Framework " but may not say "Bob's CakePHP software." Some other examples that may work for you are: [Your software] works with CakePHP Framework

[Your software] uses CakePHP Framework

[Your software] is compatible with CakePHP Framework

[Your software] is powered by CakePHP Framework

[Your software] runs on CakePHP Framework

[Your software] for use with CakePHP Framework

[Your software] for CakePHP Framework Use of trademarks to show community affiliation

This section discusses the use of our Marks for software such an application themes, skins and personas. The use of our Marks on websites is discussed below. You may use the Word Marks and the Logos in themes, personas, or skins for applications to show your support for the Project, provided that the use is non-commercial and the use is clearly decorative, as contrasted with a use that appears to be the branding for a website or application. Uses for which we are granting a license Distribution of modified software

<<Example #1: You may use the Word Marks and the Logos for the distribution of code (source or executable) on the condition that any executable is built from the official Project source code and that any modifications are limited to switching on or off features already included in the software, translations into other languages, and incorporating bug-fix patches.>> <<Example #2: You may use the Word Marks and the Logos for the distribution of executable code on the condition that it is made from official Project source code using the procedure documented for creating an executable found at <<location of build instructions.>>>> Distribution of software preloaded on hardware

<<Example #1: You may use the Word Marks and the Logos in association with hardware devices on the condition that the executable installed on the device is the official source executable for the Project, and that you do not suggest that the Project is the source of the hardware device itself but rather than the Marks are for the software incorporated into the device.>> <<Example #2: You may use use the Word Marks and the Logos in association with hardware devices on the condition that the software installed on the device is modified only so far as necessary to operate on the hardware platforms and the essential functions of the software are unchanged, and that you do not suggest that the Project is the source of the hardware device itself but rather than the Marks are for the software incorporated into the device.>> Uses we consider infringing without seeking further permission from us We will likely consider using the Marks in a software distribution that combines our software with any other software program an infringement of our Marks. In addition to creating a single executable for both software programs, we would consider your software "combined" with ours if installing our software automatically installs yours. We would not consider your software "combined" with ours if it is on the same media but requires separate, independent action to install it. Use for non-software goods and services See Universal considerations for all uses, above, which also apply. Uses we consider non-infringing Websites

You may use the Word Marks and Logos, but not the Trade Dress, on your webpage to show your support for the Project as long as: The website has branding that is easily distinguished from the Project Trade Dress;

You own branding or naming is more prominent than any Project Marks;

The Logos hyperlink to the Project website;

The site does not mislead customers into thinking that either your website, service, or product is our website, service, or product; and

The site clearly states that you are not affiliated with or endorsed by the Project. Publications and presentations

You can use the Word Marks in book and article titles, and the Logo in illustrations within the document, aslong as the use does not suggest that we have published, endorse, or agree with your work. Events

You can use the signage in the <<Brand Standards>> to promote the software and Project at events. Uses for which we are granting a license User groups

You can use the Word Marks as part of your user group name provided that: The main focus of the group is the software;

Any software or services the group provides are without cost;

The group does not make a profit;

Any charge to attend meetings are to cover the cost of the venue, food and drink only. Note that the Universal considerations for all uses, above, still apply, specifically, that you may not use or register the Marks as part of your own trademark, service mark, domain name, company name, trade name, product name or service name. Promotional goods

"Promotional goods" are non-software goods that use the Marks and that are intended to advertise the Project, promote the Project, or show membership in the Project community. <<Example #1>> You may make promotional goods for free giveaway at open source conferences and events using only the designs found on our <<Brand Standards>> site. <<Example #2>> You may make promotional goods for free giveaway at open source conferences and events provided that the goods are obtained from <<contractor for promotional goods.>> Uses we consider infringing without seeking further permission from us We will likely consider using the Marks as part of a domain name or subdomain an infringement of our Marks. We would likely consider using the Marks on promotional goods for sale an infringement of our Marks.

General Information Trademark marking and legends The first or most prominent mention of a Mark on a webpage, document, packaging, or documentation should be accompanied by a symbol indicating whether the mark is a registered trademark ("®") or an unregistered trademark ("™"). See our Trademark List for the correct symbol to use. Also, if you are using our Marks in a way described in the sections Uses for which we are granting a license, please put following notice at the foot of the page where you have used the Mark (or, if in a book, on the credits page), on any packaging or labeling, and on advertising or marketing materials: CakePHP and related Marks are trademarks of Cake Software Foundation, Inc. and Cake Development Corporation, registered in the United States and other countries. Used with permission from Cake Software Foundation, Inc. What to do when you see abuse If you are aware of any confusing use or misuse of the Marks in any way, we would appreciate you bringing this to our attention. Please contact us as described below so that we can investigate it further. Where to get further information If you have any questions about this Policy, would like to speak with us about the use of our Marks in ways not described in the Policy, or see any abuse of our Marks, please contact legal [at] cakefoundation.org