Website

Records of Processing Activities: The Data Inventory PP 33/2026 Requires and How to Build It

November 13, 2026 · 5 min read · Etzal Group Team

Indonesia's Government Regulation Number 33 of 2026 (Peraturan Pemerintah, or PP 33/2026), the implementing regulation for the Personal Data Protection Law, takes effect on 16 January 2027. According to a summary by the law firm DFDL, Article 74 requires every data controller to keep a record of all personal data processing activities with thirteen minimum elements, while processors keep their own record with four additional elements.

For a mid-sized company the consequence is concrete. By mid-January there must be one list that answers what personal data you hold, why, in which system, and on what legal basis. This article sets out what the sources report, then offers a way to build a record of processing activities from systems you already run, without opening a large project.

What the sources say

One caveat first. Every article number below comes from law-firm and consultancy summaries, not from the official text of the regulation. Check them against the official text before you rely on them.

  • DFDL (page updated 28 September 2026): the record of processing activities, often shortened to ROPA, is required by Article 74 with thirteen minimum elements. Processors, meaning parties that process data on a controller's behalf, keep their own record with four additional elements.
  • RSM Indonesia (18 September 2026) lists the processing inventory, legal basis, notice and consent as the first of six implementation priorities before 16 January 2027. RSM points to Article 30 for the bases of processing, Articles 9 and 69 for data accuracy, and Article 74 for the record of all processing activities.
  • Veritask (3 September 2026): Article 30 contains six bases of processing: explicit consent, performance of a contract, legal obligation, vital interest, public service or exercise of authority, and other legitimate interests.
  • DFDL: where the basis is legitimate interest, a three-part test is required (Article 53) together with a documented analysis (Article 54).
  • DFDL also notes the mandatory policies: a personal data processing policy, a policy for preventing and handling data protection failures, a retention policy, and a mechanism for handling compensation claims.

The thirteen elements are not itemised in the summaries we read, so we will not guess at them. All we can report is the number, as stated by DFDL. The full list has to be read in Article 74 itself.

Why the inventory comes first

Nearly every other obligation depends on this list. You cannot choose a legal basis for an activity nobody has written down. You cannot update vendor contracts until you know which vendors hold personal data. When an incident happens, the first question is whose data was affected, and the inventory holds the answer.

The level of detail decides whether the work succeeds. One row per database column is never finished; one row per department answers nothing. The workable unit is the activity: payroll, customer registration on the website, warehouse CCTV recording, the email newsletter.

Example inventory columns

The columns below are our practical suggestion, not the wording of the rule. Use them as a starting point and adjust once you have read the elements Article 74 asks for.

ColumnContent
Activity nameOne sentence a non-technical reader understands
PurposeWhy the data is processed
Data subjectsEmployees, applicants, customers, suppliers, visitors
Data typesIdentity, contact, financial, health, images
Basis of processingOne of the six bases Veritask lists for Article 30
System and locationApplication name, server location or cloud region
RecipientsVendors, affiliates, authorities that receive the data
RetentionHow long, and what happens afterwards
Row ownerThe job title accountable for it
Last reviewThe date the row was last checked

Building it from systems you already have

  1. Start from a system list, not interviews. Ask IT for the list of paid applications, databases and cloud accounts. The ERP, the CRM, the HR system, customer chat archives, email and shared folders almost certainly hold personal data.
  2. Write activities per system. One system can hold several. An HR system covers recruitment, payroll and attendance.
  3. Look for what is not on any list. Spreadsheets on laptops, online forms built by marketing, exports sent by email.
  4. Assign each row to an owner in the business. The head of HR owns the payroll row, the head of sales owns the CRM row.
  5. Fill in the basis of processing honestly. If you write legitimate interest, remember that according to DFDL this basis calls for a test and a written analysis. Link the row to that document.
  6. Flag every row that involves an outside party. That list becomes the work queue for vendor contract reviews, and for asking processors to show their own records.
  7. Keep it in one place with a change history. A shared spreadsheet with restricted edit rights is enough to begin.

Keeping it current without a large project

An inventory that is built once and left alone will be wrong within six months. What tends to work is not an annual audit but three small hooks:

  • Procurement. Every new application or vendor triggers one question: does this touch personal data. If yes, the row is added before the contract is signed.
  • System change. A change request that adds a field about people, or a new integration, includes an update to the relevant row.
  • A short quarterly review. Each row owner confirms the content is still true.

A realistic schedule to 16 January 2027

  • First two weeks: system list, owners named, and format agreed after reading Article 74.
  • Weeks three to five: rows filled in function by function, starting with HR and sales where volumes are largest.
  • Weeks six and seven: checks on legal basis, retention and the vendor list.
  • Final week: sign-off by management and a review calendar.

If your data sits in many unconnected applications, Etzal Group's enterprise software team can help map the sources, or you can contact us to talk it through.

This article is not legal advice. Confirm your company's obligations with legal counsel and the official text of PP 33/2026, and check the latest official announcements, because implementing rules from the supervisory agency have not yet been issued.

Sources

Frequently asked questions

What is a record of processing activities?

A written list of every activity in which the company uses personal data. According to DFDL's summary, Article 74 of PP 33/2026 requires it with thirteen minimum elements.

What are the thirteen minimum elements?

The summaries we read give the number but do not list them. Read Article 74 itself or ask your legal adviser before you fix a format.

Do vendors that process our data need their own record?

According to DFDL, processors keep their own record with four additional elements. Ask to see it when you review the contract.

When does the rule apply?

PP 33/2026 takes effect on 16 January 2027, according to summaries by RSM Indonesia and DFDL.

Author

Etzal Group Team

Etzal Group Team, helping businesses grow with technology. Contact us.

Related service

Website Development

Fast, SEO-ready websites that turn visitors into customers.