/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

A researcher finds 800GB of data online tied to school software maker Raptor, used by 5,300+ US districts, including evacuation plans and student medical files

More than 4 million school records, including safety procedures, student medical files, and court documents, were also publicly accessible online.

Wired Matt Burgess

Context & Ripple Effects

School systems have repeatedly faced exposure through education technology: an earlier investigation found ransomware groups publishing schoolchildren's sensitive information, while a later PowerSchool incident involving historical student and teacher data showed how a single vendor can concentrate records across many districts.

This case matters because the accessible material extends beyond ordinary student-directory data to operational safety and medical records. It adds a public-exposure route to a sector already affected by ransomware-related leaks of schoolchildren's data.

First-order effects

  • Students, families, and staff tied to affected districts face immediate privacy and safety risk from publicly accessible medical, court, and evacuation-related records.
  • Raptor and the districts using its software must determine which records were exposed and whether access pathways remain open.

Second-order effects

  • Districts are likely to scrutinize vendor data inventories, access controls, and responsibility for records held in shared school-software systems.
  • The exposure raises the operational cost of centralized school-data platforms: a weakness at one provider can create simultaneous remediation work for thousands of customers.

Third-order effects

  • If this pattern persists, school-software procurement will increasingly turn on demonstrable data governance and clear accountability across vendors and districts, not just product functionality.
  • The sector may move toward treating student-data platforms as shared critical infrastructure, because concentrated records can turn a single exposure into a system-wide incident.

The trend: Education technology is becoming a concentrated data-risk layer, making vendor security and accountability a district-wide governance issue.