Extract to table

Any data shared with Meridian in the course of the licensing relationship — whether for troubleshooting, data-quality validation, integration testing, or other operational purposes — must be limited to non-trade-secret inputs and must not include QuorumScore™ model outputs, model weights, algorithmic parameters, feature engineering logic, or any other trade-secret-protected elements

The specific drafting approach should be determined in consultation with Quorum's in-house team, but the substantive result must be the same: QuorumScore™ outputs must be excluded from the Derived Data framework, fully and unconditionally

This restriction must apply regardless of whether QuorumScore™ was trained using Meridian data as one of its inputs

Objective Transformation Standard If the MDLA includes any "sufficient transformation" requirement for third-party commercialization of Derived Data — whether applied to QuorumScore™ outputs or to other categories of Derived Data — the standard must be objective and jointly determined, not subject to Meridian's sole discretion

Under the current draft MDLA, Quorum is required to return or destroy all Meridian raw data within ninety (90) days of termination

However, the return-or-destroy obligation must not extend to QuorumScore™'s model weights, parameters, or outputs, even if those weights were influenced by training on Meridian data during the license term