---
title: "KARTE breach leaked customer data from 570 companies, 6.5m at MUFG Bank"
summary: "What Plaid, MUFG Bank and 12 other clients disclosed from 13 to 20 November: what one marketing platform held, what left, data kept after contracts ended, and a January restart."
url: https://www.thetechbag.com/blog/karte-breach-570-companies-mufg-6-5m-customers
format: Analysis
desk: "Security"
area: "Risk & compliance"
region: Global
published: 2026-11-21
facts_checked: 2026-11-21
author: TechBag (The TechBag Journal)
tags: ["KARTE data breach","Plaid KARTE unauthorized access","MUFG Bank data leak","JINS data breach","DHC data leak","ZOZO data breach","SMBC data leak","Plaid stock","Plaid","KARTE","Japan data breach","customer data platform","marketing platform","third-party risk","supplier breach","data deletion","API keys","Shimamura","Marui","Epos Card","CAMPFIRE","WealthNavi","Personal Information Protection Commission","TDnet","DPDP","data processor","CERT-In"]
cover: https://www.thetechbag.com/blog/covers/karte-breach-570-companies-mufg-6-5m-customers.png
---

# KARTE breach leaked customer data from 570 companies, 6.5m at MUFG Bank

*What Plaid, MUFG Bank and 12 other clients disclosed from 13 to 20 November: what one marketing platform held, what left, data kept after contracts ended, and a January restart.*

Analysis · Security · Risk & compliance · By TechBag · Published 2026-11-21 · Facts checked 2026-11-21 · Canonical: https://www.thetechbag.com/blog/karte-breach-570-companies-mufg-6-5m-customers

The short version

1. An attacker read data out of KARTE, the customer-experience platform of Tokyo-listed Plaid, on 13 November. Plaid counts part of the customer data linked to KARTE by 570 companies, analytics data of 487, cache data of up to 409, and the keys connecting KARTE to other services at 754. The counts overlap and do not add. KARTE has been off since 13 November; a phased restart is targeted for mid-January 2027.[3][4]
2. Each client counts its own loss: DHC about 19.11 million records, JINS up to about 18.29 million accounts, ZOZO about 15.18 million ZOZOTOWN customers, SMBC up to about 14 million, MUFG Bank about 6.5 million customers’ gender, age and region. What left was what each company had sent: at MUFG, SMBC and WealthNavi it included no names or contact details.[9][10][11][12][13]
3. Plaid says some of the data belonged to former clients and should have been deleted under its own terms. It has cut its revenue forecast for the 15 months to December by 11.1% to ¥18.5bn and now expects a ¥2.0bn net loss. Its shares closed Friday at ¥338, down 56.7% from 13 November.[4][5][22]

A bank that shows a customer the right notice in its app, or a retailer that emails a member about a sale, often does it through a platform it does not run. In Japan, hundreds of companies did it through one: KARTE. We read Plaid’s three notices, its two exchange filings of 20 November and the notices of 13 clients, in Japanese, to answer four questions: what KARTE held and why, what each client lost, how the attacker got in and what should not have been there, and what a company using such a platform can check.

## 570 companies' customer data, 754 companies' keys

Plaid says it finished its own investigation by 19 November and fixed the scope and the counts. The data entrusted to it by companies that leaked, or may have leaked, falls into four groups, and how much of each a company lost “differs by company”. The first group is the one KARTE’s clients chose to send: data a company holds about its own customers, such as membership records, linked into KARTE to be used there. That reached 570 companies. The widest group is the integration credentials, the keys and passwords that connect KARTE to other services such as email delivery: 754 companies. They contain no personal data.[4]

**Figure: Four kinds of client data left KARTE, each touching hundreds of companies**

*Companies affected by each category of data that leaked or may have leaked from KARTE, as Plaid counted them by 19 November 2026*

570

Customer data the companies linked into KARTE (member records and the like)

Plaid

487

Analytics data: end users' clicks and views, and data built from them

Plaid

409

Cache data with end-user identifiers, an estimated maximum

Plaid

754

Credentials connecting KARTE to other services; no personal data

Plaid

Source: Plaid, investigation results (TDnet and plaid.co.jp, 20 Nov 2026) · as of 20 November 2026 · A company can sit in several categories; Plaid says the counts do not add to a total

