By NOW IN QUESTION EditorialSourcing & correctionsReport an error
Rakuten Securities Data Leak: What Does an Explanation Owe Customers?
Separating account counts, an investigation and the ability to get help
Japanese-language X discussion on November 20 called for answers about Rakuten Securities’ data leak. The reported account totals cover different kinds of information. What must a company explain so that customers can make decisions while an investigation continues?
What customers were asking on November 20
J-CAST’s November 20 report, published at 19:15 JST, described calls for a press conference and Japanese X posts saying the telephone support line was difficult to reach. The company told the outlet it was considering how to report once it could present investigation results.
That establishes a documented request for explanation. It does not establish the views of all customers, nationwide X rankings or total post counts. Nor does it establish a scheduled press conference.
Why 4.47 million and 15.72 million are different figures
The company’s November 17 notice distinguishes two groups. ITmedia’s November 20 reporting also separates their information.
| Maximum affected accounts | Information potentially taken |
|---|---|
| Approximately 4.47 million | Customer identifiers plus names, addresses, employers, withdrawal accounts, declared income and financial assets, among other fields |
| Approximately 11.25 million | Branch/customer codes and login IDs |
| Approximately 15.72 million combined in November 20 reporting | The two categories together, not financial-asset information for every account |
These are account counts; they should not automatically be presented as a count of distinct people. The November 17 notice said the company had not confirmed a leak of transaction passwords or PINs, or unauthorized transactions attributable to this incident. That is a dated account of what it had confirmed, not a guarantee against future misuse.
An incident date is not a disclosure date
The company notice and ITmedia’s November 17 account distinguish occurrence, detection and disclosure.
| Date | Record |
|---|---|
| November 11 | Date of possible leakage from a test environment identified by the company |
| November 16 | Company says it detected possible unauthorized access and blocked/corrected the affected access |
| November 17 | Company disclosed the possible information leak |
| November 19 | Regulator issued a reporting demand, according to the following day’s ministerial briefing |
| November 20 | Ministerial explanation, independent coverage and reporting of Japanese X concerns |
The finance ministry’s November 20 briefing record describes a demand for facts, analysis of the cause and preventive measures. The briefing and the administrative action occurred on different days. A reporting demand is not a determination of damages or criminal responsibility.
The materials checked do not establish the full cause, every subsequent recipient of the information or the outcome of compensation and litigation. Recruiting potential participants for litigation is also different from filing a case or obtaining a judgment.
What readers can check now
The official notice and ITmedia’s November 17 account direct customers to phishing precautions, passkey settings and options to suspend transactions or withdrawals. Rather than acting through a link in an unexpected message, customers can independently open the official site and review the relevant instructions. Settings can affect how an account works, so their consequences should be read before making a change.
Publishing a checklist does not settle whether that guidance is usable. Affected-customer notifications, accessible support, dated updates and a working route for questions are separate parts of helping someone act.
Is a press conference enough?
The following is our editorial analysis. The case for a press conference is that questions and follow-up questions can expose gaps in a company’s prepared account. The company has less control over which anxieties receive attention than in a one-way announcement.
There is also a reason to avoid premature certainty. Presenting a provisional cause or count as settled can mislead customers and require corrections. Explaining uncertainty accurately is part of responsible communication.
Accepting both points leads to a further question: can the company distinguish what it knows, what it does not know, and what it will check next? An explanation is not only the delivery of a finished answer. It can also be an ongoing relationship in which another person can follow an uncertain situation.
Trust should leave room for questions
Customers cannot inspect an investigation or internal systems on the same terms as the company. Reassurance alone cannot remove that difference in access to information.
A useful explanation enables people to examine reasons, seek corrections and choose actions. Press conferences, update histories, individual notices and customer support perform different jobs. Completing one does not make the others unnecessary.
Some personal information cannot be changed as easily as a password. A company’s responsibility to explain should therefore extend beyond an apology on disclosure day to the conditions under which customers can continue making informed choices. Our Nitori data-leak article considers the related questions of authentic notices and lasting trust.
Sources and verification
Checked November 21, 2026, Japan time. We compared the November 17 company statement with the November 20 ministerial record and reporting. X attention is documented through J-CAST, not an independent count of posts. No leaked records or identifying customer material were obtained or reproduced.
- Rakuten Securities: possible customer information leak, November 17
- ITmedia NEWS: chronology and safety guidance, November 17
- Ministry of Finance: ministerial briefing, November 20
- ITmedia NEWS: regulatory response and customer protection, November 20, 16:29 JST
- J-CAST: calls for answers and Japanese X support complaints, November 20, 19:15 JST