Licence terms
Last updated
A plain-English summary of what you get when you buy a module, and how you may use it. The terms and conditions apply as well.
What you get
- A one-off payment for the module. There is no subscription and nothing renews automatically.
- 12 months of updates from the date of purchase: new versions and fixes, through Composer and as zip downloads.
- Every version released during your update period stays available to you after it ends.
- Renewing (the Renew button in My account → Products, at a discount on the module price) adds another 12 months. If your updates are still active, the new months are added to the end of the current period.
- Free modules come with the same licence, updates and Composer access; they simply cost nothing.
Platforms
Some modules have one price for Magento Open Source and another for Adobe Commerce (including Adobe Commerce Cloud). You choose the platform when you buy; the licence records it. It is the same module and the same Composer package either way. An Adobe Commerce licence also covers Magento Open Source.
Where you can use it
- One licence covers one production domain: the live address of the store that uses the module (for example
www.example.com). The first production domain that checks the licence is linked to it. - Staging and development copies are included at no extra cost: subdomains of your production domain (such as
staging.example.comordev.example.com),localhost, IP addresses and development domains ending in.testor.local. - If you move the store to another domain, you can release the old domain from My account → Products and the new one is linked on the next check.
- A store that runs several production domains needs one licence per domain.
- Agencies and freelancers may install, configure and maintain a module on a client’s store under the licence bought for that store.
Licence check
CommerceGears modules check their licence so that we can keep maintaining them. The check is designed never to get in the way of a correctly licensed store:
- How often: at most once a day per Magento installation, from Magento’s cron job, for all CommerceGears modules at once. Storefront pages never contact us.
- What is sent: the public part of your Composer key (or the licence key entered in the module settings), the store’s domain, a random installation ID, the Magento edition and version, and the names and versions of the CommerceGears modules installed. No customer, order or product data is sent. A hash derived from your private key proves the request is yours; the private key itself is never sent.
- If our licence server cannot be reached, the modules keep working as licensed.
- If our licence server reports that there is no valid licence for a module on that domain (for example the module was not bought, the purchase was refunded, or the licence is linked to another production domain):
- a notice is shown in the Magento admin and the module’s settings can no longer be changed. The module keeps working with its current settings;
- if the licence is still not valid after at least 14 days, the licence server can switch the module off. It then behaves as if it had been disabled in its settings; the storefront keeps working without it. For modules that hold records you may need (such as e-invoices, returns or shipping labels), existing records stay available and only new actions stop.
- As soon as a valid licence is in place (bought, renewed or the domain released), everything works again on the next check, or straight away with Check now in the module settings.
- The licence check does not affect versions or updates: your update period is described above.
Error reports
CommerceGears Core 2.1 and later report serious errors that happen in the code of CommerceGears modules to us, so that we can fix faults quickly. This is on by default and can be switched off at any time in Stores > Configuration > CommerceGears > General; switching it off does not affect your licence, updates or support.
- What is sent: the type, level and message of the error (by default only critical errors), up to 20 lines of the stack trace without values, the module and its version, the versions of your CommerceGears modules, Magento and PHP, the deployment mode, the store’s domain and the random installation ID of the licence check.
- What is never sent: customer, order, quote, address or payment data, the contents of requests, cookies, headers or passwords. An error message that contains personal data is not sent at all.
- When: at most once an hour, from Magento’s cron job, in small signed batches. Storefront pages never contact us, and if we cannot be reached the reports wait and nothing else changes.
- Transparency: CommerceGears > Error Reports in your admin shows every report with the exact data sent. How we handle this data is described in our privacy policy.
What you may do with the code
- Install, configure and use the module on the installations your licence covers.
- Change the code for your own use on those installations. Updates may overwrite changes made in the module’s own files, so we recommend making them with plugins or preferences in a module of your own.
You may not resell, sublicense, rent, publish or otherwise distribute the module or modified copies of it, share your Composer keys or downloads outside the installations your licence covers, or remove the licence check. Third-party open-source components included in a module remain under their own licences.
Support
If you have bought a module, you can open a support ticket about it from My account → Support tickets, for as long as you use it. There is no time limit on support. Support covers installing, configuring and using the module and fixing faults in it; custom development is quoted separately.
Refunds
You can ask for your money back within 30 days of any purchase: see the refund policy. A refunded purchase is removed from your licence.