Have Fun Teaching Data Breach

A public breach source catalogues 27,126 unique emails with user-agent details, IPs, names, payment methods, physical addresses, and purchased items and says the service is aware of the incident. August 15 is a catalogue date; no primary source establishes it as the exact access or exfiltration day.

Approximately 80,000 describes transaction rows, while 27,126 is a public breach source's unique-email measure. The local import unioned billing and customer-account email columns and produced 27,189 unique normalized emails, 63 above a public breach source's count. The difference may involve two-column union semantics, dataset version, normalization, or counting, but remains unreconciled.

Local search contains email fields only. A result does not identify anyone as a customer, teacher, parent, school, tutor, or student and cannot establish a purchase, grade or subject interest, address, IP, device or browser, payment method, field co-occurrence, compromise, or misuse. A negative result covers only the 27,189 local emails.

No password or card-number class is reported in the source. Correct names, addresses, or item details do not authenticate a sender; unexpected purchase and payment messages should be checked through independent official channels. Education roles, purchase history, and address or payment information must remain private.