CurrentWare

CurrentWare — Two distinct assets, and the licensable one is not the obvious one. The candidate asset is student web-activity telemetry from BrowseReporter: sites visited, browsing times, search queries, high-risk-site alerts and evidence of policy violations, captured by a Windows agent that keeps working when the device leaves school and is managed against Active Directory organisational units so policy groups map to age bands, departments and classrooms. But the deployment model — on-premises, a self-managed customer cloud server, or Citrix/RDP/Terminal Server — means that telemetry is wri…

CurrentWare offers (Reference, Alternative, Sentiment) — The classification asset is large and countable: millions of URLs across 100+ categories, versioned continuously — plausibly tens to hundreds of millions of mapping rows with revision history. The activity asset is genuinely unknown: if it accumulates at all, 700+ organisations of mixed school and workplace size would generate hundreds of millions to billions of visit and query records annually, but under this deployment model those rows live in customer databases and the vendor's aggregate hold is likely near zero. Do not price an activity corpus here without explicit confirmation..

Lead with the taxonomy: licensing a continuously maintained 100+ category web classification across millions of domains is directly useful for training and evaluating content-safety and URL-classification models, for ad-suitability and brand-safety pre-screening, and as ground-truth labels against which a buyer can score its own classifier — and it contains no personal data whatsoever. The institutional-override decisions are a subtler asset: records of organisations deliberately allowing a named domain inside a blocked category are human preference judgements about category boundaries, valuable for policy-calibration work. If any centralised activity history does exist, the search-query-plus-blocked-category pairs are usable for minor-safety classifier evaluation, but this must be confirmed rather than assumed given the deployment model.

The data is with 20 years of history.