Bluebird NDB Insights

Bluebird NDB Insights is an AI-powered platform for analysing and reporting on Notifiable Data Breaches (NDB). It helps organisations identify trends and risks and supports regulatory reporting. Every figure is computed from statistics published by the Office of the Australian Information Commissioner (OAIC).

At a glance

Notifications, Jul–Dec 2025
670
Up 12.6% on 595 in Jul–Dec 2024
From malicious or criminal attacks
60.4%
Of notifications, Jul–Dec 2025
Notified to the OAIC within 30 days
50.6%
308 of 609 in-range breaches

The problem

Notifications are rising, and the published record is hard to read as a whole

  • The model never writes a digit.

    Bluebird NDB InsightsAsk

Breach notifications have risen in each published half-year since January to June 2023. They reached 670 in July to December 2025, the highest in the series and 12.6% up on the same half of 2024. Privacy, risk and compliance teams need to understand the trends and meet their reporting obligations.

The published record is hard to read as a whole. Figures are restated as notifications are assessed, reporting moved from quarterly to half-yearly and then to a dashboard, and one recent period was never published.

Notifications per half-year, 2018 to 2025

The OAIC published no report for January to June 2025, so that half stays empty. The first halves of 2018 and 2019 are platform sums of quarterly reports.

View the data
PeriodNotificationsBasis
January to June 2018305Platform sum; scheme began 22 February 2018
July to December 2018507Published
January to June 2019460Platform sum
July to December 2019532Published
January to June 2020512Published
July to December 2020530Published
January to June 2021436Published
July to December 2021460Published
January to June 2022393Published
July to December 2022486Published
January to June 2023407Published
July to December 2023485Published
January to June 2024518Published
July to December 2024595Published
January to June 2025NoneNot published
July to December 2025670Published

What it does

The whole published record, in one place

NDB Insights brings the scheme's published statistics together: notifications by month and the historical series since 2018, breach detail, and the time taken to identify, respond and notify.

Each figure carries a basis label and a "Where did this come from?" link. A workspace adds three AI-assisted tools.

Restated figures and gaps stay visibleFor July to December 2022, the first-published figure of 497 sits beside the latest figure of 486, which was restated in the January to June 2023 report. January to June 2025 was not published and is shown as a gap.July to December 2022497486First publishedLatestRestated in the January toJune 2023 reportJanuary to June 2025Not publishedShown as a gap,with no estimate
  • Ask

    Describe the dashboard you want. The builder lays out the structure and citations, and the platform computes every figure.

    "The model never writes a digit."

  • Chat

    Ask questions about the published statistics. Answers are grounded in the data notes and published figures, and every figure carries a source.

    For example: "What share were malicious attacks?"

  • Reports

    Signed-in users build reports from the same figures. The report builder emits structure and citations, and the platform computes every number.

The Bluebird NDB Insights overview page, showing 670 notifications and a chart of notifications per half-year from 2018 to 2025.

See it in the live demo

Captured from the demo on 9 November 2026.

Open the demo (opens ndb.axoquant.com in a new tab)

How it works

How each figure is sourced and checked

  1. Pin the sources

    The OAIC's July to December 2025 workbook is pinned by its hash, and the 18 OAIC reports from 2018 to 2024 are transcribed into a registry.

  2. Label every figure

    Each figure is marked as a published period figure, a published month figure, or a platform sum of published figures.

  3. Keep restatements visible

    When a later report restates a figure, the latest value is shown, the first-published value is kept beside it, and the restating report is named.

  4. Check at start-up

    The platform re-sums its facts against hand-verified published totals for every period from 2018 to 2025. A mismatch stops the service.

  5. Serve with lineage

    Every figure links to where it came from, and the same figures are available through a read-only API.

What the AI does

  • Turns a plain-language description into a dashboard layout with citations.
  • Answers questions grounded in the data notes and the published figures.
  • Drafts the structure of reports built from the same figures.

What it is built not to do

  • Write a number: the platform computes every figure.
  • Give legal advice: or say whether a specific incident is an eligible data breach.
  • Identify anyone: the chat refuses requests that would identify a breach, an entity or an individual.
  • Fill a gap: an unpublished period stays a disclosed gap.

As stated in the demo's reference pages.

Inside the product

Every view, and what it shows

Views

NDB at a glanceThe latest period on one page

Notifications for the latest half-year and the change on the same half last year, the main sources of breach, the share identified within 10 days and notified within 30 days, a "What the data says" summary and the historical trend.

NotificationsBy month, and the series since 2018
  • Notifications by month from the latest workbook.
  • The historical series from 2018, including a restatement table that shows first-published and latest values.
