Data Protection Monitor
Global Privacy & Data Protection Intelligence

Arizona, USA Data Protection & Privacy Regulation

US-AZ schema gdpri-v2 trajectory: not yet assessed regulated (sectoral) overlaps: artificial-intelligence

Last updated · 10 categories · 46 claims · 34 sources in the cumulative register

Arizona's HB2861, which would require social media platforms to enable high-level privacy protections by default for minor users, passed the Arizona House in 2025, but its Senate and gubernatorial status remains unconfirmed at the time of this cycle's research.

Data collected Data published

AI-assembled from cited sources

Not covered: Cross-Border & Adequacy. Not fully checked this cycle: Regulator & Framework, Children & Vulnerable Groups (2 open gaps).

Framework & posture10 of 10 modules active
10 active · 10 binding instruments
Supervisory authorityArizona Attorney General
Next milestoneNo upcoming dated milestone on record
Record & confidence mix46 claims · 32 sources · machine-compiled
3 Confirmed30 Probable12 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

United States federal law that applies in Arizona, USA is covered once, on the United States page. This page covers Arizona, USA’s own layer: its own law, regulators and enforcement.

Jurisdiction brief

Latest update · 4 November 2026

Lead Signal

Arizona Attorney General Kris Mayes filed suit against OpenAI in Maricopa County Superior Court on 14 October 2026 under the Arizona Consumer Fraud Act, alleging deceptive design and marketing of ChatGPT that exposed Arizona minors to undisclosed harms and facilitated the collection of sensitive personal data without adequate disclosure. The filing was one of eight coordinated state actions brought the same day, alongside Iowa, Kansas, Nebraska, West Virginia, Arkansas, Idaho and Montana, signaling a deliberate multistate enforcement push against a single AI company's consumer-facing data practices.

Key regulatory facts for Arizona, USA
Key regulatory facts for Arizona, USA
Regulatory DimensionArizona, USA Standing Position
JurisdictionArizona, USA (US-AZ)
Regulatory ScopeData Protection & Privacy Regulation (10 modules, 46 sourced findings)
Regulator & FrameworkA named regulator and concrete instruments exist (breach notification statute, Consumer Fraud Act), but there is no comprehensive framework defining lawful bases, subject rights or controller obligations.
Lawful Processing & Special DataNo omnibus lawful-basis, consent, or special-category regime exists at the state level; only a narrow genetic-testing carve-out was identified.
Data Subject RightsNo comprehensive data-subject-rights regime exists in Arizona; this is a legitimate structural gap rather than an omission.
Controller/Processor DutiesBreach notification is a real, enforceable duty; the remaining accountability infrastructure (DPIA, DPO, ROPA, retention) is absent at state level.
Primary Instruments CitedRecording Law, Arizona, USA Official Instrument (recordinglaw.com arizona-data-privacy-laws), Arizona, USA Official Instrument (courtdocket.org arizona-privacy-laws-data-breach), IAPP, Security.org
Last Confirmed / Updated (34 sources in cumulative register)

#

A named regulator and concrete instruments exist (breach notification statute, Consumer Fraud Act), but there is no comprehensive framework defining lawful bases, subject rights or controller obligations.

Primary frameworkArizona Revised Statutes §18-552 (breach notification) and Arizona Consumer Fraud Act A.R.S. §44-1521 et seq.
Supervisory authorityArizona Attorney General
Traffic-light rationale — AmberA named regulator and concrete instruments exist (breach notification statute, Consumer Fraud Act), but there is no comprehensive framework defining lawful bases, subject rights or controller obligations.

Sub-modules (5)

Regulator and authorityAmber

The Arizona Attorney General enforces breach-notification and consumer-fraud statutes touching personal data; there is no standalone data-protection regulator.

Claims (3):

  • The Arizona Attorney General is the primary enforcement authority for data-breach notification and consumer-data-practice violations in Arizona, in the absence of a dedicated data-protection regulator.
  • Arizona Attorney General — Arizona's breach-notification statute (A.R.S. §18-552) and the Consumer Fraud Act; no dedicated data-protection authority exists.
  • Arizona Attorney General — A.R.S. § 18-552 requires a person conducting business in Arizona that owns, maintains or licenses unencrypted and unredacted computerized personal information to notify affected individuals following a security system breach, with the Attorney General as sole enforcer and no private right of action.

Act and instrumentsAmber

Primary instruments are the breach-notification statute (A.R.S. §18-552, amended by HB2146 in 2022) and the Consumer Fraud Act; no comprehensive privacy bill has been passed despite repeated legislative attempts.

Claims (4):

  • Arizona currently has no comprehensive consumer-privacy statute; recent legislative attempts to pass general privacy legislation have not been enacted.
  • Breach and data-security requirements in Arizona are governed by the state's breach-notification law under §18-552 of the Arizona Revised Statutes, which requires notification to consumers and to the Arizona Attorney General or the Arizona Department of Homeland Security.
  • SB1815 (Arizona comprehensive privacy bill) — SB1815, introduced 2026-02-09, defining 'child' as under 16, died in committee 2026-06-14, leaving Arizona without an omnibus privacy statute.
  • SB 1815, Arizona's most recent comprehensive consumer-privacy bill, died in committee on 2026-06-14 and is not law.

Material scopeAmber

The breach-notification statute's material scope was expanded by the 2022 amendment to broaden the definition of covered personal information, but AZ has no general material-scope definition of 'personal data' or 'processing' comparable to omnibus regimes.

