Data Protection Impact Assessment (DPIA) - Idaho

Idaho Compliance & Regulatory Updated October 19, 2026 Free Word and PDF

DATA PROTECTION IMPACT ASSESSMENT (DPIA)

State of Idaho


Organization: [________________________________]
Assessment Date: [__/__/____]
Assessment Reference No.: [________________________________]
Prepared By: [________________________________]
Department/Division: [________________________________]


1. Project Overview

Project Name / Identifier: [________________________________]

Project Owner: [________________________________]

Executive Sponsor: [________________________________]

Project Description:
[____________________________________________________________]
[____________________________________________________________]
[____________________________________________________________]

Business Justification:
[____________________________________________________________]
[____________________________________________________________]

Projected Launch Date: [__/__/____]

Project Phase: [____] (e.g., concept, design, development, deployment, ongoing operations)

Systems / Applications Involved:

System Name Vendor Environment Data Types
[________________________________] [________________________________] [____] [________________________________]
[________________________________] [________________________________] [____] [________________________________]
[________________________________] [________________________________] [____] [________________________________]

2. Scope of Processing

2.1 Data Subjects

☐ Customers / Consumers
☐ Employees / Job Applicants
☐ Vendors / Contractors
☐ End Users (App / Website)
☐ Idaho residents served by a public agency
☐ Minors (under 13)
☐ Minors (13-17)
☐ Other: [________________________________]

2.2 Categories of Personal Data Collected

Personal Information as Defined by Idaho Code § 28-51-104(5):

An Idaho resident's first name or first initial and last name in combination with any one or more of the following data elements, when either the name or the data element is not encrypted:

☐ Social Security number
☐ Driver's license number or Idaho identification card number
☐ Financial account number, or credit card or debit card number, in combination with any required security code, access code, or password that would permit access to a resident's financial account

Note: Section 28-51-104(5) does not separately enumerate medical information, health insurance information, biometric data, or username/password combinations. Organizations should assess those categories under any other applicable requirements.

2.3 Additional Data Categories (Beyond Idaho Statutory Minimum)

While not specifically enumerated in Idaho Code § 28-51-104, the following categories should be documented for comprehensive risk assessment:

☐ Medical / health information
☐ Health insurance information
☐ Biometric identifiers (fingerprints, facial geometry, etc.)
☐ Geolocation data
☐ Username or email address with password or security question
☐ Tax identification numbers
☐ Passport numbers
☐ Student records
☐ Other: [________________________________]

2.4 Volume and Retention

  • Estimated number of data subjects: [________________________________]
  • Estimated records per year: [________________________________]
  • Retention period: [________________________________]
  • Deletion/destruction triggers: [________________________________]
  • Legal hold procedures: [________________________________]

2.5 Processing Activities

☐ Collection
☐ Storage / Hosting
☐ Analysis / Profiling
☐ Automated decision-making
☐ Sharing with third parties
☐ Sale of data
☐ Cross-border transfer
☐ Other: [________________________________]


3. Legal Basis, Notices, and Rights

3.1 Idaho Data Protection Legal Landscape

This assessment addresses Idaho's security-breach definitions, notice duties, compliance routes, and enforcement provisions in Idaho Code §§ 28-51-104 through 28-51-107. Assess other state, federal, and industry-specific duties separately.

Statute Citation Scope
Identity Theft / Breach Notification Idaho Code §§ 28-51-104 to 28-51-107 Security-breach definitions, notice, compliance routes, and enforcement

3.2 Scope of This Chapter

Sections 28-51-104 through 28-51-107 address covered security breaches. They do not themselves establish a general data-access, correction, deletion, sale opt-out, or portability process. Section 28-51-107 gives enforcement authority to the entity's primary regulator and does not expressly create a private action. Analyze any rights or remedies under other applicable law separately.

3.3 Entity Classification Under Idaho Law

Idaho's breach notification statute applies differently based on entity type:

☐ State, city, or county agency -- Subject to 24-hour AG notification requirement
☐ Commercial entity -- May (but not required to) notify the AG
☐ Individual -- Same notification obligations as commercial entities
☐ Third-party data holder -- Must immediately notify and cooperate with the owner or licensee when the statutory breach and misuse conditions are met

