# Self-hosting n8n in Singapore: PDPA questions beyond server location

> A Singapore server does not settle PDPA questions for self-hosted n8n. Map connected APIs, execution data, access, patching and overseas transfers.

Source: https://www.fyadvisers.com/blog/n8n-self-hosting-pdpa-singapore/  
Author: Fiona Wang, FYAdvisers  
Published: 2026-11-08  
Last updated: 2026-11-08

Putting n8n on a server in Singapore does not answer the Personal Data Protection Act questions. The workflow can still send personal data to a connected application, an AI service, a support tool or a backup in another country. Assess the path. Then name who operates the instance.

This is not a comparison with Zapier or Make, and it is not a certificate of compliance. [System integration](/services/system-integration/) is the wider question of where data moves. Calling a model from a node is also an [AI integration](/services/ai-integration/) decision, because the payload often leaves the instance. How long to keep executions is the [retention guide](/blog/workflow-automation-data-retention-audit-logs/).

## Map the path, not the pin on the map

For a workflow that will handle people, employees or customer contacts, write a row for each hop:

| Hop | What to record |
|---|---|
| Trigger | Mailbox, form or webhook, and who can send it |
| Credentials | Where secrets live, who can read them, how they rotate |
| Each external API | Fields sent, vendor, and the region if the vendor states one |
| AI or extraction step | The document or the minimum fields. See [attachment routing](/blog/email-attachment-document-routing-automation/) for treating file text as untrusted |
| Execution data | Whether inputs and outputs are saved, who can open them, how pruning works |
| Backups | What they include, where they are copied, how a restore is tested |
| Support access | Whether an integrator can see production payloads |

A region field that only names the n8n virtual machine is an incomplete map.

## What the PDPA materials support, and what they do not

The PDPC’s [Advisory Guidelines on Key Concepts](https://www.pdpc.gov.sg/-/media/Files/PDPC/PDF-Files/Advisory-Guidelines/AG-on-Key-Concepts/Advisory-Guidelines-on-Key-Concepts-in-the-PDPA-17-May-2022.pdf) (17 May 2022) are guidance, not a new statute dated this year. In short, and without turning this article into a legal opinion:

- The protection obligation (section 24 in those guidelines) expects reasonable security arrangements for personal data in the organisation’s possession or control, including against unauthorised access, copying, modification and loss of storage media.
- The retention limitation (section 25) expects the organisation to stop retaining personal data, or to remove the means of associating it with particular individuals, when it is reasonable to assume the purpose is no longer served and retention is no longer necessary for legal or business purposes. It does not set one universal retention period.
- The transfer limitation (section 26) requires overseas transfers to meet the prescribed comparable-protection requirements. It does not ban overseas cloud services, and it does not say every server must sit in Singapore.

The guidelines also explain that the Data Protection Provisions generally do not apply to business contact information, depending on purpose and context. Do not treat every field in a B2B workflow as exempt. Employee records, identity documents and personal mobiles are not “just business contacts”. A vendor that processes data for you does not erase your responsibilities. The PDPC’s [guide to cross-border data transfers](https://www.pdpc.gov.sg/organisations/resources/guidance-by-topic/guide-to-cross-border-data-transfers) is the current landing page for that topic. Read the obligation in the guidelines and the regulations, not an empty marketing summary.

FYAdvisers is not a law firm. This is not a determination that a design complies.

## Use the product’s own security list as diligence

n8n’s [security overview](https://docs.n8n.io/hosting/securing/overview/) covers securing a self-hosted instance: security audits, SSL, SSO, restrictions on nodes and the public API, and execution-data redaction, with further policy topics. Confirm the items against the edition you will pay for. “We will self-host” is not the same sentence as “SSO is enabled”.

Self-hosting also assigns operational work: patching the host, responding to vulnerabilities, rotating credentials, restoring a backup and deciding what availability you need. Put names on those. A container left unpatched is not a privacy control.

## Execution data is a store of personal data

n8n’s [execution data](https://docs.n8n.io/hosting/scaling/execution-data/) documentation recommends saving less and pruning what you keep. Pruning is described as on by default, with a time threshold and a count threshold that are configuration, not a legal period. The page checked for this article showed defaults of 336 hours and 10,000 executions, and it noted that annotated executions are not pruned and that unfinished executions are not eligible in the same way. Those numbers are that documentation’s defaults. They will not match every version, and they are not a PDPA schedule. Failed executions often hold the payload. Include them, and include backups, or the deletion story is only true for the live disk.

The acceptance tests are: a failed run still contains a sensitive payload; a backup restores in a controlled test and you know whether the payload returned; a connected API receives data outside the hosting region you named. The third test is a mapping success when you expected the transfer, and a design failure when you did not.

## What to ask an implementer

Ask for a data-flow diagram with every third party, an access model, a restore demonstration and an export you can run if you leave. Do not accept “the server is in Singapore”, “self-hosting means we comply”, or “it is free so there is no operating cost”. There is always an operating cost. It is either on an invoice or on your own staff.

Illustrative scenario, not a client engagement: a document workflow runs on an instance in Singapore and sends extracted text to an overseas model API. The business writes that hop down, reduces the payload to the fields the step needs, and only then decides whether the safeguards for that transfer are acceptable. The virtual machine’s region was never the whole story.

Hosting is one reason to hire help rather than install it yourself: [when to hire a Zapier, Make or n8n expert](/blog/hire-zapier-make-n8n-expert-singapore/).

To list the nodes rather than the region, use the contact form or WhatsApp +65 9071 3976 ([chat](https://wa.me/6590713976)).

## Frequently asked questions

### Who patches the host and the n8n version?

Name a party for the operating system, the container or process, the n8n version and the credentials. Self-hosting moves this work to you or to an operator you pay. It does not remove it. Ask for the patch cadence in the contract, not in a diagram.

### Which controls depend on the edition?

n8n’s security documentation lists controls such as SSO, audits and restrictions that are not identical on every plan. Treat a feature as available only when it is enabled on the edition you will run. Do not assume a free self-hosted build includes every enterprise control.

### What exactly is sent to each third party?

For every node: the fields, the files, whether execution data stores the payload, and where that vendor hosts the processing. An AI step that receives a whole document is a different transfer from a step that receives an invoice total.

### Does a Singapore VM mean the PDPA is satisfied?

No. The PDPA is not a rule that all processing must occur in Singapore. Protection, retention and transfer safeguards still apply to personal data the organisation controls, including data a vendor processes for it.