Claims (2):

  • HB 2146, signed by the Arizona Governor on 29 March 2022, amended A.R.S. §18-552 and expanded the definition of personal information subject to breach-notification duties, while also introducing a 45-day notification deadline.
  • Arizona has not enacted a comprehensive consumer data-privacy statute; Arizona residents do not have general statutory rights to access, correct, or delete personal data that private businesses hold about them, outside narrow contexts such as genetic testing and student data.

Territorial scopeAmber

No AZ-specific territorial-scope provision was located extending obligations to non-established controllers; the breach statute is understood to apply based on the residency of affected individuals rather than controller location, consistent with the general pattern of US state breach laws, but this has not been independently verified for Arizona in this run.

Regulator registration and filingAmber

Arizona imposes no general controller registration or filing regime; the only filing-type obligation is notification to the AG/Department of Homeland Security for breaches affecting more than 1,000 residents.

Claims (1):

  • For breaches affecting more than 1,000 Arizona residents, HB 2146 requires notification to the three largest nationwide consumer-reporting agencies in addition to the Attorney General and the Arizona Department of Homeland Security.
Category narrative 65 words

Arizona has no dedicated data-protection authority and no omnibus consumer-privacy statute. The Arizona Attorney General (AG) is the de facto regulator, exercising authority under the state's general breach-notification statute (A.R.S. §18-552) and the Arizona Consumer Fraud Act (A.R.S. §44-1521 et seq.) for deceptive/unfair data practices. Federal FTC Act Section 5 provides an additional reactive baseline. There is no AZ-specific registration or filing regime for controllers.

Sources and claims (10)
  1. Confirmed OneTrust DataGuidance — The Arizona Attorney General is the primary enforcement authority for data-breach notification and consumer-data-practice violations in Arizona, in the absence of a dedicated data-protection regulator. observed
  2. Confirmed OneTrust DataGuidance — Arizona currently has no comprehensive consumer-privacy statute; recent legislative attempts to pass general privacy legislation have not been enacted. observed
  3. Confirmed OneTrust DataGuidance — Breach and data-security requirements in Arizona are governed by the state's breach-notification law under §18-552 of the Arizona Revised Statutes, which requires notification to consumers and to the Arizona Attorney General or the Arizona Department of Homeland Security. observed
  4. Confirmed OneTrust DataGuidance — HB 2146, signed by the Arizona Governor on 29 March 2022, amended A.R.S. §18-552 and expanded the definition of personal information subject to breach-notification duties, while also introducing a 45-day notification deadline. observed
  5. Confirmed OneTrust DataGuidance — For breaches affecting more than 1,000 Arizona residents, HB 2146 requires notification to the three largest nationwide consumer-reporting agencies in addition to the Attorney General and the Arizona Department of Homeland Security. observed
  6. Probable https://www.recordinglaw.com/us-laws/data-privacy-laws/arizona-data-privacy-laws/ — Arizona Attorney General — Arizona's breach-notification statute (A.R.S. §18-552) and the Consumer Fraud Act; no dedicated data-protection authority exists.
  7. Probable DLA Piper — SB1815 (Arizona comprehensive privacy bill) — SB1815, introduced 2026-02-09, defining 'child' as under 16, died in committee 2026-06-14, leaving Arizona without an omnibus privacy statute. observed
  8. Probable Tucson Sentinel — SB 1815, Arizona's most recent comprehensive consumer-privacy bill, died in committee on 2026-06-14 and is not law. observed
  9. Probable https://courtdocket.org/arizona-privacy-laws-data-breaches-recording-and-surveillance/ — Arizona has not enacted a comprehensive consumer data-privacy statute; Arizona residents do not have general statutory rights to access, correct, or delete personal data that private businesses hold about them, outside narrow contexts such as genetic testing and student data.
  10. Probable Arizona Attorney General's Office — Arizona Attorney General — A.R.S. § 18-552 requires a person conducting business in Arizona that owns, maintains or licenses unencrypted and unredacted computerized personal information to notify affected individuals following a security system breach, with the Attorney General as sole enforcer and no private right of action. observed

#

No omnibus lawful-basis, consent, or special-category regime exists at the state level; only a narrow genetic-testing carve-out was identified.

Supervisory authorityArizona Attorney General
Traffic-light rationale — RedNo omnibus lawful-basis, consent, or special-category regime exists at the state level; only a narrow genetic-testing carve-out was identified.

Sub-modules (4)

Lawful basesRed

No AZ statute enumerates lawful bases for processing personal data comparable to GDPR Art 6; absent a comprehensive privacy law, processing is unconstrained except where sector-specific federal law applies.

Special categoriesAmber

Arizona is one of a group of states with a statute specifically regulating direct-to-consumer genetic-testing companies; outside genetic data, no general special/sensitive-category regime exists at state level.

Claims (3):

  • Arizona is among twelve US states (alongside Alabama, California, Kentucky, Maryland, Montana, Tennessee, Texas, Utah, Virginia, Wyoming and Nebraska) with a statute specifically governing direct-to-consumer genetic-testing companies.
  • Arizona Genetic Information Privacy Act — narrow special-category-equivalent protection in place of a GDPR-style enumerated special-categories rule
  • Arizona Genetic Information Privacy Act (A.R.S. Title 44, Ch. 38) — A narrowly scoped statute applying only to direct-to-consumer genetic testing companies, effective 29 Sep 2021, requiring layered consent and giving consumers rights to access and delete genetic data and destroy biological samples; AG-enforced, penalties up to $2,500 per violation plus actual damages, no private right of action.

Pseudonymisation and anonymisationRed

No Arizona statute defines pseudonymisation or anonymisation or provides safe-harbour treatment for de-identified data.

Category narrative 62 words

