This document sets out rights and obligations regarding licensing of digital software and content obtained through the Platform. Unless expressly stated otherwise, the principles below apply; specific licence agreements and product descriptions take precedence.
1. Licensing model
The vendor grants you a limited, non‑transferable right of use without sublicensing rights unless expressly stated. Title is not transferred; only a licence to use is granted. Open‑source licences (e.g. MIT, GPL) are governed by their respective texts.
2. Copying, backup, and archiving
A reasonable number of backups may be created for personal or internal business use. Backups must not be used for redistribution to third parties, unauthorised relicensing to your customers, or circumventing closed‑source terms.
3. Installation, activation, and hardware changes
Most licences allow reinstall within reasonable limits on the same user/licence scope. Hardware locking, online activation, or device caps are stated in the product description. Bypassing activation or unlimited circumvention constitutes breach and may end access.
4. Updates and versions
Free patches, one‑year (or stated) support, major upgrades as separate products, etc., vary by product or contract. If automatic updates are offered, content and price (if any) are disclosed separately.
5. Dependencies, third‑party APIs, and copyright
External libraries, fonts, stock media, or services must be disclosed by the vendor; you must comply with copyright and licence terms in your commercial projects. Reverse engineering or library extraction is permitted only under open‑source terms or legal permission.
6. Commercial clients and team licences
Freelance, agency, or team models (per seat, per project, revenue thresholds, etc.) must be clearly stated. Otherwise the licence is limited to the registered buyer’s individual or stated corporate scope.
7. Infringement, termination, and remedies
Breach, unauthorised sharing, cracking, or piracy may lead to legal action (notice, penalties, damages) and permanent bans from the Platform. Copyright and revenue loss may be claimed under applicable law.
8. Open‑source components
If a product includes GPL, LGPL, Apache, MIT, or similar components, distribution, source provision, attribution, and derivative obligations follow those licences. Closed‑source and open‑source portions should be distinguished in the package or description; where they conflict for a component, the open‑source licence governs that component.
9. Sublicensing, consulting, and client delivery (white‑label limits)
White‑label or delivery to your clients requires clear limits on end users, devices, and domains unless stated in the product or an add‑on agreement. Unspecified sub‑licensing, reseller, or OEM distribution is not implied; written approval may be required.
For a specific product, the dedicated licence agreement is authoritative; this document is limiting where it conflicts with that product’s description.