Entity Classification for This Assessment: [________________________________]

3.4 Applicable Federal Overlays

☐ HIPAA (health data)
☐ GLBA (financial data)
☐ FERPA (educational records)
☐ COPPA (children under 13)
☐ FCRA (consumer reports)
☐ Other: [________________________________]


4. Data Flow and Transfers

4.1 Data Flow Diagram

Data Sources:

Source Data Type Collection Method Legal Basis
[________________________________] [________________________________] [________________________________] [________________________________]
[________________________________] [________________________________] [________________________________] [________________________________]
[________________________________] [________________________________] [________________________________] [________________________________]

Data Storage Locations:

System / Platform Cloud Region / Data Center Encryption at Rest Encryption in Transit
[________________________________] [________________________________] ☐ Yes ☐ No ☐ Yes ☐ No
[________________________________] [________________________________] ☐ Yes ☐ No ☐ Yes ☐ No

4.2 Third-Party Recipients

Recipient Purpose DPA in Place Due Diligence Completed
[________________________________] [________________________________] ☐ Yes ☐ No ☐ Yes ☐ No
[________________________________] [________________________________] ☐ Yes ☐ No ☐ Yes ☐ No

4.3 Cross-Border Transfers

☐ Data remains within the United States
☐ Data transferred internationally -- Transfer mechanism: [________________________________]

4.4 Access Controls

  • Role-based access control (RBAC) groups: [________________________________]
  • Least privilege principle: ☐ Implemented ☐ Not yet implemented
  • Joiner/mover/leaver process: ☐ Documented ☐ Not documented
  • Privileged access review cadence: [________________________________]

5. Security and Controls

5.1 Technical Controls

☐ Encryption at rest (standard: [________________________________])
☐ Encryption in transit (TLS version: [________________________________])
☐ Key management system: [________________________________]
☐ Network segmentation / micro-segmentation
☐ Endpoint detection and response (EDR)
☐ Logging and monitoring (SIEM: [________________________________])
☐ Data loss prevention (DLP)
☐ Automated backup and disaster recovery
☐ Vulnerability management and patch cadence: [________________________________]
☐ Intrusion detection / prevention systems
☐ Web application firewall (WAF)

Encryption condition: Under Idaho Code § 28-51-104(2), a "breach of the security of the system" means the illegal acquisition of unencrypted computerized data that materially compromises covered personal information. Determine the precise data and encryption status; do not treat encryption as an exception to independently applicable security duties.

5.2 Organizational Controls

☐ Information security policy (last reviewed: [__/__/____])
☐ Privacy policy (last reviewed: [__/__/____])
☐ Acceptable use policy
☐ Employee training cadence: [________________________________]
☐ Vendor due diligence program
☐ Incident response plan (last tested: [__/__/____])
☐ Change management procedures
☐ Data classification framework

5.3 Authentication and Authorization

☐ Multi-factor authentication (MFA) for all privileged access
☐ Single sign-on (SSO) / SAML integration
☐ Session timeout policies: [________________________________]
☐ Privileged access management (PAM) solution: [________________________________]


6. Risk Assessment

6.1 Identified Risks

Risk ID Risk Description Likelihood Impact Risk Rating Mitigation
ID-01 Unauthorized acquisition of unencrypted PI triggering breach notification [____] High [____] [________________________________]
ID-02 Public agency fails to notify AG within 24-hour window [____] High [____] [________________________________]
ID-03 Third-party vendor breach affecting Idaho residents' PI [____] [____] [____] [________________________________]
ID-04 Encryption key compromise requiring assessment of whether covered data remained protected [____] High [____] [________________________________]
ID-05 Inadequate investigation following potential breach [____] [____] [____] [________________________________]
ID-06 Failure to notify data owner/licensee by third-party holder [____] [____] [____] [________________________________]
ID-07 Children's data collected without COPPA compliance [____] [____] [____] [________________________________]
ID-08 Unauthorized insider access to PI [____] [____] [____] [________________________________]
ID-09 [________________________________] [____] [____] [____] [________________________________]

