# Incident Monitor — Japan

> Publicly disclosed personal-data incidents in Japan. Updated through a scheduled four-hour research workflow. Each original announcement remains the source of record.

## Data and methods

- [Japanese overview](https://incident-monitor-jp-3ez.pages.dev/index.md): cumulative quantities and searchable organizations.
- [English overview](https://incident-monitor-jp-3ez.pages.dev/en/index.md): the same dataset with English navigation.
- [Current CSV](https://incident-monitor-jp-3ez.pages.dev/api/data): current source snapshot, with x-data-fetched-at response header; cached for at most 15 minutes.
- [Current documented data](https://incident-monitor-jp-3ez.pages.dev/data.md): all current rows and source links, with the actual fetch timestamp.
- [Current JSON](https://incident-monitor-jp-3ez.pages.dev/dataset.json): typed columns, NULL values and source provenance; live data with a static fallback.
- [Methodology](https://incident-monitor-jp-3ez.pages.dev/methodology.md): quantity units, date rules and reuse conditions.
- [Research status](https://incident-monitor-jp-3ez.pages.dev/api/status): research execution timestamps, separate from website fetch time.

The displayed total mixes units and may overlap across affected organizations. It must not be described as a count of confirmed unique people or independent attacks. Quoting a particular case requires verification against its linked original announcement. Files named llms.txt or llms.md are navigation aids, not an assertion of preferential AI indexing.