Arizona has no general lawful-basis framework, no statutory consent-quality standard for commercial data processing, and no general special-category regime. The one notable exception is a direct-to-consumer genetic-testing statute, placing Arizona among a small group of US states regulating that narrow category. Outside genetic testing, sensitive-data handling is governed only by sector-specific federal law (HIPAA, GLBA, COPPA) which falls outside this JID's scope.

Sources and claims (4)
  1. Confirmed OneTrust DataGuidance — The Arizona Attorney General alleged in litigation against Google that the company continued collecting users' location data via settings such as Web & App Activity even after users disabled Location History, framing this as a deceptive-consent practice under the Arizona Consumer Fraud Act. observed
  2. Probable OneTrust DataGuidance — Arizona is among twelve US states (alongside Alabama, California, Kentucky, Maryland, Montana, Tennessee, Texas, Utah, Virginia, Wyoming and Nebraska) with a statute specifically governing direct-to-consumer genetic-testing companies. observed
  3. Uncertain Recording Law — Arizona Genetic Information Privacy Act — narrow special-category-equivalent protection in place of a GDPR-style enumerated special-categories rule observed
  4. Probable OpenAgreements — Arizona Genetic Information Privacy Act (A.R.S. Title 44, Ch. 38) — A narrowly scoped statute applying only to direct-to-consumer genetic testing companies, effective 29 Sep 2021, requiring layered consent and giving consumers rights to access and delete genetic data and destroy biological samples; AG-enforced, penalties up to $2,500 per violation plus actual damages, no private right of action. observed

#

No comprehensive data-subject-rights regime exists in Arizona; this is a legitimate structural gap rather than an omission.

Traffic-light rationale — RedNo comprehensive data-subject-rights regime exists in Arizona; this is a legitimate structural gap rather than an omission.

Sub-modules (5)

Access rightRed

No general AZ statutory right of access to personal data held by private businesses.

Claims (1):

  • Arizona — broad statutory rights to access, correct, or delete personal data held by private businesses

Rectification and erasureRed

No general AZ statutory right to rectify or erase personal data held by businesses.

Restriction and objectionRed

No general AZ statutory right to restrict processing or object to processing/profiling.

Data portabilityRed

No AZ statutory data-portability right exists.

Deadlines and response windowsRed

Because no general subject-rights regime exists, there are no statutory response-window deadlines for rights requests (distinct from the 45-day breach-notification deadline, which is a controller-to-regulator/consumer breach obligation, not a rights-request deadline).

Claims (1):

  • Arizona's breach-notification statute imposes a 45-day deadline for notifying affected individuals of a data breach, but this is a breach-response deadline, not a subject-access-request response window, since no general access-request regime exists in Arizona.
Category narrative 46 words

Arizona confers no general statutory rights of access, rectification, erasure, restriction, objection or portability over personal data held by private-sector businesses. Such rights exist only where a federal sectoral statute (e.g., HIPAA for health records) independently applies, which is out of scope for this state-level JID.

Sources and claims (2)
  1. Confirmed IAPP — Arizona's breach-notification statute imposes a 45-day deadline for notifying affected individuals of a data breach, but this is a breach-response deadline, not a subject-access-request response window, since no general access-request regime exists in Arizona. observed
  2. Probable BillTrack50 — Arizona — broad statutory rights to access, correct, or delete personal data held by private businesses observed

#

Breach notification is a real, enforceable duty; the remaining accountability infrastructure (DPIA, DPO, ROPA, retention) is absent at state level.

Primary frameworkArizona Revised Statutes §18-552
Supervisory authorityArizona Attorney General
Traffic-light rationale — AmberBreach notification is a real, enforceable duty; the remaining accountability infrastructure (DPIA, DPO, ROPA, retention) is absent at state level.

Sub-modules (7)

Accountability & DPIARed

No AZ statute requires DPIAs or a general accountability principle akin to GDPR Art 5/25/35.

DPO requirementsRed

No AZ statute requires appointment of a data protection officer.

Ropa requirementsRed

No AZ statute requires maintenance of records of processing activity.

Joint controller arrangementsRed

No AZ statute addresses joint-controller or processor-contract requirements.

Security measuresAmber

The breach-notification statute implies an expectation of reasonable security safeguards but does not prescribe specific technical/organisational measures comparable to GDPR Art 32.

Claims (1):

  • Arizona's breach-notification statute presumes an underlying duty of reasonable data security by penalizing failure to protect personal information that leads to a breach, though it does not itemize specific technical or organisational security measures.

Breach notificationGreen

A.R.S. §18-552, as amended by HB 2146 (2022), is Arizona's core breach-notification obligation: a 45-day notification deadline, an expanded definition of personal information (including health-care data), and enhanced AG enforcement powers.