6.2 Risk Rating Matrix

Low Impact Medium Impact High Impact Critical Impact
High Likelihood Medium High Critical Critical
Medium Likelihood Low Medium High Critical
Low Likelihood Low Low Medium High

6.3 Idaho-Specific Risk Considerations

  • Investigation requirement: Idaho law requires a "reasonable and prompt investigation" to determine the likelihood of misuse before notification is required (Idaho Code § 28-51-105(1)). Notification is required only if misuse has occurred or is "reasonably likely to occur." Failure to conduct an adequate investigation could increase liability.
  • 24-hour AG notification for public agencies: Covered agencies should have a process to meet the statutory deadline.
  • Third-party immediate notification: A holder that does not own or license the covered data must notify and cooperate with its owner or licensee immediately after discovering a covered breach if misuse occurred or is reasonably likely.
  • Intentional failure penalties: Up to $25,000 per breach for intentional failure to notify.

7. Mitigations and Residual Risk

7.1 Planned Mitigations

Risk ID Mitigation Action Owner Target Date Status
[____] [________________________________] [________________________________] [__/__/____] ☐ Not Started ☐ In Progress ☐ Complete
[____] [________________________________] [________________________________] [__/__/____] ☐ Not Started ☐ In Progress ☐ Complete
[____] [________________________________] [________________________________] [__/__/____] ☐ Not Started ☐ In Progress ☐ Complete
[____] [________________________________] [________________________________] [__/__/____] ☐ Not Started ☐ In Progress ☐ Complete

7.2 Validation and Testing

☐ Penetration testing completed (date: [__/__/____])
☐ Security audit completed (date: [__/__/____])
☐ Privacy-by-design review completed
☐ Tabletop incident response exercise conducted (date: [__/__/____])
☐ Vendor security assessments completed
☐ 24-hour AG notification drill (for public agencies) (date: [__/__/____])

7.3 Residual Risk Determination

Overall Residual Risk Rating: ☐ Low ☐ Medium ☐ High ☐ Critical

Decision: ☐ Accept ☐ Mitigate Further ☐ Transfer (Insurance) ☐ Avoid / Block Project

Justification: [____________________________________________________________]


8. Incident Response and Breach Notification

8.1 Idaho Breach Notification Requirements (Idaho Code § 28-51-105)

8.1.1 Triggering Event

A "breach of the security of the system" is the illegal acquisition of unencrypted computerized data that materially compromises the security, confidentiality, or integrity of personal information for one or more persons maintained by an agency, individual, or a commercial entity (Idaho Code § 28-51-104(2)).

Good-faith exception: Good-faith acquisition of personal information by an employee or agent for the entity's purposes is not a breach, provided the information is not used or subject to further unauthorized disclosure (Idaho Code § 28-51-104(2)).

8.1.2 Investigation Requirement

Upon becoming aware of a breach, the entity must conduct in good faith a reasonable and prompt investigation to determine the likelihood that personal information has been or will be misused. Notification is required only if the investigation determines that misuse has occurred or is reasonably likely to occur (Idaho Code § 28-51-105(1)).

8.1.3 Notification Requirements by Entity Type
Entity Type Individual Notice AG Notice Timeline
State, city, or county agency Required Required within 24 hours of discovery As soon as possible
Commercial entity Required (if misuse likely) May notify but not required As soon as possible
Individual Required (if misuse likely) May notify but not required As soon as possible
Third-party data holder N/A (notify data owner) N/A Immediately after discovering a covered breach when the misuse condition is met
8.1.4 Methods of Notification (Idaho Code § 28-51-104(4))

☐ Written notice to the most recent address in the entity's records
☐ Telephonic notice
☐ Electronic notice (if consistent with E-SIGN Act, 15 U.S.C. § 7001)
☐ Substitute notice -- available if:

  • Cost would exceed $25,000, OR
  • Affected class exceeds 50,000 residents, OR
  • Entity does not have sufficient contact information

Substitute notice requires ALL of the following:

  • Email notice (if email address is available)
  • Conspicuous posting on the entity's website (if one is maintained)
  • Notification to major statewide media
