EC Code, Methodology, Reuse, and Product Development Policy

Purpose

This policy replaces the former data-use/commercialization framing with a cleaner code/methodology/product-development framing.

No Raw Data Commercialization

Quintin N. Mahan does not claim a right to sell, license, publish, release, open-source, or commercialize raw CRS-owned operational records, raw customer records, customer relationships, independent outside source records, customer-owned records, third-party-owned records, or raw database contents merely because such information is stored in EC.

Owner Freedom Over EC Protected Materials

Quintin N. Mahan may modify, reuse, adapt, improve, sell, license, publish, release, transfer, open-source, commercialize, or otherwise use EC Protected Materials, including EC code, schemas, database design, workflows, automations, dashboards, reports, query logic, methods, processes, techniques, trade secrets, documentation, hardware designs, and platform structure, to the maximum extent permitted by law.

Company Has No Feature Control

CRS and its users cannot demand updates, prevent updates, restrict feature implementation, require feature implementation, stop feature removal, control release timing, control code decisions, control methodology, or control EC hardware decisions unless Quintin N. Mahan signs a separate written agreement stating otherwise.

Safeguards

Reuse or release of EC Protected Materials should exclude passwords, API keys, OAuth tokens, private credentials, non-public customer data, raw CRS-owned records, customer-owned records, third-party-owned records, and other protected secrets unless lawfully authorized.