Claims (8):

  • Arizona's amended breach-notification law (via HB 2146) sets a 45-day deadline for notifying affected individuals, expands the definition of covered personal information to include health-care data, and gives the Attorney General enhanced power to prosecute violators.
  • Under A.R.S. §18-552, businesses must notify affected consumers and either the Arizona Attorney General or the Arizona Department of Homeland Security in the event of a data breach, and the Attorney General holds the power to sanction violations and issue penalties.
  • Arizona A.R.S. §18-552 — notification within 45 days after determining a breach occurred, with additional notice to the AG, DHS, and the three largest nationwide consumer reporting agencies for breaches affecting more than 1,000 residents
  • Arizona businesses — Notification of affected Arizona residents within 45 days of determining that a security-system breach materially compromising unencrypted/unredacted computerized personal information has occurred.
  • AZ requires breach notification to the Attorney General and DHS above a 1,000-resident threshold within 45 days.
  • Arizona Data-Breach Notification Law (A.R.S. §§ 18-551, 18-552) — A knowing and willful violation of Arizona's breach-notification law is an unlawful practice under the Consumer Fraud Act, enforceable only by the Attorney General, who may seek a civil penalty up to the lesser of $10,000 per affected individual or total economic loss, capped at $500,000 per breach or series of related breaches, plus restitution. No private right of action exists.
  • A.R.S. § 18-552 (Notification of security system breaches) — Where a determination is made that a security breach occurred, the data owner/licensee must notify affected individuals within 45 days; where more than 1,000 Arizona residents are affected, notice is also owed to the three largest nationwide consumer reporting agencies, the Arizona Attorney General, and the Director of the Arizona Department of Homeland Security.
  • A.R.S. § 18-552 — A business must notify affected Arizona residents within 45 days after determining a security-system breach occurred affecting unencrypted and unredacted personal information, and must also notify the Attorney General and the three major consumer-reporting agencies if the breach affects more than 1,000 Arizona residents; civil penalty capped at the lesser of $10,000 per affected individual or total economic loss, and $500,000 per breach.

Retention and disposalRed

No general AZ statutory retention-limit or disposal-duty regime was located outside of sector-specific federal law.

Category narrative 33 words

Arizona imposes concrete breach-notification duties (A.R.S. §18-552) but no general accountability, DPIA, DPO, ROPA, or retention-limit obligations. Security-of-processing is addressed only implicitly through the breach statute's reasonable-security expectations and via sector-specific federal law.

Sources and claims (9)
  1. Probable OneTrust DataGuidance — Arizona's breach-notification statute presumes an underlying duty of reasonable data security by penalizing failure to protect personal information that leads to a breach, though it does not itemize specific technical or organisational security measures. observed
  2. Confirmed IAPP — Arizona's amended breach-notification law (via HB 2146) sets a 45-day deadline for notifying affected individuals, expands the definition of covered personal information to include health-care data, and gives the Attorney General enhanced power to prosecute violators. observed
  3. Confirmed OneTrust DataGuidance — Under A.R.S. §18-552, businesses must notify affected consumers and either the Arizona Attorney General or the Arizona Department of Homeland Security in the event of a data breach, and the Attorney General holds the power to sanction violations and issue penalties. observed
  4. Confirmed Security.org — Arizona A.R.S. §18-552 — notification within 45 days after determining a breach occurred, with additional notice to the AG, DHS, and the three largest nationwide consumer reporting agencies for breaches affecting more than 1,000 residents observed
  5. Probable RecordingLaw.com — Arizona businesses — Notification of affected Arizona residents within 45 days of determining that a security-system breach materially compromising unencrypted/unredacted computerized personal information has occurred. observed
  6. Probable Arizona Attorney General's Office — AZ requires breach notification to the Attorney General and DHS above a 1,000-resident threshold within 45 days. observed
  7. Confirmed Arizona Attorney General's Office — Arizona Data-Breach Notification Law (A.R.S. §§ 18-551, 18-552) — A knowing and willful violation of Arizona's breach-notification law is an unlawful practice under the Consumer Fraud Act, enforceable only by the Attorney General, who may seek a civil penalty up to the lesser of $10,000 per affected individual or total economic loss, capped at $500,000 per breach or series of related breaches, plus restitution. No private right of action exists. observed
  8. Confirmed https://www.azleg.gov/ars/18/00552.htm — A.R.S. § 18-552 (Notification of security system breaches) — Where a determination is made that a security breach occurred, the data owner/licensee must notify affected individuals within 45 days; where more than 1,000 Arizona residents are affected, notice is also owed to the three largest nationwide consumer reporting agencies, the Arizona Attorney General, and the Director of the Arizona Department of Homeland Security.
  9. Probable Arizona Attorney General's Office — A.R.S. § 18-552 — A business must notify affected Arizona residents within 45 days after determining a security-system breach occurred affecting unencrypted and unredacted personal information, and must also notify the Attorney General and the three major consumer-reporting agencies if the breach affects more than 1,000 Arizona residents; civil penalty capped at the lesser of $10,000 per affected individual or total economic loss, and $500,000 per breach. observed

#

No AZ-specific cross-border transfer, adequacy or localisation framework exists; this is a legitimate gap given the absence of a state omnibus law.

Traffic-light rationale — Not assessedNo AZ-specific cross-border transfer, adequacy or localisation framework exists; this is a legitimate gap given the absence of a state omnibus law.

Sub-modules (6)

Transfer mechanismsRed

No AZ-specific transfer mechanism statute exists.

Adequacy receivedRed

Not applicable at state level; adequacy determinations are a federal/EU-US construct.

Adequacy grantedRed

Not applicable at state level.

SCCs and BCRsRed

No AZ-specific SCC/BCR regime; any use of SCCs/BCRs by AZ-based entities derives from federal/international frameworks, not state law.

Transfer impact assessmentRed

No AZ statutory TIA requirement exists.

Data localisationRed

No AZ data-localisation mandate was identified.

Category narrative 39 words

Arizona has no state-level cross-border data-transfer regime, no adequacy mechanism, and no data-localisation mandate. Cross-border transfer questions arising from AZ-resident data are governed exclusively by federal law and mechanisms (SCCs, federal sectoral rules), which sit outside this state JID.

#

A narrow genetic-testing overlay exists; broader sectoral coverage (health, finance, education, insurance) is federal and out of scope for this state JID.

