Data Protection Monitor
Global Privacy & Data Protection Intelligence

Argentina Data Protection & Privacy Regulation

AR schema gdpri-v2 trajectory: not yet assessed regulated (omnibus) overlaps: Sentinel (AML/CFT), World Payments, artificial-intelligence

Last updated · 10 categories · 106 claims · 64 sources in the cumulative register

Argentina's data-protection regulator, the Agencia de Acceso a la Información Pública, is the control authority charged with applying Ley 25.326, the country's core data-protection statute, in force since 2000 to protect personal data recorded in files, registries or data banks, public or private, and to guarantee the right to honour, privacy and access to information.

Data collected Data published

AI-assembled from cited sources

Not fully checked this cycle: Algorithmic, Biometric & Surveillance Governance, Enforcement & Redress (3 open gaps).

Framework & posture10 of 10 modules active
10 active · 15 binding instruments
Next milestoneNo upcoming dated milestone on record
Record & confidence mix106 claims · 60 sources · machine-compiled
19 Confirmed69 Probable18 Contested / unverified
Evidence re-verified: ·Position last changed: ·
Record history & provenance ▾

Methodology & record provenance: Module confidence is derived from the underlying claims (source tier and primary excerpt retention), while statutory legal force is tracked independently.

Review status: AI-synthesised · Tier-1/2 verified · As-of date: 2026-11-17

Jurisdiction brief

Latest update · 25 October 2026

Lead Signal

Argentina's data-protection framework rests on Ley 25.326, a statute now over two decades old, and the principal development this period is a reform bill drafted by the Agencia de Acceso a la Información Pública itself. Expediente 3397-D-2026, filed on 16 July 2026 by diputado Agustín Rossi, proposes a 72-article, 13-title replacement for Ley 25.326 and Ley 26.343. Among its provisions, Article 4 would extend the regime's territorial scope to controllers not established in Argentina who process data of persons located there, offer goods or services to them, or profile them, a test that goes beyond what has been independently verified of the current statute's own extraterritorial reach. The AAIP's own authorship of the bill is notable: the regulator that currently administers Ley 25.326 is itself the drafting hand behind its proposed successor, suggesting the reform responds to gaps the regulator has identified through its own administration of the existing law.

Key regulatory facts for Argentina
Key regulatory facts for Argentina
Regulatory DimensionArgentina Standing Position
JurisdictionArgentina (AR)
Regulatory ScopeData Protection & Privacy Regulation (10 modules, 106 sourced findings)
Regulator & FrameworkComprehensive, EU-adequacy-holding statute with an active, resourced supervisory authority; amber-tending risk only from the unsettled multi-bill reform pipeline.
Lawful Processing & Special DataCore lawful-basis and sensitive-data concepts exist but are narrower/less granular than GDPR-aligned peers, with material change only at proposal stage.
Data Subject RightsCore access/rectification/erasure rights are binding and judicially enforceable today; portability/ADM-objection rights remain at proposal stage only.
Controller/Processor DutiesFoundational accountability tools exist mostly as non-binding guidance rather than statutory duties; binding DPIA/DPO/breach-notification obligations are pending, not yet in force.
Primary Instruments CitedIAPP, IAPP, Beccar Varela, Argentina.gob.ar, Argentina Official Instrument (en.wikipedia.org National_Directorate_for_Persona)
Last Confirmed / Updated (64 sources in cumulative register)

#

Comprehensive, EU-adequacy-holding statute with an active, resourced supervisory authority; amber-tending risk only from the unsettled multi-bill reform pipeline.

Primary frameworkLey 25.326 (Personal Data Protection Act) and Decreto 1558/2001
Traffic-light rationale — GreenComprehensive, EU-adequacy-holding statute with an active, resourced supervisory authority; amber-tending risk only from the unsettled multi-bill reform pipeline.

Sub-modules (5)

Regulator and authorityGreen

AAIP, an autarchic body with functional autonomy under the Jefatura de Gabinete de Ministros, is the applicable authority for Ley 25.326, the Access to Public Information Law 27.275, and the Do-Not-Call Registry Law 26.951.

Claims (7):

  • The Agencia de Acceso a la Información Pública (AAIP) is the supervisory authority for the Personal Data Protection Act No. 25.326 in Argentina.
  • Agencia de Acceso a la Información Pública (AAIP) — AAIP is the control authority and Autoridad de Aplicación of Ley 25.326.
  • Agencia de Acceso a la Información Pública (AAIP) — Under Decreto 899/17 Art. 2, every regulatory reference to the former Dirección Nacional de Protección de Datos Personales must be understood as referring to the AAIP.
  • AAIP is the application authority for Ley 25.326.
  • AAIP is the statutory control and enforcement authority for Ley 25.326.
  • The AAIP is the statutory authority of application for Ley N° 25.326 and separately holds access-to-information competence under Ley 27.275.
  • Decreto 1558/2001 Art 29 (as substituted) designates AAIP as the órgano de control of Ley 25.326, empowered to apply administrative sanctions under Art 31

Act and instrumentsGreen

Primary instruments are Ley 25.326 and Decreto 1558/2001 (amended by Decreto 1160/10), supplemented by numerous AAIP resolutions.

Claims (5):

  • Ley 25.326 of 2000 together with Decreto 1558/2001 (amended by Decreto 1160/10) form the primary legal instruments governing data protection in Argentina.
  • Bill 3397-D-2026 proposes a new DP regime replacing Ley 25.326.
  • Ley N° 25.326 — Protects personal data recorded in files, registries or data banks, public or private, to guarantee the right to honour, privacy and access to information.
  • AAIP Resolución 126/2024 grades Ley 25.326 infractions into three severity bands with corresponding fine ranges.
  • A comprehensive GDPR-aligned replacement bill for Ley 25.326 remains a legislative proposal and has not been enacted.

Material scopeGreen

The Act and Decrees apply to both public and private-sector processing of personal data.

Claims (1):

  • The Act and its implementing Decrees apply to both public and private organizations and to processing activities carried out in the territory of Argentina.

Territorial scopeAmber

Current law applies to processing carried out within Argentine territory; pending reform bills would add express extraterritorial application to controllers/processors located abroad but targeting Argentine data subjects.

Claims (3):

  • The Act and its implementing Decrees apply to both public and private organizations and to processing activities carried out in the territory of Argentina.
  • A pending Congressional reform bill would expressly extend extraterritorial application of the data protection law to controllers/processors located outside Argentina where their processing targets Argentine data subjects.
  • Pending bill Art. 4 would extend territorial scope extraterritorially.

Regulator registration and filingAmber

Under the current regime, controllers must register databases with AAIP (over 2,000 databases registered in 2022 alone); pending reform bills would eliminate this registration duty entirely.

Claims (4):

  • Under the current regime, data controllers are required to register their databases with AAIP; 2,035 databases were registered in 2022 alone.
  • Pending reform bills (Carro/Doñate, inspired by the AAIP anteproyecto) would eliminate the currently-in-force duty to register databases with the supervisory authority.
  • Database registration with AAIP is a standing obligation.
  • Ley 25.326 art. 21 requires registration of report-furnishing databases with AAIP's national registry.
Category narrative 111 words

