# Guides to business data licensing

_Updated 2026-10-14_

These guides explain how company data licensing works in general terms: which records tend to matter, what affects value, why ownership and permission come first, and how private code differs from open-source software. They are educational and are not legal advice.

- [How to license company data for AI](/learn/license-company-data-for-ai): What business data licensing is, which record types are useful, how the process works, what affects value, and the questions to ask before agreeing to anything.
- [What affects the value of business data](/learn/what-affects-business-data-value): Depth, quality, scarcity, connected workflows, retained history, and permitted uses: the factors that shape business data value, without unsupported dollar estimates.
- [Rights and permissions come before any licensing discussion](/learn/data-licensing-rights-and-permissions): Why access to data does not establish a right to license it, and the ownership, contract, and privacy questions to review before any discussion.
- [Private codebase licensing: what software teams should know](/learn/private-codebase-licensing): How proprietary repositories, commit history, tests, and review context may matter, why private code differs from open source, and the rights questions to review.