Supervisory authorityArizona Attorney General
Traffic-light rationale — AmberA narrow genetic-testing overlay exists; broader sectoral coverage (health, finance, education, insurance) is federal and out of scope for this state JID.

Sub-modules (7)

Financial sector overlayRed

No AZ-specific financial-sector data-protection overlay was located beyond the federal GLBA baseline (out of scope for this JID).

Health sector overlayAmber

No AZ-specific health-data statute beyond federal HIPAA (out of scope); AZ health providers report breaches to HHS OCR under HIPAA, as illustrated by recent AZ healthcare ransomware incidents.

Claims (1):

  • Arizona healthcare entities, such as a regional medical center and other providers, have reported large-scale ransomware and malware-related patient-data breaches to HHS OCR under federal HIPAA breach-reporting obligations, impacting hundreds of thousands of individuals.

Telecoms and eprivacyAmber

Arizona has a state-level telephone-solicitation law restricting calls to numbers on the National Do-Not-Call registry, with specified exceptions.

Claims (1):

  • Arizona has enacted a law restricting telephone solicitations to numbers on the National Do-Not-Call registry, subject to specific exceptions.

Employment dataRed

No AZ-specific employment-data-privacy statute was located; federal GINA governs genetic-information-based employment discrimination nationally, out of scope for this state JID.

Credit and scoringRed

No AZ-specific credit-scoring privacy statute was located beyond federal FCRA (out of scope).

educationRed

No AZ-specific education-sector data-privacy statute was located in this run beyond federal FERPA (out of scope).

insuranceRed

No AZ-specific insurance-sector data-privacy statute was located in this run.

Category narrative 52 words

Outside the breach-notification statute, Arizona's data-protection-relevant sectoral activity consists of a direct-to-consumer genetic-testing statute and reliance on federal sectoral overlays (HIPAA for health, GLBA for financial, COPPA for children) that are native to the US-federal JID rather than AZ. No AZ-specific insurance, education, or credit-scoring privacy statute was identified in this run.

Sources and claims (2)
  1. Probable OneTrust DataGuidance — Arizona healthcare entities, such as a regional medical center and other providers, have reported large-scale ransomware and malware-related patient-data breaches to HHS OCR under federal HIPAA breach-reporting obligations, impacting hundreds of thousands of individuals. observed
  2. Probable OneTrust DataGuidance — Arizona has enacted a law restricting telephone solicitations to numbers on the National Do-Not-Call registry, subject to specific exceptions. observed

#

No structural cookie/opt-out regime exists, but active AG enforcement under general consumer-fraud authority provides a meaningful, demonstrated deterrent against deceptive ad-tech data practices.

Primary frameworkArizona Consumer Fraud Act, A.R.S. §44-1521 et seq.
Supervisory authorityArizona Attorney General
Traffic-light rationale — AmberNo structural cookie/opt-out regime exists, but active AG enforcement under general consumer-fraud authority provides a meaningful, demonstrated deterrent against deceptive ad-tech data practices.

Sub-modules (6)

Cookies and trackersRed

No AZ cookie-consent statute exists; tracking practices are addressed only reactively via consumer-fraud enforcement.

Dark patternsRed

No AZ dark-patterns statute was located; deceptive-design practices are addressed only through the general Consumer Fraud Act.

Opt out signalsRed

No AZ statute recognizes Global Privacy Control or comparable opt-out signals.

Clean rooms and dcrRed

No AZ-specific clean-room/data-collaboration statute was located.

Cross context advertisingAmber

No AZ equivalent to CPRA 'sale'/'share' restrictions exists; the AG's Google settlement addressed deceptive location-data use for advertising under general consumer-fraud law rather than a cross-context-advertising-specific statute.

Claims (1):

  • The Arizona Attorney General secured an $85 million settlement with Google in 2022 resolving allegations that Google deceptively continued collecting and using consumers' location data for advertising purposes after users had disabled location tracking, brought under the Arizona Consumer Fraud Act.

Direct marketingAmber

Direct marketing via telephone is regulated by the AZ Do-Not-Call statute (see sectoral_watch.telecoms_and_eprivacy); no general direct-mail/email suppression statute beyond federal CAN-SPAM/TCPA was located.

Category narrative 64 words

Arizona has no cookie-consent or 'sale'/'share' opt-out statute comparable to CPRA. The principal lever against commercial ad-tech data practices is the Arizona Consumer Fraud Act, used by the AG to pursue deceptive location-tracking and data-collection practices (e.g., the $85M Google settlement and the pending Temu suit). A pending 2026 bill (HB 2489) would restrict surveillance-based pricing practices, but it is not yet in force.

Sources and claims (1)
  1. Confirmed IAPP — The Arizona Attorney General secured an $85 million settlement with Google in 2022 resolving allegations that Google deceptively continued collecting and using consumers' location data for advertising purposes after users had disabled location tracking, brought under the Arizona Consumer Fraud Act. observed

#

Meaningful legislative activity exists (biometric, AI, surveillance-pricing bills) but none confirmed in force; treat as pending/proposed pending regulator confirmation.

Traffic-light rationale — AmberMeaningful legislative activity exists (biometric, AI, surveillance-pricing bills) but none confirmed in force; treat as pending/proposed pending regulator confirmation.

Sub-modules (6)

Profiling restrictionsAmber

No AZ statute restricts profiling comparable to GDPR Art 22; the pending surveillance-pricing bill (HB 2489) touches algorithmic pricing but is not yet law.

Claims (1):

  • Arizona House Bill 2489 would restrict surveillance-based pricing practices by defining and prohibiting such practices and establishing enforcement mechanisms, but has not been confirmed enacted as of this run.

