Website

Your Software and Cloud Vendor Contracts Need Updating: Processor Rules in PP 33/2026

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

Indonesia's Government Regulation 33 of 2026 (PP 33/2026), effective 16 January 2027, requires a written agreement between a personal data controller and its processor, with defined minimum content. The regulation, which implements the Personal Data Protection Law, also requires prior written approval before a processor uses a sub-processor, and confirms that the controller stays responsible for processing it hands over.

The timing collides with the procurement calendar. Annual contracts with software houses, SaaS providers, cloud providers and agencies are commonly renewed in December and January, just before the effective date. Renewing on the old text locks the gap in for another year.

A note on sources: the article numbers below come from law-firm and consultancy summaries, not from the official text. The example clauses in this piece are practical suggestions, not official wording.

The minimum content of a processor agreement

For anyone searching "data processor agreement Indonesia", the short answer is a list of six items. According to Veritask's summary (3 September 2026), Articles 13 to 16 provide that a processor contract must contain:

  • the scope and method of processing
  • the type and purpose of processing
  • the categories of data subjects
  • the duration
  • the rights and obligations of the parties
  • oversight and audit mechanisms

Veritask notes two further points. The controller remains responsible. A processor may only engage a sub-processor with the controller's prior written approval.

RSM Indonesia (18 September 2026) refers to Article 14 for the written agreement and its minimum content, and Article 15 for written approval of sub-processors. Per RSM, processor accountability and audit duties sit in Articles 139 to 141.

DFDL's summary (page updated 28 September 2026) adds that processors keep their own record of processing, with four additional elements compared with the controller's record.

One other relationship is often confused with this one. According to Veritask, joint controllers, meaning two parties that together decide the purpose and method of processing, must have a written agreement on roles, responsibilities and a shared contact point, and they are jointly and severally liable (Articles 10 to 12).

First step: work out who your processors are

Before opening any contract, sort vendors into groups. This split is our practical assessment and should be confirmed by legal counsel.

VendorUsual positionWhat to check
Software house running your application and databaseProcessorProduction access, data copies in test environments
SaaS provider (CRM, HR, payroll)ProcessorStandard terms, sub-processor list
Cloud and hosting providerProcessorRegion, technical support access
Marketing agency holding the customer listProcessor, sometimes joint controllerWho decides how the data is used
Partner using data for its own purposesSeparate or joint controllerA different kind of agreement

The distinguishing question is simple: who decides what the data is used for. If the vendor only follows your instructions, it is a processor. If it helps set the purpose, the relationship needs a different agreement and liability may be joint.

Reviewing the contracts you already have

Take each active contract and compare it with the six items in Veritask's summary. In our experience the gaps sit in four places.

Scope is too general. "Vendor provides development and maintenance services" does not say which data is touched. Add a schedule naming the systems, data types, categories of data subjects and purpose.

A term with no clear end for the data. The contract ends, but data remains on the vendor's servers, backups and developer laptops. State what happens to data at the end: returned or deleted, within how many days, with what proof.

Audit on paper only. An audit right with no procedure is rarely used. Agree something realistic: an annual questionnaire, third-party audit reports, and a right of direct inspection after an incident.

Incidents with no deadline. PP 33/2026 gives the controller a 3 x 24 hour notification deadline, per RSM's summary. A vendor obliged to report "as soon as possible" with no number makes your deadline hard to meet. Ask for a limit in hours.

Listing sub-processors

A sub-processor is any party your vendor uses to help process the data: the cloud provider behind a SaaS product, an email delivery service, an AI model API, or a freelancer. The rule requires prior written approval, so you need to know who they are.

Practical steps:

  1. Ask each processor for a written sub-processor list: name, service, processing location.
  2. Agree how approval works. Case-by-case approval gives the most control but is slow. A list approved up front, with notice and a right to object before additions, is easier to run. Ask legal counsel which form satisfies "prior written approval".
  3. Require the vendor to bind its sub-processors to equivalent obligations.
  4. Keep the list with your processing inventory and update it when things change.

Trade-offs in negotiation

  • Large vendors rarely change standard terms. With a global cloud or SaaS provider, you usually accept their data processing addendum. Your job is to read it, note the gaps against the six items above and decide whether those gaps are acceptable.
  • Small vendors will sign anything. That is not necessarily good news. Audit and security clauses they cannot actually perform only move the problem to the day of the incident. Ask for evidence of capability, not just a signature.
  • Heavier obligations raise the price. Logs, audits and reporting deadlines are work. It is reasonable for a vendor to price them. Weigh that cost against the fact that responsibility stays with you.

As a software services provider, a company like ours sits on the processor side of this relationship. From that side the message is the same: a clear data schedule and firm deadlines make life easier for both parties.

What to do this week

  1. Pull the list of vendor contracts expiring before February 2027.
  2. Mark the vendors that touch personal data.
  3. Send a request for sub-processor lists and processing locations.
  4. Prepare one standard data processing addendum with legal counsel and use it for every renewal.

If you are drafting a contract for a new enterprise software project, put the data processing schedule into the request for proposal from the start.

This article is not legal advice. Confirm your contract terms with legal counsel and the official text of PP 33/2026.

Sources

Frequently asked questions

Who counts as a data processor?

A party that processes personal data on behalf of the controller, such as a software house running your application, a SaaS provider, a cloud provider or an agency holding your customer list.

Does responsibility move to the vendor once the contract is signed?

No. According to Veritask's summary of PP 33/2026, the controller remains responsible for processing handed to a processor.

Can a vendor use subcontractors to process the data?

According to summaries by Veritask and RSM Indonesia, a processor may only engage a sub-processor with the controller's prior written approval.

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.