Skip to main content
Indotek Digital Nusantara

Enterprise IT

Fore Coffee Data Breach: What It Means for Indonesian Companies

Fore Coffee's operator says unauthorised access to a customer data platform may affect up to about 5.7 million accounts. Komdigi says it is examining the report and that no responsible party has been determined. What is known, where reports differ, and what other companies with customer apps can prepare.

Rows of black server racks with blue network cabling in an empty data centre room with a raised tile floor
Server racks in a data centre, photographed in 2015. The picture is illustrative and does not show any system connected with this incident. Photo: Carl Lender, CC BY 2.0 (opens in a new tab)

What happened in the Fore Coffee data breach, and what should other companies take from it? PT Fore Kopi Indonesia Tbk, which operates the coffee chain, said on 28 October 2026 that there had been unauthorised access to a platform it uses to manage customer data, potentially affecting up to about 5.7 million accounts. This week the Ministry of Communication and Digital Affairs (Komdigi) said it is examining the company's report and has not determined who is responsible. No finding of fault has been made. The case matters beyond one chain because many consumer apps hold the same kinds of data, and because it is unfolding ahead of 16 January 2027, when Government Regulation 33 of 2026 on personal data protection takes effect.

What Fore has said

The company's account comes from a written statement dated 28 October, reported by CNN Indonesia and others, and a stock exchange disclosure reported by CNBC Indonesia. We did not read the filing itself. Chief executive Vico Lomar apologised to affected customers and said that protecting their data is the company's responsibility.

  • Data possibly accessed, varying by customer: name, email address, phone number, date of birth, gender, address registered in the app, PIN in hashed form and in-app purchase history.
  • Data the company says was not affected: national ID numbers and ID card photos, which it says the app never requested or stored, and payment details, including card details.
  • Containment: the company says it stopped the access and secured the related systems within 24 hours of identifying the activity.
  • Remediation: security testing, fixing the weaknesses found, updating the platform to its latest version and adding safeguards.
  • Investigation: a cybersecurity consultant is carrying out a forensic review of the app, related platforms and other relevant IT systems. The latest reports we read say this is still under way.
  • Customers: those affected are being contacted directly and asked to change their Fore PIN, or create one, and to change the same PIN wherever else they use it.

The company said it had found no sign that the accessed data had been misused. That statement was made before the forensic work was finished.

Where reports differ, and what is not known

Several details are unsettled.

  • Scale: CNN Indonesia and CNBC Indonesia report about 5.7 million affected accounts, based on an initial investigation, while Medcom and Warta Ekonomi report up to about 5.7 million.
  • Payment data: CNN Indonesia and Medcom report that it sits on a separate platform; CNBC Indonesia reports that the company does not store it on its platform. Both accounts say it was not affected.
  • Two-factor authentication: reports say the app has applied it to logins from new devices, but not whether it was in place before the incident.
  • Timing: Literasi Hukum Indonesia reports that an internal investigation ran from 19 to 27 October, and says this is not the date of the access. We did not see that period in other reports.

None of the reports we read says when the access began, how it was gained, or names the platform. The cause is not publicly established.

What Komdigi has said

Muchtarul Huda, Komdigi's Director of Digital Space Supervision Strategy and Policy, confirmed in a statement to the media that Fore reported a suspected personal data protection failure on 28 October. Warta Ekonomi dates his response 4 November; CNBC Indonesia dates it 5 November. He said the ministry is analysing the report, and that administrative action or sanctions may follow if negligence or a breach of obligations is proven. Warta Ekonomi reports that the responsible party, whether the data controller or any third party involved, will be determined from the examination and each party's obligations.

CNBC Indonesia notes that the dedicated data protection authority does not yet exist. Both reports say the draft Presidential Regulation to create it is at its final stage and has gone to the President through the State Secretariat, and that Komdigi has set up a transition task force.

The notification rules behind the case

Article 46 of Law 27 of 2022 requires a data controller to give written notice to data subjects and the authority within 3 x 24 hours of a personal data protection failure. The notice must at least state which data was exposed, when and how, and what is being done to handle and recover from it. In certain cases the public must also be told.

The law firm SIP's summary of PP 33/2026, which we read in place of the regulation's full text, says the clock starts once a failure is established as certain, proper and reasonable from documents such as system logs and forensic reports. It adds that each failure must be recorded, including the affected data, chronology, impact, recovery steps and notification time, and that administrative fines can reach 2% of annual revenue. Because the reports do not say when the failure was established, we draw no conclusion about whether any deadline was met.