Automated decision making transparencyRed

No AZ statute requires ADM transparency or an explanation right.

AI risk assessmentsAmber

A pending bill, HB 2311, would introduce disclosure, safety and content restrictions for conversational-AI services with enhanced protections for minors, but it has not been confirmed as enacted.

Claims (2):

  • Arizona House Bill 2311 would introduce disclosure, safety, and content restrictions for conversational AI services, with enhanced protections for minors, but its passage into law has not been confirmed in this run.
  • AG Mayes's suit against OpenAI alleges deceptive collection of sensitive personal data via ChatGPT's conversational design, including from minors.

Biometric regimeAmber

Senate Bill 1238 would regulate biometric-data handling by private entities and provide legal recourse for violations; introduction/first-reading was confirmed but enactment status could not be verified in this run.

Claims (3):

  • Arizona Senate Bill 1238 would regulate biometric-data handling by private entities and provide legal recourse for violations; the bill was read in the State Senate but its final enactment status could not be independently confirmed in this run.
  • Arizona State Legislature — SB1717 (2026), which would have required informed consent before commercial capture of biometric identifiers, died without passing in the 57th Legislature's 2nd Regular Session.
  • AZ SB 1717 (Biometric identifiers; commercial use; prohibitions) — Consumer Biometric Data Protection Act bill introduced 5 Feb 2026 that would have required informed consent before commercial capture of biometric identifiers and destruction duties, AG-enforced penalties up to $25,000/violation, no private right of action. Died in committee when the legislature adjourned sine die (recorded dead 13-14 Jun 2026).

Genetic dataAmber

See lawful_processing_and_special_data.special_categories: Arizona's direct-to-consumer genetic-testing statute is the only in-force genetic-data provision identified.

State surveillance carveoutsRed

No AZ-specific state-surveillance carve-out or national-security exemption provision was located in this run.

Category narrative 63 words

Arizona has no in-force profiling, ADM-transparency, or AI-risk-assessment statute. A biometric-data bill (SB 1238) proposing regulation of biometric handling by private entities with a private right of action has been introduced but its enactment status is unconfirmed in this run. Pending 2026 bills would address conversational-AI services with minor protections (HB 2311) and surveillance-based pricing (HB 2489), but neither is yet in force.

Periodic update · new data 2026-11-04

Arizona Attorney General Kris Mayes's 14 October 2026 suit against OpenAI puts the question of sensitive-data collection by conversational AI systems squarely before an Arizona court, through the vehicle of the state's general Consumer Fraud Act rather than any statute specific to algorithmic systems. The complaint alleges that OpenAI engineered ChatGPT's conversational design in a manner that collected and retained Arizonans' sensitive personal data, including health, financial, relationship and family information, obtained through the ordinary course of conversational interaction rather than through a clearly disclosed and separately consented collection mechanism, and that this occurred without adequate disclosure to users, including minors who interacted with the system.

The filing is notable for proceeding entirely outside any statutory AI-governance framework, because Arizona currently has no statutory duty requiring AI risk assessments, algorithmic impact assessments, or equivalent documentation obligations for systems of this kind. The absence of such a framework means the legal theory here rests on consumer-protection concepts, deception and unfairness in marketing and design, rather than on any AI-specific compliance duty that OpenAI is alleged to have failed to meet. That distinction matters for how the case is likely to be litigated: the state does not need to establish that OpenAI violated an algorithmic-governance statute, only that its design and marketing choices were deceptive under the ordinary consumer-fraud standard, a materially lower and more familiar evidentiary bar for Arizona courts than a novel AI-specific claim would be.

The coordinated nature of the filing, part of an eight-state action brought the same day across Iowa, Kansas, Nebraska, West Virginia, Arkansas, Arizona, Idaho and Montana, suggests the states involved are treating the underlying conduct, alleged deceptive collection of sensitive personal data through conversational AI design, as a common pattern rather than a jurisdiction-specific grievance. For Arizona specifically, this represents the state's first substantial enforcement engagement with sensitive-data practices embedded in a large-scale conversational AI product, using existing consumer-protection authority as the vehicle in the absence of any purpose-built AI statute.

The practical significance for operators of conversational or generative AI systems with an Arizona user base is that the absence of a dedicated AI statute does not equate to an absence of exposure. General consumer-protection law remains available to the Attorney General as an enforcement tool against design and disclosure practices the office considers deceptive, irrespective of whether a specific AI-governance statute exists to name the conduct directly. The case will test how far that general authority extends to conversational-design choices and data-handling practices that are inherent to how large language models function, rather than to a discrete, severable feature that could be disabled or modified in isolation.

Outlook

As at the filing date, no ruling, motion disposition, or settlement has been reported in the Arizona action, and the case should be expected to proceed over an extended timeline given its scale and the coordinated multistate posture behind it. The absence of a statutory AI-governance framework in Arizona means that, for the duration of this litigation, the practical boundaries of acceptable sensitive-data handling by conversational AI systems in the state will be shaped by how this consumer-fraud theory fares in court rather than by any legislative or regulatory text. Developments in the parallel actions filed the same day in other states may also inform how the Arizona matter proceeds, given the shared factual allegations underlying all eight filings.

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

