Taiwan's PDPA Amendment: Breach Notification, Fines and Seven System Gaps
Taiwan's 2025 PDPA amendment adds breach notification duties under a new data protection commission, effective date pending. The key rules, fine tiers and seven system gaps to close.
Current Status: Amended, Effective Date Pending
According to Taiwan's Laws and Regulations Database, the Personal Data Protection Act (PDPA) was last amended on November 11, 2025, and Article 56 leaves the effective date to the Executive Yuan. At the time of writing (November 20, 2026) the database still marks some provisions as not yet in force, with the final effective date undetermined.
The amended Article 1-1 names the Personal Data Protection Commission (PDPC) as the competent authority. The rules are written and only the start date is missing. Companies have time to prepare, and they do not control how much.
Note: this article summarizes the statutory text in the database. It is general information, not legal advice. Notification deadlines and thresholds will be set in regulations issued by the authority. Follow official announcements and consult a lawyer for specific cases.
What Changes: Three Things
1. A breach can no longer be handled quietly
Under Article 12, on learning that personal data it holds has been stolen, altered, damaged, lost or leaked, an organization must:
- Notify the data subjects.
- Report to the competent authority when the incident falls within a defined scope.
- Take prompt and effective response measures, and record the facts, impact and measures taken, and keep those records.
- Follow the content, method, deadline and scope of notification and reporting set by the authority.
The statute does not state a number of hours. That will come in the delegated regulation. Do not treat a figure circulating online as settled.
2. Fines come in tiers
| Violation (non-government entities) | Fine |
|---|---|
| Failing to report as required, to take response measures or to keep records | NT$20,000 to NT$200,000 with an order to correct; repeated fines if uncorrected |
| Failing to notify data subjects | Order to correct first; NT$20,000 to NT$200,000 per instance if uncorrected |
| Failing to implement security maintenance for personal data files | NT$20,000 to NT$2 million with an order to correct; NT$150,000 to NT$15 million per instance if uncorrected |
| Failing security maintenance in serious cases | NT$150,000 to NT$15 million with an order to correct; repeated fines if uncorrected |
Note the gap between the amounts. The ceiling for reporting failures is NT$200,000. The ceiling for inadequate security is NT$15 million. What the law really demands is protection beforehand. Reporting is the minimum afterwards.
3. One authority, with a transition period
Article 51-1 provides that for six years from the PDPC's establishment, non-government entities within a scope announced by the Executive Yuan remain under their existing sector regulator or local government, with the list reviewed for reduction every two years. In practice you may need to follow both your sector regulator and the PDPC for a while.
The requirement to appoint a data protection officer (Article 18) applies to government agencies. The statute does not impose it on ordinary companies.
Seven System Gaps to Close
The statute states duties. Inside a company the question is whether the systems can deliver them. These seven capabilities are what the notification and security duties actually require.
1. Know where personal data lives
List every location: production systems, spreadsheets, mailboxes, cloud drives, scanned paper, vendor-hosted systems. For each, note the data types, order of magnitude and owner. Without this list you cannot even state the scope of an incident.
2. Minimize permissions
Set viewing, exporting and deleting separately. Disable accounts on the day someone leaves or changes role. Shared accounts are the biggest obstacle in an investigation because you cannot tell who did what.
3. Keep access logs
Article 12 requires recording the facts and impact, which presumes the system already logs who queried, exported or changed which data and when. Store logs where ordinary users cannot alter them, with an adequate retention period.
4. Encrypt in transit and at rest
Use encrypted connections across the site, encrypt databases and backup files, and store only password hashes. If leaked data was encrypted, the actual harm and the follow-up work are far smaller.
5. Back up and rehearse restoration
The incident types in the statute include damage and loss, not only leaks. Keep backups offline or off-site and restore from them at least every six months to confirm they work.
6. Write the incident response procedure
One page that answers five questions: who decides whether it is an incident, who contains it, who handles external contact, where the notification template is, and where records are kept. Make reporting to the authority and notifying data subjects fixed steps, and run a tabletop exercise once.
7. Review outsourcing contracts
When a vendor builds or hosts the system, responsibility for the personal data stays with you. Contracts should state the processing scope, security measures, the vendor's notification deadline and cooperation duties in an incident, and return and deletion of data at termination. For the security questions to ask when selecting a vendor, see our software vendor checklist.
Priorities When Time and Budget Are Tight
- This week: complete the personal data inventory and disable all departed staff accounts and shared accounts.
- This month: confirm backups restore, write the one-page incident procedure, review the main outsourcing contracts.
- This quarter: add access logging and encryption, and run a tabletop exercise.
If an older system cannot support logging and permission control, evaluate patching against replacement using our legacy system modernization guide. For everyday protection see our SME cybersecurity checklist, and if you collect external data, review the personal data section of our web scraping legal guide.
Next Step
The direction of the new rules is clear: speak up when something happens, prevent it beforehand, and expect a far higher price for failing to prevent than for failing to report. The effective date is pending, but none of the seven items above needs to wait for an announcement.
EFFECT's maintenance and optimization service covers monitoring, backup, incident handling and permission management, and we review existing systems for personal data protection gaps. Bring your current setup to a free 30-minute consultation (NDA protected) and we will help you prioritize.
Sources
FAQ
When do the new PDPA rules take effect?
According to the Laws and Regulations Database, the effective date of the amended provisions is to be set by the Executive Yuan. At the time of writing (November 20, 2026) the database still shows the final effective date as undetermined. Check announcements from the Personal Data Protection Commission and the database periodically.
How many hours do we have to report a breach?
The amended Article 12 leaves the content, method, deadline and scope of notification and reporting to the competent authority. The statute itself gives no number of hours. The official deadline will be in the authority's regulation. In practice, prepare your internal assessment and escalation process so that it can be completed within a day or two.
Does this apply to small companies, and are the fines heavy?
The PDPA applies to every non-government entity that collects, processes or uses personal data, regardless of size. Fines are tiered: NT$20,000 to NT$200,000 for reporting-related violations, NT$20,000 to NT$2 million for failing to implement security maintenance, and NT$150,000 to NT$15 million in serious cases or where the violation is not corrected. The authority has discretion in each case, but the statutory ceilings do not vary by company size.
A vendor built and hosts our system. Who is responsible for a breach?
To data subjects and the authority, your company collected the data, and outsourcing does not remove that responsibility. Contracts should set the vendor's security measures, incident notification deadline and duty to cooperate with investigations, and reserve your right to audit. When an incident occurs you still have to complete notification and reporting yourself.
Bring us one workflow that keeps getting stuck
No complete specification required. A 30-minute first call clarifies the problem, data and desired outcome. Project ideas remain confidential.
Book a 30-Minute Call