CELAEST
Sign InSign Up
Back to home
SOFTWARE LICENSE AGREEMENT

Digital Asset License Agreement (EULA)

Legal terms and intellectual property rights governing purchased Excel macros, Python scripts, and automations.

Version 2.2·Last updated: November 2026·
01SECTION 01

Commercial License Grant

Perpetual, worldwide, non-exclusive commercial license for internal operational use within Customer's organization.

Upon purchasing or downloading macros, scripts, or software from the CELAEST Marketplace, Customer is granted a perpetual, worldwide, non-exclusive, non-transferable commercial license to execute the asset within its internal operations.

License scope covers all internal workstations, servers, and authorized personnel up to the licensed tier volume.

02SECTION 02

Use Restrictions and Anti-Piracy Protection

Public distribution, reselling, sublicensing, or posting source code to external third parties is strictly prohibited.

The granted license expressly prohibits:

Breach of these restrictions results in immediate revocation of the license without refund and authorizes legal remedies.

  • Selling, reselling, renting, leasing, sublicensing, or transferring asset source code to external third parties.
  • Posting source code to public repositories (GitHub, GitLab, forums) or open-access internet venues.
  • Bundling Marketplace scripts or macros into a competing commercial product or service.
03SECTION 03

Modifications and Derivative Works for Internal Use

Full freedom to audit, adapt, and refactor code to integrate seamlessly into your company's workflows.

Customer is granted full rights to audit, inspect, adapt, refactor, and integrate purchased source code with existing internal systems.

All derivative adaptations remain subject to the non-redistribution and confidentiality restrictions set forth herein.

04SECTION 04

Quality Verification and Sandbox Testing

Assets undergo rigorous verification, but must be validated in staging environments prior to production rollout.

Every Marketplace asset undergoes technical vetting before publication. However, because client IT topologies vary infinitely, software is delivered "as is".

Customer is strictly responsible for validating and testing all scripts in staging or sandbox environments prior to production deployment.