How do you work out how many customers a data breach affected?

By Alan Jeffries, Principal Consultant · Published · Covers the news of the week of 9 November 2026

On 12 November 2026 Sogo Hong Kong disclosed a leak of membership data, and the Privacy Commissioner estimated that about 820,000 members may be affected. That word “estimated” is where forensic work begins: the honest size of a breach depends almost entirely on what the logs can show.

In short

The number of people affected by a breach is worked out from evidence: database and application access logs, query records, exports and network traffic, matched against the records they touched. Where those logs are complete, an examiner can often narrow the affected group. Where they are missing or short, the honest answer may be every record the attacker could have reached. Keeping detailed logs for long enough, before anything happens, is what makes a precise answer possible.

What was reported

According to Dimsum Daily, Sogo Hong Kong disclosed a data leak on 12 November 2026; according to the PCPD’s preliminary information, abnormal data-read records were spotted on 5 November. The PCPD said it had received a notification, opened an investigation and estimated that about 820,000 members may be affected. The data reported as involved included membership numbers, names, phone numbers, email addresses and points balances; no payment card data was reported.

We have no knowledge of the incident beyond the public report, do not know what logs were available, and draw no conclusions about it. It is a useful example because it shows the usual first step: someone noticed unusual reads of data.

If you are a customer of any company that reports a leak like this, expect convincing scam calls and messages that quote your membership details, and call the company back on its official number before acting on any of them.

Why the first number is usually an estimate

When a breach is found, the safest early figure is often the size of the whole data set the attacker could have reached. That is not carelessness; it is caution. The figure can only come down when the evidence shows which records were actually read or copied.

  • Database and application logs can show, where this logging is enabled, which queries ran, by which account, and what they returned.
  • Export and API records show whether data was downloaded in bulk or pulled page by page.
  • Network and cloud logs show how much data left, where it went and when.
  • Account activity shows whether a legitimate login was misused, and from where.

If these records exist for the whole period of the incident, an examiner can often say with reasonable confidence which customers were affected. If they were never switched on, or were overwritten after a few days, nobody can, and the estimate has to stay wide.

What to set up before anything happens

  • Turn on access logging for databases and systems that hold customer data, not just for logins.
  • Keep logs for months, not days, and store copies where an attacker with admin access cannot delete them.
  • Record bulk exports and unusual query volumes, and alert on them.
  • Know which suppliers hold copies of your customer data and what logs they keep.

None of this prevents a breach. It decides whether, afterwards, you can tell customers with confidence which of them were affected, rather than having to warn everyone who might have been.

Notifying the PCPD and customers

As at November 2026, the Personal Data (Privacy) Ordinance does not impose a general legal duty to notify the PCPD of a data breach, although the PCPD encourages notification. Sector regulators, the critical infrastructure computer systems law (Cap. 653), contracts, insurance policies and overseas laws may impose their own duties. Take legal advice on your own position.

Whatever the legal position, customers who have been told their data may be out there should expect convincing scam calls and emails. Our article on scam calls that quote real order details explains what to tell them, and what a forensic investigation establishes covers the first steps after a breach.

Sources

Dimsum Daily, 12 Nov 2026: Sogo Hong Kong data leak

This article is general commentary on public reports, not legal advice and not a finding about any organisation named in those reports. Facts are as reported at the time of writing.

Frequently asked questions

How do you work out how many customers a data breach affected?

By examining database, application, export and network logs for the period of the incident and matching them to the records they touched. Where logs are complete, the affected group can often be narrowed; where they are missing, the honest answer may be every record that could have been reached.

Why do breach numbers change after they are first announced?

Early figures are usually the size of the data set an attacker could have reached. As the investigation examines logs and other evidence, the figure may be confirmed, reduced or, occasionally, increased.

What logs should a business keep to investigate a breach?

Access logs for databases and systems holding personal data, records of bulk exports and API use, sign-in records, and network or cloud traffic logs, kept for months rather than days and protected from deletion by anyone with administrator access.

Is notifying the PCPD of a data breach compulsory in Hong Kong?

As at November 2026, the Personal Data (Privacy) Ordinance does not impose a general legal duty to notify the PCPD of a data breach, although the PCPD encourages notification. Sector regulators, the critical infrastructure computer systems law (Cap. 653), contracts, insurance policies and overseas laws may impose their own duties. Take legal advice on your own position.

If a breach involved only names and phone numbers, is there any risk?

Yes. Names, phone numbers, emails and membership details are enough to make scam calls and messages convincing. Affected customers should treat unexpected contact that mentions their account with suspicion and call back on official numbers.

Can a forensic examiner say for certain that data was not copied?

Only as far as the evidence allows. An examiner can report that the logs reviewed show no sign of copying, but cannot prove a negative where logs are incomplete.

Talk to us before anything is changed.

A short, confidential call is usually enough to tell you what to preserve, what it will cost and whether a forensic examination is worthwhile. We take instructions from solicitors, companies and individuals in Hong Kong and across the Asia-Pacific region.

Telephone +852 5808 1071 · Signal or WhatsApp +852 9103 1852 · Email enquiries@d3forensics.com · Enquiry form