8.1.5 Law Enforcement Delay

Notice may be delayed if a law enforcement agency advises that notification will impede a criminal investigation. Notice must be provided in good faith, without unreasonable delay, and as soon as possible after law enforcement advises that notification will no longer impede the investigation (Idaho Code § 28-51-105(3)).

8.1.6 Penalties (Idaho Code § 28-51-107)
Violation Penalty
Intentional failure to disclose a breach Up to $25,000 per breach
Enforcement The entity's primary regulator as defined by § 28-51-104(6)
Additional remedies Injunctive relief
Private right of action No express private action in §§ 28-51-104 through -107; assess other law separately
8.1.7 Deemed-Compliance Routes (Idaho Code § 28-51-106)

An entity that maintains its own notification procedures as part of an information security policy and is otherwise consistent with the timing requirements of the Idaho statute is deemed to be in compliance, provided the entity notifies affected Idaho residents in accordance with its policies in the event of a breach.

8.2 Internal Incident Response Procedures

Incident Response Team Lead: [________________________________]
Legal Counsel (ID-licensed): [________________________________]
AG Notification Contact (for public agencies): Idaho Office of the Attorney General — confirm current reporting channel before submission

Response Timeline:

Step Action Responsible Party Target Timeframe
1 Identify and contain the incident [________________________________] Immediate
2 Determine if PI (as defined by Idaho Code § 28-51-104) is involved [________________________________] Within 12 hours
3 Conduct reasonable and prompt investigation [________________________________] Begin immediately
4 Determine likelihood of misuse [________________________________] Within 48-72 hours
5 If public agency: notify Idaho AG within 24 hours [________________________________] Within 24 hours of discovery
6 Engage Idaho-licensed legal counsel [________________________________] Within 24 hours
7 If third-party holder and § 28-51-105(2) breach/misuse conditions are met: notify and cooperate with data owner/licensee [________________________________] Immediately after discovery
8 Prepare and send notification to affected individuals [________________________________] As soon as possible
9 Document incident, investigation, and remediation [________________________________] Ongoing

9. State Law Overlay Summary -- Idaho

9.1 Key Compliance Obligations

Area Requirement Citation
Breach notification Notify affected ID residents as soon as possible after investigation confirms misuse likely Idaho Code § 28-51-105
Investigation Good-faith, reasonable, and prompt investigation required Idaho Code § 28-51-105(1)
Public agency AG notice Covered agency notice within 24 hours of discovery Idaho Code § 28-51-105(1)
Third-party notice Immediately notify and cooperate with data owner/licensee when role and misuse gates apply Idaho Code § 28-51-105(2)
Encryption condition Breach definition is limited to illegal acquisition of unencrypted computerized data meeting the material-compromise test Idaho Code § 28-51-104(2)
Substitute notice Cost > $25K or more than 50,000 affected Idaho residents or insufficient contact information; all stated components apply Idaho Code § 28-51-104(4)(d)
Deemed compliance Qualifying own-policy or regulator-procedure route, with the statutory timing/compliance conditions Idaho Code § 28-51-106
Penalties Up to $25,000 per breach for intentional failure Idaho Code § 28-51-107
Private right of action No express private action in this chapter Idaho Code § 28-51-107

9.2 Idaho-Specific Compliance Checklist

☐ Personal information as defined by Idaho Code § 28-51-104 has been identified and documented
☐ Entity type classification determined (public agency vs. commercial entity vs. third-party holder)
☐ Encryption status and key access reviewed for covered data at rest and in transit
☐ Incident response plan includes Idaho-specific investigation requirement
☐ Incident response plan includes 24-hour AG notification procedure (if public agency)
☐ Third-party vendor contracts require immediate notification to data owner upon breach
☐ Substitute notice procedures documented (if applicable)
☐ If relying on deemed compliance under § 28-51-106, the exact own-policy or regulator-procedure conditions are documented and satisfied
☐ Employee training on breach identification and reporting is current
☐ COPPA compliance confirmed for any children's data
☐ Federal overlay requirements documented (HIPAA, GLBA, FERPA as applicable)
☐ Cyber liability insurance coverage reviewed