The analytics group is the record of what end users did on a company’s website or app, such as pages viewed and buttons clicked, and data created from it, such as a member’s rank: 487 companies. The cache group is the hardest to count. A cache is temporary data KARTE generates to process events in real time; it is overwritten within a short time, so the contents during the attack cannot be rebuilt, and no log shows which entries were read. Plaid therefore treats everything that may have been in the cache at the time as possibly leaked, up to 409 companies.[3][4]

ReportedPlaid's own lists, counted separately

Plaid also lost data it held for itself: 79,249 email addresses registered as KARTE logins (including its Wicle service), confirmed on 16 November, and 45,816 contacts from its sales and customer-support work, with names and email addresses, confirmed on 20 November.[2][4]

Plaid’s footnote matters: “Some companies fall into more than one category, so the sum of the companies in each category does not match the total number of companies affected.” It gives no total. Some Japanese coverage has added the four to a cumulative “2,200 companies”; that counts category entries, not companies.[4][23]

## What KARTE does, and why one breach reached so many

Plaid describes KARTE, launched in March 2015, as a service that lets a company understand each end user’s situation and respond to it across its website, app and email, the way a shop assistant reacts to a customer at the counter. Its examples: a travel company sending pre-departure guidance matched to a booking, or a retailer pointing an app user to a nearby store that has the item in stock. To do that, KARTE processes behaviour data as it happens and, depending on each client’s settings, links in the client’s own member data. So it holds both what companies entrust to it and what it records and generates from their users’ behaviour.[3][4]

**Figure: KARTE held four kinds of client data, and each was a separate way to lose it**

*How customer data reaches a platform such as KARTE, with the companies Plaid counts in each category, November 2026*

1. 01A tag on the siteKARTE records what each visitor views and clicks on the client’s website or app, and builds data from it, such as a member’s rank. Analytics data: 487 companies.
2. 02Member data linked inThe client uploads fields it chooses from its own customer records, through KARTE’s “linking table” and similar features. Linked data: 570 companies.
3. 03A real-time cacheTo answer fast, KARTE keeps short-lived working data carrying end-user identifiers. Nobody can tell which entries were read. Cache data: up to 409 companies.
4. 04Keys to other servicesSecret keys and access tokens let KARTE drive email delivery and other tools on the client’s behalf. Credentials: 754 companies.

Source: Plaid, notices of 16 and 20 Nov 2026 · as of 20 November 2026

The scale sits in Plaid’s own results. On 12 November, the day before the attack, it reported that KARTE analysed the behaviour of more than 1.2 billion monthly active users in September, summed across every site and app running it, so it is not a count of people. Revenue in the twelve months to September was ¥16.41bn, up 22.5%.[6][7] The clients’ notices show what they used it for: MUFG Bank for guidance to customers on its website and apps, SMBC for displaying and sending notices in its website and app, JINS for newsletters, Shimamura for email and LINE messages, WealthNavi for pop-up notices in its app.[9][11][13][15][20]

## Each client's count is its own, and so is what left

Plaid names no clients; the clients named themselves. From 16 November dozens of companies published notices, from banks and a newspaper to retailers, a crowdfunding site and a mobile operator. Their counts use different units. DHC counts records (件), JINS counts registered accounts as a maximum, ZOZO and WealthNavi count people, and GDO says its 6,974,506 includes duplicates.[10][11][12][16][20]

**Figure: Nine clients each report more than 5 million customer records lost through KARTE**

*Largest count in each client's own notice, millions, published 17 to 20 November 2026; units differ by company*

DHC

records

19.11 m

JINS

up to, accounts

18.29 m

ZOZO (ZOZOTOWN)

people

15.18 m

SMBC

up to

14 m

Marui

records

8.83 m

Shimamura

members

7 m

GDO

up to, with duplicates

6.97 m

MUFG Bank

records

6.5 m

CAMPFIRE

records

5.82 m

Canon Marketing Japan

may have leaked

3.66 m

Optage (mineo)

up to

1.42 m

WealthNavi

people

0.91 m

|  | Value (m) |
| --- | --- |
| DHC | 19.11 |
| JINS | 18.29 |
| ZOZO (ZOZOTOWN) | 15.18 |
| SMBC | 14 |
| Marui | 8.83 |
| Shimamura | 7 |
| GDO | 6.97 |
| MUFG Bank | 6.5 |
| CAMPFIRE | 5.82 |
| Canon Marketing Japan | 3.66 |
| Optage (mineo) | 1.42 |
| WealthNavi | 0.91 |