Why this matters for any customer app

On 14 October, Bondan Widiawan, BSSN's Deputy for Cyber Security and Cryptography Operations, told the GRACS 2026 event in Jakarta that the agency had recorded about 3.1 billion traffic anomalies through October, more than 85% of them linked to malware, according to Bisnis.com. The figure counts anomalies, and the report does not say how many became incidents. He also named unauthorised access and misconfiguration as continuing problems, and urged organisations to build security in from the planning stage.

Our analysis is that the data in this case is not unusual. A name, phone number, birth date, address and purchase history are what a loyalty app typically collects, and together they can make a fake message look genuine, a risk Medcom also points to. Medcom notes too that hashing a PIN reduces the risk without removing it.

What organisations can prepare

This section is our analysis, not legal advice, and it does not imply that any of these points caused this incident.

  • List every platform that holds customer data, including those run by vendors, and agree in writing who is responsible for what. Komdigi's reference to third parties makes this a practical question.
  • Ask whether each platform needs everything it keeps, such as full addresses, birth dates and years of purchase history.
  • Keep payment and identity data apart from marketing and loyalty data, and test that the separation holds.
  • Review administrator access and software versions on customer platforms, including tools bought as a service.
  • Check that your logs could show what was accessed, when and how, and rehearse producing a written notice from them within 3 x 24 hours.
  • Decide in advance how you will contact customers after an incident, and tell them now that you will never ask for a PIN or one-time code.

What to watch next

Watch for the forensic findings, which the company says it will share once material developments are verified. Watch how Komdigi divides responsibility between controller and any third party, which would be a useful signal for vendor contracts. And watch for the Presidential Regulation creating the data protection authority, and for how notification is handled once PP 33/2026 takes effect on 16 January 2027.

Sources

  1. Fore Lapor Data Pelanggan Bocor ke Komdigi, Begini Sanksinya · CNBC Indonesia(opens in a new tab)
  2. Fore Laporkan Dugaan Kebocoran Data, Komdigi Mulai Lakukan Pemeriksaan · Warta Ekonomi(opens in a new tab)
  3. Data 5,7 Juta Pelanggan Bocor, Fore Ngadu ke Komdigi · CNBC Indonesia(opens in a new tab)
  4. Data 5,7 Juta Pelanggan Bocor, Fore Langsung Investigasi · CNN Indonesia(opens in a new tab)
  5. 5,7 Juta Akun Fore Coffee Terdampak Kebocoran Data, Ini Tanggapan dan Solusinya · Medcom.id(opens in a new tab)
  6. Fore Coffee Akui Web Pengelola Pelanggannya Dibobol Hacker, 5,7 Juta Data Bocor · kumparan(opens in a new tab)
  7. Soal Kabar Kebocoran Data, FORE Pastikan Data 5,7 Juta Pelanggan Aman · Fortune IDN(opens in a new tab)
  8. Fore Coffee Konfirmasi Akses Tanpa Izin, hingga 5,7 Juta Akun Berpotensi Terdampak · Literasi Hukum Indonesia(opens in a new tab)
  9. UU No. 27 Tahun 2022, Pasal 46 · Pasal.id(opens in a new tab)
  10. PP 33/2026 Pelindungan Data Pribadi · SIP Law Firm(opens in a new tab)
  11. BSSN Catat Anomali Trafik 3,1 Miliar hingga Oktober 2026, Didominasi Malware · Bisnis.com(opens in a new tab)

This briefing was prepared by the Indotek editorial desk with AI assistance, from the public sources listed above. It is general information, not legal or professional advice.

Cloud & Data

How Indotek can help

The questions this case raises, such as where customer data sits, who can reach it and what the records can show, are partly questions of platform design. Working through them on a company's cloud and data platforms is the kind of work Indotek does.

  • Cloud architecture: we design landing zones, network and identity so that workloads are secure by default, with access, encryption and data-location requirements shaping the design from the start.
  • Data platforms: we build lakehouse and warehouse platforms with governed ingestion, lineage and clearly owned data products, so each customer dataset has a named owner and a known path.
  • Platform engineering: we set up infrastructure as code and observability, so that changes to a platform are recorded and its behaviour can be monitored as it scales.

Let's build what comes next

Whether you are modernising a legacy environment, building an AI-powered product or exploring a new digital business, let's create technology that delivers lasting value.