This log lists every factual correction published on DataPacts, each with its date, the page, what changed and the primary source behind the corrected value. A correction is a fix to a statement that was wrong when it was published, and the log keeps each one permanently so that readers can see what changed.
The site went live on 2026-11-10, and no correction has been published as of that date. Changes that follow the world, such as a new court filing or a buyer's new terms, are updates and stay on the pages themselves. The log belongs to the reference on AI training data licensing and covers every page of it.
Published corrections, as of 2026-11-10
No corrections have been published as of 2026-11-10.
| Date | Page | What the page said | What the page says now | Primary source |
|---|---|---|---|---|
| none | No corrections published as of 2026-11-10 | n/a | n/a | n/a |
Published corrections, as of 2026-11-10.
Entries are added newest first. The as-of date in the caption moves forward whenever the log is reviewed, so an empty log with a recent date means that no correction has been needed since launch. A row is never removed once it is added, and a later row never rewrites an earlier one. If a correction itself proves wrong, a new entry is added that refers back to the earlier one.
Correction or update: how DataPacts tells them apart
A correction fixes a statement that was wrong when it was published; an update records something that changed after publication. The distinction matters because a correction says the page erred, while an update says the world moved. Keeping the two apart stops the log from filling with routine changes and keeps each entry meaningful as an admission of error.
| Correction | Update | |
|---|---|---|
| What happened | the page was wrong when published | the record changed after publication |
| Typical cases | wrong figure, date or docket number; a buyer's claim attributed to the wrong party; a pending matter written as decided | new docket entry; a buyer changes its program terms; a law's application date arrives |
| How the page shows it | corrected value with a new check date | new value or status with a new check date or as-of date |
| Listed in this log | yes | no |
Correction and update compared, as of 2026-11-10. Source: DataPacts editorial practice.
Updates carry a new check date or as-of date on the page itself and are not listed here. Each source type is re-checked on its own cycle, described in how we source, date and check every figure, and court dockets are checked before every update of a case or sale page.
A scheduled court hearing produces an update, not a correction
When a court rules on a pending matter, the page changes its status and as-of date, and that change is an update. The Spirit Airlines de-identified data sale in In re Spirit Aviation Holdings, Inc., et al., Bankr. S.D.N.Y. No. 25-11897 (SHL), was not approved as of 2026-11-09. The sale hearing is set for 2026-11-17 at 11:00 a.m. ET (Notice of Adjournment, Dkt. 1779, filed 2026-11-04). Whatever the court decides, the pages that describe the sale will change through an update, with the new status and a new as-of date shown on each page. Until an order exists, those pages describe the sale as pending and state who bid and what is before the court only as the docket records it.
It would become a correction only if a page had stated something the docket did not support at the time. Calling a successful bid a purchase, or the sale approved before an order exists, would be such a statement, because a pending matter is never written as decided.
The same rule applies to every sale in bankruptcy, and the case is covered with the others in the guide to how administrators, trustees and liquidators sell data to AI buyers.
What each log entry records
Each entry records five things:
- the date of the correction
- the page, named by its H1 and linked to its URL
- what the page said
- what it says now
- the primary source, with its issuer, document and date
The wrong value is replaced in place on the page, and the corrected value carries a new check date. The entry stays in the log permanently, and the table anchors are never renamed, so a link to the log or to a single table keeps working. Where a correction concerns a figure, the entry gives the old and the new value side by side, and the date of the primary source is the date the issuer gave, not the date of the check.
Reporting an error for this log
Errors can be reported to editorial@datapacts.com with the page and a primary source that shows the correct value. A useful report contains four things:
- the URL of the page
- the statement believed to be wrong
- the primary source that shows the correct value
- the date of that source
A report is checked against the primary source it names. A report never changes inclusion, order, tone or coverage, and no response time is promised. A report that cannot be matched to a primary source is not acted on, and a report that is confirmed leads to a dated entry in the table above. Other routes, such as buyer introductions and general questions, are described on the page where readers contact the editorial team.
Related trust pages
The corrections log works together with the editorial policy, the About page and the funding disclosure.