Sources and claims (7)
  1. Uncertain OneTrust DataGuidance — Arizona House Bill 2489 would restrict surveillance-based pricing practices by defining and prohibiting such practices and establishing enforcement mechanisms, but has not been confirmed enacted as of this run. observed
  2. Uncertain OneTrust DataGuidance — Arizona House Bill 2311 would introduce disclosure, safety, and content restrictions for conversational AI services, with enhanced protections for minors, but its passage into law has not been confirmed in this run. observed
  3. Uncertain OneTrust DataGuidance — Arizona Senate Bill 1238 would regulate biometric-data handling by private entities and provide legal recourse for violations; the bill was read in the State Senate but its final enactment status could not be independently confirmed in this run. observed
  4. Probable Recording Law — Arizona State Legislature — SB1717 (2026), which would have required informed consent before commercial capture of biometric identifiers, died without passing in the 57th Legislature's 2nd Regular Session. observed
  5. Confirmed Arizona Attorney General's Office — AG Mayes's suit against OpenAI alleges deceptive collection of sensitive personal data via ChatGPT's conversational design, including from minors. observed
  6. Probable Recording Law — AZ SB 1815 (Personal data; consumers; controllers; requirements) — A comprehensive consumer data-privacy bill introduced 10 Feb 2026 (57th Legislature, 2nd Regular Session) that would have created CCPA/VCDPA-style access, correction, deletion, portability and opt-out rights, AG-only enforcement with a 30-day cure period and civil penalties up to $7,500/violation, no private right of action. Died in committee 14 Jun 2026. observed
  7. Probable Recording Law — AZ SB 1717 (Biometric identifiers; commercial use; prohibitions) — Consumer Biometric Data Protection Act bill introduced 5 Feb 2026 that would have required informed consent before commercial capture of biometric identifiers and destruction duties, AG-enforced penalties up to $25,000/violation, no private right of action. Died in committee when the legislature adjourned sine die (recorded dead 13-14 Jun 2026). observed

#

Active pending legislative pipeline on minors' data exists, but nothing AZ-specific is confirmed in force; federal COPPA is the operative baseline, and is out of scope for this JID.

Supervisory authorityArizona Attorney General
Traffic-light rationale — AmberActive pending legislative pipeline on minors' data exists, but nothing AZ-specific is confirmed in force; federal COPPA is the operative baseline, and is out of scope for this JID.

Sub-modules (5)

Age verificationAmber

Arizona House Bill 2920 would mandate age verification for app stores and developers handling minors' accounts, but enactment is unconfirmed.

Claims (1):

  • Arizona House Bill 2920 would mandate age verification, parental consent, and data-sharing duties for app stores and developers handling minors' accounts, but its enactment status has not been independently confirmed in this run.

Minor profiling bansAmber