| Company (notice) | Count, as stated | What left | Not in it, as stated |
| --- | --- | --- | --- |
| DHC (18 Nov) | About 19.11m records | Name, email, date of birth, age, gender, member ID, newsletter settings | Card data, shop password |
| JINS (17 Nov) | About 18.29m accounts, all registered; a maximum | Member ID, email, surname, date of birth, age, gender, postcode, prefecture | Passwords, card data |
| ZOZO (20 Nov) | ZOZOTOWN about 15.18m people, incl. former members; WEAR about 13.93m | Member ID, age, gender, postcode; for about 47,000 also display name, email, phone | Passwords |
| SMBC (20 Nov) | Up to about 14m | Date of birth, age band, gender, whether a phone is registered, notice flags | Name, contact details, account numbers, PINs, logins |
| Marui Group (20 Nov) | Marui about 8.83m; Epos Card about 8.5m | Marui: name, gender, date of birth, email. Epos: customer number, gender; about 60,000 may include name, age, income, cash-advance limit | Card numbers, PINs |
| Shimamura (17 Nov) | About 7m members; about 50,000 family entries | Date of birth, gender, prefecture, postcode; children's birth year and month | Name, phone, full address, card data (never in KARTE) |
| GDO (17 Nov) | Up to 6,974,506, incl. duplicates | Identifier, birthday or birth month, age group, postcode, mail preferences | Name, email, phone, payment data |
| MUFG Bank (18 Nov) | About 6.5m | Gender, age, region (prefecture or major city) | Anything that identifies or contacts a customer |
| CAMPFIRE (18 Nov) | 5,819,779 | Email address, hashed user ID | Name, address, phone, password, card and account data (never sent) |
| Canon Marketing Japan (20 Nov) | About 3.66m, may have leaked | Member ID, prefecture, city, postcode, age, date of birth, gender, newsletter status | Name, phone, email, card data |
| Optage, mineo (18 Nov) | Up to 1.42m | Email, gender, age group, postcode, prefecture, birthday or anniversary, option start dates | Payment data, ID documents, logins (never sent) |
| WealthNavi (18 Nov) | About 910,000 people | Customer code, birth year and month, prefecture | Name, address, email, phone, ID images, logins (never sent) |

Source: Each company's own notice (sources 9 to 20) · as of 20 November 2026 · Not additive: one person can be a customer of several clients; labels as each company gives them

TechBag countTwelve notices, no total

The twelve are the largest counts among the client notices we opened; Nikkei, which says email addresses, phone numbers, gender and birth month “may have leaked” in a form that cannot be turned back into the original, gives no count. We do not add the twelve: the units differ, several are maximums, and one person can shop at JINS, ZOZO and DHC.[21]

The column that decides how much harm a leak can do is the third. MUFG Bank’s 6.5 million records are gender, age and region, which it says “do not include information that lets a third party identify a customer or contact them”. SMBC’s cannot be tied to names; WealthNavi sent only a customer code, birth month and prefecture; Nikkei and CAMPFIRE hashed what they sent. DHC and Marui sent names and email addresses, and those left with the rest.[9][10][13][14][17][20][21]

## How the attacker got in, and data that should have been gone

Plaid has described the entry twice. On 16 November: in the early hours of 13 November a third party exploited a vulnerability in its servers to steal credentials for connecting to its systems and databases, read data out of them, and used the stolen credentials to take over Plaid’s own accounts and reach KARTE’s management screens. On 20 November, more precisely: the attacker tried several routes intermittently, and finally exploited a flaw in the internal processing of part of a public route used to retrieve data. Plaid detected the access at 08:59, began shutting servers down at about 14:27 and had cut off the attacker’s traffic and revoked the stolen credentials by about 15:23. It has seen no new access since. It names no attacker, and neither do we.[2][4]

**Figure: Clients learned their data had left two days after the shutdown; Plaid's counts came a week after it**

*Steps in the KARTE breach from Plaid's and its clients' notices, Japan time, 13 to 24 November 2026*

| Date | Event | Detail |
| --- | --- | --- |
| 13 Nov 2026 | Intrusion found; KARTE shut down | Detected 08:59; servers stopped from about 14:27; contained by about 15:23 |
| 14 Nov 2026 | WealthNavi cuts its link | Data link stopped, KARTE credentials revoked; DHC, ZOZO and GDO say they acted on the 13th |
| 15 Nov 2026 | Clients told data left | JINS, ZOZO, GDO and Nikkei say Plaid reported it that day |
| 16 Nov 2026 | Plaid confirms a leak | 79,249 login emails, integration keys, linked customer data; no counts yet |
| 17 Nov 2026 | Clients publish | JINS up to about 18.29m accounts; Shimamura about 7m; GDO |
| 18 Nov 2026 | MUFG Bank: about 6.5m | DHC: about 19.11m records |
| 20 Nov 2026 | Plaid: 570, 487, 409, 754 | Former clients' data included; restart mid-January; forecast cut |
| 24 Nov 2026 | Detailed data to clients | Plaid's planned start of company-by-company files |