Breach detailWho and what was affected, and how
  • Individuals affected: published in ranges. The large-breach threshold changed over the series, so it travels with each figure.
  • Kinds of information: contact, identity, financial, health, tax file numbers, other sensitive information and, from 2025, digital ID.
  • Source of breach: malicious or criminal attack, human error and system fault.
  • Top sectors, and sectors and movers.
TimeTo identify, respond and notify

Time taken in calendar days from when the entity became aware of the incident, from the workbook's bands. The 30-day window reflects the assessment obligation in section 26WH of the Privacy Act. Where no whole-period median is published, no median is shown.

ReferenceThe definitional authority for every figure
  • Data notes: what the figures count, the categories, publication cadence and known source quirks. The chat answers are grounded in this text.
  • How to use, API access and data provenance.
APIThe same figures, as read-only JSON
  • /api/: dataset information, dimensions and keys.
  • /api/figures: every platform-computed figure with its basis.
  • /api/facts: the underlying facts, filterable by period, month, dimension, category and measure.
  • /api/measures: the dimensions and their measures.

The API never returns a number the platform did not compute from the pinned sources.

Data and method

Published counts, labelled and reconciled

Every figure carries the as-of date of the report that published it. Coverage was checked against every readable source on 12 September 2026.

Where one figure comes from

Notifications, July to December 2025

670

Basis
Period
Source file
NDB Data 1 July 2025 to 31 Dec 2025.xlsx
As at
29/06/2026
SHA-256 (first 12)
18a1b7fecd90
Published on
data.gov.au
Data sources
SourceUsed for
OAIC Notifiable Data Breaches workbook, 1 July to 31 December 2025, as at 29 June 2026 (data.gov.au)The latest period and monthly figures
OAIC Notifiable Data Breaches reports, 2018 to July–December 2024 (18 reports)The historical series, and timeliness trend lines from 2020 to 2023
Platform sums of published figuresThe 2018 and 2019 first-half totals, labelled as derived

Source of breach, July to December 2025

Share of the 670 notifications. The three groups do not sum to 100% because the OAIC workbook publishes "Other" and "Currently unknown" only monthly.

Gaps and quirks, disclosed

Headline figures, 1 July to 31 December 2025
FigureWhat it means
670Notifications received, up 12.6% on 595 in the same half of 2024
60.4%Notifications where a malicious or criminal attack was the source
37.8%Cyber incidents
29%Human error
5.2%System faults
58.7%Breaches identified within 10 days (349 of 595 in-range breaches)
50.6%Breaches notified to the OAIC within 30 days (308 of 609 in-range breaches)

Cyber incidents (253 of 670) are one part of malicious or criminal attacks (405 of 670), alongside social engineering or impersonation (88), rogue employee or insider threat (34), and theft of paperwork or storage devices (30). Source: OAIC NDB statistics via data.gov.au, as computed by NDB Insights.

Trust and security

Aggregate data only, with set limits on the chat

Data used
Aggregate, published statistics from the OAIC. No breach, entity or individual is identified.
Chat limits
Refuses legal advice, questions about whether a specific incident is an eligible data breach, and anything that would identify a breach, an entity or an individual.
Figures
Computed by the platform from pinned sources. The model never writes a digit.
Integrity checks
At start-up, facts are re-summed against hand-verified published totals and the pinned workbook hash. A mismatch stops the service.
Restatements
The latest published value is shown with the first-published value beside it, and the restating report is named.

Common questions

Why do 60.4% and 37.8% both describe attacks?

The OAIC's "malicious or criminal attack" category includes cyber incidents, rogue employees and insider threats, social engineering or impersonation, and theft of paperwork or storage devices. In July to December 2025, cyber incidents made up 253 of the 405 malicious or criminal notifications.

Why is January to June 2025 missing?

The OAIC published no report for that half: its statistics dashboard replaced the report cycle. Rather than read values off a chart, the platform shows the period as a disclosed gap.

How current is the data?

The latest published period, July to December 2025, is on the site from the OAIC workbook as at 29 June 2026. Coverage was last checked on 12 September 2026.

Can we use the figures in our own tools?

Yes. A read-only JSON API returns the same platform-computed figures and facts, and never a number the platform did not compute from the pinned sources.

Get started

From the public record to your own reports

  1. Explore the demo

    Every page is open, with sources linked.

  2. Try the chat

    Ask about notifications, sources of breach or sectors.

  3. Build your reports

    Talk to us about using Ask and Reports with your team.

Sources

Last reviewed: 9 November 2026.

Talk to us about your next initiative

Contact us How to procure us