BrightCat data is licensed to enterprise clients under the BrightCat Master Data License Agreement (MDLA). This page summarizes the framework for buyers, procurement teams, and legal reviewers evaluating how BrightCat access works in a commercial relationship. The summary is educational; the MDLA itself governs any licensed engagement.
Licensing, not sale
BrightCat data is licensed, never sold. Clients receive the right to use the data under defined terms; BrightCat retains all rights, title, and interest in the underlying data, intelligence layer, methodology, and derivative works. A license agreement does not transfer ownership and does not convey the right to resell, redistribute, or sublicense the data to third parties.
Use scope
The standard license permits the client's internal business use of BrightCat data across defined use cases — analytics, underwriting, portfolio monitoring, retention modeling, customer acquisition, valuation, and similar enterprise applications. The scope is written to match the client's actual business need rather than restricting use to a single narrow case.
Some use cases require explicit coverage in the license. These include AI and machine learning model training on BrightCat data, incorporation of BrightCat data into derivative products or services offered to third parties, and any use that extends access beyond the named licensee organization. These use cases are not prohibited; they are addressed through specific licensing provisions so both parties have clarity about what is permitted.
Term flexibility
License terms are structured around the client's commercial needs. Annual and multi-year terms are both available, with pricing that reflects the length and scope of the engagement. Renewal terms are included in the base agreement. No setup fees. No hidden costs.
Restrictions
Standard restrictions exist to protect the integrity of the BrightCat dataset and the commercial interests of all clients. These include:
- No resale or redistribution of BrightCat data to third parties outside the named licensee
- No sublicensing of access credentials or delivery endpoints
- No reverse engineering of the property-intelligence methodology
- No removal of BrightCat attribution from licensed outputs where attribution is required
- No use inconsistent with the licensed use scope (e.g., unlicensed AI model training)
Remedies for material breach are defined in the MDLA and include financial remedies scaled to the impact of the breach.
Confidentiality and data handling
The MDLA includes mutual confidentiality provisions appropriate for enterprise data engagements. Clients are responsible for protecting their delivery credentials and for applying reasonable security measures to the data inside their environment. BrightCat's delivery posture (Snowflake Secure Data Share, MCP connector with scoped OAuth, encrypted file delivery) is summarized on the
Security and Compliance page.
Jurisdiction
BrightCat Data Ltd. is a UK-registered private limited company. Standard commercial agreements are governed by the laws of England and Wales, with jurisdiction provisions tailored to the client's own jurisdiction where appropriate (particularly for Canadian clients, where mirrored jurisdiction provisions are common).
How to review the MDLA
The current MDLA reference document is available to enterprise procurement and legal teams under NDA as part of due diligence. This summary page is designed for general buyer orientation; the MDLA itself is the governing commercial document and includes the complete set of terms, definitions, remedies, and schedules that a licensed engagement operates under.
Procurement, legal, or commercial teams can request MDLA access by contacting
alexandria@brightcatdata.com. Standard response is one to three business days.
This page is a summary of the BrightCat licensing framework. The MDLA itself is the binding commercial document.