Update, November 20 (evening): Two more cases this week show data outliving the contract it was collected for. PLAID said on November 20 that the data leaked from its KARTE platform includes that of companies whose contracts had ended, which its terms required it to delete but which it kept because of "deficiencies in human operations and management". The northern city of Rumoi in Hokkaido said on November 19 that resident register data from 2022, up to 71,002 records, and data on up to 4,503 people listed as needing support (要支援者), including disability categories and care levels, may have leaked from a development PC at its GIS contractor's partner company. The PC was infected with information-stealing malware in early November, and the data was still on it after the contract had ended. The same PC held data for two more Hokkaido municipalities: the town of Shintoku says resident register data on 6,001 people and 986 people needing support, handed over for a contract in fiscal 2019, was on it, and Iwamizawa says land and building tax data, without owners' names, was too. In our view, these are the vendor copies this article warned about. When a contract ends, deletion should be a condition of closing it: ask the vendor, and any company it passed the data to, to delete it, and get that in writing. A deletion that depends on someone remembering does not happen.
Key takeaways
- A month ago, Japanese companies hit by this year's breaches were promising to hold less personal data. In November they started deleting it.
- Monogatari, whose Yakiniku King app lost 10.79 million members' data, removed names, name readings and phone numbers from all 11 of its restaurant apps on November 16, months ahead of plan. The Yakiniku King app also dropped the day of members' birth dates. Existing data is being deleted from its member database.
- infoQ, a survey site breached in October, reopened on November 18 after deleting every member's name, phone number, address and bank account details.
- Two companies with no reported breach went further. The soba chain Yudetaro is ending its birthday club and will erase members' data. The doll maker Azone closed its own online shop and member programs, and now sells through Rakuten Ichiba.
- In our view, this is the most useful response to the breach wave we have seen. Two cautions apply. Deletion has to reach every copy of the data, and much of it is not disappearing but moving to platforms, where this month's KARTE breach showed the risk concentrates.
Who deleted what#
| Company | What changed | Breached? |
|---|---|---|
| Monogatari (Yakiniku King, Yuzuan, Marugen Ramen and others; 11 apps) | On November 16, removed names, name readings and phone numbers from registration, and the day of the birth date in the Yakiniku King app. Existing entries are being deleted from the apps and the company's member database. Email addresses are kept for now | Yes: Yakiniku King app, 10.79 million members, October |
| infoQ (GMO Research & AI) | On reopening on November 18, deleted all members' names, phone numbers, postcodes, addresses below the prefecture and bank account details; ended exchanges for Amazon gift codes | Yes: 894,082 members, October |
| Times Car (Park24) | Identity document images now deleted as soon as registration is checked; all stored images to be deleted by the end of October | Yes: images for about 1.6 million accounts, September |
| Yudetaro (soba chain) | Birthday club closed to new members; the last coupons go out for December birthdays, then members' data is deleted. The Nikkei reports about 4,000 members | No. It cites the run of leaks at other companies |
| Azone International (dolls) | Closed its online shop AZONET and ended its paid fan club and free member programs; members withdrawn and their data deleted; sales moved to its Rakuten Ichiba store | No breach stated. It cites the risk of cyberattacks |
The regulator is pushing in the same direction. On November 18, the Personal Information Protection Commission told rental car operators that they have no legal duty to keep images of customers' identity documents after checking them, and asked them to delete the images without delay.
From promises to deletions#
When we looked at this year's app breaches in October, the best we could report was a commitment. Monogatari had said its apps would stop holding names and phone numbers from the first half of 2027. It did it on November 16, and it is deleting what it already holds, not only collecting less from now on.
The details are as telling as the decision. A name and phone number had been collected so the store reservation system could confirm bookings. The day of the birth date is the part a birthday coupon does not need: the month is enough. These are fields that were collected because they could be, and that turned out to be removable without changing reservations, coupons or points, as the company's notices say.
infoQ went further than its breach required. Its attackers had taken names, addresses and phone numbers. On reopening, it deleted those fields for every member, along with bank account details, and it stopped offering the Amazon gift codes that the attackers had cashed out. A survey site needs a way to pay rewards and to reach members. It does not need their full address.
Companies that were not breached#
Yudetaro and Azone are the more striking cases, because neither reports a breach. Yudetaro's notice says plainly that no leak has occurred, and that it is ending the birthday club because of "the succession of personal data leaks at companies". Azone says it now treats not holding customers' personal data as its top priority.
Both made the same calculation: a member program has a value, and so does the risk of running it. For a soba chain with a birthday coupon, the value is small. For a doll maker selling to collectors, the online shop was more important, which is why Azone did not give up selling online. It moved to a marketplace.
Where the data goes#
That move is the part to watch. Yakiniku King and Yuzuan still take reservations through EPARK and ebica, where customers must still enter their names and phone numbers. Azone's customers will now buy through Rakuten Ichiba. The data does not disappear. It moves to platforms whose business is running such systems.
That is often the better place for it, as we argued in October: a reservation or shopping platform can defend a member database at a scale a restaurant chain cannot. But this month showed the other side. KARTE, a customer platform used by many Japanese retailers, was breached, and seven of its clients, including DHC with 19.11 million records and JINS with 18.29 million, are now on our list of the year's largest breaches. One breached platform reaches every company that moved its data there.
Our view#
This is the most useful response to the breach wave so far. Every other measure, patching, monitoring, new teams, makes a breach less likely. Deleting data limits what any breach can take, however good or bad the defenses are. A name that is not stored cannot be leaked, and an ID image that was deleted after the check cannot be used for fraud years later. It is also the measure that respects customers most directly: they gave the data for a purpose, and the purpose did not need it.
Deletion has to reach every copy. Removing a field from an app's database is the visible part. The same data also sits in backups, logs, analysis copies, test environments and vendors' systems, and this month Rakuten Securities lost data from exactly such a copy. A deletion notice should say what it covers: the live database only, or backups and copies too, and by when. None of the notices we read says that.
Moving data to a platform moves the risk, not removes it. Using EPARK or Rakuten Ichiba is a reasonable choice for a company that cannot defend its own member system. But it should be a deliberate choice, with the questions we listed in October: what the platform holds, how it is protected, and how quickly it will report an incident. KARTE's clients learned of their breach from the platform, and several have published only first reports.
The companies that acted without a breach deserve the most credit. Yudetaro and Azone gave up something their customers liked, and Azone is compensating its members to do it. In our view, more companies should ask the same question before attackers ask it for them: which data, and which programs, are worth the risk of holding.
What this means for practitioners#
- List the fields you hold and why. For each, ask whether the service works without it. Monogatari found that reservations, coupons and points did.
- Delete, do not just stop collecting. Plan the deletion of existing data, and include backups, logs, analytics and test copies, and vendors.
- Prefer partial data where it is enough: a birth month instead of a full date, a prefecture instead of an address.
- If you move to a platform, review it as a supplier: what it stores, its security, and its incident reporting.
- Check the regulator's line on images. The PPC's November 18 alert says there is no duty to keep identity document images after the check, at least for rental cars. Keeping them is a choice.
What this means for readers#
- Check what your apps still ask for. If an app asks for more than it needs, consider leaving the field blank where you can, or not using the program.
- When a company ends a member program, use your points or vouchers before the deadline. Azone and infoQ have set deadlines and conditions.
Japanese terms at a glance#
| Japanese | Reading | Meaning |
|---|---|---|
| 会員登録項目の見直し | kaiin tōroku kōmoku no minaoshi | Review of membership registration fields |
| 個人情報非保持化 | kojin jōhō hi-hoji-ka | Moving to not holding personal data |
| 退会(お客様情報を削除) | taikai (okyakusama jōhō o sakujo) | Withdrawal (customer data deleted) |
| 生年月日の日付 | seinengappi no hizuke | The day of the birth date |
| 本人確認書類の画像 | honnin kakunin shorui no gazō | Image of an identity document |
| 予約・順番受付サイト | yoyaku / junban uketsuke saito | Reservation and queue booking site |