Skip to main content
Intelligent Security Governance — 340+ Frameworks Powered by Ayurak AI
Blog/Compliance Guides

Indiana Consumer Data Protection Act (ICDPA): A Practical Compliance Guide

What Indiana's consumer privacy law requires, who it covers, how the Attorney General enforces it, and a step-by-step path to being ready for the January 1, 2026 effective date.

Indiana Consumer Data Protection Act (ICDPA): A Practical Compliance Guide

The Indiana Consumer Data Protection Act (ICDPA) is a state privacy law that gives Indiana residents rights over their personal data and imposes duties on the businesses that control and process it. It was enacted in 2023 as Senate Bill 5 and took effect on January 1, 2026. This guide covers what it requires and how to prepare.

What it is

The ICDPA is a state statute passed by the Indiana General Assembly and signed in May 2023. It is mandatory law, not a standard or certification scheme. It follows the general model of the Virginia Consumer Data Protection Act, using the vocabulary of "controllers," "processors," "consumers" and "sensitive data." It is lighter than California's regime in several respects.

Its purpose is to give residents transparency and control over how their personal data is collected, used, shared and sold, and to require basic safeguards and accountability from businesses. Indiana has no dedicated privacy regulator. The Attorney General enforces the law.

Because state privacy law is an active area, check the current statute text and any amendments or Attorney General guidance before finalizing your program. This article reflects the law as enacted in 2023.

Who it applies to

The ICDPA applies to persons that conduct business in Indiana or produce products or services targeted to Indiana residents, and that meet one of two volume thresholds in a calendar year:

  • they control or process personal data of at least 100,000 Indiana consumers; or
  • they control or process personal data of at least 25,000 Indiana consumers and derive more than 50 percent of gross revenue from the sale of personal data.

A "consumer" is an Indiana resident acting in an individual or household context. People acting in an employment or commercial context are excluded, so HR and B2B contact data are generally outside the law. That is a notable difference from California.

The law contains entity-level and data-level exemptions. Entity-level exemptions generally include government bodies, financial institutions and data subject to the Gramm-Leach-Bliley Act, HIPAA covered entities and business associates, nonprofits, and higher education institutions. Data-level exemptions cover categories such as protected health information under HIPAA and data regulated under certain other federal laws. Exemption details matter, so confirm them against the statute for your specific situation rather than assuming a whole organization is out of scope.

Key requirements and control areas

Consumer rights

Controllers must honor requests from consumers to:

  • confirm whether their data is being processed and access it;
  • correct inaccuracies in personal data they previously provided to the controller;
  • delete personal data provided by or obtained about them;
  • obtain a copy or a representative summary of data they previously provided, in a portable format where technically feasible;
  • opt out of targeted advertising, the sale of personal data, and profiling used for decisions with legal or similarly significant effects.

Controllers generally have 45 days to respond, with a possible extension where reasonably necessary. If a request is denied, the consumer must be told how to appeal, and the controller must respond to appeals within a set period and explain the outcome, including how to contact the Attorney General if the appeal is denied.

Controller duties

  • Data minimization and purpose limitation: collect only what is adequate, relevant and reasonably necessary for the disclosed purposes, and do not process for incompatible purposes without consent.
  • Security: maintain reasonable administrative, technical and physical data security practices appropriate to the volume and nature of the data.
  • Non-discrimination: do not discriminate against consumers for exercising their rights.
  • Privacy notice: provide a clear notice covering categories of data processed, purposes, how to exercise rights and appeal, categories shared with third parties, and categories of third parties. Sales of data or targeted advertising must be clearly disclosed along with the opt-out method.
  • Sensitive data: obtain consent before processing sensitive data. This category includes racial or ethnic origin, religious beliefs, health diagnoses, sexual orientation, citizenship or immigration status, genetic and biometric data, precise geolocation, and personal data of a known child. Children's data must be handled in line with COPPA.

Data protection assessments

Controllers must conduct and document data protection assessments for higher-risk activities: targeted advertising, sale of personal data, certain profiling, processing of sensitive data, and other processing presenting heightened risk of harm. Assessments weigh the benefits of processing against risks to consumers and the safeguards applied. The Attorney General may request them in an investigation. The assessment obligation applies to processing activities from a date tied to the effective date, so confirm the exact scope in the statute.

Processor contracts

Processors must follow the controller's instructions and assist with consumer requests, security and assessments. A written contract must set out the processing instructions, nature and purpose, data types, duration, confidentiality duties, deletion or return at the end of services, and audit or assessment cooperation, along with flow-down obligations for subprocessors.

De-identified data

Controllers holding de-identified data must take reasonable measures against re-identification, publicly commit to maintaining it in that form, and contractually require recipients to comply.

Assessment, audit and enforcement

