The following is provided as a simplified overview of our Asset licenses.<\/strong> We want to give you peace of mind that license terms won’t suddenly change and compromise your project after you’ve begun developing it or even published it.<\/p>\n\n\n\n To that end, our licenses state that only the following changes can be mandatory:<\/strong> To stay informed of any license changes, you should visit our Announcements<\/a> page once per month, or subscribe to our newsletter<\/a>.<\/strong><\/p>\n\n\n\n License versions are made of 3 numbers: for example, 1.2.3<\/strong>. In short:<\/strong> You must always assign the latest Sub-Version…:<\/strong> Please be aware that license hoarding<\/em> is not permitted: License Sub-Versions apply to specific Asset Sub-Versions:<\/strong>
Nothing written here overrules our license terms<\/a> nor is legally binding or contractual.
Always refer to the actual Candy Arts licenses for the most accurate information.<\/strong><\/strong><\/p>\n\n\n\n
\n\n\n\nLicense Terms Guarantee<\/h4>\n\n\n\n
\u2022 Limited changes for administrative or legal purposes: for example to change our brand name, to make corrections or clarifications to the text, or to comply with laws, regulations or court decisions.
\u2022 Changes that increase your rights or reduce your obligations.
\u2022 Those changes are called license Updates<\/strong>.
\u2022 If you object to an Update, the only option is to stop using our Assets. You can contact us<\/a><\/strong> within 60 days of an Update and, if your objections are legitimate, we may give you time to do so, during which your project will remain subject to the previous terms.
All other changes to the license terms can’t be mandatory:<\/strong>
\u2022 Those changes are called license Sub-Versions<\/strong>.
\u2022 If you refuse them, you can continue to use our Assets under the terms your projects already have.
\u2022 In return, your projects must also retain their current scope: if you want to change to another licensing tier, or update to newer versions of our Assets, you must agree to the latest terms.<\/p>\n\n\n\n
\n\n\n\nVersion Numbers<\/h4>\n\n\n\n
\u2022 1 is the Major Version<\/strong> number.
\u2022 2 is the Sub-Version<\/strong> number.
\u2022 3 is the Update<\/strong> number.<\/p>\n\n\n\n
\u2022 Major Version numbers indicate different products, so different licenses apply to them.
\u2022 Sub-Versions don’t apply automatically.
\u2022 Updates apply automatically to their corresponding Sub-Version.
For example:
\u2022 If you assign License 1.4.2 to a project, and we publish License 1.4.3, it immediately applies.
\u2022 1.5.3 would not apply automatically to License 1.4.2 because it’s an Update to a different Sub-Version.<\/p>\n\n\n\n
\u2022 …When you assign a new license to a project.
\u2022 …When you change to another licensing tier.
\u2022 …When you choose to upgrade a license to a newer Sub-Version.
\u2022 Until you do any of the above, you don’t have to upgrade Sub-Versions just because we published a new one.<\/p>\n\n\n\n
This is the act of assigning an early version of a license to a project in order to secure the license terms for later, with no plans to actually develop the project now or in the near future.<\/p>\n\n\n\n
For example, License 1.4.0 might say that it applies to Asset 1.2.x or less:
\u2022 It can be used with Asset 1.0.x, 1.1.x, and 1.2.x.
\u2022 It can’t be used with Asset 1.3.x or higher.
\u2022 If you want to use Asset 1.3.x, you will need to upgrade to the latest Sub-Version.
\u2022 The ‘x’ means any number: in this example, the license can be used with Asset 1.2.0, 1.2.1, 1.2.2, etc.<\/p>\n\n\n\n