Skip to content
Kardu

Photo by Ása Steinarsdóttir on Unsplash

← Back to blogLaw 21.719

Is GDPR compliance enough for Chile's Law 21.719?

7 min · September 2026 · César Mella Diaz

Last updated: 20 October 2026


In 30 seconds

  • If you already comply with GDPR you don't start from zero with the Chilean law, but you don't comply automatically either.
  • What changes most: blocking in 2 business days, notifying people by type of data, and transfers leaving Chile.
  • It's set to take effect on December 1, 2026; a bill in Congress could move it to 2027.

Complying with GDPR isn't complying with Law 21.719, but it helps

If your company operates in Europe and already runs a GDPR program, getting to Chile's Law 21.719 doesn't mean starting from zero. The underlying principles —data minimization, transparency, data subject rights, breach notification— are almost the same. But "almost the same" isn't "the same", and Chile's Personal Data Protection Agency doesn't automatically accept your GDPR compliance as valid in Chile.

Law 21.719 is set to take effect on December 1, 2026. A bill in Congress could postpone it to 2027, but it isn't law yet, and either way the underlying obligation is coming.

This is what changes in practice.

The differences at a glance

GDPR Law 21.719
Deadline to answer data subject requests 1 month, extendable by another 2 30 calendar days, extendable once by another 30 days
Temporary blocking of data Within the general deadline 2 business days
Maximum fine €20M or 4% of global turnover, whichever is higher 20,000 UTM; if a company that isn't a small business reoffends, up to 2% or 4% of its annual revenue
Breach notice to the authority Within 72 hours, unless there is no risk to people Without undue delay, if there is a reasonable risk to people
Breach notice to affected people If there's a high risk to them If the breach is reportable and involves sensitive data, data about children under 14, or data about debts or economic, financial or commercial obligations
Compliance program Part of accountability Certifiable prevention model that counts as a mitigating factor

Deadlines: temporary blocking is the exception that bites

GDPR gives you one month to answer an access, rectification or erasure request, extendable by two more months. Law 21.719 gives you 30 calendar days, extendable once by another 30.

Deadlines to answer rights requests: GDPR vs Law 21.719GDPR: 1 month, extendable by another 2 months. Law 21.719: 30 calendar days, extendable once by another 30 days. Temporary blocking under Law 21.719: 2 business days. Deadline to answer a request, in days GDPR 1 month + 2 extension Law 21.719 30 days + 30 extension Temporary blocking (Chile) 2 business days 0 30 60 90 days Light bar: possible extension. Blocking is counted in business days.

But there's one exception worth keeping front of mind. When someone asks you to rectify or erase their data, or objects to its processing, they can also ask you to block it while you decide. That temporary blocking request has to state its grounds, and you have 2 business days to answer it. Blocking doesn't require you to delete anything: only to stop processing that data in the meantime.

If your internal process is calibrated to GDPR's weeks, adjust it for Chile. And treat blocking as a separate request with its own workflow, because two business days leave no room for it to get lost in a shared inbox.

Fines: UTM, but not only UTM

GDPR calculates its maximum fines as a percentage of global turnover: up to 4% or €20 million, whichever is higher. Law 21.719 sets them in UTM (Unidad Tributaria Mensual, a Chilean monetary unit): up to 5,000 UTM for minor infringements, 10,000 for serious ones and 20,000 for very serious ones. At the September 2026 UTM value, 20,000 UTM is over 1.4 billion Chilean pesos, a fraction of the European cap.

The gap narrows with repeat offences. If a company that isn't a small business commits another serious or very serious infringement, the fine can reach 2% or 4% of its annual revenue for the last year, depending on the severity, if that figure is higher than the UTM fine. And if it racks up very serious infringements within a 24-month period, the Agency can suspend its data processing operations for up to 30 days.

Security breaches: the playbook carries over, the notification rule doesn't

Both laws require you to notify the authority of breaches that pose a risk to people. GDPR sets a 72-hour deadline; Law 21.719 sets no hours, but requires you to do it without undue delay and by the fastest means available.

The important difference is when you also have to notify the people affected. GDPR requires it when the breach poses a high risk to them. Once a breach has to be reported to the Agency, Chilean law doesn't look at whether the risk is high but at the type of data: you have to notify each affected person when it involves sensitive data, data about children under 14, or data about debts or economic, financial, banking or commercial obligations. If you can't reach each person, you have to publish a notice in a national media outlet.