10. Approvals and Accountability

Role Name Signature Date
Privacy Lead / DPO [________________________________] [________________________________] [__/__/____]
Information Security Officer [________________________________] [________________________________] [__/__/____]
Legal Counsel (ID-licensed) [________________________________] [________________________________] [__/__/____]
Business Owner [________________________________] [________________________________] [__/__/____]
Executive Approver [________________________________] [________________________________] [__/__/____]

Next Review Date: [__/__/____]


11. Attachments

☐ Data flow diagrams and architecture documentation
☐ Records of processing activities (ROPA) entry
☐ Vendor list and data processing agreements
☐ Information security policy (for applicable § 28-51-106 notice-procedure route)
☐ Penetration test reports
☐ Incident response playbook (ID-specific)
☐ Breach notification letter template (ID-specific)
☐ AG notification template (for public agencies)
☐ Insurance policy summary (cyber liability)


Sources and References

  • Idaho Legislature, Title 28 Chapter 51 (Identity Theft): https://legislature.idaho.gov/statutesrules/idstat/title28/t28ch51/
  • Idaho Code § 28-51-104: https://legislature.idaho.gov/statutesrules/idstat/title28/t28ch51/sect28-51-104/
  • Idaho Code § 28-51-105: https://legislature.idaho.gov/statutesrules/idstat/title28/t28ch51/sect28-51-105/
  • Idaho Office of the Attorney General, Security Breaches: https://www.ag.idaho.gov/consumer-protection/security-breaches/

Insert Image

Insert Table

Watch Ezel in action (sample case)Choose a plan

All changes saved
Save
Export
Export as DOCX
Export as PDF
Generating PDF...
data_protection_impact_assessment_id.pdf
Ready to export as PDF or Word
AI is editing...
Chat
Review

Draft it in the editor

The AI drafts each section from your answers and you review every word. Drafting from scratch takes hours; finish yours for $99 one time.

  • Built on this template
    Uses the Idaho version and the statutes it cites.
  • Formatted like the template
    Captions, numbering and layout stay intact.
  • AI editing
    Rewrite any section from your own notes.
  • Export as PDF and Word
    Yours to review, sign, or file.
Secure checkout via Stripe
Need to customize this document?

About this template

Last updated
October 19, 2026
Citations checked
October 19, 2026
Jurisdiction
Idaho
Category
Compliance & Regulatory

Legal authority

  • Idaho Code § 28-51-104 (definitions of personal information, breach, and notice)
  • Idaho Code § 28-51-105 (investigation and breach notice)
  • Idaho Code § 28-51-106 (deemed-compliance procedures)
  • Idaho Code § 28-51-107 (regulator enforcement and intentional-failure fine)

Compliance documents are what regulated businesses use to prove they follow the rules that apply to their industry, whether that is privacy, anti-money-laundering, consumer protection, or sector-specific requirements. Regulators look for consistent policies, up-to-date records, and clear evidence of employee training. The cost of getting compliance paperwork right is almost always smaller than the cost of an enforcement action, fine, or public disclosure.

Not legal advice

This template is provided for informational purposes. We recommend having an attorney review any legal document before signing, especially for high-value or complex matters.

Checked against the law it cites

A reviewer verified this template's legal citations against the official source on October 19, 2026.

Idaho Code § 28-51-104(5) (checked October 19, 2026): "when either the name or the data elements are not encrypted"

Idaho Code § 28-51-105(1) (checked October 19, 2026): "conduct in good faith a reasonable and prompt investigation to determine the likelihood that personal information has been or will be misused"

Idaho Code § 28-51-106(1) (checked October 19, 2026): "maintains its own notice procedures as part of an information security policy for the treatment of personal information"

Idaho Code § 28-51-107 (checked October 19, 2026): "shall be subject to a fine of not more than twenty-five thousand dollars ($25,000) per breach of the security of the system."

Draft your Data Protection Impact Assessment (DPIA) - Idaho in the editor

Answer a few questions, let the AI editor draft each section from your answers, review it, and download Word and PDF. $99 one time, or $249 per month for every document and every Ezel app.