Guides & insights
What buyers check, what the law says, and what to prepare before any data leaves your systems. Written for owners and operators, sourced to primary documents, and honest about what nobody can promise.
Before a software company licenses its operating data, check six things: contract rights, inventory, de-identification, security evidence, an evaluation sample and the licence terms. A sourced checklist.
Read the guide → Procurement dataWhat makes procurement, AP and spend data licensable: coverage, history, point-in-time integrity, normalisation, the six data-quality dimensions, panel stability and rights. A practical profile template.
Read the guide → Privacy & rightsBusiness datasets still hold personal data. What de-identified and anonymous mean under CCPA and GDPR, when data-broker rules apply, the DOJ Data Security Program, and the contract clauses to insist on.
Read the guide →Also on this site: what has actually been paid for data, in public deals, and a six-question estimate of where a company’s records land.
Policy watch · updates automatically
Before a company licenses any dataset, the rules on personal data, data brokers and AI are the part that moves fastest. This list is pulled from the official Federal Register API and filtered by keyword, so you can see what federal agencies have most recently published. It is not a summary, not legal advice, and not a signal of buyer demand or prices.
Source: Federal Register API (U.S. Government, public domain). Snapshot taken 2026-09-22T22:48:31Z UTC; refreshed from the live API when you load this page, at most every 12 hours.
See what a readiness review covers, and ask for one. Free, and nothing is shared with anyone without your written go-ahead.