Source: Plaid, notices of 13, 16 and 20 Nov; JINS, ZOZO, GDO, WealthNavi, MUFG Bank, DHC notices · as of 20 November 2026

The 20 November notice also corrected the 16 November one. That had called the affected companies “client companies”; in fact they include companies whose contracts had ended in whole or in part.[4]

> Under our terms of use, this information should have been deleted once the contract or use ended, but it was kept because of failings in human operations and in our management system.Plaid, TDnet filing of 20 November 2026 (our translation)

Plaid has not deleted that data yet: it says the records must be preserved for the forensic investigation by an outside body that will precede the restart, and that it will delete them when that investigation ends. It has not said how many of the 570 companies were former clients, or how long their data had stayed. It warns that its contact details for former clients may be out of date and asks them to write to a dedicated address.[4]

The keys are the other open risk. Plaid asked every client using KARTE’s integrations to revoke the credentials, warning that otherwise an attacker could reach the connected services and cause “unintended writing or leaking of data” there. Plaid gives no count of keys, only of companies: 754.[2][4]

## A January restart, fees waived, a ¥2.6bn swing to loss

Plaid has decided that blocking the route in is not enough: it says KARTE needs a rebuild of its system structure to stay hardened over the longer term, with verification by a third party, and has set mid-January 2027 as the target for a phased restart. It will not charge for November or for the rest of the shutdown. Its measures to prevent a repeat, including deletion after contracts end, will follow the investigation.[3][4] Some clients have set their own terms: Optage says it will not use KARTE again until it has confirmed its safety, and WealthNavi says it will review what it links before any restart.[19][20]

The same afternoon Plaid cut its forecast for the 15 months to 31 December 2026, a longer year while it moves its year-end from September. Revenue: ¥18.5bn, down from ¥20.8bn. Operating result: a ¥900m loss instead of a ¥1.6bn profit. Net result: a ¥2.0bn loss instead of a ¥600m profit, a swing of ¥2.6bn. It gives the waived fees as the reason.[5]

**Figure: Plaid's shares fell 56.7% in the five trading days after the breach**

*Plaid (TSE Growth, 4165) daily closing price, yen, 2 to 20 November 2026*

|  | Plaid |
| --- | --- |
| 2 Nov | 733 |
| 4 Nov | 721 |
| 5 Nov | 718 |
| 6 Nov | 681 |
| 9 Nov | 718 |
| 10 Nov | 760 |
| 11 Nov | 738 |
| 12 Nov | 741 |
| 13 Nov | 781 |
| 16 Nov | 649 |
| 17 Nov | 549 |
| 18 Nov | 449 |
| 19 Nov | 389 |
| 20 Nov | 338 |

