Privacy Unpacked

Corrections and changes

Every change to a breach record after it was first published, with the reason: 29 corrections, 649 updates in the last 180 days. Follow the log (Atom feed).

How we correct the tracker

  • Every change is logged. When a record changes after it is published, the change is listed here and on the record’s own page, with the date and the reason. We do not quietly rewrite records.
  • Corrections are marked. A record taken down a step (from “confirmed” to “reported”, say) or fixed by an editor is a correction. A new official notice or a count that grew is an update.
  • How each source is read. Official notices are read by code from the regulators’ own registers. News reports are read by an AI model, and every fact it takes from an article is checked word for word against that article; what cannot be found is dropped. A breach is “confirmed” only by an official notice, or when an article quotes the organisation itself or an authority confirming it.
  • Right of reply. If your organisation is on the tracker, you can send us a statement. We publish factual statements on the record’s page, dated and attributed, and log them here.
  • Found a mistake? Tell us, with a source if you have one. We check it against the official record and log the correction here.

The log

From the data breach tracker: official notices, breach databases and the news, every fact with its source. Open data (CC BY 4.0) · How the tracker works · Official registers · Corrections and changes · Found a mistake? Tell us and we correct it.