The Iowa Consumer Data Protection Act (ICDPA) is a state privacy statute that took effect on January 1, 2025. It gives Iowa residents a set of rights over their personal data and places duties on the businesses that control or process it. Compared with some other US state privacy laws it is lighter in places, but it still requires a working rights-request process, contract terms with processors, and reasonable security.
What it is
The ICDPA is a state law enacted by the Iowa legislature and signed in 2023, and it is codified in the Iowa Code as chapter 715D. It is mandatory law, not a standard, certification scheme or voluntary framework. It is enforced by the Iowa Attorney General, and no certification or registration is needed to comply.
Like most US state privacy laws other than California's, it follows the "controller and processor" model that originated in the GDPR and came into US state law through Virginia's statute. A controller decides why and how personal data is processed. A processor handles data on a controller's behalf. Each role carries its own obligations.
The purpose is to give consumers transparency and some control over how their data is collected, used and sold, and to require businesses to handle that data responsibly. Because state privacy laws have been amended and added to quickly, check the current statutory text and any attorney general guidance before relying on this summary for a specific decision.
Who it applies to
The law applies to a person that conducts business in Iowa, or produces products or services targeted to Iowa consumers, and that meets one of two thresholds in a calendar year:
- It controls or processes personal data of at least 100,000 Iowa consumers; or
- It controls or processes personal data of at least 25,000 Iowa consumers and derives more than 50 percent of its gross revenue from the sale of personal data.
There is no revenue threshold, so a small company with a large user base can be covered. A "consumer" is an Iowa resident acting in an individual or household context. People acting in a commercial or employment context are not consumers under the law, so most employee and B2B contact data falls outside it.
Several entity types are exempt, including government bodies, financial institutions and data subject to the Gramm-Leach-Bliley Act, HIPAA covered entities and business associates, nonprofits, and institutions of higher education. The law also exempts certain categories of data, such as protected health information and data governed by FERPA or the Fair Credit Reporting Act. Entity-level and data-level exemptions differ, so work out which applies to each of your datasets rather than assuming a whole company is in or out.
Key requirements and control areas
Consumer rights
Controllers must honor requests from consumers. The rights include:
- Confirming whether a controller is processing their data and accessing it;
- Deleting personal data, which under Iowa's law is narrower than in some states because it is tied to data the consumer provided;
- Obtaining a portable copy of data they previously provided;
- Opting out of the sale of personal data.
Iowa's rights list is shorter than in many comparable laws. Notably, it does not include a right to correct inaccuracies. Controllers generally have 90 days to respond to a request, with a possible extension, and must offer a way to appeal a refusal. Check the current text for how targeted advertising is handled, as this is where state laws differ most.
Privacy notice and transparency
Controllers must give consumers a reasonably accessible privacy notice describing the categories of data processed, the purposes, how to exercise rights and appeal decisions, the categories of data shared with third parties, and the categories of third parties. If a controller sells personal data or engages in targeted advertising, it must disclose that clearly and explain how to opt out.
Data minimization and purpose limitation
Unlike Virginia and several other states, the ICDPA does not impose express data minimization or purpose limitation duties. Limiting collection to what is necessary is still good practice and is required by many other state laws, and it depends on knowing what data you hold and why.
Security
Controllers must establish, implement and maintain reasonable administrative, technical and physical data security practices appropriate to the volume and nature of the data. The statute does not prescribe specific controls, so "reasonable" is judged against recognized practice. Many organizations point to ISO 27001, NIST CSF or SOC 2 controls as evidence.
Sensitive data
Sensitive data covers categories such as racial or ethnic origin, religious beliefs, health diagnoses, sexual orientation, citizenship or immigration status, biometric data used for identification, precise geolocation, and data of known children. Controllers must give clear notice and an opportunity to opt out before processing it, in contrast to the opt-in consent model in some other states. Confirm the exact mechanism against the current text.
Children's data
Processing data of a known child under 13 must follow the verifiable parental consent requirements of the federal Children's Online Privacy Protection Act (COPPA).
Processor contracts
A controller and processor must have a contract that sets out processing instructions, the nature and purpose of processing, the type of data, duration, and the processor's duties. These typically include confidentiality, deletion or return of data at the end of services, making information available to show compliance, and flowing obligations to subcontractors.
Non-discrimination and deidentified data
Controllers may not discriminate against consumers for exercising their rights. Controllers that use deidentified data must take reasonable steps to ensure it cannot be linked to an individual, publicly commit to keeping it deidentified, and contractually bind recipients.
What it does not require
Unlike several other state laws, the ICDPA does not require formal data protection assessments for high-risk processing, and does not mandate recognition of universal opt-out signals. Companies operating in several states often still do these things to satisfy stricter laws, so it can be simpler to adopt a single higher standard.
Assessment, audit and enforcement
There is no certification, external audit or registration regime. Compliance is supervised by the Iowa Attorney General, who has exclusive enforcement authority. The law does not create a private right of action for consumers.
Before bringing an action, the Attorney General must give the controller or processor written notice identifying the alleged violations and a cure period, which is commonly cited as 90 days. If the violation is cured and the business provides a written statement saying so, no action follows. Where violations continue, the statute authorizes civil penalties per violation, up to a capped amount. Check the current text for the exact figure.
The cure period reduces immediate exposure, but it is not a plan. You will need to show that you can fix a problem quickly, which depends on knowing what your processes and evidence look like before a notice arrives.
A practical path to compliance
- Determine applicability. Count the Iowa consumers whose data you control or process annually, estimate the share of revenue from data sales, and check entity-level and data-level exemptions. Document the conclusion and revisit it each year.
- Map your personal data. Inventory what you collect from Iowa consumers, where it is stored, which systems and vendors touch it, and what purposes it serves. Separate sensitive data and children's data.
- Define roles. Decide, for each processing activity, whether you act as controller or processor, and identify who is a third party or a sale recipient.
- Update the privacy notice. Make sure it covers the required disclosures, including sale, targeted advertising and how to submit and appeal requests.
- Build the rights-request workflow. Set up intake channels, identity verification, routing to data owners, deadlines, extension handling, the appeals path and records of every response.
- Handle sensitive and children's data. Implement the notice and opt-out mechanism for sensitive data, and parental consent flows if you knowingly process data of children under 13.
- Review processor and vendor contracts. Add the required terms and confirm vendors can support deletion, access and compliance information requests.
- Document security practices. Align with a recognized framework and keep evidence of access control, encryption, logging, vulnerability management and incident response.
- Monitor and prepare to cure. Track control health, keep a response plan for an Attorney General notice, and train staff who handle requests.
How it maps to other frameworks
These are overlaps, not equivalences. Meeting another framework does not by itself make you ICDPA compliant.
- Other US state privacy laws. The ICDPA closely resembles the Virginia, Utah and Connecticut statutes in structure. Rights handling, notices and processor contracts can often be built once and adapted, though differences in definitions, thresholds and opt-out mechanics remain.
- GDPR. Both use the controller and processor model and similar rights, but the GDPR needs a legal basis for processing and has stricter obligations overall.
- ISO 27001 and SOC 2. These overlap with the security requirement, since they supply evidence of reasonable safeguards. They do not cover consumer rights, notices or sale disclosures.
- NIST CSF and NIST Privacy Framework. Useful for structuring security and privacy risk management programs that support the "reasonable practices" expectation.
- COPPA. Directly referenced for parental consent for children under 13.
FAQs
When did the ICDPA take effect?
It took effect on January 1, 2025. Covered organizations are expected to comply now.
Does the ICDPA apply to employee data?
Generally no. The law defines consumers as individuals acting in a personal or household context and excludes people acting in a commercial or employment context. Employee and B2B data is largely out of scope, but check how your own data is used.
Can consumers sue under the ICDPA?
No. There is no private right of action. Enforcement belongs to the Iowa Attorney General.
Is a data protection assessment required?
The ICDPA does not require formal data protection assessments. Many organizations still perform them to meet other state laws or the GDPR, and they are good practice for high-risk processing.
Is there a cure period?
Yes. The Attorney General must give notice and an opportunity to cure before enforcing, and the commonly cited period is 90 days. Do not rely on it as a compliance strategy.
Do small businesses need to comply?
Only if they meet the thresholds. There is no revenue test, so a small business with enough Iowa consumers' data, or one that earns most of its revenue from selling data, can be covered. Exemptions for certain entities and data types may still apply.
How Aristiun helps
Aristiun is the AI-powered compliance automation and threat modeling platform, powered by Ayurak AI. For privacy laws like the ICDPA, the hard part is showing that controls actually operate, not just that policies exist. You can browse compliance frameworks to see how related requirements fit together.
- Collect evidence automatically from connected systems such as AWS, Azure, GCP and GitHub, instead of using manual screenshots and spreadsheets.
- Map each piece of evidence to controls across all applicable frameworks at once, so one evidence base can support the ICDPA's security expectations alongside ISO 27001, SOC 2 or other regimes.
- Monitor control effectiveness and get alerts when controls drift out of compliance, so you can remediate early.
- Map vendor controls to your compliance requirements to support processor oversight, and use AI-powered gap analysis to identify missing evidence.