AboutServicesMediaInsightsInvestigation FAQContact📞 24H Hotline
0800-090-007
DATA GOVERNANCE · MERCHANT RISK

The platform has an incident. What can the merchant actually say?The 91APP inquiry and the limits of waiting for a vendor update

DATE 2026.10.20
UPDATED 2026.10.29
Relieved Xianyu Global Investigations Network

The data may sit on a vendor platform, but the customer will ask your brand what happened. When the vendor says it is still investigating, should a merchant wait for a final number or first establish which records it sent to the platform?

An unknown scope is not the same as no impact. That distinction should govern every internal memo and customer response.

What matters first

Establish the facts and gaps before deciding on investigation or legal action.

  • The regulator had not confirmed an affected-person count on 20 October.
  • Separate platform-held records from merchant-held records and shared workflows.
  • Preserve agreements, integrations, access logs and notification times.
  • Give customers a reliable verification channel without guessing the outcome.
  • Counsel and privacy specialists should assess legal notification duties.

1. News observation: keep the unknowns visible

On 20 October 2026, Taiwan’s Administration for Digital Industries said 91APP had announced unauthorised extraction from its Commerce Cloud database following an automated attack. An administrative inspection was under way. The types and number of affected records and people remained unconfirmed that day.

That statement does not establish that every merchant or customer was affected. It gives merchants a reason to request a verifiable scope and update schedule rather than fill gaps with rumours.

2. Outsourcing a platform does not outsource the questions

A brand should know what fields it shares, why, for how long and who may access them. Written responsibilities may be clear while the actual route of an order through membership, payment and delivery systems remains hard to reconstruct.

Trace one real order flow and document each transfer. That gives counsel and security staff a useful map for assessing whether any notice is required.

3. Four records to assemble

01
Inventory
List data fields and integration routes between the merchant and platform.
02
Preserve
Keep notices, backend logs, configuration versions and public statements.
03
Separate
Mark confirmed facts, open questions and vendor answers.
04
Coordinate
Give legal, security, support and the vendor a clear escalation path.

4. Customer trust needs dated, sourced answers

The regulator warned that consumers should verify supposed order, refund or account notices through their existing official website or app and avoid unknown links, passwords and codes. Merchants can use a single verified support route to reinforce that advice.

Do not claim zero risk while scope is unresolved. If notification is required, let the facts and applicable rules guide it; keep a dated record of each correction.

5. What Relieved Xianyu can do

Within an authorised scope, we can organise data-flow records, notice versions, a timeline and unresolved questions for counsel and security specialists.

We do not replace the regulator, promise complete attribution or make statutory notification decisions. Technical examination needs the appropriate access and qualified team.

6. Final reminder: the data may be elsewhere, but the trust is yours

A merchant need not wait for a vendor to declare the matter closed before identifying its own records and unanswered questions.

A credible answer can say what is known, what is not and when the next update will be available.

Frequently asked questions
How many people were affected?
+
The regulator had not confirmed the data categories, record count or affected-person count in its 20 October statement. Do not backfill this dated article with later reports. Merchants should request a documented scope, update schedule and notification plan.
What should a merchant do if the vendor holds the data?
+
Inventory the fields and integrations, preserve the vendor notice and relevant agreements, then have legal, security and privacy staff assess obligations. Vendor custody does not make the merchant’s customer relationship disappear, but it does not prove any party violated the law.
How should support handle fake refund messages?
+
Offer one verified route through the existing app or website. Ask customers not to follow unknown links or supply passwords or one-time codes. Record suspicious messages and escalation times; do not ask customers to reveal full sensitive details over an unsolicited call.
Can we say our customer records are safe?
+
Avoid absolute assurances while the scope is unresolved. Explain the systems checked, what remains to be verified and where a dated update will appear. Align all public statements so support, legal and the vendor do not contradict each other.
Should we shut down the whole store?
+
That depends on active access risk, alternatives and professional incident response. Assess what permissions can be limited and what services can continue safely before deciding. A headline alone is not enough to order a shutdown.
Can an investigator submit the legal breach notice?
+
A risk team can organise records and gaps, but the entity with the duty, deadline and required content must be identified with qualified legal advice. We cannot substitute for the regulator’s assessment or guarantee no later misuse.

Sources

CONFIDENTIAL CONTACT

Does a platform incident involve your brand?

Start with a redacted map of data flows, notices and unanswered questions before sharing sensitive records.

📞LINE contact iconWhatsApp contact icon