Argentina's data-protection regime is anchored in Ley 25.326 (Personal Data Protection Act, 2000) and its implementing Decreto 1558/2001 (as amended by Decreto 1160/10). The Agencia de Acceso a la Información Pública (AAIP) is the supervisory authority, having absorbed the functions of the former Dirección Nacional de Protección de Datos Personales. The Act applies to public and private data processing carried out in Argentine territory and underpins the EU's 2003 adequacy finding. Two parallel legislative tracks (Carro/Doñate bills inspired by the AAIP's own anteproyecto, and the independently filed Yeza bill 1751-D-2026) are pending before Congress to replace the 25-year-old Act wholesale, including express extraterritorial scope and removal of the current database-registration duty.

Periodic update · new data 2026-10-25

Argentina's data-protection framework is anchored in Ley 25.326, administered by the Agencia de Acceso a la Información Pública, which was created under Ley 27.275 in 2016 and designated as the application authority for the data-protection statute. This institutional architecture is unchanged this period. What has moved is the substantive reform agenda sitting above that architecture: Expediente 3397-D-2026, filed on 16 July 2026 by diputado Agustín Rossi, proposes a 72-article, 13-title replacement for both Ley 25.326 and Ley 26.343. The bill was drafted by the AAIP itself, which is a notable structural point, since it means the regulator administering the current statute is also the author of its proposed successor, implying the reform reflects gaps or limitations the AAIP has identified through its own enforcement and administration experience rather than an externally imposed legislative initiative.

Among the bill's provisions, Article 4 would extend the regime's territorial scope to controllers not established in Argentina who process the data of persons located there, who offer goods or services to those persons, or who profile them. This extraterritorial test, if enacted, would be a material expansion relative to the current statute, though the current statute's own extraterritorial reach has not been independently verified this period, so the degree of actual expansion cannot be precisely quantified. The bill is one of at least three pending reform proposals; it has been filed but has not reached floor debate in the Chamber of Deputies, and no enactment timeline is confirmed.

The broader significance for an operator or counsel tracking Argentina's regulatory trajectory is that this is now a live, regulator-authored reform process rather than a purely academic or civil-society-driven proposal, which may carry different legislative momentum than externally drafted bills have historically had in this area.

Outlook

The central marker to watch is whether Expediente 3397-D-2026 advances to committee consideration or floor debate in the Chamber of Deputies, and whether its extraterritorial Article 4 provision, along with the bill's broader 72-article scope, survives legislative process intact. Given the bill's AAIP authorship, its progress may also signal the regulator's own enforcement priorities for the remainder of the current statutory regime while reform is pending.

1 earlier distinct update
Periodic update · new data 2026-10-05

Argentina's data-protection supervisory authority remains the Agencia de Acceso a la Informacion Publica (AAIP), which holds this competence under Ley 25.326 alongside a separate access-to-information mandate. The law also requires every person or entity that processes third-party personal data to register their databases with the AAIP's national registry as a condition of lawfulness, though compliance with that registration duty is reported to be widely incomplete among obliged entities.

This period's material development is the filing, on 16 July 2026, of expediente 3397-D-2026 by Diputado Rossi, a bill that would repeal both Ley 25.326 and Ley 26.343 and replace them with a new statutory framework. What sets this bill apart from other pending reform proposals is that it was elaborated by the AAIP itself, arising out of a public-consultation process the agency opened under Resolucion AAIP No. 119/22. The Rossi bill is not alone: it now sits alongside at least two other competing proposals before Congress, the Yeza bill (Proyecto 1751-D-2026) and a bill attributed to Carro and Donate, each addressing different gaps in the current regime. As of this period, none of the three bills has established committee traction, and none has been enacted. Until one does, the AAIP's supervisory role and the registration obligation under the existing Ley 25.326 continue to apply unchanged.

Outlook

The principal question going forward is which, if any, of the three competing reform bills gains committee momentum. The Rossi bill's direct lineage from an AAIP-led consultation process gives it a degree of institutional standing the other two proposals lack, but institutional origin alone does not determine legislative priority, and no committee assignment or hearing schedule has been established from sources reached this period. A resolution of this three-way contest, in either direction, would be the clearest signal of whether Argentina is moving toward a materially modernised data-protection statute or whether Ley 25.326 continues as the operative framework for the foreseeable future.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (21)
  1. Confirmed IAPP — The Agencia de Acceso a la Información Pública (AAIP) is the supervisory authority for the Personal Data Protection Act No. 25.326 in Argentina. observed
  2. Confirmed DataGuidance — Ley 25.326 of 2000 together with Decreto 1558/2001 (amended by Decreto 1160/10) form the primary legal instruments governing data protection in Argentina. observed
  3. Confirmed DataGuidance — The Act and its implementing Decrees apply to both public and private organizations and to processing activities carried out in the territory of Argentina. observed
  4. Probable IAPP — A pending Congressional reform bill would expressly extend extraterritorial application of the data protection law to controllers/processors located outside Argentina where their processing targets Argentine data subjects. observed
  5. Confirmed IAPP — Under the current regime, data controllers are required to register their databases with AAIP; 2,035 databases were registered in 2022 alone. observed
  6. Probable IAPP — Pending reform bills (Carro/Doñate, inspired by the AAIP anteproyecto) would eliminate the currently-in-force duty to register databases with the supervisory authority. observed
  7. Probable Beccar Varela — Bill 3397-D-2026 proposes a new DP regime replacing Ley 25.326. observed
  8. High Boletín Oficial de la República Argentina — Agencia de Acceso a la Información Pública (AAIP) — AAIP is the control authority and Autoridad de Aplicación of Ley 25.326. observed
  9. High Argentina.gob.ar — Ley N° 25.326 — Protects personal data recorded in files, registries or data banks, public or private, to guarantee the right to honour, privacy and access to information. observed
  10. Confirmed Boletín Oficial de la República Argentina — Agencia de Acceso a la Información Pública (AAIP) — Under Decreto 899/17 Art. 2, every regulatory reference to the former Dirección Nacional de Protección de Datos Personales must be understood as referring to the AAIP. observed
  11. Probable https://en.wikipedia.org/wiki/National_Directorate_for_Personal_Data_Protection — AAIP is the application authority for Ley 25.326.
  12. Probable Beccar Varela — Pending bill Art. 4 would extend territorial scope extraterritorially. observed
  13. Uncertain https://foro.ar/articles/proteccion-datos-ley-25326 — Database registration with AAIP is a standing obligation.
  14. Probable Argentina.gob.ar — AAIP is the statutory control and enforcement authority for Ley 25.326. observed
  15. Probable Wikipedia — AAIP Resolución 126/2024 grades Ley 25.326 infractions into three severity bands with corresponding fine ranges. observed
  16. Probable Argentina.gob.ar / AAIP — Ley 25.326 art. 21 requires registration of report-furnishing databases with AAIP's national registry. observed
  17. Probable Primary statutory record — 5 ON LINE S.R.L. — database suspension by the AAIP on 2026-11-02
  18. Probable Primary statutory record — unnamed company — information-failure sanction by the AAIP on 2026-11-02
  19. Probable Wikipedia — The AAIP is the statutory authority of application for Ley N° 25.326 and separately holds access-to-information competence under Ley 27.275. observed
  20. Uncertain Argentina.gob.ar / AAIP — A comprehensive GDPR-aligned replacement bill for Ley 25.326 remains a legislative proposal and has not been enacted. observed
  21. Confirmed AFIP, Biblioteca Electrónica (Decreto 1558/2001, texto actualizado) — Decreto 1558/2001 Art 29 (as substituted) designates AAIP as the órgano de control of Ley 25.326, empowered to apply administrative sanctions under Art 31 observed

#

Core lawful-basis and sensitive-data concepts exist but are narrower/less granular than GDPR-aligned peers, with material change only at proposal stage.

Primary frameworkLey 25.326, Arts. 5–7; Decreto 1558/2001
Traffic-light rationale — AmberCore lawful-basis and sensitive-data concepts exist but are narrower/less granular than GDPR-aligned peers, with material change only at proposal stage.

Sub-modules (4)

Lawful basesAmber

Consent is the dominant lawful basis under current law; the Yeza bill would introduce six alternative bases including legitimate interest.

Claims (2):

  • Under the current legal framework, consent operates as the almost-exclusive lawful basis for processing personal data in Argentina.
  • The pending Yeza bill (1751-D-2026) proposes six alternative lawful bases for processing — consent, contractual performance, legal obligations, vital interests, public interest and legitimate interest — with legitimate interest expressly covering AI training subject to a rights-prevalence test.

Special categoriesAmber

Sensitive data categories are defined in the current Act; AAIP guidance addresses genetic data, and reform bills propose an expanded definition covering gender identity, genetic and biometric data.

Claims (2):

  • Reform bills propose replacing the current definition of sensitive data with a broader one covering information on private life or capable of causing discrimination or high risk, expressly listing gender identity, genetic and biometric data as examples.
  • AAIP Resolución 255/2022 sets out guiding criteria and best-practice indicators for the application of the Personal Data Protection Act with respect to genetic data.

Pseudonymisation and anonymisationRed

Neither the Act nor the Decree substantively defines pseudonymisation or anonymisation safe-harbours.

Category narrative 91 words

Consent is the near-exclusive lawful basis under the current Act, a point the pending Yeza reform bill explicitly seeks to broaden by introducing six alternative bases (consent, contract performance, legal obligation, vital interests, public interest, legitimate interest — the last expressly covering AI-model training subject to a balancing test). Special/sensitive data ('datos sensibles') are already regulated, with AAIP soft-law (Resolución 255/2022) addressing genetic data specifically; reform proposals would broaden the definition to expressly include gender identity, genetic and biometric data. Pseudonymisation/anonymisation are not substantively addressed in the current Act or Decree.

No periodic updates recorded in this cycle

Sources and claims (4)
  1. Probable IAPP — Under the current legal framework, consent operates as the almost-exclusive lawful basis for processing personal data in Argentina. observed
  2. Probable IAPP — The pending Yeza bill (1751-D-2026) proposes six alternative lawful bases for processing — consent, contractual performance, legal obligations, vital interests, public interest and legitimate interest — with legitimate interest expressly covering AI training subject to a rights-prevalence test. observed
  3. Probable IAPP — Reform bills propose replacing the current definition of sensitive data with a broader one covering information on private life or capable of causing discrimination or high risk, expressly listing gender identity, genetic and biometric data as examples. observed
  4. Confirmed IAPP — AAIP Resolución 255/2022 sets out guiding criteria and best-practice indicators for the application of the Personal Data Protection Act with respect to genetic data. observed

#

Core access/rectification/erasure rights are binding and judicially enforceable today; portability/ADM-objection rights remain at proposal stage only.

Primary frameworkLey 25.326, Arts. 14–16; Constitución Nacional Art. 43 (habeas data)
Traffic-light rationale — GreenCore access/rectification/erasure rights are binding and judicially enforceable today; portability/ADM-objection rights remain at proposal stage only.

Sub-modules (5)

Access rightGreen

Access is enforceable via habeas data, a constitutionally-entrenched simplified judicial procedure.

Claims (5):

  • The Argentine Constitution provides a special, simplified and rapid judicial remedy known as 'habeas data' to protect personal data, elevating data protection to the status of a fundamental right.
  • Habeas data is constitutionally anchored and judicially applied.
  • Ley 25.326 art. 14 — free access to personal data once every six months
  • Ley N° 25.326 — Right of access may only be exercised free of charge at intervals not less than six months, unless the data subject shows a legitimate interest for more frequent access
  • AAIP enforcement decision (2021) — AAIP fined ARS 80,000 (approx USD 733) for not attending within time/form a data subject's access/rectification/suppression request

Rectification and erasureGreen

Rectification/erasure rights are actively enforced; AAIP sanctioned Rappi for failing to act on an erasure request in time.

Claims (2):

  • AAIP sanctioned Rappi Arg S.A.S. for failing to respond in due time and form to a data subject's request for erasure of personal data.
  • A separate 2022 bill proposes a standalone 'right to be forgotten' requiring search-engine providers to implement an accessible electronic form for erasure requests, with a 10-business-day compliance window and judicial recourse for denial or inaccuracy.

Restriction and objectionAmber

Reform bills add an objection right against automated decisions producing legal or adverse effects; no current binding restriction/objection right beyond consent withdrawal identified.

Claims (1):

  • Pending reform bills introduce new data-subject rights not present in the current Act, including data portability and objection to automated decisions producing legal effects or materially adversely affecting the data subject.

Data portabilityRed

Portability is not part of the current Act; it is proposed in pending reform bills.

Claims (3):

  • Pending reform bills introduce new data-subject rights not present in the current Act, including data portability and objection to automated decisions producing legal effects or materially adversely affecting the data subject.
  • Carro / Doñate reform bills — The 2026 Carro and Doñate reform bills propose introducing a data-portability right and a right to object to automated decisions producing legal or significantly adverse effects.
  • Pending reform bills (3397-D-2026, 1751-D-2026) — Data portability and a right to object to automated decisions with legal or significantly adverse effects, rights not currently codified in Ley 25.326.

Deadlines and response windowsAmber

Reform bills propose a non-extendable 10-business-day deadline to satisfy data-subject requests, criticized by commentators as impractical.

Claims (2):

  • Pending reform bills propose a non-extendable 10-business-day deadline for controllers to satisfy data-subject rights requests, a timeframe criticized by commentators as difficult for the private sector to meet.
  • A 5-day response window is reported but unverified against the statute.
Category narrative 82 words

Data subjects currently hold rights of information, access, rectification, updating, erasure and consent-withdrawal, enforceable through the constitutionally-entrenched 'habeas data' judicial remedy. Enforcement practice confirms erasure rights are actively policed (AAIP sanctioned Rappi for failing to honor a deletion request). Pending reform bills would add portability and a right to object to automated decisions with legal or materially adverse effect, alongside a proposed (contested) 10-business-day non-extendable response deadline; a separate 2022 bill would create a standalone 'right to be forgotten' against search engines.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and claims (12)
  1. Confirmed EUR-Lex — The Argentine Constitution provides a special, simplified and rapid judicial remedy known as 'habeas data' to protect personal data, elevating data protection to the status of a fundamental right. observed
  2. Confirmed IAPP — AAIP sanctioned Rappi Arg S.A.S. for failing to respond in due time and form to a data subject's request for erasure of personal data. observed
  3. Probable IAPP — Pending reform bills introduce new data-subject rights not present in the current Act, including data portability and objection to automated decisions producing legal effects or materially adversely affecting the data subject. observed
  4. Probable IAPP — Pending reform bills propose a non-extendable 10-business-day deadline for controllers to satisfy data-subject rights requests, a timeframe criticized by commentators as difficult for the private sector to meet. observed
  5. Probable IAPP — A separate 2022 bill proposes a standalone 'right to be forgotten' requiring search-engine providers to implement an accessible electronic form for erasure requests, with a 10-business-day compliance window and judicial recourse for denial or inaccuracy. observed
  6. High IAPP — Carro / Doñate reform bills — The 2026 Carro and Doñate reform bills propose introducing a data-portability right and a right to object to automated decisions producing legal or significantly adverse effects. observed
  7. Uncertain IAPP — Pending reform bills (3397-D-2026, 1751-D-2026) — Data portability and a right to object to automated decisions with legal or significantly adverse effects, rights not currently codified in Ley 25.326. observed
  8. Probable BossBot — Habeas data is constitutionally anchored and judicially applied. observed
  9. Probable BossBot — Ley 25.326 art. 14 — free access to personal data once every six months observed
  10. Uncertain oficioia.app — A 5-day response window is reported but unverified against the statute. observed
  11. Confirmed InfoLEG, Ministerio de Justicia y Derechos Humanos de la Nación — Ley N° 25.326 — Right of access may only be exercised free of charge at intervals not less than six months, unless the data subject shows a legitimate interest for more frequent access observed
  12. Probable IAPP (International Association of Privacy Professionals) — AAIP enforcement decision (2021) — AAIP fined ARS 80,000 (approx USD 733) for not attending within time/form a data subject's access/rectification/suppression request observed

#

Foundational accountability tools exist mostly as non-binding guidance rather than statutory duties; binding DPIA/DPO/breach-notification obligations are pending, not yet in force.

Primary frameworkLey 25.326; AAIP Resolución 47/2018 (recommended security measures); AAIP DPIA Guide
Traffic-light rationale — AmberFoundational accountability tools exist mostly as non-binding guidance rather than statutory duties; binding DPIA/DPO/breach-notification obligations are pending, not yet in force.

Sub-modules (7)

Accountability & DPIAAmber

No statutory DPIA duty; AAIP has issued a non-binding DPIA Guide.

Claims (3):

  • The current Act does not provide for a requirement to conduct a Data Protection Impact Assessment, unlike the GDPR, although AAIP's non-binding Guide provides for such a practice.
  • Argentina data-protection law — Argentina's current data-protection law lacks a mandatory Data Protection Impact Assessment requirement.
  • No mandatory DPO or DPIA under current law.

DPO requirementsRed

No current DPO requirement; reform bills would introduce one.

Claims (3):

  • Unlike the GDPR, the current Act does not provide for a requirement to appoint a Data Protection Officer.
  • Pending reform bills introduce the figure of a data protection officer/delegate as a modern institute not present in the current Act.
  • Ley 25.326 regime — Legal commentary describes the absence of a mandatory data-protection-officer requirement and structural tools such as preventive/embedded compliance under the current regime.

Ropa requirementsRed

No general ROPA duty under the Act itself; sector-specific instances (e.g., RENAPER internal policy) impose GDPR-style processing records, but this is not a generalized statutory duty.

Joint controller arrangementsRed

No specific joint-controller regime identified in current law.

Security measuresAmber

AAIP Resolución 47/2018 sets recommended (non-mandatory) technical and organizational security measures.

Claims (1):

  • AAIP's Resolución 47/2018 ('Recommended Security Measures') specifies suggested security procedures for controllers, including record-keeping recommendations.

Breach notificationAmber

No general legal breach-notification obligation exists today; it is best practice only, though enforcement has penalized failure to act on breaches. Reform bills would impose a mandatory 72-hour notification duty.

Claims (8):

  • Reporting information security incidents is a best practice rather than a mandatory legal requirement under the Argentine Data Privacy Law; there is no general legal obligation to notify a data breach.
  • AAIP imposed an administrative fine on Cencosud SA after a security breach became public and the company failed to take recommended measures to prevent, notify and remedy the breach or notify affected users.
  • The AAIP-drafted data protection reform bill would impose an obligation to notify data breaches to the DPA without undue delay and within 72 hours of becoming aware, where the breach is likely to pose a risk to data subjects' rights, plus notification to affected data subjects for high-risk breaches.
  • Argentina data-protection statute — No codified data-breach notification obligation to the regulator or affected data subjects.
  • No comprehensive breach-notification regime exists.
  • No statutory breach-notification duty exists under Ley 25.326.
  • Ley 25.326 does not impose a GDPR-style breach-notification duty to the AAIP or to data subjects.
  • Resolución AAIP 47/2018 — Ley 25.326 sets no statutory duty or deadline to notify breaches; AAIP Res 47/2018 only recommends (non-binding) that controllers report a security incident to the AAIP, including nature of breach, data/subject categories affected, and mitigation measures

Retention and disposalRed

No dedicated statutory retention/disposal regime identified beyond general purpose-limitation principles.

Category narrative 83 words

The current Act imposes no DPIA or DPO obligation, though AAIP soft-law (a non-binding DPIA Guide and Resolución 47/2018 recommended security measures) fills part of the gap. There is no general legal duty to notify data breaches today — reporting is 'best practice' only — but AAIP has fined controllers (e.g., Cencosud) for failing to take recommended breach-prevention/notification steps. Pending reform bills would introduce a mandatory DPO figure and a 72-hour breach-notification duty to both AAIP and affected data subjects, mirroring GDPR-style timelines.

No periodic updates recorded in this cycle

Sources and claims (15)
  1. Confirmed DataGuidance — The current Act does not provide for a requirement to conduct a Data Protection Impact Assessment, unlike the GDPR, although AAIP's non-binding Guide provides for such a practice. observed
  2. Confirmed DataGuidance — Unlike the GDPR, the current Act does not provide for a requirement to appoint a Data Protection Officer. observed
  3. Probable IAPP — Pending reform bills introduce the figure of a data protection officer/delegate as a modern institute not present in the current Act. observed
  4. Confirmed DataGuidance — AAIP's Resolución 47/2018 ('Recommended Security Measures') specifies suggested security procedures for controllers, including record-keeping recommendations. observed
  5. Confirmed IAPP — Reporting information security incidents is a best practice rather than a mandatory legal requirement under the Argentine Data Privacy Law; there is no general legal obligation to notify a data breach. observed
  6. Confirmed IAPP — AAIP imposed an administrative fine on Cencosud SA after a security breach became public and the company failed to take recommended measures to prevent, notify and remedy the breach or notify affected users. observed
  7. Probable IAPP — The AAIP-drafted data protection reform bill would impose an obligation to notify data breaches to the DPA without undue delay and within 72 hours of becoming aware, where the breach is likely to pose a risk to data subjects' rights, plus notification to affected data subjects for high-risk breaches. observed
  8. High Diario Judicial — Argentina data-protection law — Argentina's current data-protection law lacks a mandatory Data Protection Impact Assessment requirement. observed
  9. High Diario Judicial — Argentina data-protection statute — No codified data-breach notification obligation to the regulator or affected data subjects. observed
  10. Probable Argentina.gob.ar — Ley 25.326 regime — Legal commentary describes the absence of a mandatory data-protection-officer requirement and structural tools such as preventive/embedded compliance under the current regime. observed
  11. Probable Diario Judicial — No mandatory DPO or DPIA under current law. observed
  12. Probable Diario Judicial — No comprehensive breach-notification regime exists. observed
  13. Uncertain IAPP — No statutory breach-notification duty exists under Ley 25.326. observed
  14. Probable Wikipedia — Ley 25.326 does not impose a GDPR-style breach-notification duty to the AAIP or to data subjects. observed
  15. Confirmed Agencia de Acceso a la Información Pública (AAIP) / argentina.gob.ar normativa — Resolución AAIP 47/2018 — Ley 25.326 sets no statutory duty or deadline to notify breaches; AAIP Res 47/2018 only recommends (non-binding) that controllers report a security incident to the AAIP, including nature of breach, data/subject categories affected, and mitigation measures observed

#

Adequacy-holding jurisdiction with an active, modernizing transfer-mechanism toolkit (BCRs, dual SCC regimes); no TIA or localisation mandate identified.

Primary frameworkLey 25.326, Art. 12; AAIP Resolución 198/2023 (SCC RIPD); Resolución 159/2018 (BCR guidelines)
Traffic-light rationale — GreenAdequacy-holding jurisdiction with an active, modernizing transfer-mechanism toolkit (BCRs, dual SCC regimes); no TIA or localisation mandate identified.

Sub-modules (6)

Transfer mechanismsGreen

Transfers are permitted via consent, contractual clauses, or self-regulatory systems providing adequate protection where the destination lacks an adequacy finding.

Claims (3):

  • The LPDP prohibits, in principle, international transfers of personal data to countries or international organizations lacking an adequate level of data protection, but permits such transfers where data subjects consent or where contractual clauses or self-regulatory systems guarantee adequate protection levels.
  • Ley 25.326 — Transfer of personal data to countries or international/supranational bodies not providing adequate protection levels is prohibited.
  • Ley 25.326 art. 12 governs international data transfers; AAIP Disposición 60/2016 provides model clauses.

Adequacy receivedGreen

Not applicable in the classic sense — Argentina is a data exporter jurisdiction; see adequacy_granted for the relevant inbound EU recognition.

Claims (1):

  • Commission Decision 2003/490/EC (Argentina adequacy) — EU adopted adequacy decision for Argentina 30 June 2003; the first periodic review (15 Jan 2024) confirmed transfers from EU to Argentina continue to benefit from adequate safeguards

Adequacy grantedGreen

The European Commission recognized Argentina as providing an adequate level of data protection on 30 June 2003, a decision that remains in force.

Claims (5):

  • On 30 June 2003, Argentina was recognized by the European Commission as providing an adequate level of protection for personal data.
  • European Commission — Argentina holds an EU Commission adequacy decision confirming an adequate level of data protection for personal-data transfers from the EU.
  • Argentina holds an EU adequacy decision.
  • The EU continues to recognise Argentina as providing an adequate level of data protection.
  • A draft Chamber of Deputies resolution requests the Executive, via the AAIP, report on the legal basis for Argentina's international data-transfer commitments and on which body determines third-country adequacy.

SCCs and BCRsGreen

AAIP maintains both its own model clauses (2016) and the newer RIPD Standard Contractual Clauses (2023), alongside BCR guidelines (2018).

Claims (2):

  • Via Resolución 198/2023, AAIP approved the Red Iberoamericana de Protección de Datos (RIPD) Standard Contractual Clauses for international transfers of personal data, compatible with its own pre-existing model clauses.
  • AAIP's Resolución 159/2018 established guidelines and basic content requirements for Binding Corporate Rules as a self-regulatory transfer mechanism for corporate groups.

Transfer impact assessmentRed

No formal Transfer Impact Assessment requirement analogous to Schrems II-style TIAs was identified in Argentine law or AAIP guidance.

Data localisationRed

No general data-localisation mandate was identified in the Argentine data protection framework.

Category narrative 79 words

Argentina received an EU Commission adequacy decision in 2003 — one of the earliest such findings — which remains in effect. The domestic Act prohibits transfers to jurisdictions lacking adequate protection unless the data subject consents or contractual/self-regulatory safeguards apply. AAIP has actively expanded transfer tooling: Binding Corporate Rules guidance (Resolución 159/2018) and, more recently, adoption of the Red Iberoamericana de Protección de Datos Standard Contractual Clauses (Resolución 198/2023), which coexist with Argentina's own earlier model clauses (Disposición 60-E/2016).

No periodic updates recorded in this cycle

Sources and claims (11)
  1. Confirmed EUR-Lex — On 30 June 2003, Argentina was recognized by the European Commission as providing an adequate level of protection for personal data. observed
  2. Confirmed IAPP — The LPDP prohibits, in principle, international transfers of personal data to countries or international organizations lacking an adequate level of data protection, but permits such transfers where data subjects consent or where contractual clauses or self-regulatory systems guarantee adequate protection levels. observed
  3. Confirmed IAPP — Via Resolución 198/2023, AAIP approved the Red Iberoamericana de Protección de Datos (RIPD) Standard Contractual Clauses for international transfers of personal data, compatible with its own pre-existing model clauses. observed
  4. Confirmed IAPP — AAIP's Resolución 159/2018 established guidelines and basic content requirements for Binding Corporate Rules as a self-regulatory transfer mechanism for corporate groups. observed
  5. High Argentina.gob.ar — Ley 25.326 — Transfer of personal data to countries or international/supranational bodies not providing adequate protection levels is prohibited. observed
  6. Probable Diario Judicial — European Commission — Argentina holds an EU Commission adequacy decision confirming an adequate level of data protection for personal-data transfers from the EU. observed
  7. Probable IAPP — Argentina holds an EU adequacy decision. observed
  8. Probable Diario Judicial — Ley 25.326 art. 12 governs international data transfers; AAIP Disposición 60/2016 provides model clauses. observed
  9. Probable LegalPilot — The EU continues to recognise Argentina as providing an adequate level of data protection. observed
  10. Confirmed Boletín Oficial de la República Argentina — A draft Chamber of Deputies resolution requests the Executive, via the AAIP, report on the legal basis for Argentina's international data-transfer commitments and on which body determines third-country adequacy. observed
  11. Confirmed European Commission — Commission Decision 2003/490/EC (Argentina adequacy) — EU adopted adequacy decision for Argentina 30 June 2003; the first periodic review (15 Jan 2024) confirmed transfers from EU to Argentina continue to benefit from adequate safeguards observed

#

Health and financial overlays are well-documented and active; employment, credit-scoring, education and insurance sub-modules carry no substantiated findings.

Primary frameworkLey 25.326; Ley 26.529 (Patient Rights); Ley 27.553 (Telemedicine); Ley 26.951 (No Llame); BCRA cybersecurity regulations
Traffic-light rationale — AmberHealth and financial overlays are well-documented and active; employment, credit-scoring, education and insurance sub-modules carry no substantiated findings.

Sub-modules (7)

Financial sector overlayAmber

The Central Bank of Argentina (BCRA) maintains stringent cybersecurity regulations applicable to the financial sector, overlaying general LPDP obligations.

Claims (1):

  • The Central Bank of Argentina (BCRA) maintains stringent cybersecurity regulations that financial-sector entities must adhere to in order to ensure operational resilience and maintain customer trust.

Health sector overlayGreen

Telemedicine and digital-prescription platforms must comply with both the LPDP and the Patient Rights Law, given health data's sensitive-data status.

Claims (1):

  • Ley 27.553 on electronic/digital prescriptions requires that telehealth platforms used for medical and psychological consultations comply with Ley 25.326 and the Patient Rights Law 26.529, given that health data is classified as sensitive data subject to professional-secrecy principles.

Telecoms and eprivacyAmber

The Do-Not-Call Registry regime (Ley 26.951, updated by Resolución 126/2024) governs telemarketing communications, overlapping with general data-protection enforcement.

Claims (1):

  • AAIP's Resolución 126/2024 introduced a revised classification of infractions and sanctions regime for both the Personal Data Protection Law and the Do-Not-Call Registry Law, consolidating the prior regulatory framework.

Employment dataRed

No substantiated employment-specific data-protection overlay was located in the sources reviewed.

Credit and scoringRed

No credit-scoring-specific data-protection overlay was substantiated in the sources reviewed.

educationRed

No education-sector-specific data-protection overlay was substantiated in the sources reviewed.

insuranceRed

No insurance-sector-specific data-protection overlay was substantiated in the sources reviewed.

Category narrative 70 words

Sectoral overlays are most developed in health (telemedicine/digital prescriptions must comply with both the LPDP and the Patient Rights Law 26.529, with sensitive-data confidentiality duties for health professionals) and in the Central Bank's (BCRA) cybersecurity regulations for financial-sector data. Telemarketing/direct-communications are separately regulated under the Do-Not-Call Registry Law 26.951, recently updated via Resolución 126/2024. No sector-specific findings were substantiated for employment data, credit/scoring, education, or insurance within the sources reviewed.

No periodic updates recorded in this cycle

Sources and claims (3)
  1. Confirmed IAPP — Ley 27.553 on electronic/digital prescriptions requires that telehealth platforms used for medical and psychological consultations comply with Ley 25.326 and the Patient Rights Law 26.529, given that health data is classified as sensitive data subject to professional-secrecy principles. observed
  2. Probable DataGuidance — The Central Bank of Argentina (BCRA) maintains stringent cybersecurity regulations that financial-sector entities must adhere to in order to ensure operational resilience and maintain customer trust. observed
  3. Confirmed IAPP — AAIP's Resolución 126/2024 introduced a revised classification of infractions and sanctions regime for both the Personal Data Protection Law and the Do-Not-Call Registry Law, consolidating the prior regulatory framework. observed

#

Only direct marketing (telemarketing) is substantiated; five of six sub-modules carry no evidenced Argentine-specific regime.

Primary frameworkLey 26.951 (Registro Nacional No Llame); Ley 25.326
Traffic-light rationale — RedOnly direct marketing (telemarketing) is substantiated; five of six sub-modules carry no evidenced Argentine-specific regime.

Sub-modules (6)

Cookies and trackersRed

No dedicated cookie/tracker consent regime for Argentina was located.

Dark patternsRed

No Argentina-specific dark-pattern prohibition was located.

Opt out signalsRed

No Global Privacy Control or DAA-equivalent opt-out signal recognition regime was located for Argentina.

Clean rooms and dcrRed

No clean-room / data-collaboration-room specific rules were located for Argentina.

Cross context advertisingRed

No CPRA-style 'sale'/'share' cross-context advertising framework was located for Argentina.

Direct marketingAmber

The Do-Not-Call Registry regime governs telemarketing consent/suppression, with active AAIP enforcement against unsolicited telemarketing practices.

Claims (2):

  • AAIP fined FCA Automobiles Argentina and Telefónica Móviles Argentina, each roughly ARS 10 million, for data protection violations involving unsolicited telemarketing practices.
  • Resolución AAIP 126/2024 — Approves a revised classification of infractions and a procedure/form for sanctioning breaches relating to the Registro Nacional 'No Llame' (Ley 26.951)
Category narrative 56 words

Direct marketing is the only well-substantiated sub-module: the Do-Not-Call Registry (Ley 26.951) plus AAIP enforcement (fines against FCA Automobiles Argentina and Telefónica Móviles Argentina for unsolicited telemarketing) evidence an active suppression/consent regime for telephone marketing. No dedicated cookie/tracker consent law, dark-pattern prohibition, GPC-style opt-out-signal recognition, clean-room rules, or CPRA-style cross-context 'sale/share' framework were identified for Argentina.

No periodic updates recorded in this cycle

Sources and claims (2)
  1. Confirmed DataGuidance — AAIP fined FCA Automobiles Argentina and Telefónica Móviles Argentina, each roughly ARS 10 million, for data protection violations involving unsolicited telemarketing practices. observed
  2. Confirmed Argentina.gob.ar (Boletín Oficial de la República Argentina) — Resolución AAIP 126/2024 — Approves a revised classification of infractions and a procedure/form for sanctioning breaches relating to the Registro Nacional 'No Llame' (Ley 26.951) observed

#

Existing binding guidance (Resolución 4/2019) covers automated processing/video surveillance; the more comprehensive ADM-objection right and facial-recognition-specific regime remain at bill stage.

Primary frameworkAAIP Resolución 4/2019; pending Facial Recognition Bill (Yeza); pending LPDP reform bills
Traffic-light rationale — AmberExisting binding guidance (Resolución 4/2019) covers automated processing/video surveillance; the more comprehensive ADM-objection right and facial-recognition-specific regime remain at bill stage.

Sub-modules (6)

Profiling restrictionsAmber

No dedicated profiling-restriction regime beyond the pending ADM-objection right proposal.

Claims (1):

  • Pending reform bills add a data-subject right to object to automated decisions that produce legal effects or negatively affect the data subject, a right not present in the current Act.

Automated decision making transparencyAmber

Resolución 4/2019 addresses automated data processing; reform bills add an explicit objection right for ADM with legal/adverse effect.

Claims (3):

  • AAIP's Resolución 4/2019 specifies mandatory guidelines for the application of the Act, addressing topics including video surveillance and automated data processing.
  • Pending reform bills add a data-subject right to object to automated decisions that produce legal effects or negatively affect the data subject, a right not present in the current Act.
  • Proyecto Carro/Doñate — Would introduce a right to oppose automated decisions that produce legal effects or negatively affect the data subject; no such right exists under current Ley 25.326.

AI risk assessmentsAmber

The pending facial-recognition bill requires a prior impact assessment before security-purpose deployment; AAIP separately runs an AI transparency program.

Claims (3):

  • A pending bill (deputy Yeza) establishes that facial recognition systems to be used for public-security purposes must undergo a prior impact assessment and an AAIP authorization process before implementation.
  • AAIP has created a Transparency and Protection of Personal Data Program specifically addressing the use of Artificial Intelligence.
  • AAIP Resolución 161/2023 — Non-binding guidelines for the use of AI in the public and private sectors under the existing data-protection framework.

Biometric regimeAmber

No general biometric-data statute exists; the pending facial-recognition bill is the most developed sector-specific proposal, covering authorization, prohibited uses and human-oversight requirements.

Claims (6):

  • A pending bill (deputy Yeza) establishes that facial recognition systems to be used for public-security purposes must undergo a prior impact assessment and an AAIP authorization process before implementation.
  • The pending facial-recognition bill expressly prohibits certain uses such as mass surveillance or routine tracking of persons not suspected of having committed crimes, in line with EU AI Act standards.
  • The pending facial-recognition bill requires human oversight of automated identifications performed by facial recognition systems.
  • Online gambling platforms (Argentina, sector practice) — Secondary sector-level sources report that online gambling platforms apply mandatory biometric identity verification through RENAPER, though this is a sectoral practice rather than a general AAIP biometric-data rule.
  • Disposición AAIP 4/2019 — biometric data as data obtained through a specific technical process relating to physical, physiological or behavioural characteristics permitting unique identification
  • RENAPER / Gobierno de la Ciudad de Buenos Aires (SRFP facial-recognition system) — Judicial amparo (CABA, Judge Gallardo) and MPF investigation found queries to RENAPER's database exceeded the purpose authorised by convenio with CABA for the Facial Recognition System for Fugitives, migrating exorbitant volumes of biometric data; SRFP suspended April 2022

Genetic dataAmber

Genetic data is addressed via AAIP Resolución 255/2022 best-practice guidance (see lawful_processing_and_special_data module for the underlying claim).

Claims (1):

  • AAIP Resolución 255/2022 sets out guiding criteria and best-practice indicators for the application of the Personal Data Protection Act with respect to genetic data.

State surveillance carveoutsAmber

The pending facial-recognition bill expressly prohibits mass surveillance and routine tracking of non-suspects, functioning as a proposed limitation on state-surveillance carveouts.

Claims (3):

  • The pending facial-recognition bill expressly prohibits certain uses such as mass surveillance or routine tracking of persons not suspected of having committed crimes, in line with EU AI Act standards.
  • Proyecto 1751-D-2026 / Expediente 3397-D-2026 — Competing bills to repeal and replace Ley 25.326 remain in committee with no committee report as of late September 2026
  • Expediente 3397-D-2026 — Bill to create a new data-protection regime and repeal Ley 25.326 and Ley 26.343 was introduced in the Chamber of Deputies on 16 July 2026 by Deputy Agustín Rossi
Category narrative 99 words

AAIP's Resolución 4/2019 already provides mandatory guidelines covering video surveillance and automated data processing, and AAIP has stood up a dedicated Transparency and Protection of Personal Data Program addressing AI. The most granular near-term development is deputy Yeza's dedicated facial-recognition bill, which would require a prior impact assessment and AAIP authorization before deployment for public-security purposes, expressly ban mass surveillance/routine tracking of non-suspects, and mandate human oversight of automated identifications — explicitly modeled on EU AI Act standards. Separately, the broader LPDP reform bills would add a right to object to automated decisions with legal or materially adverse effect.

No periodic updates recorded in this cycle

Sources and claims (13)
  1. Probable IAPP — A pending bill (deputy Yeza) establishes that facial recognition systems to be used for public-security purposes must undergo a prior impact assessment and an AAIP authorization process before implementation. observed
  2. Probable IAPP — The pending facial-recognition bill expressly prohibits certain uses such as mass surveillance or routine tracking of persons not suspected of having committed crimes, in line with EU AI Act standards. observed
  3. Probable IAPP — The pending facial-recognition bill requires human oversight of automated identifications performed by facial recognition systems. observed
  4. Confirmed IAPP — AAIP has created a Transparency and Protection of Personal Data Program specifically addressing the use of Artificial Intelligence. observed
  5. Confirmed DataGuidance — AAIP's Resolución 4/2019 specifies mandatory guidelines for the application of the Act, addressing topics including video surveillance and automated data processing. observed
  6. Probable IAPP — Pending reform bills add a data-subject right to object to automated decisions that produce legal effects or negatively affect the data subject, a right not present in the current Act. observed
  7. High BDO Argentina — AAIP Resolución 161/2023 — Non-binding guidelines for the use of AI in the public and private sectors under the existing data-protection framework. observed
  8. Uncertain LegalPilot — Online gambling platforms (Argentina, sector practice) — Secondary sector-level sources report that online gambling platforms apply mandatory biometric identity verification through RENAPER, though this is a sectoral practice rather than a general AAIP biometric-data rule. observed
  9. Probable IAPP — Proyecto Carro/Doñate — Would introduce a right to oppose automated decisions that produce legal effects or negatively affect the data subject; no such right exists under current Ley 25.326. observed
  10. Probable Abogados.com.ar — Disposición AAIP 4/2019 — biometric data as data obtained through a specific technical process relating to physical, physiological or behavioural characteristics permitting unique identification observed
  11. Probable IAPP — Proyecto 1751-D-2026 / Expediente 3397-D-2026 — Competing bills to repeal and replace Ley 25.326 remain in committee with no committee report as of late September 2026 observed
  12. Confirmed Ministerio Público Fiscal de la Nación (Argentina) — RENAPER / Gobierno de la Ciudad de Buenos Aires (SRFP facial-recognition system) — Judicial amparo (CABA, Judge Gallardo) and MPF investigation found queries to RENAPER's database exceeded the purpose authorised by convenio with CABA for the Facial Recognition System for Fugitives, migrating exorbitant volumes of biometric data; SRFP suspended April 2022 observed
  13. Probable Abogados.com.ar — Expediente 3397-D-2026 — Bill to create a new data-protection regime and repeal Ley 25.326 and Ley 26.343 was introduced in the Chamber of Deputies on 16 July 2026 by Deputy Agustín Rossi observed

#

Binding coverage of children's data exists only via soft-law guidance (Resolución 4/2019); dedicated statutory minor-protection provisions remain at proposal stage, and three of five sub-modules are unsubstantiated.

Primary frameworkAAIP Resolución 4/2019; pending LPDP reform bills
Traffic-light rationale — AmberBinding coverage of children's data exists only via soft-law guidance (Resolución 4/2019); dedicated statutory minor-protection provisions remain at proposal stage, and three of five sub-modules are unsubstantiated.

Sub-modules (5)

Age verificationRed

No dedicated statutory age-verification mechanism was located.

Minor profiling bansRed

No dedicated minor-profiling ban was located.

Education settingsRed

No education-settings-specific children's-data rule was located.

Dependent adultsRed

No dependent-adult-specific data protection provision was located.

Category narrative 59 words

The current Act does not refer to children at all; AAIP's Resolución 4/2019 fills part of the gap by requiring consent for processing children's data. Pending reform bills would specifically regulate minors' personal data, generally treating consent given by persons aged 16 or older as valid. No substantiated findings were located for minor-profiling bans, education-settings-specific rules, or dependent-adult protections.

No periodic updates recorded in this cycle

Sources and claims (3)
  1. Confirmed DataGuidance — Although the current Act does not refer to children, AAIP's Resolución 4/2019 provides for a requirement to obtain consent when processing children's personal data. observed
  2. Probable IAPP — A pending reform bill specifically regulates the processing of minors' personal data, generally treating consent given by persons sixteen years of age or older for the processing of their personal data as valid. observed
  3. Confirmed BDO Argentina — AAIP maintains published materials directed at safeguarding the data-protection rights of children and adolescents in digital environments. observed

#

Regulator is demonstrably active with a documented inspection/sanction track record and a judicially-enforceable private remedy; amber-tending on funding/capacity and collective-redress sub-modules, which are unsubstantiated.

Primary frameworkLey 25.326, Art. 31; AAIP Resolución 332/2020 (Guía de Fiscalización); Constitución Nacional Art. 43 (habeas data)
Traffic-light rationale — GreenRegulator is demonstrably active with a documented inspection/sanction track record and a judicially-enforceable private remedy; amber-tending on funding/capacity and collective-redress sub-modules, which are unsubstantiated.

Sub-modules (6)

Regulator powers and penaltiesGreen

AAIP holds investigative/inspection powers (Resolución 332/2020) and applies penalties under Art. 31 LPDP; a reform would raise ceilings materially, including a global-turnover-based option.

Claims (11):

  • AAIP's Guía de Fiscalización (Resolución 332/2020) empowers it to conduct planned or spontaneous inspections, request judicial authorization where a subject fails to cooperate, and use verbal, visual, documentary and technical investigation techniques.
  • A pending reform proposes fines set between five and one million movable accounting units (based on an initial unit value of ARS 10,000), with the AAIP's own bill version adding an alternative graduation of 2% to 4% of the infringer's total global annual turnover.
  • Resolución AAIP N° 126/2024 — Modernised the AAIP's sanctions regime by indexing fines to an 'unidad móvil' initially set at AR$100,000 with semi-annual updates, in force from 1 June 2024.
  • AAIP maintains a public Registro de Infractores de las leyes 25.326 y 26.951 and a formal electronic voluntary-payment mechanism (VEP/QR/Boleta de Pago) for assessed fines.
  • AAIP applies tiered fine bands per secondary reporting.
  • Ley 25.326 arts. 29-31 grant AAIP a tiered sanction power, graded by Resolución 126/2024.
  • On 2 November 2026 the AAIP sanctioned 5 ON LINE S.R.L. by suspending its database until its personal-data processing complies with Ley 25.326.
  • On 2 November 2026 the AAIP sanctioned a separate company for failing to provide requested information in an Art. 16 erasure-duty investigation.
  • Resolución AAIP 126/2024 — Repeals Disposición DNPDP 7/05 and AAIP Resoluciones 12/18, 240/22, 243/19 and 244/22 (sanctions/graduation regime for Ley 25.326 and No Llame registry breaches), with effect from entry into force
  • Resolución AAIP 126/2024 — Approves classification of infractions and sanction-graduation regime for Ley 25.326 and Ley 26.951: minor/serious/very serious; fine ARS 1,000-100,000 under Art 31; very serious band ARS 90,001-100,000, serious ARS 80,001-90,000
  • AAIP enforcement decision (database registration, 2021) — AAIP dismissed imputation for late database registration (subsanada) but fined ARS 30,001 (approx USD 275) for remaining infractions

Enforcement activity indexGreen

AAIP issued 63 resolutions in 2022 alone, 52 of them sanctionatory, evidencing sustained enforcement activity; more recent fines (FCA Automobiles, Telefónica) confirm continuity.

Claims (5):

  • In 2022, AAIP opened 491 complaint files under the Personal Data Protection Law (27% more than 2021) and issued 63 resolutions, 52 of which were sanctionatory, imposing fines totaling approximately ARS 7,383,061.
  • AAIP — Sanctioned Rappi Arg S.A.S. for failing to timely respond to a data-subject deletion request.
  • AAIP sanctioning action, 2 November 2026 — AAIP sanctioned companies for unlawful processing in telephone debt-collection and reprimanded Banco de Galicia
  • AAIP inspection procedure (sporting associations, 2021) — AAIP required entities to state compliance with data-protection duties within a 15-business-day administrative deadline under Art 29 inspection powers
  • AAIP sanctioning action, 2 November 2026 — AAIP sanctioned companies for unlawful processing in telephone debt-collection and issued a reprimand (apercibimiento) to Banco de Galicia y Buenos Aires S.A.U. for failing to provide information requested in an Art 16 erasure-duty investigation

Regulator funding and capacityAmber

No specific budget or headcount data for AAIP was substantiated in the sources reviewed.

Claims (1):

  • AAIP — mainly reactive and complaint-dependent supervisory model, with fines described as low relative to international standards

Collective redress and class actionsAmber

No data-protection-specific collective-redress or class-action mechanism was substantiated in the sources reviewed.

Private right of actionGreen

The constitutionally-entrenched habeas data remedy provides data subjects a direct judicial avenue independent of AAIP's administrative process.

Claims (1):

  • Argentine legislation provides effective and dissuasive sanctions, both administrative and criminal, and enforcement of data protection rules is guaranteed through the special, simplified and rapid habeas data judicial remedy alongside general judicial remedies.

Recent developments 180dAmber

Within the last 180 days, two Congressional reform bills (Carro, Doñate) were introduced (reported February 2026) alongside an independently-filed comprehensive replacement bill by deputy Yeza (1751-D-2026, reported June 2026); none has been enacted as of the run date.

Claims (4):

  • Two bills recently introduced in Congress — one by deputy Pablo Carro and another by senator Martín Doñate — propose a comprehensive reform of Ley 25.326, inspired by the AAIP's own draft that lost parliamentary status at the end of 2024.
  • A new bill (project 1751-D-2026) filed by deputy Martín Yeza proposes to entirely replace the current Personal Data Protection Law with a 72-article, 13-title framework expressly repealing the current law and its regulations, drawing on South Korean, UK and Singaporean models plus GDPR influence.
  • Deputy Agustín Rossi — On 16 July 2026, expediente 3397-D-2026 was introduced in the Chamber of Deputies, proposing a new comprehensive data-protection regime and the repeal of Leyes 25.326 and 26.343, substantially reproducing the AAIP-drafted bill from June 2023.
  • Deputy Martín Yeza — Expediente 1751-D-2026 proposes a fresh 72-article regime across 13 titles that would expressly repeal the current statute and its implementing regulations.
Category narrative 149 words

AAIP exercises active investigative and sanctioning powers under its Guía de Fiscalización (Resolución 332/2020), including planned and spontaneous inspections and the ability to seek judicial authorization when a subject fails to cooperate. Current sanctions are set under Article 31 of the LPDP; a pending reform (mirrored in both the AAIP-drafted bill and other Congressional projects) would substantially raise the ceiling — fines expressed in movable accounting units up to one million units, and in the AAIP version alternatively graduated at 2–4% of the infringer's global annual turnover. 2022 enforcement data show 491 complaint files opened (up 27% year-on-year) and 63 resolutions issued, 52 of them sanctionatory. The constitutionally-entrenched habeas data remedy affords a private right of action independent of AAIP's administrative process. Recent 180-day developments include the Carro and Doñate reform bills (Feb 2026) and the independently-filed Yeza bill 1751-D-2026 (June 2026), none of which have yet been enacted.

Periodic update · new data 2026-11-08

Argentina's Agencia de Acceso a la Información Pública (AAIP) published two sanction decisions on 2 November 2026, marking an active enforcement day under Ley N° 25.326 de Protección de los Datos Personales. The AAIP sanctioned 5 ON LINE S.R.L. by suspending its database until the company's personal-data processing complies with the statute, following an investigation opened in April 2026 into alleged unlawful processing in connection with debt-collection activity. In a separate decision issued the same day, the AAIP sanctioned a second, unnamed company for failing to provide information the regulator had requested in the course of an investigation into compliance with the Article 16 erasure duty. The identity of the second sanctioned entity and the specific penalty amount were not disclosed in the material available.

Taken together, the two decisions illustrate the AAIP exercising two distinct enforcement powers in parallel: a substantive sanction tied to the underlying lawfulness of processing in a specific commercial context, and a procedural sanction tied to a regulated entity's failure to cooperate with an active investigation. The database-suspension remedy against 5 ON LINE S.R.L. is a structurally significant enforcement tool, as it operates on the processing activity itself rather than imposing a purely monetary consequence, and it followed a seven-month investigation period from opening to decision. The non-cooperation sanction, by contrast, signals that the AAIP treats a regulated entity's responsiveness to its own information requests as independently enforceable, separate from any eventual finding on the underlying erasure-duty complaint. Both actions sit against a statutory backdrop, Ley 25.326, that was enacted well before the GDPR-era wave of breach-notification and accountability obligations, meaning Argentina's enforcement activity under this framework proceeds without the breach-notification trigger that drives a large share of enforcement casework in GDPR-aligned regimes.

The two decisions extend a pattern of enforcement activity already associated with the Ley 25.326 regime, in which the AAIP has used database suspension as a remedy of first resort against unlawful processing by commercial actors. The 5 ON LINE S.R.L. matter, with its basis in debt-collection-related processing, places this enforcement action within a recognisable sectoral pattern: debt-collection and credit-reporting activity has repeatedly drawn AAIP scrutiny, reflecting the tension between the sector's reliance on personal data and the statute's baseline lawfulness requirements. The Article 16 non-cooperation sanction is less common in the public record and signals that procedural obligations toward the regulator carry independent enforcement weight, not merely as an adjunct to a substantive finding.

Outlook

The amount and legal basis of the penalty imposed in the Article 16 non-cooperation matter, together with the identity of the sanctioned company, remain unconfirmed in the material reviewed; disclosure of the AAIP's full decision would clarify both. For 5 ON LINE S.R.L., the suspension remains in force until the company demonstrates compliant processing, so the practical question going forward is whether and when the company satisfies that condition and the suspension is lifted. More broadly, two enforcement decisions issued on a single day indicate the AAIP is maintaining an active caseload under Ley 25.326 notwithstanding the absence of a GDPR-style breach-notification duty in the statute, and further decisions arising from the same investigative docket would be the next indicator to watch.

1 earlier distinct update
Periodic update · new data 2026-09-28

Argentina's legislative reform picture escalated this cycle with the introduction of a third distinct comprehensive data-protection reform bill. On 16 July 2026, Deputy Agustin Rossi introduced expediente 3397-D-2026 in the Chamber of Deputies. The bill proposes a new comprehensive data-protection regime and would repeal both Ley 25.326, the operative statute, and Ley 26.343. Notably, the bill substantially reproduces the text of a bill originally drafted by the AAIP itself and circulated in June 2023, suggesting continuity of substantive policy content across what is otherwise a change in legislative sponsor and vehicle.

This joins expediente 1751-D-2026, proposed by Deputy Martin Yeza and reported previously, which sets out an entirely fresh 72-article regime organised across 13 titles and would expressly repeal both the current statute and its implementing regulations. Between these two bills and the underlying June 2023 AAIP proposal that expediente 3397-D-2026 substantially reproduces, Argentina's Congress now has multiple, only partially overlapping, comprehensive reform vehicles under simultaneous consideration. Neither bill has advanced to enactment, and neither has been reported as having secured committee approval or a floor vote timeline.

Separately, on the existing enforcement infrastructure, the Agencia de Acceso a la Informacion Publica maintains a public Registro de Infractores de las leyes 25.326 y 26.951, together with a formal electronic voluntary-payment mechanism, described variously as VEP, QR, or Boleta de Pago, for the payment of assessed fines. This is a standing enforcement-transparency mechanism under the current regime and represents no change this cycle, but it underscores that the current AAIP enforcement apparatus, however dated the substantive statute it enforces may be considered by reform proponents, continues to operate with a functioning public transparency and payment-collection infrastructure.

The overall picture for enforcement and redress in Argentina this cycle is therefore one of legislative escalation layered on top of a stable, functioning, if dated, enforcement infrastructure: the AAIP continues to operate its existing enforcement tools under Ley 25.326 without interruption, while the legislative branch pursues, in parallel, at least two and arguably three distinct paths toward eventually replacing that statute altogether.

Outlook

With three broadly comprehensive reform proposals now in play, expediente 3397-D-2026, expediente 1751-D-2026, and the AAIP's own June 2023 text that the former substantially reproduces, the near-term question is not whether reform will eventually occur but which vehicle, if any, gains legislative traction first. Watch for committee assignment or hearing scheduling on either numbered expediente, or for any move to consolidate the competing texts into a single bill, as the clearest indicators of which reform path is gaining momentum.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (22)
  1. Confirmed IAPP — AAIP's Guía de Fiscalización (Resolución 332/2020) empowers it to conduct planned or spontaneous inspections, request judicial authorization where a subject fails to cooperate, and use verbal, visual, documentary and technical investigation techniques. observed
  2. Probable IAPP — A pending reform proposes fines set between five and one million movable accounting units (based on an initial unit value of ARS 10,000), with the AAIP's own bill version adding an alternative graduation of 2% to 4% of the infringer's total global annual turnover. observed
  3. Confirmed IAPP — In 2022, AAIP opened 491 complaint files under the Personal Data Protection Law (27% more than 2021) and issued 63 resolutions, 52 of which were sanctionatory, imposing fines totaling approximately ARS 7,383,061. observed
  4. Confirmed EUR-Lex — Argentine legislation provides effective and dissuasive sanctions, both administrative and criminal, and enforcement of data protection rules is guaranteed through the special, simplified and rapid habeas data judicial remedy alongside general judicial remedies. observed
  5. Confirmed IAPP — Two bills recently introduced in Congress — one by deputy Pablo Carro and another by senator Martín Doñate — propose a comprehensive reform of Ley 25.326, inspired by the AAIP's own draft that lost parliamentary status at the end of 2024. observed
  6. Confirmed IAPP — A new bill (project 1751-D-2026) filed by deputy Martín Yeza proposes to entirely replace the current Personal Data Protection Law with a 72-article, 13-title framework expressly repealing the current law and its regulations, drawing on South Korean, UK and Singaporean models plus GDPR influence. observed
  7. Probable Argentina.gob.ar / AAIP — Deputy Agustín Rossi — On 16 July 2026, expediente 3397-D-2026 was introduced in the Chamber of Deputies, proposing a new comprehensive data-protection regime and the repeal of Leyes 25.326 and 26.343, substantially reproducing the AAIP-drafted bill from June 2023. observed
  8. Probable Wikipedia — Deputy Martín Yeza — Expediente 1751-D-2026 proposes a fresh 72-article regime across 13 titles that would expressly repeal the current statute and its implementing regulations. observed
  9. High La Defensa — Resolución AAIP N° 126/2024 — Modernised the AAIP's sanctions regime by indexing fines to an 'unidad móvil' initially set at AR$100,000 with semi-annual updates, in force from 1 June 2024. observed
  10. High IAPP — AAIP — Sanctioned Rappi Arg S.A.S. for failing to timely respond to a data-subject deletion request. observed
  11. Confirmed BDO Argentina — AAIP maintains a public Registro de Infractores de las leyes 25.326 y 26.951 and a formal electronic voluntary-payment mechanism (VEP/QR/Boleta de Pago) for assessed fines. observed
  12. Uncertain foro.ar — AAIP applies tiered fine bands per secondary reporting. observed
  13. Probable oficioia.app — AAIP — mainly reactive and complaint-dependent supervisory model, with fines described as low relative to international standards observed
  14. Probable Wikipedia — Ley 25.326 arts. 29-31 grant AAIP a tiered sanction power, graded by Resolución 126/2024. observed
  15. Confirmed Argentina.gob.ar — On 2 November 2026 the AAIP sanctioned 5 ON LINE S.R.L. by suspending its database until its personal-data processing complies with Ley 25.326. observed
  16. Confirmed Argentina.gob.ar — On 2 November 2026 the AAIP sanctioned a separate company for failing to provide requested information in an Art. 16 erasure-duty investigation. observed
  17. Confirmed Agencia de Acceso a la Información Pública (AAIP) / Argentina.gob.ar — AAIP sanctioning action, 2 November 2026 — AAIP sanctioned companies for unlawful processing in telephone debt-collection and reprimanded Banco de Galicia observed
  18. Confirmed Argentina.gob.ar (Boletín Oficial de la República Argentina) — Resolución AAIP 126/2024 — Repeals Disposición DNPDP 7/05 and AAIP Resoluciones 12/18, 240/22, 243/19 and 244/22 (sanctions/graduation regime for Ley 25.326 and No Llame registry breaches), with effect from entry into force observed
  19. Probable Boletín Oficial de la República Argentina — Resolución AAIP 126/2024 — Approves classification of infractions and sanction-graduation regime for Ley 25.326 and Ley 26.951: minor/serious/very serious; fine ARS 1,000-100,000 under Art 31; very serious band ARS 90,001-100,000, serious ARS 80,001-90,000 observed
  20. Probable IAPP (International Association of Privacy Professionals) — AAIP inspection procedure (sporting associations, 2021) — AAIP required entities to state compliance with data-protection duties within a 15-business-day administrative deadline under Art 29 inspection powers observed
  21. Probable IAPP (International Association of Privacy Professionals) — AAIP enforcement decision (database registration, 2021) — AAIP dismissed imputation for late database registration (subsanada) but fined ARS 30,001 (approx USD 275) for remaining infractions observed
  22. Confirmed Agencia de Acceso a la Información Pública (AAIP) / Argentina.gob.ar — AAIP sanctioning action, 2 November 2026 — AAIP sanctioned companies for unlawful processing in telephone debt-collection and issued a reprimand (apercibimiento) to Banco de Galicia y Buenos Aires S.A.U. for failing to provide information requested in an Art 16 erasure-duty investigation observed
No categories match.

No categories match your current search or filter selection.

Provenance and declared absence

Disclosure model: category cards load OPEN; narratives render in full; standing narratives load as a clamped teaser with an explicit “read full” control carrying the true word count. No text is hidden without disclosing how much of it there is.

Sub-modules are DP-specific nested subsections with their own real per-sub-module traffic light, rendered under each category across all regulatory modules.

Traffic-light dots are REAL data (baseline.<category>.traffic_light), not renderer-invented taxonomy, and are never suppressed -- unlike WPM, where a RAG dot would be forbidden as invented severity.

Family/accent taxonomy is renderer-level presentation config, not a JID field; it decorates the RAG dot, it does not replace it. Colour is always duplicated in text and is never the sole carrier of meaning.

Suppressed by doctrine: derived risk score. Not shown on this page.

Band honesty: uncertainty bands are computed against a frozen build clock of 2026-11-17. A year-precision row is never promoted into a tighter band.

Envelope: baseline resolved at jurisdiction_json.baseline; 10 categories, 57 sub-module(s), 106 claim(s) (106 category placement(s)), 64 source(s) in the cumulative register.

Audit trail

Machine checkChallenged on 17 Nov 2026: not upheld (36 confirmed against the cited source; 2 contradicted by the cited source; 17 could not be checked). An automated, adversarial test run by a second model; no person has assessed the result.

Think something on this page is wrong? Report an error.

GDPR article map

Cross-reference: which category/sub-module covers each UK GDPR article (37 mapped).

Show article map
GDPR article to category mapping
ArticleCategorySub-module
Art. 5Controller/Processor Dutiesaccountability and dpia
Art. 6Lawful Processing & Special Datalawful bases
Art. 7Lawful Processing & Special Dataconsent thresholds
Art. 9Lawful Processing & Special Dataspecial categories
Art. 13Data Subject Rightsaccess right
Art. 14Data Subject Rightsaccess right
Art. 15Data Subject Rightsaccess right
Art. 16Data Subject Rightsrectification and erasure
Art. 17Data Subject Rightsrectification and erasure
Art. 18Data Subject Rightsrestriction and objection
Art. 19Data Subject Rightsrestriction and objection
Art. 20Data Subject Rightsdata portability
Art. 21Data Subject Rightsrestriction and objection
Art. 22Algorithmic, Biometric & Surveillance Governanceautomated decision making transparency
Art. 25Controller/Processor Dutiesaccountability and dpia
Art. 28Controller/Processor Dutiesjoint controller arrangements
Art. 30Controller/Processor Dutiesropa requirements
Art. 32Controller/Processor Dutiessecurity measures
Art. 33Controller/Processor Dutiesbreach notification
Art. 34Controller/Processor Dutiesbreach notification
Art. 35Controller/Processor Dutiesaccountability and dpia
Art. 37Controller/Processor Dutiesdpo requirements
Art. 38Controller/Processor Dutiesdpo requirements
Art. 39Controller/Processor Dutiesdpo requirements
Art. 44Cross-Border & Adequacytransfer mechanisms
Art. 45Cross-Border & Adequacyadequacy granted
Art. 46Cross-Border & Adequacysccs and bcrs
Art. 47Cross-Border & Adequacysccs and bcrs
Art. 48Cross-Border & Adequacytransfer mechanisms
Art. 49Cross-Border & Adequacytransfer mechanisms
Art. 77Enforcement & Redressprivate right of action
Art. 78Enforcement & Redressprivate right of action
Art. 79Enforcement & Redressprivate right of action
Art. 80Enforcement & Redresscollective redress and class actions
Art. 82Enforcement & Redressprivate right of action
Art. 83Enforcement & Redressregulator powers and penalties
Art. 84Enforcement & Redressregulator powers and penalties