On 18 November 2026, Japanese anime and music retailer CDJapan, run by Neowing Corporation, published a second report that made its breach far larger than first disclosed. The notice describes two separate thefts. One was a bulk copy of the database on 6 November, taking 360,538 historical card records (registered or used 2005–2018) and the contact details of 791,111 members with a card-registration history. The other was skimming code on the computer checkout page, live from 6 November at 9:06 PM to 13 November at 7:52 PM JST. It logged 1,152 page displays, of which 490 involved a submit action.
The case is a useful test of how Japan's privacy regime treats a breach at a retailer that sells to the world. It also shows why data localisation is the wrong lens for it.
What happened, and what the first notice missed
Per the company's notices, the attacker got in on 5 November at about 2:55 PM through a vulnerability, according to PrivacyAffairs' reading of the reports, in a product image page. CDJapan filed a first report with the Personal Information Protection Commission (PPC) on 13 November. That first notice covered only 285 cards and did not mention the database copy. Five days later the figures were multiples larger, after an outside forensics review.
The revised scope matters, but so do its limits. CDJapan says the 2005–2018 card records contain numbers, expiry dates and names but no security codes, and that the cards have since expired. The cardholders most exposed are the ones who paid by card on a computer during the skimming week, because that code captured security codes. The notice does not say that every card used since 2005 was stolen with its code, though some social posts read it that way.
The legal frame: reporting, not residency
The Act on the Protection of Personal Information (APPI) is the governing statute. In the official English translation, Article 26 requires businesses to report leaks, loss or damage of personal data to the PPC and, separately, to notify the affected individuals. CDJapan's 13 November filing and its 18 November update fit that pattern: report early, then correct the record.
Here the strongest case for stricter rules deserves a fair hearing. A first report that understates a breach by a factor of thousands can leave customers unprotected for days. Regulators in several jurisdictions have pushed for fixed clocks and detailed content requirements for exactly that reason. A critic could fairly say CDJapan's first notice gave customers a misleadingly small picture.
But the remedy for an incomplete first report is not a heavier ex ante regime. A prompt, provisional report followed by a corrected one is how a forensics-driven investigation normally works. Regulators and consumers are better served by early signals and honest revisions than by delayed, polished disclosures. The policy question for the PPC is whether it can verify that the later report is complete, not whether the first one was perfect.
Where cross-border handling actually bites
CDJapan sells to fans abroad, and it says it is also submitting reports to overseas data protection authorities, including those in the EU and the UK. PrivacyAffairs says it has asked how many affected customers live there and had no answer at the time of writing.
This is the part of the case that touches the data-localisation debate. Article 28 of the APPI governs provision of personal data to third parties in foreign countries. It does so through consent, with exceptions for recipients that have a system meeting PPC standards or that sit in a country the Commission designates as equivalent. That is a conditional-transfer regime, not a localisation mandate. Nothing in it requires data to stay in Japan. The PPC's English legal index also lists supplementary rules for data transferred from the EU and UK under an adequacy decision, which shows how Japan has built its framework around interoperability rather than borders.
The CDJapan facts show why that design is sound. The data was stolen from a Japanese-hosted shop through a web vulnerability and a checkout script. Where the servers sat made no difference. A rule requiring foreign customers' data to be stored in Japan, or Japanese customers' data to stay onshore, would not have stopped either attack. Localisation mandates tend to concentrate data in fewer, more attractive targets and raise compliance costs most for small exporters, the kind of niche retailer that serves global fandoms.
What regulators should do instead
The real gaps are operational. First, the skimming code ran for a week on a payment page, which points to script and page integrity monitoring as the control that matters. Second, the database held card records from 2005–2018, which is a retention problem. CDJapan says it will permanently delete them, but regulators should ask why they were kept at all. Third, a single incident now triggers parallel reporting in Japan, the EU and the UK, so the useful reform is mutual recognition of one incident filing rather than three separate clocks.
The PPC can pursue all three through guidance and supervision of this case without new statutory powers. A proportionate approach would press for retention limits and checkout-script controls, check that the second report is complete, and coordinate with its EU and UK counterparts. It would not treat the incident as grounds to restrict where data is stored.
The takeaway
CDJapan's breach grew from 285 cards to hundreds of thousands of records in five days. That is a story about detection, retention and disclosure discipline. Japan's APPI already has a workable reporting duty and a conditional, non-localising transfer regime. Regulators should use the first and leave the second alone.