Mergers and Acquisitions in Indonesia: Joint Liability for Personal Data Starts at Signing
November 13, 2026 · 5 min read · Etzal Group Team
Indonesia's Government Regulation Number 33 of 2026 (Peraturan Pemerintah, or PP 33/2026) on personal data protection takes effect on 16 January 2027, and one of its provisions reaches directly into corporate transactions. According to a summary by the law firm DFDL, the parties to a transaction that has been signed but not yet completed are treated as joint controllers, jointly and severally liable from the moment of signing.
For a finance director or head of IT, that changes how the period between signing and closing should be read. It is usually treated as a waiting period. If DFDL's reading is right, then for personal data it is already a period of shared responsibility.
We should say this plainly at the start: the evidence is thin. We found the corporate transaction provisions described in detail in only one source, and that source is a law-firm summary, not the official text. Treat this article as a list of questions for your transaction advisers, not as a legal conclusion.
What the sources report
- DFDL (page updated 28 September 2026): under Articles 11, 12 and 63, parties to a signed but uncompleted transaction are treated as joint controllers with joint and several liability from signing.
- Veritask (3 September 2026): joint controllers must have a written agreement setting out roles, responsibilities, their interrelated purposes, the jointly determined means of processing, and a joint contact point. They are jointly and severally liable. Veritask cites Articles 10 to 12.
- Allen & Gledhill (23 October 2026): PP 33, enacted on 16 July 2026 and effective 16 January 2027, covers corporate restructuring and data breach response among other areas.
- DFDL: for data not obtained directly from the data subject, notice must be given within 30 working days of collection or acquisition (Article 64). Elsewhere, the same page says "30 days" without the word working. The two are not the same, and we cannot tell which is correct without the text of the article.
Joint and several liability means an injured party can pursue either party for the whole obligation, leaving the parties to settle the split between themselves.
Why this matters for deals closing in early 2027
A deal signed in late 2026 and closed after 16 January 2027 will cross the effective date while still incomplete. That is exactly the situation DFDL describes.
In practice, personal data in M&A tends to be handled last. Financial and tax due diligence finish first, while questions about who holds the target's customer data, in which system and on what basis only surface when system integration begins. Under this provision that order becomes expensive. A data incident at the target during the interim period could, on DFDL's reading, be the buyer's problem too.
Three periods, three questions
| Period | The data question to answer |
|---|---|
| Before signing | What personal data is disclosed in the data room, and to whom |
| Signing to closing | Who bears an incident, who is the contact point, what may be exchanged |
| After closing | When systems are merged, and whether data subjects must be notified |
What follows is our practical advice, not the wording of the rule.
Before signing: the data room
- Disclose aggregates, not individuals. Headcount by grade and salary bands are usually enough for valuation. A list of names with salaries and identity numbers is rarely needed at this stage.
- Redact what must be shown. Key customer contracts can be disclosed with individuals' names masked.
- Log who accessed what. Data room access logs are cheap evidence that becomes very useful if questions arise later.
- Ask the target for its processing inventory. If it has none, that is a due diligence finding in itself and a basis for negotiating warranties.
Between signing and closing
This is the period DFDL highlights. Put these questions to your transaction counsel before the agreement is final:
- Whether the sale and purchase agreement should be accompanied by a joint controller agreement containing the elements Veritask lists: roles, responsibilities, purposes, means of processing and a joint contact point.
- How outward joint liability is balanced inwardly. An indemnity between buyer and seller does not remove liability to third parties, but it decides who finally bears the cost.
- Who decides and reports if a data incident occurs at the target during this period, and how quickly the other side is told.
- Which data may already flow to the buyer for integration planning, and what must wait for closing.
On the IT side, the strongest temptation is to start migration early so that day one runs smoothly. The trade-off is clear. The earlier data moves, the smoother the integration, but the more data the buyer already holds if the deal falls through. A common middle path is to plan with schemas and masked sample data, then move the real data after closing.
After closing
- Map before you merge. Two CRMs holding the same customers do not automatically share a legal basis. Consent given to the target for one purpose may not cover the buyer's purposes.
- Settle the notice question. Because DFDL writes 30 working days in one place and 30 days in another, plan on the shorter figure until your counsel confirms the wording of Article 64.
- Close old access. Vendor and employee accounts at the target that are no longer needed are the most preventable source of incidents.
- Unify the incident procedure. From day one it must be clear who to call, whichever company the event occurs in.
What belongs in the deal budget
Finance leaders should add three lines that are often missed: personal data due diligence as a workstream of its own, the cost of masking data for integration planning, and a reserve for compliance remediation at the target after closing. All three are far cheaper to decide before the price is fixed.
If your transaction involves merging ERP, CRM or HR systems, Etzal Group's enterprise software team can help design a migration sequence that keeps real data where it is until the right moment.
This article is not legal advice. We read the corporate transaction provisions of PP 33/2026 from summaries, so confirm the wording and how it applies to your deal with legal counsel, and check the latest official announcements before you decide.
Sources
Frequently asked questions
When does a buyer become responsible for the target's personal data?
According to DFDL's summary of Articles 11, 12 and 63 of PP 33/2026, from signing, not from closing. Confirm that reading with your transaction counsel.
What must the parties have between them?
According to Veritask, joint controllers need a written agreement covering roles, responsibilities, purposes, the means of processing and a joint contact point.
Must data subjects be told after data changes hands?
DFDL says notice for indirectly obtained data is due within 30 working days under Article 64, but elsewhere on the same page it says 30 days. Check the article itself.
Related service
Free consultation
Not sure where to start? We will map the right system for your business, free.