In practice: you can reuse your incident response playbook, but not the rule that decides when to notify affected people. A leak of customer debt data that in Europe might stop at a notice to the authority requires notifying every affected customer in Chile.

International transfers: review your data flows to and from Chile

A company that already complies with GDPR usually has its data flows within Europe sorted out. Law 21.719 introduces its own international transfer regime in Chile, and it applies to data leaving Chile: to your European headquarters, to your cloud providers or to any other country. Data travelling the other way, from Europe to Chile, is still governed by GDPR. And it isn't only about which way the data travels: who processes it, and from where, matters too.

A transfer is lawful if the destination country has an adequate level of protection according to the Agency, or if it's covered by contractual clauses, binding corporate rules or other instruments with adequate safeguards. The Agency has to publish the list of adequate countries and the model clauses on its website. Until then, take stock of which data leaves Chile, where it goes and under which contract.

Identifying the data subject: the Agency decides

Law 21.719 tasks the Agency with defining how a data subject exercising their rights is authenticated. Until it publishes that criterion, design your request channel so it can adapt. GDPR, by contrast, leaves identification up to each controller.

The infringement prevention model: what GDPR doesn't have

GDPR requires you to demonstrate that you comply (accountability), but it has no equivalent to this. Chilean law lets you voluntarily adopt an infringement prevention model: a compliance program with a defined set of minimum elements, including appointing a data protection officer. The regulation governing how it's implemented, certified and supervised was published in September 2026.

If the model is certified and the Agency sanctions you, it counts as a mitigating factor. It doesn't exempt you from liability, but it reduces your exposure. And here your GDPR program is a good starting point: the data inventory, records of processing and policies you already have are the foundation of that program.

What to do if you already comply with GDPR

Don't redo the work from scratch: use your data inventory, your records of processing and your breach playbook as the base. Then adjust what's specific to Chile:

What you reuse from your GDPR work and what you adjust for ChileYou reuse: the data inventory, the record of processing, the breach protocol and the policies. You adjust: a 2-business-day workflow for blocking, notifying people by type of data, transfers leaving Chile and the decision on the prevention model. YOU REUSE Data inventory Record of processing Breach protocol Policies YOU ADJUST FOR CHILE Blocking in 2 business days Notice by type of data Transfers out of Chile Prevention model You don’t start from zero, but you don’t comply automatically either.

The most common mistake is assuming European compliance carries over automatically. The most expensive one is treating Law 21.719 as an isolated project without building on what you already have.

For the full picture of Law 21.719 —when it applies, sanctions and what it means for an SME— read Chile's Law 21.719: compliance guide.

Operating between Europe and Chile and want one system for both jurisdictions? Talk to us and we'll go through it together.

Frequently asked questions

If my company complies with GDPR, does it already comply with Law 21.719?

Not automatically. They share similar principles and rights, but Law 21.719 has its own authority, its own deadlines, its own fines and different rules for notifying people affected by a breach and for transferring data out of Chile.

What response deadlines does Law 21.719 set?

30 calendar days to answer access, rectification, erasure, objection and portability requests, extendable once by another 30. The exception is the temporary blocking of data: you have to answer within 2 business days.

Do Law 21.719 fines depend on revenue?

In general they are set in UTM (a Chilean monetary unit), with a maximum of 20,000 UTM for the most serious infringements. But if a company that isn't a small business repeats a serious or very serious infringement, the fine can reach 2% or 4% of its annual revenue, if that figure is higher.

Do I have to notify people affected by a breach the same way as under GDPR?

Not with the same criterion. GDPR requires notifying affected people when there is a high risk to them. Law 21.719, when the breach has to be reported to the Agency because it poses a reasonable risk, requires notifying affected people if it involves sensitive data, data about children under 14, or data about debts or economic, financial, banking or commercial obligations, even if the risk isn't high.

What is the infringement prevention model?

A voluntary compliance program that Chilean law allows you to certify with the Agency. If it's certified, it counts as a mitigating factor if the Agency sanctions you. It doesn't exempt you from liability.

César Mella Diaz

César Mella Diaz

Kardu Founder

LinkedIn →

← Back to blog