Source: Kabutan daily prices (TSE data); Plaid notices · as of 20 November 2026 (Friday's close) · Plaid's first exchange notice came at 17:00 on 13 November, after the close

Plaid closed Friday at ¥338, down 13.1% on the day, on 14.43 million shares traded against 1.22 million on 13 November; Kabutan puts its market value at ¥14.0bn.[22]

TechBag countWhat the forecast implies for October to December

Plaid booked ¥16.41bn of revenue in the twelve months to September. The old forecast left about ¥4.39bn for the last three months of the 15-month year; the new one leaves about ¥2.09bn. The subtraction is ours.[5][6]

Our viewWhat a company using a marketing-data platform can check

Deletion on exit: ask for written confirmation that your data is erased when a contract ends, and check it, since Plaid’s terms required deletion and data stayed anyway. Your own exits too: ZOZO’s count includes members who had left. What you send: the clients that sent age bands or hashed IDs lost exactly that. Keys: know every credential the platform holds for your other services, scope it to what the platform needs, and be ready to revoke it the day the platform goes dark, as WealthNavi did within a day. And ask how the platform would tell you what left: KARTE’s cache could not be reconstructed.[4][12][20]

Three things to watch: the company files Plaid starts sending on 24 November, and the notices they will prompt; whether the mid-January restart holds; and how many of the 570 were former clients. The same shape of breach ran through [ARARA’s mailing service and its 380 clients](https://www.thetechbag.com/blog/arara-81-million-email-addresses-380-clients-japan), through [one booking system and ten airlines](https://www.thetechbag.com/blog/amadeus-breach-airlines-one-supplier), and through the [vendor breaches at Chase, Visa and Mastercard](https://www.thetechbag.com/blog/chase-visa-mastercard-vendor-breaches-one-week).

In India, the company answers for its processor, and deletion is its duty

None of the notices we read names an Indian company or Indian users. The case still maps onto Indian law. The Digital Personal Data Protection Act, 2023 makes a company responsible for processing done on its behalf by a data processor (section 8(1)), requires it to protect data its processor holds and to report a breach to the Data Protection Board and each affected person (sections 8(5) and 8(6)), and requires it to erase data once the purpose is served and to “cause its Data Processor to erase” it too (section 8(7)). Plaid’s admission concerns exactly that step: data kept after contracts ended.[24]

Those duties, and the Rules’ breach-reporting rule (Rule 7), apply from 13 May 2027.[25] Today, CERT-In’s Directions of 28 April 2022 already require a body corporate to report a data breach or data leak within six hours of noticing it.[26] For an Indian company with a customer-data or marketing platform, the questions in section 5 belong in the contract now. The [data security posture management guide](https://www.thetechbag.com/browse/data-security-privacy/dspm) covers tools that find where copies of customer data sit, and [third-party management tools](https://www.thetechbag.com/onetrust/onetrust-third-party-management) keep the register of which supplier holds what.

How we did this

Figures as of 21 November 2026, 9pm IST

Every count is from the company that published it: Plaid’s notices of 13, 16 and 20 November, its TDnet filings of 20 November and its results of 12 November; each client’s own notice. All were read in Japanese; quotations and labels are our translations. Dates and times are Japan time. The client table shows the largest counts among the notices we opened, with each company’s own unit and qualifier; Francfranc’s notice could not be opened and is left out, and Shimamura’s PDF was read through a text reader after a direct request was refused. ZOZO’s bar shows its ZOZOTOWN figure only. Plaid’s four category counts are not added, as Plaid says they must not be; the “2,200” figure is isotop’s cumulative sum, cited only to show why.

TechBag arithmetic: the 56.7% fall from ¥781 (13 November) to ¥338 (20 November), from Kabutan’s daily table, which is not the exchange’s own; the implied October to December revenue (¥20.8bn and ¥18.5bn less the ¥16.41bn reported for October 2025 to September 2026). The ¥2.6bn swing is the filing’s own figure. KARTE’s 1.2 billion monthly active users is Plaid’s sum across sites, not a count of people. No attribution of the intrusion has been published, and none is made here. Nothing published after 9pm IST on 21 November is included.

Spotted an error? Write to us; corrections are published at the foot of the piece.

Sources

1. [Plaid: report on unauthorised access to our service (Japanese)](https://plaid.co.jp/news/20261113/) — 13 November 2026 Last updated 20 November 2026.
2. [Plaid: apology and notice on the leak of information possibly including personal data through unauthorised access (Japanese)](https://plaid.co.jp/news/20261116/) — 16 November 2026
3. [Plaid: results of our investigation into the unauthorised access to KARTE, and the outlook for restarting the service (Japanese)](https://plaid.co.jp/news/20261120/) — 20 November 2026
4. [Plaid: investigation results on the unauthorised access to KARTE and the outlook for restart (TDnet, Japanese)](https://www.release.tdnet.info/inbs/140120261119583758.pdf) — 20 November 2026
5. [Plaid: notice of revision to the earnings forecast for the period to December 2026 (TDnet, Japanese)](https://www.release.tdnet.info/inbs/140120261119583763.pdf) — 20 November 2026
6. [Plaid: summary of consolidated results, fourth quarter of the period to December 2026 (Japanese)](https://pdf.irpocket.com/C4165/xoA3/Laiu/F82z/qmxl.pdf) — 12 November 2026
7. [Plaid: results presentation, fourth quarter of the period to December 2026 (Japanese)](https://pdf.irpocket.com/C4165/xoA3/Laiu/CcGy/ztS4.pdf) — 12 November 2026
8. [Plaid: progress updates on the unauthorised access (Japanese)](https://plaid.co.jp/notice/202611191100/) — 17 to 19 November 2026
9. [MUFG Bank: unauthorised access to a service provided by our contractor (Japanese)](https://www.bk.mufg.jp/news/news2026/pdf/news1118.pdf) — 18 November 2026
10. [DHC: apology and notice on the leak of customer information through unauthorised access to KARTE (Japanese)](https://dhc-corporate.co.jp/cms_dH8vjpRq/wp-content/uploads/2026/11/2d7a589cb5008fbc262624582782444f.pdf) — 18 November 2026
11. [JINS Holdings: personal data leak through unauthorised access at a subsidiary's contractor (TDnet, Japanese)](https://www.release.tdnet.info/inbs/140120261117582109.pdf) — 17 November 2026
12. [ZOZO: unauthorised access to the external service KARTE used by the company (Japanese)](https://corp.zozo.com/information/20261120-482917/) — 20 November 2026
13. [Sumitomo Mitsui Banking Corporation: information leak through unauthorised access at a contractor (Japanese)](https://www.smbc.co.jp/news/pdf/j20261120_01.pdf) — 20 November 2026
14. [Marui Group: partial leak of customers' personal data through unauthorised access to KARTE (Japanese)](https://www.0101maruigroup.co.jp/nr/26_1120_1) — 20 November 2026
15. [Shimamura: leak of some member information through unauthorised access to KARTE, first report (Japanese)](https://www.shimamura.gr.jp/assets-c/uploads/release20261117_Informationleak.pdf) — 17 November 2026
16. [Golf Digest Online: leak of customer information through unauthorised access to KARTE (Japanese)](https://company.golfdigest.co.jp/corp/pr/2026111701.html) — 17 November 2026
17. [CAMPFIRE: unauthorised access to the KARTE mail system, second report (Japanese)](https://campfire.co.jp/press/2026/11/18/campfire/) — 18 November 2026
18. [Canon Marketing Japan: unauthorised access to a service provided by our contractor (Japanese)](https://corporate.jp.canon/info/2026/20261120) — 20 November 2026
19. [Optage: customer information leak following unauthorised access at Plaid (Japanese)](https://optage.co.jp/press/2026/press_15.html) — 18 November 2026
20. [WealthNavi: unauthorised access at our contractor (Japanese)](https://corp.wealthnavi.com/news/info/861) — 18 November 2026
21. [Nikkei Inc.: possible leak of personal data through unauthorised access to a contractor's external service (Japanese)](https://www.nikkei.co.jp/nikkeiinfo/news/information/1574.html) — 17 November 2026
22. [Kabutan: Plaid (4165) daily share prices and market value (Japanese; TSE data)](https://kabutan.jp/stock/kabuka?code=4165) — read 21 November 2026 Closes to Friday 20 November.
23. [isotop news: Plaid's information leak reaches a cumulative 2,200 companies (Japanese)](https://news.isotop.jp/archives/10769) — 21 November 2026
24. [Digital Personal Data Protection Act, 2023, sections 8(1), 8(5), 8(6), 8(7)](https://www.meity.gov.in/static/uploads/2024/06/2bf1f0e9f04e6fb4f8fef35e82c42aa5.pdf) — 11 August 2023
25. [MeitY, Digital Personal Data Protection Act, 2023 and DPDP Rules, 2025 (notified 13 November 2025; Rule 7 from 13 May 2027)](https://www.meity.gov.in/data-protection-framework) — 13 November 2025
26. [CERT-In, Directions under section 70B(6) of the IT Act (six-hour reporting; Annexure I items xi and xii, Data Breach and Data Leak)](https://www.cert-in.org.in/PDF/CERT-In_Directions_70B_28.04.2022.pdf) — 28 April 2022

**Disclosure.** TechBag is a software reseller: it earns when companies buy through it, including from vendors named here. The analysis is TechBag’s own; no vendor paid for or saw this piece before publication. Facts are labelled reported, TechBag count or our view.

**Read this next:** [Japan’s listed firms leaked 350m records in ten months, over 10 times last year](https://www.thetechbag.com/blog/japan-listed-companies-350m-records-leaked-10x) — Japan’s wider count: listed firms leaked 350m records in the ten months to October, over 10 times last year, in 215 incidents.

Go deeper on TechBag

- [OneTrust Third-Party Management](https://www.thetechbag.com/onetrust/onetrust-third-party-management) — a register of which supplier holds which customer data, and what it must delete
- [Data security posture management guide](https://www.thetechbag.com/browse/data-security-privacy/dspm) — tools that find where copies of customer data sit, including at suppliers
- [Privileged access management guide](https://www.thetechbag.com/browse/identity-access/privileged-access-management) — controls on the service credentials and keys a platform holds