No confirmed AZ statute specifically bans profiling of minors; HB 2861 and HB 2858 (enhancing minors' social-media privacy protections) are pending and unconfirmed as enacted.

Claims (1):

  • Arizona House Bill 2861 would enhance privacy protections for minors on social media platforms, and House Bill 2858 similarly seeks to enhance online privacy and safety for minors on social media, but neither has been confirmed enacted in this run.

Education settingsRed

No AZ-specific education-settings child-data statute was identified in this run.

Dependent adultsRed

No AZ-specific dependent-adults data-protection provision was located in this run.

Category narrative 73 words

Arizona has no in-force comprehensive minors'-data statute. Multiple 2026-session bills address minors' online safety and social-media data practices (HB 2861, HB 2858, HB 2920 covering age verification/parental consent for app stores) alongside intimate-image/deepfake bills (SB 1462, SB 1336, HB 2678), but enactment status for the privacy-specific bills is not confirmed in this run. Federal COPPA applies nationally but is out of scope for this state JID. No AZ-specific dependent-adults data-protection provision was identified.

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

Sources and claims (2)
  1. Uncertain OneTrust DataGuidance — Arizona House Bill 2920 would mandate age verification, parental consent, and data-sharing duties for app stores and developers handling minors' accounts, but its enactment status has not been independently confirmed in this run. observed
  2. Uncertain OneTrust DataGuidance — Arizona House Bill 2861 would enhance privacy protections for minors on social media platforms, and House Bill 2858 similarly seeks to enhance online privacy and safety for minors on social media, but neither has been confirmed enacted in this run. observed

#

Enforcement powers and recent activity are real and material, but redress avenues remain reactive/consumer-fraud-based rather than a dedicated private right of action under a comprehensive privacy statute.

Primary frameworkArizona Consumer Fraud Act, A.R.S. §44-1521 et seq.; A.R.S. §18-552
Supervisory authorityArizona Attorney General
Traffic-light rationale — AmberEnforcement powers and recent activity are real and material, but redress avenues remain reactive/consumer-fraud-based rather than a dedicated private right of action under a comprehensive privacy statute.

Sub-modules (6)

Regulator powers and penaltiesGreen

The AG holds sanction and penalty power under the breach-notification statute and broad injunctive/monetary remedies under the Consumer Fraud Act, evidenced by the $85M Google settlement.

Claims (4):

  • The Arizona Attorney General obtained an $85 million settlement with Google in 2022 for deceptive location-data practices found to violate the Arizona Consumer Fraud Act, with the bulk of proceeds directed to the state general fund and $5 million earmarked for attorney-general education programs.
  • Arizona Attorney General — civil penalties up to $10,000 per affected individual, capped at $500,000 per breach or series of related breaches, plus restitution, for knowing and willful violations
  • Only the Arizona AG may enforce breach-notification violations, with penalties up to $10,000 per individual capped at $500,000 per breach.
  • A.R.S. § 18-552(G) — Only the Arizona Attorney General may enforce a breach-notification violation; civil penalty capped at the lesser of $10,000 per affected individual or total economic loss, and a $500,000 maximum per breach or related series; no private right of action.

Enforcement activity indexAmber

Recent AG enforcement activity includes the Google location-data settlement and a lawsuit against Temu for unlawful data collection and inadequate privacy disclosures.

Claims (3):

  • The Arizona Attorney General has sued Temu alleging unlawful data collection and inadequate privacy disclosures, representing recent state enforcement activity against a commercial data practice.
  • Arizona Attorney General — On 2026-07-14, joined a 42-state coalition settlement with the 23andMe bankruptcy trustee over a genetic-data breach affecting 6.9 million customers, citing the Genetic Information Privacy Act as applicable to DTC genetic-testing companies.
  • Arizona Attorney General — On 2026-08-26, announced a $17.1 billion multistate settlement with Meta Platforms over youth-safety/addictive-design allegations, with Arizona receiving approximately $223 million.

Regulator funding and capacityRed

No specific AZ AG privacy-unit funding or headcount data was located in this run.

Collective redress and class actionsRed

No AZ-specific statutory collective-redress mechanism for data-privacy claims beyond general Arizona class-action procedure was identified in this run.

Private right of actionAmber

No general private right of action for data-privacy violations exists in Arizona; pending SB 1238 (biometric data) reportedly would include legal recourse for violations, but enactment is unconfirmed.

Claims (1):

  • Pending Arizona Senate Bill 1238 would regulate biometric-data handling by private entities and provide for legal recourse for violations, which would constitute a private right of action if enacted, but enactment has not been confirmed in this run.

Recent developments 180dAmber

Within the last 180 days, the most notable AZ-specific development identified is the Attorney General's lawsuit against Temu over data-collection and privacy-disclosure practices; multiple minors'-privacy and biometric/AI bills remain pending in the 2026 legislative session.

Claims (2):

  • The Arizona Attorney General has sued Temu alleging unlawful data collection and inadequate privacy disclosures, representing recent state enforcement activity against a commercial data practice.
  • On 14 October 2026, Arizona Attorney General Kris Mayes filed suit against OpenAI alleging deceptive design and data-collection practices harming Arizona minors.
Category narrative 83 words

The Arizona Attorney General has demonstrated active, real enforcement capacity against deceptive data practices under the Consumer Fraud Act, most notably the 2022 $85 million Google location-data settlement and the more recent lawsuit against Temu alleging unlawful data collection and inadequate privacy disclosures. Arizona's breach-notification statute gives the AG additional sanction and penalty powers. No AZ-specific private right of action for general data-privacy violations was identified; some breach/biometric bills (e.g., pending SB 1238) propose private rights of action but are not confirmed enacted.

No periodic updates recorded in this cycle

Sources and claims (9)
  1. Confirmed NAAG — The Arizona Attorney General obtained an $85 million settlement with Google in 2022 for deceptive location-data practices found to violate the Arizona Consumer Fraud Act, with the bulk of proceeds directed to the state general fund and $5 million earmarked for attorney-general education programs. observed
  2. Probable OneTrust DataGuidance — The Arizona Attorney General has sued Temu alleging unlawful data collection and inadequate privacy disclosures, representing recent state enforcement activity against a commercial data practice. observed
  3. Uncertain OneTrust DataGuidance — Pending Arizona Senate Bill 1238 would regulate biometric-data handling by private entities and provide for legal recourse for violations, which would constitute a private right of action if enacted, but enactment has not been confirmed in this run. observed
  4. Confirmed Arizona Attorney General's Office — On 14 October 2026, Arizona Attorney General Kris Mayes filed suit against OpenAI alleging deceptive design and data-collection practices harming Arizona minors. observed
  5. Confirmed Arizona Attorney General's Office — Arizona Attorney General — civil penalties up to $10,000 per affected individual, capped at $500,000 per breach or series of related breaches, plus restitution, for knowing and willful violations observed
  6. Confirmed https://www.azag.gov/press-release/attorney-general-mayes-announces-multistate-settlement-bankruptcy-claims-against — Arizona Attorney General — On 2026-07-14, joined a 42-state coalition settlement with the 23andMe bankruptcy trustee over a genetic-data breach affecting 6.9 million customers, citing the Genetic Information Privacy Act as applicable to DTC genetic-testing companies.
  7. Confirmed Arizona Attorney General — Arizona Attorney General — On 2026-08-26, announced a $17.1 billion multistate settlement with Meta Platforms over youth-safety/addictive-design allegations, with Arizona receiving approximately $223 million. observed
  8. Probable Recording Law — Only the Arizona AG may enforce breach-notification violations, with penalties up to $10,000 per individual capped at $500,000 per breach. observed
  9. Probable Shredding PHX — A.R.S. § 18-552(G) — Only the Arizona Attorney General may enforce a breach-notification violation; civil penalty capped at the lesser of $10,000 per affected individual or total economic loss, and a $500,000 maximum per breach or related series; no private right of action. 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), 46 claim(s) (46 category placement(s)), 34 source(s) in the cumulative register.

Audit trail

Machine checkChallenged on 24 Oct 2026: not settled (6 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 (38 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 received
Art. 46Cross-Border & Adequacysccs and bcrs
Art. 47Cross-Border & Adequacysccs and bcrs
Art. 48Cross-Border & Adequacydata localisation
Art. 49Cross-Border & Adequacytransfer mechanisms
Art. 77Enforcement & Redressregulator powers and penalties
Art. 78Enforcement & Redressprivate right of action
Art. 79Enforcement & Redressprivate right of action
Art. 80Enforcement & Redresscollective redress and class actions
Art. 81Enforcement & Redressregulator powers and penalties
Art. 82Enforcement & Redressprivate right of action
Art. 83Enforcement & Redressregulator powers and penalties
Art. 84Enforcement & Redressregulator powers and penalties