There is no certification or third-party attestation under the ICDPA. Compliance is demonstrated through your own documentation: notices, request logs, assessments, contracts and security records. The Indiana Attorney General has exclusive enforcement authority, and the law does not create a private right of action.

Before bringing an action, the Attorney General must give a written notice of the alleged violation and a cure period, reported as 30 days. If the controller cures and provides a written statement that it has done so and that no further violations will occur, an action may not proceed. The law provides for civil penalties per violation, commonly reported as up to $7,500; verify the current figure and cure-period language in the statute. Because the cure right is a safety net and not a plan, build the program so you can show a documented, working process on the day a notice arrives.

A practical path to compliance

  1. Determine applicability. Count Indiana consumers whose data you process, separate out employment and B2B contexts, and review exemptions for your entity and data types.
  2. Map your data. Inventory what personal data you collect, where it is stored, which systems and vendors touch it, and which elements are sensitive data.
  3. Identify high-risk processing. Flag targeted advertising, data sales, profiling and sensitive data use, since these trigger opt-outs, consent and assessments.
  4. Update privacy notices. Align public disclosures with actual practices and describe how to submit and appeal requests.
  5. Build the request workflow. Set up intake, identity verification, routing to data owners, response deadlines, appeals and recordkeeping.
  6. Implement consent and opt-out controls. Collect consent for sensitive data, and honor opt-outs across advertising tags, data-sharing integrations and downstream partners. Consider supporting browser-based opt-out signals, as other states require them even if Indiana's text does not clearly do so.
  7. Complete data protection assessments. Document benefits, risks and mitigations for each high-risk activity, and keep them current.
  8. Revise vendor contracts. Add processor terms and check that processors can support deletion, access and assessments.
  9. Verify security. Confirm safeguards are reasonable for the data you hold and that you can show evidence of them.
  10. Train and monitor. Train staff who handle requests, and review the program regularly as the law and guidance evolve.

How it maps to other frameworks

These overlaps are partial. Meeting another framework does not equal ICDPA compliance.

  • Other US state privacy laws: The closest overlap, especially with Virginia, Connecticut, Colorado and similar laws. Rights, assessments and processor contracts are structurally alike, but definitions, exemptions, cure periods and opt-out signal rules differ, so a multi-state program needs a jurisdiction-by-jurisdiction check.
  • ISO 27001: Supports the reasonable security duty through its risk management and Annex A controls. It does not address consumer rights or notices. ISO 27701 extends toward privacy management and overlaps more with controller and processor duties.
  • SOC 2: The Security and Confidentiality criteria, and optionally Privacy, provide evidence for safeguards and vendor practices. A SOC 2 report is not a statement of ICDPA compliance.
  • NIST CSF and NIST Privacy Framework: Useful for structuring security and privacy risk management, including data mapping and governance. Both are voluntary.
  • GDPR: Overlaps in data minimization, purpose limitation, rights, and assessments, but the ICDPA uses an opt-out model for much processing where GDPR requires a lawful basis, so GDPR readiness does not carry over directly.

FAQs

When does the ICDPA take effect?

January 1, 2026. The law is now in effect and the Attorney General can enforce it, so request workflows, notices and contracts should already be in place.

Does it apply to employee data?

Generally no. The definition of consumer excludes individuals acting in a commercial or employment context, so typical HR and B2B contact data falls outside the law.

Can individuals sue under the ICDPA?

No. The Attorney General has exclusive enforcement authority and the statute does not create a private right of action. Other laws, such as consumer protection or data breach statutes, may still apply separately.

Is a small business exempt?

The law has no revenue threshold. Applicability depends on the number of Indiana consumers whose data you process, or the share of revenue from selling data. Smaller businesses may fall below the thresholds, but the exemptions and thresholds should be checked carefully.

Do we need to honor universal opt-out signals?

The statute as enacted does not clearly require it in the way some other states do. Many organizations honor such signals across states for operational simplicity. Check current text and guidance.

How Aristiun helps

Aristiun is the AI-powered compliance automation and threat modeling platform, powered by Ayurak AI. For privacy programs like the ICDPA, the work comes down to showing that controls exist and keep working, and doing that once across overlapping state laws and security frameworks. See the compliance frameworks Aristiun covers.

  • Map controls across 340+ frameworks, so a single evidence base supports ICDPA work alongside other privacy laws and security standards.
  • Collect evidence automatically from connected systems such as AWS, Azure, GCP and GitHub, instead of using manual screenshots and spreadsheets.
  • Monitor control effectiveness and get alerts when controls drift, so you can remediate before an auditor or regulator finds issues.
  • Generate threat models from code, IaC and architecture diagrams (including LINDDUN for privacy) to inform data protection assessments, and produce auditor-friendly reports.

Found this insightful?

Share it with your security team or save it for later.

Get Started

Ready to secure your organization?

See how Aristiun automates compliance and strengthens your security posture across 340+ frameworks.