Website

Data in Singapore Cloud or Overseas AI APIs: Indonesia's Cross-Border Transfer Rules

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

Indonesia's Government Regulation 33 of 2026 (PP 33/2026), effective 16 January 2027, sets an order of legal bases for sending personal data out of the country: a destination with equivalent or higher protection, then binding safeguards, then data subject consent. The agency expected to assess equivalence has not been established, so companies using foreign cloud regions, global SaaS or AI model APIs have to decide under uncertainty.

Nearly every mid-sized company is affected. Data rarely "goes abroad" through a conscious decision. It leaves through software subscriptions, automatic backups and an AI feature someone in marketing switched on.

A note on sources: the article numbers below come from law-firm and consultancy summaries, not from the official text. Even the article range is cited differently, with one source writing 160 to 166 and another 160 to 168.

What the regulation asks for

According to Veritask's summary (3 September 2026), Articles 160 to 166 require the controller to map transfer flows, assess the risk and inform data subjects. Article 165 sets the order:

  1. The destination country provides equivalent or higher personal data protection.
  2. If not, adequate and binding safeguards must be in place.
  3. If neither exists, data subject consent is needed.

DFDL's summary (page updated 28 September 2026) calls the three-tier hierarchy mandatory. On DFDL's reading, the first two tiers cannot yet be used: equivalence decisions and binding safeguard instruments, such as standard contractual clauses and binding corporate rules, are waiting for the agency (the Lembaga). Consent is available, but limited to non-repetitive transfers, a limited number of data subjects, and after a risk assessment.

To be clear, that is DFDL's reading, not a government statement. RSM Indonesia (18 September 2026) puts it more cautiously: destination equivalence and standard contractual clauses depend on follow-up action by the agency (Articles 167, 168 and 170).

Katadata reported on 5 November 2026 that the draft presidential regulation (Perpres) creating the supervisory agency has been submitted to the President through the Ministry of State Secretariat, and that the agency is planned to assess whether transfers of personal data out of Indonesia meet the requirements. The draft is not yet law. This can change quickly, so check the latest official announcement before any major decision.

The sources we read do not name a single country as recognised. Do not assume Singapore or any other country is on a list.

First step: map the outbound flows

The duty to map transfer flows is the part you can do now without waiting for anyone. The checklist below is our practical suggestion.

FlowExampleOften missed
Cloud and hostingA region outside IndonesiaBackups and replicas in a second region
SaaSCRM, HR, email, file storageData location not stated in the contract
AI model APIsChatbot, document summaries, translationConversation text contains names, numbers, addresses
Parent or group companyHR and customer reports to SingaporeDirect read access to Indonesian systems
Vendor supportOverseas engineers entering productionRemote access counts as a flow
Analytics and advertisingPixels and SDKs on sites and appsInstalled by an agency, unknown to IT

For each row, record what data, whose, to which country, through which vendor, how often and whether it is really needed.

Choosing a realistic basis now

There is no neat answer while the first and second tier instruments are pending. What you can do is reduce exposure and document your reasoning. The four options below are our advice, each with a trade-off.

Keep data in Indonesia where the option exists. Some cloud and SaaS providers offer in-country data location. That removes the transfer question for stored data. Trade-off: cost may be higher, some features may be missing, and overseas support access still needs checking.

Reduce the data before it leaves. For AI APIs, remove or mask names, identity numbers, phone numbers and addresses before text is sent. If what leaves can no longer be linked to a person, the risk falls sharply. Trade-off: answer quality may drop, and poor masking gives false comfort.

Put contractual safeguards in place now. Although the agency's standard contractual clauses do not exist yet, you can still ask vendors to sign commitments on data protection, processing location and sub-processors. Do not assume this automatically satisfies the second tier. Treat it as a foundation to adjust when official instruments appear.

Use consent only for narrow cases. Per DFDL, consent is limited to non-repetitive transfers involving a limited number of data subjects. That suits a one-off event, not a daily sync of the customer database.

For routine flows to a parent company, ask group legal counsel how they intend to structure the intra-group transfer basis, and prepare the risk assessment now.

What not to do

  • Rush every system to another provider before mapping flows. Emergency migrations create new security risks.
  • Treat a vendor's "we are compliant" statement as a transfer basis. Ask for processing locations and a sub-processor list in writing.
  • Wait for the agency and do nothing. The mapping and risk assessment are needed in every scenario.

What to do this week

  1. Ask each system owner to fill in the outbound flow table above.
  2. Send data location and sub-processor questions to your ten largest vendors.
  3. Flag AI features that send customer text to overseas services and decide whether masking can be added.
  4. Schedule a discussion with legal counsel on flows to the parent company.

If the mapping shows a need to mask data before calling an AI model, or to move workloads to a local region, our AI consulting and enterprise software teams can help design it.

This article on Indonesia cross-border data transfer is not legal advice. Confirm the transfer basis for your case with legal counsel and the official text of PP 33/2026.

Sources

Frequently asked questions

Can personal data still be stored in an overseas cloud?

PP 33/2026 is summarised not as a ban but as an ordered basis for transfer: equivalent protection in the destination country, then binding safeguards, then data subject consent. Confirm the basis you rely on with legal counsel.

Which countries are recognised as equivalent?

The sources we read name none. According to DFDL and RSM Indonesia, equivalence decisions depend on a supervisory agency that has not yet been established.

Is customer consent enough as a transfer basis?

According to DFDL's summary, consent is available but limited to non-repetitive transfers, a limited number of data subjects and after a risk assessment, which makes it hard to use for routine flows.

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.