open-agreements 0.7.7 → 0.8.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (704) hide show
  1. package/LICENSE +201 -21
  2. package/README.de.md +16 -29
  3. package/README.es.md +16 -29
  4. package/README.md +45 -54
  5. package/README.pt-br.md +16 -29
  6. package/README.template.md +19 -25
  7. package/README.zh.md +16 -29
  8. package/content/recipes/nvca-certificate-of-incorporation/fields/acquisition_exception_shares.json +36 -0
  9. package/content/recipes/nvca-certificate-of-incorporation/fields/adjustment_notice_days.json +22 -0
  10. package/content/recipes/nvca-certificate-of-incorporation/fields/common_shares_authorized.json +22 -0
  11. package/content/recipes/nvca-certificate-of-incorporation/fields/company_name.json +29 -0
  12. package/content/recipes/nvca-certificate-of-incorporation/fields/conversion_notice_days.json +22 -0
  13. package/content/recipes/nvca-certificate-of-incorporation/fields/dividend_formula_alt.json +22 -0
  14. package/content/recipes/nvca-certificate-of-incorporation/fields/dividend_rate_per_share.json +22 -0
  15. package/content/recipes/nvca-certificate-of-incorporation/fields/dividend_rate_percent.json +22 -0
  16. package/content/recipes/nvca-certificate-of-incorporation/fields/effective_date.json +22 -0
  17. package/content/recipes/nvca-certificate-of-incorporation/fields/number_of_classes.json +29 -0
  18. package/content/recipes/nvca-certificate-of-incorporation/fields/original_issue_price.json +22 -0
  19. package/content/recipes/nvca-certificate-of-incorporation/fields/par_value.json +36 -0
  20. package/content/recipes/nvca-certificate-of-incorporation/fields/preferred_director_seats.json +22 -0
  21. package/content/recipes/nvca-certificate-of-incorporation/fields/preferred_shares_authorized.json +22 -0
  22. package/content/recipes/nvca-certificate-of-incorporation/fields/preferred_shares_designated_portion.json +29 -0
  23. package/content/recipes/nvca-certificate-of-incorporation/fields/preferred_shares_outstanding_threshold.json +29 -0
  24. package/content/recipes/nvca-certificate-of-incorporation/fields/qualified_financing_notice_days.json +22 -0
  25. package/content/recipes/nvca-certificate-of-incorporation/fields/redemption_interest_rate.json +22 -0
  26. package/content/recipes/nvca-certificate-of-incorporation/fields/redemption_start_date.json +22 -0
  27. package/content/recipes/nvca-certificate-of-incorporation/fields/registered_agent_address.json +22 -0
  28. package/content/recipes/nvca-certificate-of-incorporation/fields/registered_agent_name.json +22 -0
  29. package/content/recipes/nvca-certificate-of-incorporation/fields/series_designation.json +22 -0
  30. package/content/recipes/nvca-certificate-of-incorporation/fields/signature_page_marker.json +22 -0
  31. package/content/recipes/nvca-certificate-of-incorporation/fields/specify_percentage.json +22 -0
  32. package/content/recipes/nvca-certificate-of-incorporation/fields/strategic_partnership_exception_shares.json +22 -0
  33. package/content/recipes/nvca-certificate-of-incorporation/fields/time_zone.json +22 -0
  34. package/content/recipes/nvca-certificate-of-incorporation/fields/total_authorized_shares.json +22 -0
  35. package/content/recipes/nvca-certificate-of-incorporation/template-manifest.json +77 -0
  36. package/content/recipes/nvca-stock-purchase-agreement/fields/agreement_date_month_day.json +27 -0
  37. package/content/recipes/nvca-stock-purchase-agreement/fields/agreement_year_two_digits.json +27 -0
  38. package/content/recipes/nvca-stock-purchase-agreement/fields/company_name.json +25 -0
  39. package/content/recipes/nvca-stock-purchase-agreement/fields/investor_counsel.json +27 -0
  40. package/content/recipes/nvca-stock-purchase-agreement/fields/minimum_shares_initial_closing.json +39 -0
  41. package/content/recipes/nvca-stock-purchase-agreement/fields/optional_plural_suffix.json +27 -0
  42. package/content/recipes/nvca-stock-purchase-agreement/fields/par_value_per_share.json +28 -0
  43. package/content/recipes/nvca-stock-purchase-agreement/fields/purchase_price_per_share.json +28 -0
  44. package/content/recipes/nvca-stock-purchase-agreement/fields/series_designation.json +159 -0
  45. package/content/recipes/nvca-stock-purchase-agreement/metadata.yaml +1 -1
  46. package/content/recipes/nvca-stock-purchase-agreement/template-manifest.json +24 -0
  47. package/content/templates/bonterms-mutual-nda/template.docx +0 -0
  48. package/content/templates/openagreements-board-consent-safe/.template.generated.json +0 -1
  49. package/content/templates/openagreements-employee-ip-inventions-assignment/.template.generated.json +9 -5
  50. package/content/templates/openagreements-employee-ip-inventions-assignment/README.md +2 -0
  51. package/content/templates/openagreements-employee-ip-inventions-assignment/metadata.yaml +8 -9
  52. package/content/templates/openagreements-employee-ip-inventions-assignment/template.docx +0 -0
  53. package/content/templates/openagreements-employee-ip-inventions-assignment/template.md +3 -4
  54. package/content/templates/openagreements-employment-confidentiality-acknowledgement/metadata.yaml +0 -9
  55. package/content/templates/openagreements-employment-confidentiality-acknowledgement/template.docx +0 -0
  56. package/content/templates/openagreements-employment-confidentiality-acknowledgement/template.json +0 -1
  57. package/content/templates/openagreements-employment-offer-letter/.template.generated.json +9 -5
  58. package/content/templates/openagreements-employment-offer-letter/README.md +17 -5
  59. package/content/templates/openagreements-employment-offer-letter/metadata.yaml +8 -9
  60. package/content/templates/openagreements-employment-offer-letter/template.docx +0 -0
  61. package/content/templates/openagreements-employment-offer-letter/template.md +3 -4
  62. package/content/templates/openagreements-restrictive-covenant-florida/.template.generated.json +9 -5
  63. package/content/templates/openagreements-restrictive-covenant-florida/README.md +2 -2
  64. package/content/templates/openagreements-restrictive-covenant-florida/metadata.yaml +10 -12
  65. package/content/templates/openagreements-restrictive-covenant-florida/template.docx +0 -0
  66. package/content/templates/openagreements-restrictive-covenant-florida/template.md +3 -4
  67. package/content/templates/openagreements-restrictive-covenant-wyoming/.template.generated.json +9 -5
  68. package/content/templates/openagreements-restrictive-covenant-wyoming/metadata.yaml +10 -12
  69. package/content/templates/openagreements-restrictive-covenant-wyoming/template.docx +0 -0
  70. package/content/templates/openagreements-restrictive-covenant-wyoming/template.md +3 -4
  71. package/content/templates/openagreements-stockholder-consent-safe/.template.generated.json +0 -1
  72. package/dist/core/checklist/format-checklist-docx.d.ts.map +1 -1
  73. package/dist/core/checklist/format-checklist-docx.js +4 -1
  74. package/dist/core/checklist/format-checklist-docx.js.map +1 -1
  75. package/dist/core/engine.d.ts.map +1 -1
  76. package/dist/core/engine.js +2 -40
  77. package/dist/core/engine.js.map +1 -1
  78. package/dist/core/fill-pipeline.d.ts +0 -8
  79. package/dist/core/fill-pipeline.d.ts.map +1 -1
  80. package/dist/core/fill-pipeline.js +54 -30
  81. package/dist/core/fill-pipeline.js.map +1 -1
  82. package/dist/core/humanize-docx.d.ts.map +1 -1
  83. package/dist/core/humanize-docx.js +16 -6
  84. package/dist/core/humanize-docx.js.map +1 -1
  85. package/dist/core/recipe/bracket-normalizer.d.ts.map +1 -1
  86. package/dist/core/recipe/bracket-normalizer.js +3 -7
  87. package/dist/core/recipe/bracket-normalizer.js.map +1 -1
  88. package/dist/core/recipe/cleaner.js +5 -5
  89. package/dist/core/recipe/cleaner.js.map +1 -1
  90. package/dist/core/recipe/index.d.ts +1 -1
  91. package/dist/core/recipe/index.d.ts.map +1 -1
  92. package/dist/core/recipe/index.js +57 -4
  93. package/dist/core/recipe/index.js.map +1 -1
  94. package/dist/core/recipe/ooxml-parts.d.ts +11 -0
  95. package/dist/core/recipe/ooxml-parts.d.ts.map +1 -1
  96. package/dist/core/recipe/ooxml-parts.js +22 -0
  97. package/dist/core/recipe/ooxml-parts.js.map +1 -1
  98. package/dist/core/recipe/patcher.d.ts.map +1 -1
  99. package/dist/core/recipe/patcher.js +2 -5
  100. package/dist/core/recipe/patcher.js.map +1 -1
  101. package/dist/core/recipe/source-drift.d.ts +19 -0
  102. package/dist/core/recipe/source-drift.d.ts.map +1 -1
  103. package/dist/core/recipe/source-drift.js +32 -2
  104. package/dist/core/recipe/source-drift.js.map +1 -1
  105. package/dist/core/selector.d.ts.map +1 -1
  106. package/dist/core/selector.js +49 -4
  107. package/dist/core/selector.js.map +1 -1
  108. package/dist/core/selectors/index.d.ts +40 -0
  109. package/dist/core/selectors/index.d.ts.map +1 -0
  110. package/dist/core/selectors/index.js +64 -0
  111. package/dist/core/selectors/index.js.map +1 -0
  112. package/dist/core/selectors/loader.d.ts +16 -0
  113. package/dist/core/selectors/loader.d.ts.map +1 -0
  114. package/dist/core/selectors/loader.js +80 -0
  115. package/dist/core/selectors/loader.js.map +1 -0
  116. package/dist/core/selectors/manifest-schema.d.ts +123 -0
  117. package/dist/core/selectors/manifest-schema.d.ts.map +1 -0
  118. package/dist/core/selectors/manifest-schema.js +93 -0
  119. package/dist/core/selectors/manifest-schema.js.map +1 -0
  120. package/dist/core/selectors/patch.d.ts +24 -0
  121. package/dist/core/selectors/patch.d.ts.map +1 -0
  122. package/dist/core/selectors/patch.js +68 -0
  123. package/dist/core/selectors/patch.js.map +1 -0
  124. package/dist/core/selectors/postconditions.d.ts +24 -0
  125. package/dist/core/selectors/postconditions.d.ts.map +1 -0
  126. package/dist/core/selectors/postconditions.js +50 -0
  127. package/dist/core/selectors/postconditions.js.map +1 -0
  128. package/dist/core/selectors/resolve.d.ts +32 -0
  129. package/dist/core/selectors/resolve.d.ts.map +1 -0
  130. package/dist/core/selectors/resolve.js +36 -0
  131. package/dist/core/selectors/resolve.js.map +1 -0
  132. package/dist/core/unified-pipeline.d.ts +3 -1
  133. package/dist/core/unified-pipeline.d.ts.map +1 -1
  134. package/dist/core/unified-pipeline.js +19 -5
  135. package/dist/core/unified-pipeline.js.map +1 -1
  136. package/gemini-extension.json +1 -1
  137. package/node_modules/@usejunior/docx-core/LICENSE +202 -21
  138. package/node_modules/@usejunior/docx-core/NOTICE +2 -0
  139. package/node_modules/@usejunior/docx-core/README.md +2 -2
  140. package/node_modules/@usejunior/docx-core/dist/.tsbuildinfo +1 -1
  141. package/node_modules/@usejunior/docx-core/dist/atomizer.d.ts +55 -0
  142. package/node_modules/@usejunior/docx-core/dist/atomizer.d.ts.map +1 -1
  143. package/node_modules/@usejunior/docx-core/dist/atomizer.js +139 -14
  144. package/node_modules/@usejunior/docx-core/dist/atomizer.js.map +1 -1
  145. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/auxiliaryIdCollision.d.ts +99 -0
  146. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/auxiliaryIdCollision.d.ts.map +1 -0
  147. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/auxiliaryIdCollision.js +415 -0
  148. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/auxiliaryIdCollision.js.map +1 -0
  149. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/documentReconstructor.d.ts.map +1 -1
  150. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/documentReconstructor.js +403 -113
  151. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/documentReconstructor.js.map +1 -1
  152. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/formattingFidelity.d.ts +99 -0
  153. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/formattingFidelity.d.ts.map +1 -0
  154. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/formattingFidelity.js +449 -0
  155. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/formattingFidelity.js.map +1 -0
  156. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/inPlaceModifier-bookmarks.d.ts +37 -0
  157. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/inPlaceModifier-bookmarks.d.ts.map +1 -0
  158. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/inPlaceModifier-bookmarks.js +189 -0
  159. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/inPlaceModifier-bookmarks.js.map +1 -0
  160. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/inPlaceModifier-containers.d.ts +74 -0
  161. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/inPlaceModifier-containers.d.ts.map +1 -0
  162. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/inPlaceModifier-containers.js +171 -0
  163. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/inPlaceModifier-containers.js.map +1 -0
  164. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/inPlaceModifier-deletion.d.ts +88 -0
  165. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/inPlaceModifier-deletion.d.ts.map +1 -0
  166. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/inPlaceModifier-deletion.js +326 -0
  167. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/inPlaceModifier-deletion.js.map +1 -0
  168. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/inPlaceModifier-postprocess.d.ts +85 -0
  169. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/inPlaceModifier-postprocess.d.ts.map +1 -0
  170. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/inPlaceModifier-postprocess.js +402 -0
  171. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/inPlaceModifier-postprocess.js.map +1 -0
  172. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/inPlaceModifier-presplit.d.ts +39 -0
  173. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/inPlaceModifier-presplit.d.ts.map +1 -0
  174. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/inPlaceModifier-presplit.js +265 -0
  175. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/inPlaceModifier-presplit.js.map +1 -0
  176. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/inPlaceModifier-shared.d.ts +62 -0
  177. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/inPlaceModifier-shared.d.ts.map +1 -0
  178. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/inPlaceModifier-shared.js +139 -0
  179. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/inPlaceModifier-shared.js.map +1 -0
  180. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/inPlaceModifier-wrappers.d.ts +198 -0
  181. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/inPlaceModifier-wrappers.d.ts.map +1 -0
  182. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/inPlaceModifier-wrappers.js +475 -0
  183. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/inPlaceModifier-wrappers.js.map +1 -0
  184. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/inPlaceModifier.d.ts +6 -290
  185. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/inPlaceModifier.d.ts.map +1 -1
  186. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/inPlaceModifier.js +23 -1828
  187. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/inPlaceModifier.js.map +1 -1
  188. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/pipeline.d.ts +36 -2
  189. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/pipeline.d.ts.map +1 -1
  190. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/pipeline.js +456 -224
  191. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/pipeline.js.map +1 -1
  192. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/trackChangesAcceptorAst.d.ts.map +1 -1
  193. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/trackChangesAcceptorAst.js +199 -173
  194. package/node_modules/@usejunior/docx-core/dist/baselines/atomizer/trackChangesAcceptorAst.js.map +1 -1
  195. package/node_modules/@usejunior/docx-core/dist/baselines/wmlcomparer/DotnetCli.d.ts.map +1 -1
  196. package/node_modules/@usejunior/docx-core/dist/baselines/wmlcomparer/DotnetCli.js +7 -0
  197. package/node_modules/@usejunior/docx-core/dist/baselines/wmlcomparer/DotnetCli.js.map +1 -1
  198. package/node_modules/@usejunior/docx-core/dist/cli/compare-two.d.ts.map +1 -1
  199. package/node_modules/@usejunior/docx-core/dist/cli/compare-two.js +3 -1
  200. package/node_modules/@usejunior/docx-core/dist/cli/compare-two.js.map +1 -1
  201. package/node_modules/@usejunior/docx-core/dist/cli/conformance-adapter.d.ts +3 -0
  202. package/node_modules/@usejunior/docx-core/dist/cli/conformance-adapter.d.ts.map +1 -0
  203. package/node_modules/@usejunior/docx-core/dist/cli/conformance-adapter.js +93 -0
  204. package/node_modules/@usejunior/docx-core/dist/cli/conformance-adapter.js.map +1 -0
  205. package/node_modules/@usejunior/docx-core/dist/cli/index.d.ts.map +1 -1
  206. package/node_modules/@usejunior/docx-core/dist/cli/index.js +5 -1
  207. package/node_modules/@usejunior/docx-core/dist/cli/index.js.map +1 -1
  208. package/node_modules/@usejunior/docx-core/dist/compare-types.d.ts +197 -0
  209. package/node_modules/@usejunior/docx-core/dist/compare-types.d.ts.map +1 -0
  210. package/node_modules/@usejunior/docx-core/dist/compare-types.js +2 -0
  211. package/node_modules/@usejunior/docx-core/dist/compare-types.js.map +1 -0
  212. package/node_modules/@usejunior/docx-core/dist/core-types.d.ts +5 -1
  213. package/node_modules/@usejunior/docx-core/dist/core-types.d.ts.map +1 -1
  214. package/node_modules/@usejunior/docx-core/dist/core-types.js +5 -1
  215. package/node_modules/@usejunior/docx-core/dist/core-types.js.map +1 -1
  216. package/node_modules/@usejunior/docx-core/dist/footnotes.d.ts +8 -3
  217. package/node_modules/@usejunior/docx-core/dist/footnotes.d.ts.map +1 -1
  218. package/node_modules/@usejunior/docx-core/dist/footnotes.js +8 -3
  219. package/node_modules/@usejunior/docx-core/dist/footnotes.js.map +1 -1
  220. package/node_modules/@usejunior/docx-core/dist/generation/compile.d.ts +22 -0
  221. package/node_modules/@usejunior/docx-core/dist/generation/compile.d.ts.map +1 -0
  222. package/node_modules/@usejunior/docx-core/dist/generation/compile.js +58 -0
  223. package/node_modules/@usejunior/docx-core/dist/generation/compile.js.map +1 -0
  224. package/node_modules/@usejunior/docx-core/dist/generation/context.d.ts +42 -0
  225. package/node_modules/@usejunior/docx-core/dist/generation/context.d.ts.map +1 -0
  226. package/node_modules/@usejunior/docx-core/dist/generation/context.js +65 -0
  227. package/node_modules/@usejunior/docx-core/dist/generation/context.js.map +1 -0
  228. package/node_modules/@usejunior/docx-core/dist/generation/emit/comments-part.d.ts +36 -0
  229. package/node_modules/@usejunior/docx-core/dist/generation/emit/comments-part.d.ts.map +1 -0
  230. package/node_modules/@usejunior/docx-core/dist/generation/emit/comments-part.js +116 -0
  231. package/node_modules/@usejunior/docx-core/dist/generation/emit/comments-part.js.map +1 -0
  232. package/node_modules/@usejunior/docx-core/dist/generation/emit/document-part.d.ts +24 -0
  233. package/node_modules/@usejunior/docx-core/dist/generation/emit/document-part.d.ts.map +1 -0
  234. package/node_modules/@usejunior/docx-core/dist/generation/emit/document-part.js +60 -0
  235. package/node_modules/@usejunior/docx-core/dist/generation/emit/document-part.js.map +1 -0
  236. package/node_modules/@usejunior/docx-core/dist/generation/emit/emit-context.d.ts +28 -0
  237. package/node_modules/@usejunior/docx-core/dist/generation/emit/emit-context.d.ts.map +1 -0
  238. package/node_modules/@usejunior/docx-core/dist/generation/emit/emit-context.js +19 -0
  239. package/node_modules/@usejunior/docx-core/dist/generation/emit/emit-context.js.map +1 -0
  240. package/node_modules/@usejunior/docx-core/dist/generation/emit/font-table-part.d.ts +16 -0
  241. package/node_modules/@usejunior/docx-core/dist/generation/emit/font-table-part.d.ts.map +1 -0
  242. package/node_modules/@usejunior/docx-core/dist/generation/emit/font-table-part.js +74 -0
  243. package/node_modules/@usejunior/docx-core/dist/generation/emit/font-table-part.js.map +1 -0
  244. package/node_modules/@usejunior/docx-core/dist/generation/emit/header-footer-part.d.ts +23 -0
  245. package/node_modules/@usejunior/docx-core/dist/generation/emit/header-footer-part.d.ts.map +1 -0
  246. package/node_modules/@usejunior/docx-core/dist/generation/emit/header-footer-part.js +57 -0
  247. package/node_modules/@usejunior/docx-core/dist/generation/emit/header-footer-part.js.map +1 -0
  248. package/node_modules/@usejunior/docx-core/dist/generation/emit/numbering-part.d.ts +29 -0
  249. package/node_modules/@usejunior/docx-core/dist/generation/emit/numbering-part.d.ts.map +1 -0
  250. package/node_modules/@usejunior/docx-core/dist/generation/emit/numbering-part.js +102 -0
  251. package/node_modules/@usejunior/docx-core/dist/generation/emit/numbering-part.js.map +1 -0
  252. package/node_modules/@usejunior/docx-core/dist/generation/emit/package-parts.d.ts +24 -0
  253. package/node_modules/@usejunior/docx-core/dist/generation/emit/package-parts.d.ts.map +1 -0
  254. package/node_modules/@usejunior/docx-core/dist/generation/emit/package-parts.js +121 -0
  255. package/node_modules/@usejunior/docx-core/dist/generation/emit/package-parts.js.map +1 -0
  256. package/node_modules/@usejunior/docx-core/dist/generation/emit/paragraph.d.ts +24 -0
  257. package/node_modules/@usejunior/docx-core/dist/generation/emit/paragraph.d.ts.map +1 -0
  258. package/node_modules/@usejunior/docx-core/dist/generation/emit/paragraph.js +63 -0
  259. package/node_modules/@usejunior/docx-core/dist/generation/emit/paragraph.js.map +1 -0
  260. package/node_modules/@usejunior/docx-core/dist/generation/emit/properties.d.ts +36 -0
  261. package/node_modules/@usejunior/docx-core/dist/generation/emit/properties.d.ts.map +1 -0
  262. package/node_modules/@usejunior/docx-core/dist/generation/emit/properties.js +157 -0
  263. package/node_modules/@usejunior/docx-core/dist/generation/emit/properties.js.map +1 -0
  264. package/node_modules/@usejunior/docx-core/dist/generation/emit/run.d.ts +16 -0
  265. package/node_modules/@usejunior/docx-core/dist/generation/emit/run.d.ts.map +1 -0
  266. package/node_modules/@usejunior/docx-core/dist/generation/emit/run.js +71 -0
  267. package/node_modules/@usejunior/docx-core/dist/generation/emit/run.js.map +1 -0
  268. package/node_modules/@usejunior/docx-core/dist/generation/emit/section.d.ts +29 -0
  269. package/node_modules/@usejunior/docx-core/dist/generation/emit/section.d.ts.map +1 -0
  270. package/node_modules/@usejunior/docx-core/dist/generation/emit/section.js +117 -0
  271. package/node_modules/@usejunior/docx-core/dist/generation/emit/section.js.map +1 -0
  272. package/node_modules/@usejunior/docx-core/dist/generation/emit/settings-part.d.ts +13 -0
  273. package/node_modules/@usejunior/docx-core/dist/generation/emit/settings-part.d.ts.map +1 -0
  274. package/node_modules/@usejunior/docx-core/dist/generation/emit/settings-part.js +68 -0
  275. package/node_modules/@usejunior/docx-core/dist/generation/emit/settings-part.js.map +1 -0
  276. package/node_modules/@usejunior/docx-core/dist/generation/emit/styles-part.d.ts +16 -0
  277. package/node_modules/@usejunior/docx-core/dist/generation/emit/styles-part.d.ts.map +1 -0
  278. package/node_modules/@usejunior/docx-core/dist/generation/emit/styles-part.js +82 -0
  279. package/node_modules/@usejunior/docx-core/dist/generation/emit/styles-part.js.map +1 -0
  280. package/node_modules/@usejunior/docx-core/dist/generation/emit/table.d.ts +26 -0
  281. package/node_modules/@usejunior/docx-core/dist/generation/emit/table.d.ts.map +1 -0
  282. package/node_modules/@usejunior/docx-core/dist/generation/emit/table.js +209 -0
  283. package/node_modules/@usejunior/docx-core/dist/generation/emit/table.js.map +1 -0
  284. package/node_modules/@usejunior/docx-core/dist/generation/emit/theme-part.d.ts +21 -0
  285. package/node_modules/@usejunior/docx-core/dist/generation/emit/theme-part.d.ts.map +1 -0
  286. package/node_modules/@usejunior/docx-core/dist/generation/emit/theme-part.js +151 -0
  287. package/node_modules/@usejunior/docx-core/dist/generation/emit/theme-part.js.map +1 -0
  288. package/node_modules/@usejunior/docx-core/dist/generation/emit/web-settings-part.d.ts +12 -0
  289. package/node_modules/@usejunior/docx-core/dist/generation/emit/web-settings-part.d.ts.map +1 -0
  290. package/node_modules/@usejunior/docx-core/dist/generation/emit/web-settings-part.js +19 -0
  291. package/node_modules/@usejunior/docx-core/dist/generation/emit/web-settings-part.js.map +1 -0
  292. package/node_modules/@usejunior/docx-core/dist/generation/errors.d.ts +22 -0
  293. package/node_modules/@usejunior/docx-core/dist/generation/errors.d.ts.map +1 -0
  294. package/node_modules/@usejunior/docx-core/dist/generation/errors.js +29 -0
  295. package/node_modules/@usejunior/docx-core/dist/generation/errors.js.map +1 -0
  296. package/node_modules/@usejunior/docx-core/dist/generation/index.d.ts +13 -0
  297. package/node_modules/@usejunior/docx-core/dist/generation/index.d.ts.map +1 -0
  298. package/node_modules/@usejunior/docx-core/dist/generation/index.js +12 -0
  299. package/node_modules/@usejunior/docx-core/dist/generation/index.js.map +1 -0
  300. package/node_modules/@usejunior/docx-core/dist/generation/ordering.d.ts +46 -0
  301. package/node_modules/@usejunior/docx-core/dist/generation/ordering.d.ts.map +1 -0
  302. package/node_modules/@usejunior/docx-core/dist/generation/ordering.js +119 -0
  303. package/node_modules/@usejunior/docx-core/dist/generation/ordering.js.map +1 -0
  304. package/node_modules/@usejunior/docx-core/dist/generation/recipes.d.ts +87 -0
  305. package/node_modules/@usejunior/docx-core/dist/generation/recipes.d.ts.map +1 -0
  306. package/node_modules/@usejunior/docx-core/dist/generation/recipes.js +232 -0
  307. package/node_modules/@usejunior/docx-core/dist/generation/recipes.js.map +1 -0
  308. package/node_modules/@usejunior/docx-core/dist/generation/structural-checks.d.ts +24 -0
  309. package/node_modules/@usejunior/docx-core/dist/generation/structural-checks.d.ts.map +1 -0
  310. package/node_modules/@usejunior/docx-core/dist/generation/structural-checks.js +318 -0
  311. package/node_modules/@usejunior/docx-core/dist/generation/structural-checks.js.map +1 -0
  312. package/node_modules/@usejunior/docx-core/dist/generation/theme-colors.d.ts +4 -0
  313. package/node_modules/@usejunior/docx-core/dist/generation/theme-colors.d.ts.map +1 -0
  314. package/node_modules/@usejunior/docx-core/dist/generation/theme-colors.js +18 -0
  315. package/node_modules/@usejunior/docx-core/dist/generation/theme-colors.js.map +1 -0
  316. package/node_modules/@usejunior/docx-core/dist/generation/types.d.ts +266 -0
  317. package/node_modules/@usejunior/docx-core/dist/generation/types.d.ts.map +1 -0
  318. package/node_modules/@usejunior/docx-core/dist/generation/types.js +63 -0
  319. package/node_modules/@usejunior/docx-core/dist/generation/types.js.map +1 -0
  320. package/node_modules/@usejunior/docx-core/dist/generation/validate-spec.d.ts +27 -0
  321. package/node_modules/@usejunior/docx-core/dist/generation/validate-spec.d.ts.map +1 -0
  322. package/node_modules/@usejunior/docx-core/dist/generation/validate-spec.js +363 -0
  323. package/node_modules/@usejunior/docx-core/dist/generation/validate-spec.js.map +1 -0
  324. package/node_modules/@usejunior/docx-core/dist/index.d.ts +9 -150
  325. package/node_modules/@usejunior/docx-core/dist/index.d.ts.map +1 -1
  326. package/node_modules/@usejunior/docx-core/dist/index.js +14 -0
  327. package/node_modules/@usejunior/docx-core/dist/index.js.map +1 -1
  328. package/node_modules/@usejunior/docx-core/dist/integration/generation-probes.d.ts +15 -0
  329. package/node_modules/@usejunior/docx-core/dist/integration/generation-probes.d.ts.map +1 -0
  330. package/node_modules/@usejunior/docx-core/dist/integration/generation-probes.js +84 -0
  331. package/node_modules/@usejunior/docx-core/dist/integration/generation-probes.js.map +1 -0
  332. package/node_modules/@usejunior/docx-core/dist/integration/libreoffice-oracle.d.ts +49 -0
  333. package/node_modules/@usejunior/docx-core/dist/integration/libreoffice-oracle.d.ts.map +1 -0
  334. package/node_modules/@usejunior/docx-core/dist/integration/libreoffice-oracle.js +290 -0
  335. package/node_modules/@usejunior/docx-core/dist/integration/libreoffice-oracle.js.map +1 -0
  336. package/node_modules/@usejunior/docx-core/dist/integration/synthetic-docx-fixture.d.ts +134 -0
  337. package/node_modules/@usejunior/docx-core/dist/integration/synthetic-docx-fixture.d.ts.map +1 -0
  338. package/node_modules/@usejunior/docx-core/dist/integration/synthetic-docx-fixture.js +298 -0
  339. package/node_modules/@usejunior/docx-core/dist/integration/synthetic-docx-fixture.js.map +1 -0
  340. package/node_modules/@usejunior/docx-core/dist/primitives/accept_changes.d.ts +4 -3
  341. package/node_modules/@usejunior/docx-core/dist/primitives/accept_changes.d.ts.map +1 -1
  342. package/node_modules/@usejunior/docx-core/dist/primitives/accept_changes.js +163 -77
  343. package/node_modules/@usejunior/docx-core/dist/primitives/accept_changes.js.map +1 -1
  344. package/node_modules/@usejunior/docx-core/dist/primitives/comments.d.ts +12 -3
  345. package/node_modules/@usejunior/docx-core/dist/primitives/comments.d.ts.map +1 -1
  346. package/node_modules/@usejunior/docx-core/dist/primitives/comments.js +374 -97
  347. package/node_modules/@usejunior/docx-core/dist/primitives/comments.js.map +1 -1
  348. package/node_modules/@usejunior/docx-core/dist/primitives/content_fingerprint.d.ts +29 -0
  349. package/node_modules/@usejunior/docx-core/dist/primitives/content_fingerprint.d.ts.map +1 -0
  350. package/node_modules/@usejunior/docx-core/dist/primitives/content_fingerprint.js +63 -0
  351. package/node_modules/@usejunior/docx-core/dist/primitives/content_fingerprint.js.map +1 -0
  352. package/node_modules/@usejunior/docx-core/dist/primitives/document.d.ts +94 -15
  353. package/node_modules/@usejunior/docx-core/dist/primitives/document.d.ts.map +1 -1
  354. package/node_modules/@usejunior/docx-core/dist/primitives/document.js +377 -234
  355. package/node_modules/@usejunior/docx-core/dist/primitives/document.js.map +1 -1
  356. package/node_modules/@usejunior/docx-core/dist/primitives/document_view-comments.d.ts +18 -0
  357. package/node_modules/@usejunior/docx-core/dist/primitives/document_view-comments.d.ts.map +1 -0
  358. package/node_modules/@usejunior/docx-core/dist/primitives/document_view-comments.js +160 -0
  359. package/node_modules/@usejunior/docx-core/dist/primitives/document_view-comments.js.map +1 -0
  360. package/node_modules/@usejunior/docx-core/dist/primitives/document_view-headings.d.ts +45 -0
  361. package/node_modules/@usejunior/docx-core/dist/primitives/document_view-headings.d.ts.map +1 -0
  362. package/node_modules/@usejunior/docx-core/dist/primitives/document_view-headings.js +247 -0
  363. package/node_modules/@usejunior/docx-core/dist/primitives/document_view-headings.js.map +1 -0
  364. package/node_modules/@usejunior/docx-core/dist/primitives/document_view-styles.d.ts +11 -0
  365. package/node_modules/@usejunior/docx-core/dist/primitives/document_view-styles.d.ts.map +1 -0
  366. package/node_modules/@usejunior/docx-core/dist/primitives/document_view-styles.js +104 -0
  367. package/node_modules/@usejunior/docx-core/dist/primitives/document_view-styles.js.map +1 -0
  368. package/node_modules/@usejunior/docx-core/dist/primitives/document_view-toon.d.ts +37 -0
  369. package/node_modules/@usejunior/docx-core/dist/primitives/document_view-toon.d.ts.map +1 -0
  370. package/node_modules/@usejunior/docx-core/dist/primitives/document_view-toon.js +199 -0
  371. package/node_modules/@usejunior/docx-core/dist/primitives/document_view-toon.js.map +1 -0
  372. package/node_modules/@usejunior/docx-core/dist/primitives/document_view-types.d.ts +165 -0
  373. package/node_modules/@usejunior/docx-core/dist/primitives/document_view-types.d.ts.map +1 -0
  374. package/node_modules/@usejunior/docx-core/dist/primitives/document_view-types.js +2 -0
  375. package/node_modules/@usejunior/docx-core/dist/primitives/document_view-types.js.map +1 -0
  376. package/node_modules/@usejunior/docx-core/dist/primitives/document_view.d.ts +50 -101
  377. package/node_modules/@usejunior/docx-core/dist/primitives/document_view.d.ts.map +1 -1
  378. package/node_modules/@usejunior/docx-core/dist/primitives/document_view.js +287 -326
  379. package/node_modules/@usejunior/docx-core/dist/primitives/document_view.js.map +1 -1
  380. package/node_modules/@usejunior/docx-core/dist/primitives/dom-helpers.d.ts +9 -0
  381. package/node_modules/@usejunior/docx-core/dist/primitives/dom-helpers.d.ts.map +1 -1
  382. package/node_modules/@usejunior/docx-core/dist/primitives/dom-helpers.js +10 -1
  383. package/node_modules/@usejunior/docx-core/dist/primitives/dom-helpers.js.map +1 -1
  384. package/node_modules/@usejunior/docx-core/dist/primitives/footnotes.d.ts +4 -3
  385. package/node_modules/@usejunior/docx-core/dist/primitives/footnotes.d.ts.map +1 -1
  386. package/node_modules/@usejunior/docx-core/dist/primitives/footnotes.js +232 -44
  387. package/node_modules/@usejunior/docx-core/dist/primitives/footnotes.js.map +1 -1
  388. package/node_modules/@usejunior/docx-core/dist/primitives/formatting_tags.d.ts +7 -0
  389. package/node_modules/@usejunior/docx-core/dist/primitives/formatting_tags.d.ts.map +1 -1
  390. package/node_modules/@usejunior/docx-core/dist/primitives/formatting_tags.js +22 -11
  391. package/node_modules/@usejunior/docx-core/dist/primitives/formatting_tags.js.map +1 -1
  392. package/node_modules/@usejunior/docx-core/dist/primitives/index.d.ts +12 -0
  393. package/node_modules/@usejunior/docx-core/dist/primitives/index.d.ts.map +1 -1
  394. package/node_modules/@usejunior/docx-core/dist/primitives/index.js +11 -0
  395. package/node_modules/@usejunior/docx-core/dist/primitives/index.js.map +1 -1
  396. package/node_modules/@usejunior/docx-core/dist/primitives/layout.d.ts +4 -3
  397. package/node_modules/@usejunior/docx-core/dist/primitives/layout.d.ts.map +1 -1
  398. package/node_modules/@usejunior/docx-core/dist/primitives/layout.js +45 -3
  399. package/node_modules/@usejunior/docx-core/dist/primitives/layout.js.map +1 -1
  400. package/node_modules/@usejunior/docx-core/dist/primitives/locator.d.ts +76 -0
  401. package/node_modules/@usejunior/docx-core/dist/primitives/locator.d.ts.map +1 -0
  402. package/node_modules/@usejunior/docx-core/dist/primitives/locator.js +223 -0
  403. package/node_modules/@usejunior/docx-core/dist/primitives/locator.js.map +1 -0
  404. package/node_modules/@usejunior/docx-core/dist/primitives/merge_runs.d.ts +21 -3
  405. package/node_modules/@usejunior/docx-core/dist/primitives/merge_runs.d.ts.map +1 -1
  406. package/node_modules/@usejunior/docx-core/dist/primitives/merge_runs.js +32 -10
  407. package/node_modules/@usejunior/docx-core/dist/primitives/merge_runs.js.map +1 -1
  408. package/node_modules/@usejunior/docx-core/dist/primitives/minimal_save.d.ts +38 -0
  409. package/node_modules/@usejunior/docx-core/dist/primitives/minimal_save.d.ts.map +1 -0
  410. package/node_modules/@usejunior/docx-core/dist/primitives/minimal_save.js +323 -0
  411. package/node_modules/@usejunior/docx-core/dist/primitives/minimal_save.js.map +1 -0
  412. package/node_modules/@usejunior/docx-core/dist/primitives/namespaces.d.ts +53 -0
  413. package/node_modules/@usejunior/docx-core/dist/primitives/namespaces.d.ts.map +1 -1
  414. package/node_modules/@usejunior/docx-core/dist/primitives/namespaces.js +59 -0
  415. package/node_modules/@usejunior/docx-core/dist/primitives/namespaces.js.map +1 -1
  416. package/node_modules/@usejunior/docx-core/dist/primitives/reject_changes.d.ts +6 -4
  417. package/node_modules/@usejunior/docx-core/dist/primitives/reject_changes.d.ts.map +1 -1
  418. package/node_modules/@usejunior/docx-core/dist/primitives/reject_changes.js +187 -91
  419. package/node_modules/@usejunior/docx-core/dist/primitives/reject_changes.js.map +1 -1
  420. package/node_modules/@usejunior/docx-core/dist/primitives/revision-parts.d.ts +7 -0
  421. package/node_modules/@usejunior/docx-core/dist/primitives/revision-parts.d.ts.map +1 -0
  422. package/node_modules/@usejunior/docx-core/dist/primitives/revision-parts.js +27 -0
  423. package/node_modules/@usejunior/docx-core/dist/primitives/revision-parts.js.map +1 -0
  424. package/node_modules/@usejunior/docx-core/dist/primitives/revision-vocabulary.d.ts +7 -0
  425. package/node_modules/@usejunior/docx-core/dist/primitives/revision-vocabulary.d.ts.map +1 -0
  426. package/node_modules/@usejunior/docx-core/dist/primitives/revision-vocabulary.js +39 -0
  427. package/node_modules/@usejunior/docx-core/dist/primitives/revision-vocabulary.js.map +1 -0
  428. package/node_modules/@usejunior/docx-core/dist/primitives/schema-corpus-capture.d.ts +19 -0
  429. package/node_modules/@usejunior/docx-core/dist/primitives/schema-corpus-capture.d.ts.map +1 -0
  430. package/node_modules/@usejunior/docx-core/dist/primitives/schema-corpus-capture.js +29 -0
  431. package/node_modules/@usejunior/docx-core/dist/primitives/schema-corpus-capture.js.map +1 -0
  432. package/node_modules/@usejunior/docx-core/dist/primitives/sectPrAudit.d.ts +19 -0
  433. package/node_modules/@usejunior/docx-core/dist/primitives/sectPrAudit.d.ts.map +1 -0
  434. package/node_modules/@usejunior/docx-core/dist/primitives/sectPrAudit.js +165 -0
  435. package/node_modules/@usejunior/docx-core/dist/primitives/sectPrAudit.js.map +1 -0
  436. package/node_modules/@usejunior/docx-core/dist/primitives/semantic_tags.d.ts +7 -0
  437. package/node_modules/@usejunior/docx-core/dist/primitives/semantic_tags.d.ts.map +1 -1
  438. package/node_modules/@usejunior/docx-core/dist/primitives/semantic_tags.js +23 -4
  439. package/node_modules/@usejunior/docx-core/dist/primitives/semantic_tags.js.map +1 -1
  440. package/node_modules/@usejunior/docx-core/dist/primitives/serialize_html.d.ts +37 -0
  441. package/node_modules/@usejunior/docx-core/dist/primitives/serialize_html.d.ts.map +1 -0
  442. package/node_modules/@usejunior/docx-core/dist/primitives/serialize_html.js +395 -0
  443. package/node_modules/@usejunior/docx-core/dist/primitives/serialize_html.js.map +1 -0
  444. package/node_modules/@usejunior/docx-core/dist/primitives/serialize_markdown.d.ts +16 -0
  445. package/node_modules/@usejunior/docx-core/dist/primitives/serialize_markdown.d.ts.map +1 -0
  446. package/node_modules/@usejunior/docx-core/dist/primitives/serialize_markdown.js +300 -0
  447. package/node_modules/@usejunior/docx-core/dist/primitives/serialize_markdown.js.map +1 -0
  448. package/node_modules/@usejunior/docx-core/dist/primitives/serialize_plaintext.d.ts +15 -0
  449. package/node_modules/@usejunior/docx-core/dist/primitives/serialize_plaintext.d.ts.map +1 -0
  450. package/node_modules/@usejunior/docx-core/dist/primitives/serialize_plaintext.js +154 -0
  451. package/node_modules/@usejunior/docx-core/dist/primitives/serialize_plaintext.js.map +1 -0
  452. package/node_modules/@usejunior/docx-core/dist/primitives/styles.d.ts +15 -0
  453. package/node_modules/@usejunior/docx-core/dist/primitives/styles.d.ts.map +1 -1
  454. package/node_modules/@usejunior/docx-core/dist/primitives/styles.js +33 -22
  455. package/node_modules/@usejunior/docx-core/dist/primitives/styles.js.map +1 -1
  456. package/node_modules/@usejunior/docx-core/dist/primitives/table_context.d.ts +19 -0
  457. package/node_modules/@usejunior/docx-core/dist/primitives/table_context.d.ts.map +1 -0
  458. package/node_modules/@usejunior/docx-core/dist/primitives/table_context.js +189 -0
  459. package/node_modules/@usejunior/docx-core/dist/primitives/table_context.js.map +1 -0
  460. package/node_modules/@usejunior/docx-core/dist/primitives/tables.d.ts.map +1 -1
  461. package/node_modules/@usejunior/docx-core/dist/primitives/tables.js +13 -3
  462. package/node_modules/@usejunior/docx-core/dist/primitives/tables.js.map +1 -1
  463. package/node_modules/@usejunior/docx-core/dist/primitives/text.d.ts +2 -1
  464. package/node_modules/@usejunior/docx-core/dist/primitives/text.d.ts.map +1 -1
  465. package/node_modules/@usejunior/docx-core/dist/primitives/text.js +116 -12
  466. package/node_modules/@usejunior/docx-core/dist/primitives/text.js.map +1 -1
  467. package/node_modules/@usejunior/docx-core/dist/primitives/track-changes-emitter.d.ts +148 -0
  468. package/node_modules/@usejunior/docx-core/dist/primitives/track-changes-emitter.d.ts.map +1 -0
  469. package/node_modules/@usejunior/docx-core/dist/primitives/track-changes-emitter.js +291 -0
  470. package/node_modules/@usejunior/docx-core/dist/primitives/track-changes-emitter.js.map +1 -0
  471. package/node_modules/@usejunior/docx-core/dist/primitives/validate_ai_revisions.d.ts +35 -0
  472. package/node_modules/@usejunior/docx-core/dist/primitives/validate_ai_revisions.d.ts.map +1 -0
  473. package/node_modules/@usejunior/docx-core/dist/primitives/validate_ai_revisions.js +323 -0
  474. package/node_modules/@usejunior/docx-core/dist/primitives/validate_ai_revisions.js.map +1 -0
  475. package/node_modules/@usejunior/docx-core/dist/primitives/xml-helpers.d.ts +29 -0
  476. package/node_modules/@usejunior/docx-core/dist/primitives/xml-helpers.d.ts.map +1 -0
  477. package/node_modules/@usejunior/docx-core/dist/primitives/xml-helpers.js +35 -0
  478. package/node_modules/@usejunior/docx-core/dist/primitives/xml-helpers.js.map +1 -0
  479. package/node_modules/@usejunior/docx-core/dist/primitives/xml.d.ts +5 -0
  480. package/node_modules/@usejunior/docx-core/dist/primitives/xml.d.ts.map +1 -1
  481. package/node_modules/@usejunior/docx-core/dist/primitives/xml.js +5 -0
  482. package/node_modules/@usejunior/docx-core/dist/primitives/xml.js.map +1 -1
  483. package/node_modules/@usejunior/docx-core/dist/primitives/zip.d.ts +1 -0
  484. package/node_modules/@usejunior/docx-core/dist/primitives/zip.d.ts.map +1 -1
  485. package/node_modules/@usejunior/docx-core/dist/primitives/zip.js +21 -3
  486. package/node_modules/@usejunior/docx-core/dist/primitives/zip.js.map +1 -1
  487. package/node_modules/@usejunior/docx-core/dist/shared/field-structure.d.ts +14 -0
  488. package/node_modules/@usejunior/docx-core/dist/shared/field-structure.d.ts.map +1 -0
  489. package/node_modules/@usejunior/docx-core/dist/shared/field-structure.js +166 -0
  490. package/node_modules/@usejunior/docx-core/dist/shared/field-structure.js.map +1 -0
  491. package/node_modules/@usejunior/docx-core/dist/shared/ooxml/namespaces.d.ts +4 -1
  492. package/node_modules/@usejunior/docx-core/dist/shared/ooxml/namespaces.d.ts.map +1 -1
  493. package/node_modules/@usejunior/docx-core/dist/shared/ooxml/namespaces.js +4 -1
  494. package/node_modules/@usejunior/docx-core/dist/shared/ooxml/namespaces.js.map +1 -1
  495. package/node_modules/@usejunior/docx-core/package.json +13 -9
  496. package/node_modules/@xmldom/xmldom/CHANGELOG.md +186 -70
  497. package/node_modules/@xmldom/xmldom/index.d.ts +144 -19
  498. package/node_modules/@xmldom/xmldom/lib/dom.js +705 -343
  499. package/node_modules/@xmldom/xmldom/lib/grammar.js +14 -0
  500. package/node_modules/@xmldom/xmldom/package.json +13 -10
  501. package/package.json +7 -7
  502. package/server.json +3 -3
  503. package/skills/{cloud-service-agreement → agreements/cloud-service-agreement}/SKILL.md +2 -2
  504. package/skills/{nda → agreements/cloud-service-agreement}/template-filling-execution.md +2 -2
  505. package/skills/{data-privacy-agreement → agreements/data-privacy-agreement}/SKILL.md +15 -4
  506. package/skills/{safe → agreements/data-privacy-agreement}/template-filling-execution.md +12 -6
  507. package/skills/{employment-contract → agreements/employment-contract}/SKILL.md +3 -3
  508. package/skills/{cloud-service-agreement → agreements/employment-contract}/template-filling-execution.md +12 -6
  509. package/skills/{nda → agreements/nda}/SKILL.md +2 -2
  510. package/skills/{open-agreements → agreements/nda}/template-filling-execution.md +12 -6
  511. package/skills/{open-agreements → agreements/open-agreements}/SKILL.md +13 -30
  512. package/skills/agreements/open-agreements/template-filling-execution.md +98 -0
  513. package/skills/{safe → agreements/safe}/SKILL.md +2 -2
  514. package/skills/agreements/safe/template-filling-execution.md +98 -0
  515. package/skills/{services-agreement → agreements/services-agreement}/SKILL.md +3 -3
  516. package/skills/agreements/services-agreement/template-filling-execution.md +98 -0
  517. package/skills/{venture-financing → agreements/venture-financing}/SKILL.md +3 -3
  518. package/skills/agreements/venture-financing/template-filling-execution.md +98 -0
  519. package/skills/{client-email → client-workflows/client-email}/SKILL.md +1 -1
  520. package/skills/{delaware-franchise-tax → client-workflows/delaware-franchise-tax}/SKILL.md +1 -1
  521. package/skills/{edit-docx-agreement → client-workflows/edit-docx-agreement}/SKILL.md +1 -1
  522. package/skills/{iso-27001-evidence-collection → compliance/iso-27001-evidence-collection}/SKILL.md +1 -1
  523. package/skills/{iso-27001-internal-audit → compliance/iso-27001-internal-audit}/SKILL.md +1 -1
  524. package/skills/{soc2-readiness → compliance/soc2-readiness}/SKILL.md +1 -1
  525. package/skills/{canonical-markdown-authoring → internal/canonical-markdown-authoring}/SKILL.md +2 -3
  526. package/skills/{recipe-quality-audit → internal/recipe-quality-audit}/SKILL.md +2 -1
  527. package/skills/{unit-test-philosophy → internal/unit-test-philosophy}/SKILL.md +2 -0
  528. package/skills/legal-explainers/data-privacy-law-explainer/CONTRIBUTING.md +7 -0
  529. package/skills/legal-explainers/data-privacy-law-explainer/LICENSE +269 -0
  530. package/skills/legal-explainers/data-privacy-law-explainer/NOTICE +7 -0
  531. package/skills/legal-explainers/data-privacy-law-explainer/SKILL.md +113 -0
  532. package/skills/legal-explainers/data-privacy-law-explainer/content/alabama.md +211 -0
  533. package/skills/legal-explainers/data-privacy-law-explainer/content/alaska.md +155 -0
  534. package/skills/legal-explainers/data-privacy-law-explainer/content/arizona.md +181 -0
  535. package/skills/legal-explainers/data-privacy-law-explainer/content/arkansas.md +219 -0
  536. package/skills/legal-explainers/data-privacy-law-explainer/content/california.md +107 -0
  537. package/skills/legal-explainers/data-privacy-law-explainer/content/colorado.md +87 -0
  538. package/skills/legal-explainers/data-privacy-law-explainer/content/connecticut.md +83 -0
  539. package/skills/legal-explainers/data-privacy-law-explainer/content/delaware.md +85 -0
  540. package/skills/legal-explainers/data-privacy-law-explainer/content/district-of-columbia.md +153 -0
  541. package/skills/legal-explainers/data-privacy-law-explainer/content/florida.md +234 -0
  542. package/skills/legal-explainers/data-privacy-law-explainer/content/georgia.md +149 -0
  543. package/skills/legal-explainers/data-privacy-law-explainer/content/hawaii.md +167 -0
  544. package/skills/legal-explainers/data-privacy-law-explainer/content/idaho.md +149 -0
  545. package/skills/legal-explainers/data-privacy-law-explainer/content/illinois.md +238 -0
  546. package/skills/legal-explainers/data-privacy-law-explainer/content/indiana.md +93 -0
  547. package/skills/legal-explainers/data-privacy-law-explainer/content/iowa.md +99 -0
  548. package/skills/legal-explainers/data-privacy-law-explainer/content/kansas.md +155 -0
  549. package/skills/legal-explainers/data-privacy-law-explainer/content/kentucky.md +87 -0
  550. package/skills/legal-explainers/data-privacy-law-explainer/content/louisiana.md +209 -0
  551. package/skills/legal-explainers/data-privacy-law-explainer/content/maine.md +163 -0
  552. package/skills/legal-explainers/data-privacy-law-explainer/content/maryland.md +85 -0
  553. package/skills/legal-explainers/data-privacy-law-explainer/content/massachusetts.md +260 -0
  554. package/skills/legal-explainers/data-privacy-law-explainer/content/michigan.md +175 -0
  555. package/skills/legal-explainers/data-privacy-law-explainer/content/minnesota.md +93 -0
  556. package/skills/legal-explainers/data-privacy-law-explainer/content/mississippi.md +132 -0
  557. package/skills/legal-explainers/data-privacy-law-explainer/content/missouri.md +179 -0
  558. package/skills/legal-explainers/data-privacy-law-explainer/content/montana.md +105 -0
  559. package/skills/legal-explainers/data-privacy-law-explainer/content/nebraska.md +83 -0
  560. package/skills/legal-explainers/data-privacy-law-explainer/content/nevada.md +212 -0
  561. package/skills/legal-explainers/data-privacy-law-explainer/content/new-hampshire.md +91 -0
  562. package/skills/legal-explainers/data-privacy-law-explainer/content/new-jersey.md +95 -0
  563. package/skills/legal-explainers/data-privacy-law-explainer/content/new-mexico.md +174 -0
  564. package/skills/legal-explainers/data-privacy-law-explainer/content/new-york.md +195 -0
  565. package/skills/legal-explainers/data-privacy-law-explainer/content/north-carolina.md +205 -0
  566. package/skills/legal-explainers/data-privacy-law-explainer/content/north-dakota.md +169 -0
  567. package/skills/legal-explainers/data-privacy-law-explainer/content/ohio.md +171 -0
  568. package/skills/legal-explainers/data-privacy-law-explainer/content/oklahoma.md +168 -0
  569. package/skills/legal-explainers/data-privacy-law-explainer/content/oregon.md +103 -0
  570. package/skills/legal-explainers/data-privacy-law-explainer/content/pennsylvania.md +99 -0
  571. package/skills/legal-explainers/data-privacy-law-explainer/content/rhode-island.md +93 -0
  572. package/skills/legal-explainers/data-privacy-law-explainer/content/south-carolina.md +175 -0
  573. package/skills/legal-explainers/data-privacy-law-explainer/content/south-dakota.md +176 -0
  574. package/skills/legal-explainers/data-privacy-law-explainer/content/tennessee.md +89 -0
  575. package/skills/legal-explainers/data-privacy-law-explainer/content/texas.md +89 -0
  576. package/skills/legal-explainers/data-privacy-law-explainer/content/utah.md +83 -0
  577. package/skills/legal-explainers/data-privacy-law-explainer/content/vermont.md +267 -0
  578. package/skills/legal-explainers/data-privacy-law-explainer/content/virginia.md +85 -0
  579. package/skills/legal-explainers/data-privacy-law-explainer/content/washington.md +247 -0
  580. package/skills/legal-explainers/data-privacy-law-explainer/content/west-virginia.md +141 -0
  581. package/skills/legal-explainers/data-privacy-law-explainer/content/wisconsin.md +156 -0
  582. package/skills/legal-explainers/data-privacy-law-explainer/content/wyoming.md +185 -0
  583. package/skills/legal-explainers/data-privacy-law-explainer/manifest.json +519 -0
  584. package/skills/legal-explainers/non-compete-contract-explainer/CONTRIBUTING.md +7 -0
  585. package/skills/legal-explainers/non-compete-contract-explainer/LICENSE +269 -0
  586. package/skills/legal-explainers/non-compete-contract-explainer/NOTICE +7 -0
  587. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/SKILL.md +1 -1
  588. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/alabama.md +5 -5
  589. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/alaska.md +5 -5
  590. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/american-samoa.md +6 -6
  591. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/arizona.md +6 -4
  592. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/arkansas.md +5 -5
  593. package/skills/legal-explainers/non-compete-contract-explainer/content/au.md +208 -0
  594. package/skills/legal-explainers/non-compete-contract-explainer/content/australian-capital-territory.md +220 -0
  595. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/california.md +5 -5
  596. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/cnmi.md +4 -4
  597. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/colorado.md +5 -5
  598. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/connecticut.md +5 -5
  599. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/delaware.md +7 -7
  600. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/district-of-columbia.md +5 -5
  601. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/florida.md +5 -5
  602. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/georgia.md +7 -7
  603. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/guam.md +4 -4
  604. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/hawaii.md +5 -5
  605. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/idaho.md +5 -5
  606. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/illinois.md +5 -5
  607. package/skills/{non-compete-contract-explainer/content/india.md → legal-explainers/non-compete-contract-explainer/content/in.md} +5 -5
  608. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/indiana.md +5 -5
  609. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/iowa.md +5 -5
  610. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/kansas.md +5 -5
  611. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/kentucky.md +5 -5
  612. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/louisiana.md +9 -9
  613. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/maine.md +6 -6
  614. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/maryland.md +5 -5
  615. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/massachusetts.md +5 -5
  616. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/michigan.md +5 -5
  617. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/minnesota.md +5 -5
  618. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/mississippi.md +5 -5
  619. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/missouri.md +5 -5
  620. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/montana.md +5 -5
  621. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/nebraska.md +5 -5
  622. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/nevada.md +5 -5
  623. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/new-hampshire.md +5 -5
  624. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/new-jersey.md +5 -5
  625. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/new-mexico.md +5 -5
  626. package/skills/legal-explainers/non-compete-contract-explainer/content/new-south-wales.md +218 -0
  627. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/new-york.md +5 -5
  628. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/north-carolina.md +5 -5
  629. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/north-dakota.md +5 -5
  630. package/skills/legal-explainers/non-compete-contract-explainer/content/northern-territory.md +214 -0
  631. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/ohio.md +5 -5
  632. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/oklahoma.md +5 -5
  633. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/oregon.md +12 -12
  634. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/pennsylvania.md +5 -5
  635. package/skills/{non-compete-contract-explainer/content/philippines.md → legal-explainers/non-compete-contract-explainer/content/ph.md} +5 -5
  636. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/puerto-rico.md +4 -4
  637. package/skills/legal-explainers/non-compete-contract-explainer/content/queensland.md +206 -0
  638. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/rhode-island.md +5 -5
  639. package/skills/{non-compete-contract-explainer/content/singapore.md → legal-explainers/non-compete-contract-explainer/content/sg.md} +5 -5
  640. package/skills/legal-explainers/non-compete-contract-explainer/content/south-australia.md +236 -0
  641. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/south-carolina.md +5 -5
  642. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/south-dakota.md +5 -5
  643. package/skills/legal-explainers/non-compete-contract-explainer/content/tasmania.md +224 -0
  644. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/tennessee.md +5 -5
  645. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/texas.md +5 -5
  646. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/utah.md +5 -5
  647. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/vermont.md +29 -11
  648. package/skills/legal-explainers/non-compete-contract-explainer/content/victoria.md +218 -0
  649. package/skills/{non-compete-contract-explainer/content/us-virgin-islands.md → legal-explainers/non-compete-contract-explainer/content/virgin-islands.md} +5 -5
  650. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/virginia.md +5 -5
  651. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/washington.md +5 -5
  652. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/west-virginia.md +5 -5
  653. package/skills/legal-explainers/non-compete-contract-explainer/content/western-australia.md +224 -0
  654. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/wisconsin.md +5 -5
  655. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/content/wyoming.md +19 -15
  656. package/skills/{non-compete-contract-explainer → legal-explainers/non-compete-contract-explainer}/manifest.json +225 -76
  657. package/content/templates/bonterms-mutual-nda/signing.yaml +0 -35
  658. package/dist/core/signing-config.d.ts +0 -46
  659. package/dist/core/signing-config.d.ts.map +0 -1
  660. package/dist/core/signing-config.js +0 -67
  661. package/dist/core/signing-config.js.map +0 -1
  662. package/skills/services-agreement/template-filling-execution.md +0 -81
  663. package/skills/shared/template-filling-execution.md +0 -92
  664. /package/skills/{cloud-service-agreement → agreements/cloud-service-agreement}/CONNECTORS.md +0 -0
  665. /package/skills/{data-privacy-agreement → agreements/data-privacy-agreement}/CONNECTORS.md +0 -0
  666. /package/skills/{employment-contract → agreements/employment-contract}/CONNECTORS.md +0 -0
  667. /package/skills/{nda → agreements/nda}/CONNECTORS.md +0 -0
  668. /package/skills/{open-agreements → agreements/open-agreements}/CONNECTORS.md +0 -0
  669. /package/skills/{safe → agreements/safe}/CONNECTORS.md +0 -0
  670. /package/skills/{services-agreement → agreements/services-agreement}/CONNECTORS.md +0 -0
  671. /package/skills/{venture-financing → agreements/venture-financing}/CONNECTORS.md +0 -0
  672. /package/skills/{delaware-franchise-tax → client-workflows/delaware-franchise-tax}/CONNECTORS.md +0 -0
  673. /package/skills/{delaware-franchise-tax → client-workflows/delaware-franchise-tax}/reference/ecorp-portal-playwright-notes.md +0 -0
  674. /package/skills/{delaware-franchise-tax → client-workflows/delaware-franchise-tax}/reference/faq.md +0 -0
  675. /package/skills/{delaware-franchise-tax → client-workflows/delaware-franchise-tax}/reference/filing-instructions.md +0 -0
  676. /package/skills/{delaware-franchise-tax → client-workflows/delaware-franchise-tax}/reference/tax-calculation.md +0 -0
  677. /package/skills/{edit-docx-agreement → client-workflows/edit-docx-agreement}/CONNECTORS.md +0 -0
  678. /package/skills/{iso-27001-evidence-collection → compliance/iso-27001-evidence-collection}/CONNECTORS.md +0 -0
  679. /package/skills/{iso-27001-evidence-collection → compliance/iso-27001-evidence-collection}/rules/api-exports.md +0 -0
  680. /package/skills/{iso-27001-evidence-collection → compliance/iso-27001-evidence-collection}/rules/evidence-types.md +0 -0
  681. /package/skills/{iso-27001-evidence-collection → compliance/iso-27001-evidence-collection}/rules/screenshot-guide.md +0 -0
  682. /package/skills/{iso-27001-internal-audit → compliance/iso-27001-internal-audit}/CONNECTORS.md +0 -0
  683. /package/skills/{iso-27001-internal-audit → compliance/iso-27001-internal-audit}/rules/access-control.md +0 -0
  684. /package/skills/{iso-27001-internal-audit → compliance/iso-27001-internal-audit}/rules/business-continuity.md +0 -0
  685. /package/skills/{iso-27001-internal-audit → compliance/iso-27001-internal-audit}/rules/change-management.md +0 -0
  686. /package/skills/{iso-27001-internal-audit → compliance/iso-27001-internal-audit}/rules/encryption.md +0 -0
  687. /package/skills/{iso-27001-internal-audit → compliance/iso-27001-internal-audit}/rules/incident-response.md +0 -0
  688. /package/skills/{iso-27001-internal-audit → compliance/iso-27001-internal-audit}/rules/isms-management.md +0 -0
  689. /package/skills/{iso-27001-internal-audit → compliance/iso-27001-internal-audit}/rules/logging-monitoring.md +0 -0
  690. /package/skills/{iso-27001-internal-audit → compliance/iso-27001-internal-audit}/rules/people-controls.md +0 -0
  691. /package/skills/{iso-27001-internal-audit → compliance/iso-27001-internal-audit}/rules/supplier-management.md +0 -0
  692. /package/skills/{soc2-readiness → compliance/soc2-readiness}/CONNECTORS.md +0 -0
  693. /package/skills/{soc2-readiness → compliance/soc2-readiness}/rules/change-vendor-management.md +0 -0
  694. /package/skills/{soc2-readiness → compliance/soc2-readiness}/rules/communication-info.md +0 -0
  695. /package/skills/{soc2-readiness → compliance/soc2-readiness}/rules/control-activities.md +0 -0
  696. /package/skills/{soc2-readiness → compliance/soc2-readiness}/rules/control-environment.md +0 -0
  697. /package/skills/{soc2-readiness → compliance/soc2-readiness}/rules/logical-access.md +0 -0
  698. /package/skills/{soc2-readiness → compliance/soc2-readiness}/rules/monitoring-activities.md +0 -0
  699. /package/skills/{soc2-readiness → compliance/soc2-readiness}/rules/optional-categories.md +0 -0
  700. /package/skills/{soc2-readiness → compliance/soc2-readiness}/rules/privacy-criteria.md +0 -0
  701. /package/skills/{soc2-readiness → compliance/soc2-readiness}/rules/risk-assessment.md +0 -0
  702. /package/skills/{soc2-readiness → compliance/soc2-readiness}/rules/system-operations.md +0 -0
  703. /package/skills/{canonical-markdown-authoring → internal/canonical-markdown-authoring}/CONNECTORS.md +0 -0
  704. /package/skills/{unit-test-philosophy → internal/unit-test-philosophy}/references/allure-test-spec-writing-guide.md +0 -0
@@ -0,0 +1,149 @@
1
+ ---
2
+ jurisdiction: "Idaho"
3
+ slug: idaho
4
+ countryCode: US
5
+ snapshotAsOf: "2026-06-19"
6
+ lastReviewed: "2026-06-11"
7
+ canonicalUrl: https://openagreements.org/practice-guides/privacy/us/idaho
8
+ license: CC BY 4.0
9
+ stale: false
10
+ ---
11
+
12
+ > [!IMPORTANT]
13
+ > **Informational only — not legal advice.** This is a snapshot of an OpenAgreements practice note,
14
+ > provided for general information. It is not legal advice, does not create an attorney-client
15
+ > relationship, and is not a substitute for a licensed attorney in the relevant jurisdiction.
16
+ > Laws change; verify against the canonical version before relying on it.
17
+ >
18
+ > **Canonical:** https://openagreements.org/practice-guides/privacy/us/idaho · **Snapshot as of:** 2026-06-19 · License: CC BY 4.0 · © openagreements.org
19
+
20
+ # Idaho Consumer Privacy Law[^about]
21
+
22
+ Idaho has no comprehensive consumer-privacy statute. The operative state framework is the data-breach notification provisions of Idaho Code §§ 28-51-104 to 28-51-107 plus the Idaho Consumer Protection Act as the deception hook, layered under the federal overlay (FTC Act § 5, GLBA, HIPAA, COPPA) — with two narrow new laws (social-media minors, conversational AI) arriving July 2026 and July 2027.
23
+
24
+
25
+ ## At a glance
26
+
27
+ | Question | Idaho |
28
+ | --- | --- |
29
+ | **Law coverage** | No comprehensive law |
30
+ | **Summary** | Idaho has not enacted a comprehensive consumer-privacy law, so there are no general data-rights, notice-at-collection, consent, or processor-contract duties under state law. The operative state statutes are the breach-notification provisions in the identity-theft chapter — a misuse-triggered notice duty with no day-count deadline and no regulator notice for private businesses — and the Idaho Consumer Protection Act, which makes a privacy policy you publish but do not follow a deceptive practice. Build to the federal overlay (FTC Act § 5, GLBA, HIPAA, COPPA) and the breach statute, and watch two narrow 2026 enactments, one on social-media minors and one on conversational AI. |
31
+ | **Main law** | Idaho Code §§ 28-51-104 to 28-51-107 (data-breach notification) plus the Idaho Consumer Protection Act, Idaho Code § 48-601 et seq. — Idaho has no comprehensive consumer-privacy statute |
32
+ | **Privacy policy required?** | No Idaho statute requires a consumer privacy policy or fixes its contents; the binding constraints are FTC Act § 5 and the Idaho Consumer Protection Act's ban on misleading or deceptive practices, plus GLBA, HIPAA, and COPPA where the business is in scope |
33
+ | **Who does it cover?** | Any agency, individual, or commercial entity (for profit or not) that conducts business in Idaho and owns or licenses computerized personal information about Idaho residents; no revenue or consumer-volume threshold |
34
+ | **Can consumers sue?** | Limited path |
35
+ | **Privacy policy rule** | No state policy checklist |
36
+ | **Consent for sensitive data?** | No special rule |
37
+ | **Browser opt-out signals?** | Not required |
38
+ | **Lawsuit detail** | Not under the breach statute — enforcement runs through each entity's primary regulator; the Idaho Consumer Protection Act gives purchasers a private action for actual damages or $1,000 (Idaho Code § 48-608), with narrow 2026 sectoral enactments to track separately |
39
+ | **Who enforces it?** | Idaho Attorney General (the primary regulator for most businesses; the Department of Finance and Department of Insurance for their licensees) |
40
+
41
+ ## Which privacy laws apply to your business in Idaho? {#which-privacy-laws-apply}
42
+
43
+ **Short answer.** There is no comprehensive Idaho consumer-privacy law. The operative state framework has two pieces. First, the breach-notification provisions of the identity-theft chapter apply to any city, county, or state agency, individual, or commercial entity that conducts business in Idaho and owns or licenses computerized data that includes personal information about an Idaho resident [^breach-duty-scope] — *commercial entity* sweeps in essentially every legal entity, for profit or not [^commercial-entity-def], and there is no revenue or volume threshold. Second, the Idaho Consumer Protection Act (ICPA) bans, among other listed practices, engaging in any act or practice that is otherwise misleading, false, or deceptive to the consumer — the hook that reaches privacy misrepresentations [^icpa-catchall].
44
+
45
+ Idaho has not enacted an omnibus privacy statute of the kind now common in other states, so Idaho residents have no general state-law rights to access, delete, or correct their personal data or to opt out of its sale, and businesses face no state notice-at-collection, consent, data-protection-assessment, or processor-contract duties. The breach statute governs incident response; the ICPA governs what you tell consumers. The rest of an Idaho-facing privacy program rides the federal overlay: Section 5 of the FTC Act reaches deceptive or unfair privacy practices nationwide, the Gramm-Leach-Bliley Act governs financial institutions, HIPAA governs covered health entities and their business associates, and the Children's Online Privacy Protection Act governs services directed to children under 13.
46
+
47
+ Around that spine, Idaho legislates by sector and by harm rather than by data inventory. Recent examples include payment-card receipt truncation, an age-verification law for adult sites with a ban on retaining identifying information, genetic-testing restrictions on employers, license-plate-reader limits for government agencies, and mortgage trigger-lead disclosure rules — none of which imposes general data-handling duties on a typical business.
48
+
49
+ Two 2026 enactments deserve a calendar entry: the Stop Harms from Addictive Social Media Act (House Bill 542, 2026 Session Laws chapter 268) and the Conversational AI Safety Act (Senate Bill 1297, 2026 Session Laws chapter 249). Treat both as narrow sectoral watchlist items, not as an omnibus privacy regime. *Open codification question:* both acts were designated as a new chapter 21 of title 48, Idaho Code, with overlapping section numbers, so until the code commission resolves the collision in the July 2026 compilation, cite these laws by session-law chapter rather than by a section number in chapter 21.
50
+
51
+ ## What must your Idaho privacy policy contain? {#privacy-policy-contents}
52
+
53
+ **Short answer.** No Idaho statute requires a general consumer privacy policy or fixes what it must say. The binding rule is that whatever you publish has to be true. Under Section 5 of the FTC Act, unfair or deceptive acts or practices in or affecting commerce are unlawful [^ftc5-deceptive], and the Idaho Consumer Protection Act separately declares unlawful any act or practice that is otherwise misleading, false, or deceptive to the consumer [^icpa-deception-policy] — so a privacy policy that misstates how you actually collect, use, share, retain, or secure data is actionable under both. Where a sectoral regime applies, that regime supplies the contents: a HIPAA covered entity, for example, must give individuals adequate notice of the uses and disclosures of their protected health information and of their rights and the entity's duties [^hipaa-notice], and a GLBA financial institution must deliver a privacy notice before sharing nonpublic personal information with nonaffiliated third parties [^glba-notice].
54
+
55
+ In practice the Idaho drafting question is less what must be included and more does the policy match actual practice. The ICPA's list of unlawful practices carries a knowledge element — it reaches a person who knows, or in the exercise of due care should know, that a practice is deceptive [^icpa-deception-policy] — which arguably extends to negligently inaccurate policy statements, not just deliberate ones. And unlike the ICPA's private remedy, the Attorney General's enforcement powers carry no purchase-or-lease or ascertainable-loss limit, so public enforcement does not depend on showing that any consumer paid for anything.
56
+
57
+ Build the policy from the overlay that actually binds you: the GLBA privacy-notice rules if you are a financial institution, the HIPAA Notice of Privacy Practices if you are a covered entity, HIPAA business-associate and security obligations if you are a business associate, a COPPA notice if COPPA applies, and the comprehensive laws of other states whose residents you reach — many of which mandate a posted policy regardless of where your business sits. For everyone else, follow best practice — describe the categories of data collected, the purposes, the third parties you share with, and how users exercise any choices you offer — and then honor it, because in Idaho the enforceable obligation is consistency between the statement and the conduct.
58
+
59
+ ## What must your contracts with vendors say? {#vendor-contracts}
60
+
61
+ **Short answer.** Idaho has no data-processing-agreement requirement — no state statute prescribes controller-to-processor terms, audit rights, deletion clauses, or subprocessor flow-downs. The one vendor-facing duty in Idaho law is a breach-response rule: an entity that maintains computerized personal information it does not own or license must notify and cooperate with the data's owner or licensee immediately following discovery of a breach if misuse of an Idaho resident's information occurred or is reasonably likely to occur [^breach-maintainer-notice].
62
+
63
+ Where a federal or sectoral regime is in scope, it supplies the contracting obligations: the GLBA Safeguards Rule requires financial institutions to oversee service providers, including by requiring them by contract to implement and maintain appropriate safeguards [^glba-safeguards], and HIPAA business-associate rules require a compliant agreement establishing the permitted uses and disclosures of protected health information [^hipaa-baa]. Outside those verticals, the prudent move is to carry the same protections forward as a matter of best practice — processing limited to documented instructions, confidentiality, reasonable security, breach notification back to your business, and return or deletion of data at the end of the engagement — even though no Idaho statute compels them.
64
+
65
+ The maintainer-notice rule is worth writing into vendor contracts anyway. The statute requires the vendor to notify the owner immediately and to share information relevant to the breach, but it sets no contractual specifics — so a well-drafted agreement should fix the notice channel, the timeline, and the cooperation duties the statute leaves general, and should allocate who pays for resident notification, since under Idaho law the notice duty to residents stays with the entity that owns or licenses the data.
66
+
67
+ ## Do Idaho residents have rights to access, delete, or opt out? {#consumer-rights}
68
+
69
+ **Short answer.** No. Idaho law gives consumers no general rights to access, correct, delete, or port their personal data, no right to opt out of its sale or of targeted advertising, and no duty on businesses to honor universal opt-out signals such as Global Privacy Control. The generally applicable Idaho resident-facing disclosure duty is breach notice when the breach statute's trigger is met: if a covered entity's investigation determines that misuse of a resident's personal information has occurred or is reasonably likely, the entity must give that resident notice as soon as possible [^rights-breach-notice].
70
+
71
+ The rights an Idaho resident does hold come from federal sectoral law, where applicable. A GLBA financial institution must give consumers the opportunity to opt out before their nonpublic personal information is disclosed to nonaffiliated third parties [^glba-optout]. Under COPPA, a parent can refuse to permit an operator's further use, maintenance, or future collection of the child's personal information [^coppa-parental]. HIPAA adds access, amendment, and accounting rights for protected health information, and the FCRA adds access and dispute rights in consumer reports. Residents of other states may also carry their home-state rights into dealings with an Idaho business that meets those statutes' thresholds — the absence of an Idaho law does not insulate an Idaho company from California, Colorado, or Washington requests.
72
+
73
+ One narrow set of state-law rights is scheduled to arrive under the Stop Harms from Addictive Social Media Act (2026 Session Laws chapter 268), but it is a sectoral social-media minors law, not a general access, deletion, or opt-out regime. Track that act separately before treating it as an operational consumer-rights workflow.
74
+
75
+ ## When must you notify people of a data breach in Idaho? {#breach-notification}
76
+
77
+ **Short answer.** When your investigation shows misuse — not merely access. An entity that becomes aware of a breach must conduct a good-faith, reasonable, and prompt investigation into the likelihood of misuse; if the investigation determines that misuse of an Idaho resident's information has occurred or is reasonably likely to occur, notice must go to the affected resident in the most expedient time possible and without unreasonable delay [^breach-trigger-timing]. A reportable breach is the illegal acquisition of unencrypted computerized data that materially compromises the security, confidentiality, or integrity of personal information [^breach-def] — so encryption is a built-in safe harbor. There is no day-count deadline and no statutory notice-content checklist.
78
+
79
+ Be precise about who owes notice to whom, because Idaho splits the regulator-notice duty by entity type. A government *agency* that becomes aware of a breach must notify the office of the Idaho Attorney General within twenty-four hours of discovery [^breach-agency-ag-notice]. A private business owes no notice to the Attorney General or any other state regulator at any threshold — Idaho is one of the few states where a commercial breach never has to be reported to a state agency; the only mandatory recipients are the affected residents themselves (and the data's owner, if you are a vendor holding someone else's data). Notice may be written, telephonic, or electronic, with substitute notice (email plus website posting plus statewide media) available when costs would exceed $25,000, more than 50,000 residents are affected, or contact information is insufficient [^breach-notice-methods], and notice may be delayed at law enforcement's request [^breach-law-enforcement-delay].
80
+
81
+ *Personal information* is also narrower than in modern statutes: a resident's name combined with an unencrypted Social Security number, driver's license or Idaho ID number, or a financial-account or card number with its access code [^breach-personal-info] — no medical, biometric, health-insurance, or online-credential elements. Two compliance off-ramps round out the scheme: an entity that follows its own information-security-policy notice procedures consistent with the statute's timing is deemed compliant, and an entity regulated by state or federal law that follows its primary or functional regulator's breach procedures is likewise deemed compliant [^breach-safe-harbor] — which effectively lets GLBA- and HIPAA-regulated businesses run their federal playbooks. The cost of getting it wrong is concentrated on concealment: an entity that intentionally fails to give notice faces a fine of up to $25,000 per breach, enforceable by its primary regulator — the Attorney General for most businesses [^breach-fine].
82
+
83
+ ## Can a consumer sue your business in Idaho over privacy? {#consumer-lawsuit}
84
+
85
+ **Short answer.** Not under the breach statute — that chapter creates no private right of action. Enforcement belongs to each entity's primary regulator, which may bring a civil action to enforce compliance and enjoin further violations when it believes an entity failed to give required notice [^breach-enforcement]; for businesses not overseen by the Department of Finance, the Department of Insurance, or a federal regulator, that primary regulator is the Attorney General [^primary-regulator-def]. The consumer's route is the Idaho Consumer Protection Act: a person who purchases or leases goods or services and suffers an ascertainable loss from a deceptive practice — which can include a privacy promise the business did not keep — may sue for actual damages or $1,000, whichever is greater [^icpa-pra].
86
+
87
+ The ICPA action comes with real teeth and real limits. A prevailing plaintiff recovers mandatory attorney's fees [^icpa-fees], courts may award punitive damages for repeated or flagrant violations, and an elderly (62 or older) or disabled plaintiff who proves an enumerated severe loss adds an enhanced penalty of $15,000 or treble actual damages [^icpa-elderly]. But standing requires a purchase or lease plus ascertainable loss — whether a user of a free, ad-supported service can satisfy that is untested in Idaho appellate case law — and class actions are largely defanged: the statute caps a class's statutory recovery at $1,000 total for the class [^icpa-pra], leaving only actual damages (hard to prove in privacy cases) uncapped.
88
+
89
+ Public enforcement faces none of those limits. The Attorney General may sue for injunctions, consumer restitution, and civil penalties of up to $5,000 per violation plus expenses, investigative costs, and attorney's fees [^icpa-ag-penalties] — and must ordinarily first give the target written notice and an opportunity to execute an assurance of voluntary compliance or consent judgment [^icpa-avc], Idaho's nearest analog to a cure period. Two narrower sectoral remedies round out the picture. A merchant that prints more than the last five digits of a payment-card number or prints the expiration date on a receipt faces civil penalties; the cardholder's personal action is expressly keyed to a receipt that printed the payment-card number and the prosecuting attorney's failure to act within sixty days [^card-receipt-action]. And the 2026 social-media minors and conversational-AI enactments should be tracked as narrow sectoral remedy changes, not as general consumer-privacy causes of action.
90
+
91
+ [^about]: By Steven Obiajulu, J.D. Published by [openagreements.org](https://openagreements.org). Last reviewed 2026-06-11. License: CC BY 4.0. Steven Obiajulu, J.D. is admitted in New York, not Idaho. This article synthesizes Idaho primary law and is not legal advice from a Idaho-admitted attorney. This article is for informational purposes only and does not create an attorney-client relationship.
92
+
93
+ [^breach-duty-scope]: **Idaho Code § 28-51-105** — "A city, county or state agency, individual or a commercial entity that conducts business in Idaho and that owns or licenses computerized data that includes personal information about a resident of Idaho shall, when it becomes aware of a breach of the security of the system, 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-105(1).* <https://legislature.idaho.gov/statutesrules/idstat/Title28/T28CH51/SECT28-51-105/>
94
+
95
+ [^commercial-entity-def]: **Idaho Code § 28-51-104** — "‘Commercial entity’ includes corporation, business trust, estate, trust, partnership, limited partnership, limited liability partnership, limited liability company, association, organization, joint venture and any other legal entity, whether for profit or not-for-profit." *Idaho Code § 28-51-104(3).* <https://legislature.idaho.gov/statutesrules/idstat/Title28/T28CH51/SECT28-51-104/>
96
+
97
+ [^icpa-catchall]: **Idaho Code § 48-603** — "Engaging in any act or practice that is otherwise misleading, false, or deceptive to the consumer" *Idaho Code § 48-603(17).* <https://legislature.idaho.gov/statutesrules/idstat/Title48/T48CH6/SECT48-603/>
98
+
99
+ [^ftc5-deceptive]: **FTC Act § 5** — "Unfair methods of competition in or affecting commerce, and unfair or deceptive acts or practices in or affecting commerce, are hereby declared unlawful." *15 U.S.C. § 45(a)(1).* <https://www.law.cornell.edu/uscode/text/15/45#:~:text=Unfair%20methods%20of%20competition%20in,commerce%2C%20are%20hereby%20declared%20unlawful.>
100
+
101
+ [^icpa-deception-policy]: **Idaho Code § 48-603** — "The following unfair methods of competition and unfair or deceptive acts or practices in the conduct of any trade or commerce are hereby declared to be unlawful, where a person knows, or in the exercise of due care should know, that he has in the past, or is: (1) Passing off goods or services as those of another; (2) Causing likelihood of confusion or of misunderstanding as to the source, sponsorship, approval, or certification of goods or services; (3) Causing likelihood of confusion or of misunderstanding as to affiliation, connection, or association with, or certification by, another; (4) Using deceptive representations or designations of geographic origin in connection with goods or services; (5) Representing that goods or services have sponsorship, approval, characteristics, ingredients, uses, benefits, or quantities that they do not have or that a person has a sponsorship, approval, status, affiliation, connection, qualifications or license that he does not have; (6) Representing that goods are original or new if they are deteriorated, altered, reconditioned, reclaimed, used, or secondhand; (7) Representing that goods or services are of a particular standard, quality, or grade, or that goods are of a particular style or model, if they are of another; (8) Disparaging the goods, services, or business of another by false or misleading representation of fact; (9) Advertising goods or services with intent not to sell them as advertised; (10) Advertising goods or services with intent not to supply reasonably expectable public demand, unless the advertisement discloses a limitation of quantity; (11) Making false or misleading statements of fact concerning the reasons for, existence of, or amounts of price reductions; (12) Obtaining the signature of the buyer to a contract when it contains blank spaces to be filled in after it has been signed; (13) Failing to deliver to the consumer at the time of the consumer’s signature a legible copy of the contract or of any other document that the seller or lender has required or requested the buyer to sign, and that he has signed, during or after the contract negotiation; (14) Making false or misleading statements of fact concerning the age, extent of use, or mileage of any goods; (15) Promising or offering to pay, credit or allow to any buyer or lessee any compensation or reward in consideration of his giving to the seller or lessor the names of prospective purchasers or lessees, or otherwise aiding the seller or lessor in making a sale or lease to another person, if the earning of the rebate, discount or other value is contingent upon the occurrence of an event subsequent to the time the buyer or lessee agrees to buy or lease; (16) Representing that services, replacements or repairs are needed if they are not needed, or providing services, replacements or repairs that are not needed; (17) Engaging in any act or practice that is otherwise misleading, false, or deceptive to the consumer" *Idaho Code § 48-603.* <https://legislature.idaho.gov/statutesrules/idstat/Title48/T48CH6/SECT48-603/>
102
+
103
+ [^hipaa-notice]: **HIPAA Notice of Privacy Practices** — "an individual has a right to adequate notice of the uses and disclosures of protected health information that may be made by the covered entity, and of the individual's rights and the covered entity's legal duties with respect to protected health information" *45 C.F.R. § 164.520(a)(1).* <https://www.law.cornell.edu/cfr/text/45/164.520#:~:text=an%20individual%20has%20a%20right,respect%20to%20protected%20health%20information>
104
+
105
+ [^glba-notice]: **GLBA privacy notice** — "a financial institution may not, directly or through any affiliate, disclose to a nonaffiliated third party any nonpublic personal information, unless such financial institution provides or has provided to the consumer a notice that complies with section 6803 of this title." *15 U.S.C. § 6802(a).* <https://www.law.cornell.edu/uscode/text/15/6802#:~:text=a%20financial%20institution%20may%20not%2C,section%206803%20of%20this%20title.>
106
+
107
+ [^breach-maintainer-notice]: **Idaho Code § 28-51-105** — "An agency, individual or a commercial entity that maintains computerized data that includes personal information that the agency, individual or the commercial entity does not own or license shall give notice to and cooperate with the owner or licensee of the information of any breach of the security of the system immediately following discovery of a breach if misuse of personal information about an Idaho resident occurred or is reasonably likely to occur." *Idaho Code § 28-51-105(2).* <https://legislature.idaho.gov/statutesrules/idstat/Title28/T28CH51/SECT28-51-105/>
108
+
109
+ [^glba-safeguards]: **GLBA Safeguards Rule** — "Requiring your service providers by contract to implement and maintain such safeguards" *16 C.F.R. § 314.4(f)(2).* <https://www.law.cornell.edu/cfr/text/16/314.4#:~:text=Requiring%20your%20service%20providers%20by,implement%20and%20maintain%20such%20safeguards>
110
+
111
+ [^hipaa-baa]: **HIPAA Business Associate Contracts** — "A contract between the covered entity and a business associate must: (i) Establish the permitted and required uses and disclosures of protected health information by the business associate." *45 C.F.R. § 164.504(e)(2).* <https://www.law.cornell.edu/cfr/text/45/164.504#:~:text=A%20contract%20between%20the%20covered,information%20by%20the%20business%20associate.>
112
+
113
+ [^rights-breach-notice]: **Idaho Code § 28-51-105** — "If the investigation determines that the misuse of information about an Idaho resident has occurred or is reasonably likely to occur, the agency, individual or the commercial entity shall give notice as soon as possible to the affected Idaho resident." *Idaho Code § 28-51-105(1).* <https://legislature.idaho.gov/statutesrules/idstat/Title28/T28CH51/SECT28-51-105/>
114
+
115
+ [^glba-optout]: **GLBA opt-out** — "A financial institution may not disclose nonpublic personal information to a nonaffiliated third party unless— (A) such financial institution clearly and conspicuously discloses to the consumer, in writing or in electronic form or other form permitted by the regulations prescribed under section 6804 of this title, that such information may be disclosed to such third party; (B) the consumer is given the opportunity, before the time that such information is initially disclosed, to direct that such information not be disclosed to such third party; and (C) the consumer is given an explanation of how the consumer can exercise that nondisclosure option." *15 U.S.C. § 6802(b)(1).* <https://www.law.cornell.edu/uscode/text/15/6802#:~:text=A%20financial%20institution%20may%20not%20disclose,can%20exercise%20that%20nondisclosure%20option.>
116
+
117
+ [^coppa-parental]: **COPPA parental rights** — "the opportunity at any time to refuse to permit the operator’s further use or maintenance in retrievable form, or future online collection, of personal information from that child" *15 U.S.C. § 6502(b)(1)(B)(ii).* <https://www.law.cornell.edu/uscode/text/15/6502#:~:text=the%20opportunity%20at%20any%20time,personal%20information%20from%20that%20child>
118
+
119
+ [^breach-trigger-timing]: **Idaho Code § 28-51-105** — "If the investigation determines that the misuse of information about an Idaho resident has occurred or is reasonably likely to occur, the agency, individual or the commercial entity shall give notice as soon as possible to the affected Idaho resident. Notice must be made in the most expedient time possible and without unreasonable delay, consistent with the legitimate needs of law enforcement and consistent with any measures necessary to determine the scope of the breach, to identify the individuals affected, and to restore the reasonable integrity of the computerized data system." *Idaho Code § 28-51-105(1).* <https://legislature.idaho.gov/statutesrules/idstat/Title28/T28CH51/SECT28-51-105/>
120
+
121
+ [^breach-def]: **Idaho Code § 28-51-104** — "‘Breach of the security of the system’ means the illegal acquisition of unencrypted computerized data that materially compromises the security, confidentiality, or integrity of personal information for one (1) or more persons maintained by an agency, individual or a commercial entity." *Idaho Code § 28-51-104(2).* <https://legislature.idaho.gov/statutesrules/idstat/Title28/T28CH51/SECT28-51-104/>
122
+
123
+ [^breach-agency-ag-notice]: **Idaho Code § 28-51-105** — "When an agency becomes aware of a breach of the security of the system, it shall, within twenty-four (24) hours of such discovery, notify the office of the Idaho attorney general." *Idaho Code § 28-51-105(1).* <https://legislature.idaho.gov/statutesrules/idstat/Title28/T28CH51/SECT28-51-105/>
124
+
125
+ [^breach-notice-methods]: **Idaho Code § 28-51-104** — "‘Notice’ means: (a) Written notice to the most recent address the agency, individual or commercial entity has in its records; (b) Telephonic notice; (c) Electronic notice, if the notice provided is consistent with the provisions regarding electronic records and signatures set forth in 15 U.S.C. section 7001; or (d) Substitute notice, if the agency, individual or the commercial entity required to provide notice demonstrates that the cost of providing notice will exceed twenty-five thousand dollars ($25,000), or that the number of Idaho residents to be notified exceeds fifty thousand (50,000), or that the agency, individual or the commercial entity does not have sufficient contact information to provide notice. Substitute notice consists of all of the following: (i) E-mail notice if the agency, individual or the commercial entity has e-mail addresses for the affected Idaho residents; and (ii) Conspicuous posting of the notice on the website page of the agency, individual or the commercial entity if the agency, individual or the commercial entity maintains one; and (iii) Notice to major statewide media." *Idaho Code § 28-51-104(4).* <https://legislature.idaho.gov/statutesrules/idstat/Title28/T28CH51/SECT28-51-104/>
126
+
127
+ [^breach-law-enforcement-delay]: **Idaho Code § 28-51-105** — "Notice required by this section may be delayed if a law enforcement agency advises the agency, individual or commercial entity that the notice will impede a criminal investigation. Notice required by this section must be made in good faith, without unreasonable delay and as soon as possible after the law enforcement agency advises the agency, individual or commercial entity that notification will no longer impede the investigation." *Idaho Code § 28-51-105(3).* <https://legislature.idaho.gov/statutesrules/idstat/Title28/T28CH51/SECT28-51-105/>
128
+
129
+ [^breach-personal-info]: **Idaho Code § 28-51-104** — "‘Personal information’ means an Idaho resident’s first name or first initial and last name in combination with any one (1) or more of the following data elements that relate to the resident, when either the name or the data elements are not encrypted: (a) Social security number; (b) Driver’s license number or Idaho identification card number; or (c) Account number, or credit 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." *Idaho Code § 28-51-104(5).* <https://legislature.idaho.gov/statutesrules/idstat/Title28/T28CH51/SECT28-51-104/>
130
+
131
+ [^breach-safe-harbor]: **Idaho Code § 28-51-106** — "An agency, individual or a commercial entity that maintains its own notice procedures as part of an information security policy for the treatment of personal information, and whose procedures are otherwise consistent with the timing requirements of section 28-51-105, Idaho Code, is deemed to be in compliance with the notice requirements of section 28-51-105, Idaho Code, if the agency, individual or the commercial entity notifies affected Idaho residents in accordance with its policies in the event of a breach of security of the system. (2) An individual or a commercial entity that is regulated by state or federal law and that maintains procedures for a breach of the security of the system pursuant to the laws, rules, regulations, guidances, or guidelines established by its primary or functional state or federal regulator is deemed to be in compliance with section 28-51-105, Idaho Code, if the individual or the commercial entity complies with the maintained procedures when a breach of the security of the system occurs." *Idaho Code § 28-51-106(1)-(2).* <https://legislature.idaho.gov/statutesrules/idstat/Title28/T28CH51/SECT28-51-106/>
132
+
133
+ [^breach-fine]: **Idaho Code § 28-51-107** — "Any agency, individual or commercial entity that intentionally fails to give notice in accordance with section 28-51-105, Idaho Code, shall be subject to a fine of not more than twenty-five thousand dollars ($25,000) per breach of the security of the system." *Idaho Code § 28-51-107.* <https://legislature.idaho.gov/statutesrules/idstat/Title28/T28CH51/SECT28-51-107/>
134
+
135
+ [^breach-enforcement]: **Idaho Code § 28-51-107** — "In any case in which an agency’s, commercial entity’s or individual’s primary regulator has reason to believe that an agency, individual or commercial entity subject to that primary regulator’s jurisdiction under section 28-51-104(6), Idaho Code, has violated section 28-51-105, Idaho Code, by failing to give notice in accordance with that section, the primary regulator may bring a civil action to enforce compliance with that section and enjoin that agency, individual or commercial entity from further violations." *Idaho Code § 28-51-107.* <https://legislature.idaho.gov/statutesrules/idstat/Title28/T28CH51/SECT28-51-107/>
136
+
137
+ [^primary-regulator-def]: **Idaho Code § 28-51-104** — "the primary regulator of a commercial entity or individual licensed by the department of finance is the department of finance, the primary regulator of a commercial entity or individual licensed by the department of insurance is the department of insurance and, for all agencies and all other commercial entities or individuals, the primary regulator is the attorney general." *Idaho Code § 28-51-104(6).* <https://legislature.idaho.gov/statutesrules/idstat/Title28/T28CH51/SECT28-51-104/>
138
+
139
+ [^icpa-pra]: **Idaho Code § 48-608** — "Any person who purchases or leases goods or services and thereby suffers any ascertainable loss of money or property, real or personal, as a result of the use or employment by another person of a method, act or practice declared unlawful by this chapter, may treat any agreement incident thereto as voidable or, in the alternative, may bring an action to recover actual damages or one thousand dollars ($1,000), whichever is the greater; provided, however, that in the case of a class action, the class may bring an action for actual damages or a total for the class that may not exceed one thousand dollars ($1,000), whichever is the greater." *Idaho Code § 48-608(1).* <https://legislature.idaho.gov/statutesrules/idstat/Title48/T48CH6/SECT48-608/>
140
+
141
+ [^icpa-fees]: **Idaho Code § 48-608** — "In any action brought by a person under this section, the court shall award, in addition to the relief provided in this section, reasonable attorney’s fees to the plaintiff if he prevails." *Idaho Code § 48-608(5).* <https://legislature.idaho.gov/statutesrules/idstat/Title48/T48CH6/SECT48-608/>
142
+
143
+ [^icpa-elderly]: **Idaho Code § 48-608** — "An elderly person or a disabled person who brings an action under subsection (1) of this section shall, in addition to the remedies available under subsection (1) of this section, recover from the offending party an enhanced penalty of fifteen thousand dollars ($15,000) or treble the actual damages, whichever is greater. (a) In order to recover the enhanced penalty, the court must find that the offending party knew or should have known that his conduct was perpetrated against an elderly or disabled person and that his conduct caused one (1) of the following: (i) Loss or encumbrance of the elderly or disabled person’s primary residence; (ii) Loss of more than twenty-five percent (25%) of the elderly or disabled person’s principal monthly income; (iii) Loss of more than twenty-five percent (25%) of the funds belonging to the elderly or disabled person set aside by the elderly or disabled person for retirement or for personal or family care or maintenance; (iv) Loss of more than twenty-five percent (25%) of the monthly payments that the elderly or disabled person receives under a pension or retirement plan; or (v) Loss of assets essential to the health or welfare of the elderly or disabled person. (b) If the court orders restitution under subsection (1) of this section for a pecuniary or monetary loss suffered by an elderly or disabled person, the court shall require that the restitution be paid by the offending party before he pays the enhanced penalty imposed by this subsection. (c) In this subsection: (i) ‘Disabled person’ means a person who has an impairment of a physical, mental or emotional nature that substantially limits at least one (1) major life activity. (ii) ‘Elderly person’ means a person who is at least sixty-two (62) years of age." *Idaho Code § 48-608(2).* <https://legislature.idaho.gov/statutesrules/idstat/Title48/T48CH6/SECT48-608/>
144
+
145
+ [^icpa-ag-penalties]: **Idaho Code § 48-606** — "Whenever the attorney general has reason to believe that any person is using, has used, or is about to use any method, act or practice declared by this chapter to be unlawful, and that proceedings would be in the public interest, he may bring an action in the name of the state against such person: (a) To obtain a declaratory judgment that a method, act or practice violates the provisions of this chapter; (b) To enjoin any method, act or practice that violates the provisions of this chapter by issuance of a temporary restraining order or preliminary or permanent injunction, upon the giving of appropriate notice to that person as provided by the Idaho rules of civil procedure; (c) To recover on behalf of consumers actual damages or restitution of money, property or other things received from such consumers in connection with a violation of the provisions of this chapter; (d) To order specific performance by the violator; (e) To recover from the alleged violator civil penalties of up to five thousand dollars ($5,000) per violation for violation of the provisions of this chapter; and (f) To recover from the alleged violator reasonable expenses, investigative costs and attorney’s fees incurred by the attorney general." *Idaho Code § 48-606(1).* <https://legislature.idaho.gov/statutesrules/idstat/Title48/T48CH6/SECT48-606/>
146
+
147
+ [^icpa-avc]: **Idaho Code § 48-606** — "Unless the attorney general finds in writing that the purposes of this chapter will be substantially and materially impaired by delay in instituting legal proceedings, he shall, before initiating any legal proceedings as provided in this section, give notice in writing that such proceedings are contemplated to the person against whom proceedings are contemplated and allow such person a reasonable opportunity to appear before the attorney general and execute an assurance of voluntary compliance or a consent judgment as in this chapter provided." *Idaho Code § 48-606(3).* <https://legislature.idaho.gov/statutesrules/idstat/Title48/T48CH6/SECT48-606/>
148
+
149
+ [^card-receipt-action]: **Idaho Code § 28-51-103** — "A merchant who accepts a payment card for the transaction of business may not print more than the last five (5) digits of the payment card’s account number or print the payment card’s expiration date on a receipt provided to the cardholder. This subsection does not apply to a transaction in which the sole means of recording the payment card’s account number or expiration date is by handwriting or by an imprint or copy of the payment card. Effective January 1, 2004, this section applies to all receipts that are electronically printed using a cash register or other machine or device that is first used on or after July 1, 2003. Effective January 1, 2005, this section applies to all receipts that are electronically printed, including those printed using a cash register or other machine or device that is first used before July 1, 2003. (3) A merchant who violates this section shall be subject to a civil penalty of not more than two hundred fifty dollars ($250) for the first violation and one thousand dollars ($1,000) for a second or subsequent violation. An action to recover the civil penalty may be brought by a prosecuting attorney. If the prosecuting attorney does not file an action for such a civil penalty within sixty (60) days from the date the violation is reported by the cardholder whose payment card number was printed on a receipt in violation of this section, the cardholder may file such action." *Idaho Code § 28-51-103(2)-(3).* <https://legislature.idaho.gov/statutesrules/idstat/Title28/T28CH51/SECT28-51-103/>
@@ -0,0 +1,238 @@
1
+ ---
2
+ jurisdiction: "Illinois"
3
+ slug: illinois
4
+ countryCode: US
5
+ snapshotAsOf: "2026-06-19"
6
+ lastReviewed: "2026-06-11"
7
+ canonicalUrl: https://openagreements.org/practice-guides/privacy/us/illinois
8
+ license: CC BY 4.0
9
+ stale: false
10
+ ---
11
+
12
+ > [!IMPORTANT]
13
+ > **Informational only — not legal advice.** This is a snapshot of an OpenAgreements practice note,
14
+ > provided for general information. It is not legal advice, does not create an attorney-client
15
+ > relationship, and is not a substitute for a licensed attorney in the relevant jurisdiction.
16
+ > Laws change; verify against the canonical version before relying on it.
17
+ >
18
+ > **Canonical:** https://openagreements.org/practice-guides/privacy/us/illinois · **Snapshot as of:** 2026-06-19 · License: CC BY 4.0 · © openagreements.org
19
+
20
+ # Illinois Consumer Privacy Law (BIPA)[^about]
21
+
22
+ Illinois has no comprehensive consumer-privacy act, but the Biometric Information Privacy Act (740 ILCS 14) is the most litigated state privacy statute in the country — written consent and a public retention policy are required, and private plaintiffs can sue for liquidated damages without proving actual harm.
23
+
24
+
25
+ ## At a glance
26
+
27
+ | Question | Illinois |
28
+ | --- | --- |
29
+ | **Law coverage** | Specific data types only |
30
+ | **Summary** | Illinois has not enacted a comprehensive consumer-privacy law, but it is the highest-exposure privacy state in the country for one reason — the Biometric Information Privacy Act. Before collecting a fingerprint, face scan, or voiceprint, a business must publish a written retention-and-destruction policy and obtain informed written consent, and any person whose rights are violated can sue for $1,000 or $5,000 in liquidated damages per person without proving actual harm, on a five-year limitations period. A 2024 amendment capped repeated identical scans at one recovery per person per method of collection, and in April 2026 the Seventh Circuit held that cap applies retroactively to pending cases. Genetic data carries parallel private-suit exposure under GIPA, and breach notification under the Personal Information Protection Act is the Attorney General's lane. |
31
+ | **Main law** | Biometric Information Privacy Act (BIPA), 740 ILCS 14 — Illinois has no comprehensive consumer-privacy law; BIPA sits alongside the Genetic Information Privacy Act (410 ILCS 513), the Personal Information Protection Act breach statute (815 ILCS 530), and the Consumer Fraud Act |
32
+ | **Privacy policy required?** | Yes for biometric data — BIPA § 15(a) requires a written, publicly available policy with a retention schedule and destruction guidelines; no Illinois statute fixes the contents of a general consumer privacy policy, so FTC Act § 5 and the Consumer Fraud Act truthfulness rules govern the rest |
33
+ | **Who does it cover?** | BIPA reaches any private entity — any individual, partnership, corporation, LLC, association, or other group — that handles biometric identifiers or biometric information of people in Illinois, with no revenue or volume threshold; government agencies and GLBA financial institutions are carved out |
34
+ | **Can consumers sue?** | Yes |
35
+ | **Privacy policy rule** | Policy required only for specific data |
36
+ | **Consent for sensitive data?** | Only for certain data types |
37
+ | **Browser opt-out signals?** | Not required |
38
+ | **Lawsuit detail** | Yes — BIPA § 20 allows suit without actual injury beyond the statutory violation under Rosenbach; GIPA § 40 separately provides a private right of action and liquidated damages of $2,500/$15,000 per violation |
39
+ | **Who enforces it?** | BIPA is enforced through private plaintiffs; GIPA has a private right of action, with insurer-related § 30 violations handled through the Illinois Insurance Code; PIPA is enforced through the Consumer Fraud and Deceptive Business Practices Act |
40
+
41
+ ## Which privacy laws apply to your business in Illinois? {#which-privacy-laws-apply}
42
+
43
+ **Short answer.** Illinois has no comprehensive consumer-privacy statute, but it is anything but a light-touch state. The headline law is the Biometric Information Privacy Act (BIPA), which the General Assembly enacted on the finding that the public welfare, security, and safety will be served by regulating the collection, use, safeguarding, handling, storage, retention, and destruction of biometric identifiers and information [^stat-bipa-5-findings]. BIPA applies to any private entity — any individual, partnership, corporation, limited liability company, association, or other group, however organized — with no revenue or data-volume threshold [^stat-bipa-10-private-entity]. Around it sit three more statutes: the Genetic Information Privacy Act (GIPA), which makes genetic testing information confidential and privileged [^stat-gipa-15-confidential]; the Personal Information Protection Act (PIPA), the breach-notification statute that reaches essentially every entity handling nonpublic personal information of Illinois residents [^stat-pipa-5-data-collector]; and the Consumer Fraud and Deceptive Business Practices Act, which supplies the enforcement hook for deceptive privacy practices.
44
+
45
+ What Illinois lacks is the omnibus controller-processor framework other states have adopted: there are no general rights to access, correct, delete, or opt out of the sale of personal data, no notice-at-collection mandate, and no data-protection-assessment duty under current Illinois law. What Illinois has instead is sharper teeth on three specific data types — biometric, genetic, and breached personal information — and, uniquely among the states, private rights of action with liquidated damages on the first two. That combination has made Illinois the national center of privacy class-action litigation rather than of regulatory enforcement.
46
+
47
+ The federal overlay fills the rest of the program: FTC Act § 5 reaches deceptive or unfair privacy practices nationwide, GLBA governs financial institutions, HIPAA governs covered health entities, and COPPA governs services directed to children under 13.
48
+
49
+ ## What must your Illinois privacy policy contain? {#privacy-policy-contents}
50
+
51
+ **Short answer.** It depends on whether you touch biometric data. If you possess biometric identifiers or biometric information — fingerprints, face geometry, voiceprints, retina or iris scans — BIPA § 15(a) imposes a specific, written-policy mandate: you must develop a written policy, made available to the public, establishing a retention schedule and guidelines for permanently destroying the data when the initial purpose for collecting it has been satisfied or within 3 years of the individual's last interaction with your business, whichever occurs first [^stat-15a-written-policy]. You must then actually follow that schedule: absent a valid warrant or subpoena, a private entity must comply with its established retention schedule and destruction guidelines [^stat-15a-comply]. For everything else, no Illinois statute fixes the contents of a general consumer privacy policy — the governing rule is that whatever you publish must be true, because a policy that misstates your practices is a deceptive act under FTC Act § 5 [^fed-ftc5-deceptive] and under the Illinois Consumer Fraud Act [^stat-icfa-2-deceptive].
52
+
53
+ Section 15(a) is the piece businesses most often miss, and it is the cheapest BIPA violation to avoid because it does not depend on consent mechanics. The duty attaches to *possession* of biometric data, and it has four components on the face of the statute: (1) a *written* policy, (2) *made available to the public* — posted, not kept in a drawer; (3) a *retention schedule* tied to the statute's two ceilings (purpose satisfied, or 3 years after the individual's last interaction, whichever comes first); and (4) *guidelines for permanently destroying* the data. The companion sentence converts the policy from paper to obligation: once the schedule exists, the entity must comply with it unless a court-issued warrant or subpoena intervenes [^stat-15a-comply]. Plaintiffs routinely plead § 15(a) alongside the consent claims, so a biometric privacy policy that is unwritten, unposted, or unenforced is itself a freestanding basis for liquidated damages.
54
+
55
+ For the non-biometric remainder of a privacy policy, build to the federal and sectoral overlay — GLBA privacy notices for financial institutions, the HIPAA notice of privacy practices for covered entities, a COPPA notice for child-directed services — and follow best practice for everyone else: describe the categories of data collected, the purposes, the third parties you share with, and how users exercise any choices you offer. The enforceable Illinois obligation outside BIPA is consistency between the statement and the conduct, because the Consumer Fraud Act declares deceptive acts or practices, including the concealment, suppression or omission of any material fact, unlawful [^stat-icfa-2-deceptive].
56
+
57
+ > [!CAUTION]
58
+ > **Drafting note.**
59
+ >
60
+ > Write the BIPA retention-and-destruction policy *before* the first scan is collected, and post it where the public can find it. The statute makes the written, publicly available policy a duty of every private entity in possession of biometric data, with a destruction deadline of purpose-satisfied or 3 years after the individual's last interaction, whichever occurs first — a policy drafted after collection begins, or one that exists but was never published, leaves the company exposed on § 15(a) even if its consent paperwork is perfect [^stat-15a-written-policy].
61
+
62
+ ## Do you need written consent to collect fingerprints or face scans in Illinois? {#biometric-consent}
63
+
64
+ **Short answer.** Yes — before collection, in writing, and after specific disclosures. BIPA § 15(b) prohibits a private entity from collecting, capturing, purchasing, receiving through trade, or otherwise obtaining a person's biometric identifier or biometric information unless it first informs the person in writing that the data is being collected or stored, informs the person in writing of the specific purpose and length of term of the collection, and receives a written release executed by the subject [^stat-15b-consent]. A biometric identifier means a retina or iris scan, fingerprint, voiceprint, or scan of hand or face geometry [^stat-10-biometric-identifier]. Three companion duties travel with the data: no private entity may sell, lease, trade, or otherwise profit from a person's biometric data [^stat-15c-no-profit]; disclosure to anyone else requires the subject's consent or another narrow statutory basis [^stat-15d-disclosure]; and the data must be stored and protected using the reasonable standard of care within the entity's industry, at least as protectively as other confidential and sensitive information [^stat-15e-safeguards].
65
+
66
+ The order of operations is what trips businesses up: the statute says *first*. Consent collected after the first scan does not cure the collection that already happened, and the disclosures must cover both the specific purpose and the length of term of the collection — a generic onboarding acknowledgment that never mentions storage duration misses an element on the face of § 15(b). In the workplace, the statute's definition of a *written release* expressly contemplates a release executed by an employee as a condition of employment, and — since the 2024 amendment — an electronic signature qualifies [^stat-10-written-release]. So a compliant biometric time-clock or facility-access program is achievable with ordinary HR paperwork: written notice of what is collected, why, and for how long, plus a signed (or e-signed) release, all completed before enrollment.
67
+
68
+ Scope limits matter in both directions. The definition excludes photographs, writing samples, physical descriptions, and information captured from a patient in a health care setting [^stat-10-biometric-identifier]. Plaintiffs have litigated faceprints computed *from* photographs under the *scan of face geometry* language, so photo-based systems still deserve BIPA review. And BIPA does not apply to everyone: it carves out financial institutions subject to GLBA Title V [^stat-bipa-25-glba], state and local government agencies [^q3-stat-bipa-10-private-entity], and contractors working for them [^stat-bipa-25-contractors].
69
+
70
+ > [!NOTE]
71
+ > **Practice note.**
72
+ >
73
+ > Treat the no-profit rule as a flat ban, not a consent question. Section 15(c) prohibits selling, leasing, trading, or otherwise profiting from biometric identifiers or biometric information outright — unlike collection under § 15(b) or disclosure under § 15(d), there is no consent mechanism that authorizes monetizing the data itself, so a business model that prices access to biometric databases cannot be papered over with releases [^stat-15c-no-profit].
74
+
75
+ ## Can someone sue your business under BIPA without proving actual harm? {#bipa-lawsuit-exposure}
76
+
77
+ **Short answer.** Yes — this is the feature that makes Illinois unlike any other state. BIPA § 20 gives any person aggrieved by a violation a right of action in state circuit court or as a supplemental claim in federal court, with liquidated damages of $1,000 per negligent violation or $5,000 per intentional or reckless violation (or actual damages if greater), plus attorneys' fees and costs [^stat-20a-damages]. In *Rosenbach v. Six Flags Entertainment Corp.*, the Illinois Supreme Court held that "an individual need not allege some actual injury or adverse effect, beyond violation of his or her rights under the Act, in order to qualify as an ‘aggrieved’ person and be entitled to seek liquidated damages and injunctive relief pursuant to the Act"[^case-rosenbach] [^case-rosenbach]. And the window is long: in *Tims v. Black Horse Carriers, Inc.*, the court held that the five-year catchall limitations period of section 13-205 of the Code of Civil Procedure controls claims under the Act [^case-tims].
78
+
79
+ The mechanics deserve emphasis because each element compounds the others. The violation *is* the injury — a fingerprint collected without the § 15(b) disclosures and release is actionable the day it is scanned, with no identity theft, data breach, or out-of-pocket loss required. The *Rosenbach* court was explicit that this is the design, not an accident: "When private entities face liability for failure to comply with the law’s requirements without requiring affected individuals or customers to show some injury beyond violation of their statutory rights, those entities have the strongest possible incentive to conform to the law and prevent problems before they occur and cannot be undone."[^case-rosenbach-deterrence] [^case-rosenbach-deterrence] Stack the per-person liquidated amounts across a workforce or user base, add a five-year reach-back under *Tims*, and a routine timekeeping or photo-tagging practice becomes a class action with eight-or-nine-figure exposure.
80
+
81
+ BIPA exposure management is litigation prevention: compliant paperwork, vendor disclosures, and retention policies matter more than regulator relations. The Illinois Supreme Court explained in *Rosenbach* that, other than the private right of action authorized in section 20, no other enforcement mechanism is available [^case-rosenbach-no-agency].
82
+
83
+ > [!NOTE]
84
+ > **Practice note.**
85
+ >
86
+ > Do not read the per-person figures as an automatic award. Even while reaffirming its plaintiff-friendly accrual rule, the Illinois Supreme Court treated runaway aggregate damages as a policy problem for the General Assembly and respectfully suggested that the legislature review those concerns and make clear its intent on the assessment of damages under the Act [^q4-cothron-invitation]. The legislature accepted that invitation in 2024 — the next question covers how the amendment changed the arithmetic — but no business should price its compliance posture on judicial or legislative moderation arriving in time.
87
+
88
+ ## How are BIPA damages counted in Illinois — per person or per scan — after the 2024 amendment? {#per-scan-damages}
89
+
90
+ **Short answer.** For repeated, identical collections: one recovery per person, per method — and that cap now governs pending cases too. The sequence matters. In *Cothron v. White Castle System, Inc.* (Feb. 17, 2023), the Illinois Supreme Court held that "a separate claim accrues under the Act each time a private entity scans or transmits an individual’s biometric identifier or information in violation of section 15(b) or 15(d)"[^case-cothron-per-scan] [^case-cothron-per-scan] — the per-scan reading that produced multibillion-dollar class exposure. The General Assembly answered with Public Act 103-0769, effective August 2, 2024, which added subsections 20(b) and 20(c): an entity that repeatedly collects the same biometric identifier from the same person using the same method of collection has committed a single violation, for which the aggrieved person is entitled to, at most, one recovery [^stat-20b-single-recovery], with the same rule for repeated disclosures of the same data to the same recipient [^stat-20c-single-disclosure]. And on April 1, 2026, the Seventh Circuit in *Gregg v. Central Transport LLC* held that "this amendment applies retroactively because it impacts only the statutory damages available to plaintiffs—it does not change BIPA’s substantive standards of liability"[^case-gregg-retroactive] [^case-gregg-retroactive].
91
+
92
+ The 2023–2026 arc is worth a timeline, because each date changed the settlement value of every pending BIPA case:
93
+
94
+ -
95
+ -
96
+ -
97
+
98
+ > [!NOTE]
99
+ > **Practice note.**
100
+ >
101
+ > The single-recovery rule is narrower than the headline suggests. The statutory text caps recovery only where the *same* biometric identifier is taken from the *same* person using the *same method of collection* — and, for disclosure, only as to the *same recipient* [^stat-20b-single-recovery] [^stat-20c-single-disclosure]. A business that runs a fingerprint time clock *and* a face-scan access system, or that shares biometric data with multiple vendors, can still face multiple recoveries per person, and class exposure still scales with headcount because every affected person keeps his or her own recovery.
102
+
103
+ ## Can you ask Illinois employees or job applicants for genetic tests or genetic information? {#genetic-information-employment}
104
+
105
+ **Short answer.** No. The Genetic Information Privacy Act (GIPA) prohibits an employer, employment agency, labor organization, or licensing agency from directly or indirectly soliciting, requesting, requiring, or purchasing genetic testing or genetic information of a person or a person's family member — or administering a genetic test — as a condition of employment, a preemployment application, membership, or licensure [^stat-gipa-25-employment]. GIPA provides private-suit exposure: any person aggrieved by a violation may sue and recover liquidated damages of $2,500 per negligent violation or $15,000 per intentional or reckless violation (or actual damages if greater), plus attorneys' fees, subject to the Illinois Insurance Code remedy for insurer violations of section 30 [^stat-gipa-40-damages].
106
+
107
+ Two statutory features give the employment prohibition a long reach. First, the ban covers both the person and the person's family member when the request is tied to employment, preemployment application, labor-organization membership, or licensure [^stat-gipa-25-employment]. Second, *genetic testing* expressly includes direct-to-consumer commercial genetic testing [^stat-gipa-10-definitions], so consumer DNA-kit results are covered the same as clinical tests. The statute also bars employers from using genetic testing or genetic information to affect terms or conditions, limit or classify employees, or retaliate against anyone alleging a violation [^stat-gipa-25-employment]. It separately prohibits offering employment, membership, licensure, pay, or benefits in return for taking a genetic test [^stat-gipa-25-pay-benefit], with narrow statutory provisions for workplace wellness programs [^stat-gipa-25-wellness], employee-requested workers' compensation testing [^stat-gipa-25-workers-comp], and toxic-substance genetic monitoring [^stat-gipa-25-toxic-monitoring].
108
+
109
+ The practical risk is indirect collection. The statute reaches requests made through employment agencies, licensing agencies, labor organizations, and other employment-related channels, so Illinois hiring and occupational-health forms should be reviewed for genetic testing or genetic-information fields before they are given to applicants or employees [^stat-gipa-25-employment].
110
+
111
+ > [!CAUTION]
112
+ > **Drafting note.**
113
+ >
114
+ > Strip family-medical-history questions out of Illinois hiring and occupational-health paperwork, including forms administered by third-party clinics on your behalf. The statutory prohibition reaches *indirect* solicitation and requests made as a condition of a preemployment application [^stat-gipa-25-employment], so routing the questionnaire through an outside examiner does not take the inquiry outside GIPA — and each affected applicant carries $2,500-to-$15,000 liquidated-damages exposure [^stat-gipa-40-damages].
115
+
116
+ ## Do Illinois residents have rights to access, delete, or opt out of the sale of their data? {#consumer-rights-opt-outs}
117
+
118
+ **Short answer.** Not as general rights — Illinois has no omnibus statute granting access, correction, deletion, portability, or sale opt-outs across all personal data, and no Illinois law requires businesses to honor universal opt-out preference signals such as Global Privacy Control. What Illinois residents have instead are targeted, data-type-specific controls with unusual force: biometric data cannot be collected at all without prior written notice and a written release [^q7-stat-15b-consent], and it must be destroyed when the collection purpose is satisfied or within 3 years of the person's last interaction with the business [^q7-stat-15a-destruction]; genetic test results cannot be disclosed in identifiable form except to the tested person and those the person authorizes [^q7-stat-gipa-30-disclosure].
119
+
120
+ The practical translation: an Illinois consumer cannot email a retailer and demand a copy or deletion of an ordinary marketing profile the way a resident of an omnibus-law state can. But for the two data types the legislature singled out, the Illinois model is stronger than a rights-request regime — it is consent-or-nothing on the front end (biometrics may not be obtained without a release; genetic information may not be solicited by employers at all), an automatic destruction clock rather than a deletion request [^q7-stat-15a-destruction], and a flat ban on profiting from biometric data that no opt-in can waive. A business cannot paper around these rules with terms of service, and the rights are self-executing through the private rights of action covered above rather than through a regulator's complaint portal.
121
+
122
+ ## When must you notify people of a data breach in Illinois? {#breach-notification}
123
+
124
+ **Short answer.** In the most expedient time possible and without unreasonable delay. Under the Personal Information Protection Act (PIPA), any data collector that owns or licenses personal information concerning an Illinois resident must notify the resident, at no charge, following discovery or notification of a breach — with delay tolerated only for measures necessary to determine the breach's scope and restore the system's integrity, security, and confidentiality [^stat-pipa-10-notice]. A breach means unauthorized acquisition of computerized data that compromises the security, confidentiality, or integrity of personal information [^stat-pipa-5-breach]. If a single breach requires notice to more than 500 Illinois residents, the data collector must also notify the Attorney General [^stat-pipa-10e-ag], and a violation of the Act is an unlawful practice under the Consumer Fraud and Deceptive Business Practices Act [^stat-pipa-20-icfa].
125
+
126
+ *Personal information* under PIPA is broader than the classic name-plus-SSN formula. It covers a name combined with an unencrypted Social Security number, driver's license or state ID number, financial-account or card data, medical information (expressly including information provided to a website or mobile application), health-insurance information, or unique biometric data used to authenticate an individual [^stat-pipa-5-personal-info] — and, separately, a username or email address combined with a password or security question and answer, a category with its own lighter notice option directing users to change credentials [^stat-pipa-10-credential-notice]. Encrypted or redacted data is outside the quoted definition unless the keys were acquired without authorization through the breach [^stat-pipa-5-personal-info]. The AG notice for 500-plus-resident breaches must arrive no later than the consumer notices, and the Attorney General may publish the breached entity's name [^stat-pipa-10e-ag]. The duties cannot be contracted away: any waiver of PIPA is void and unenforceable [^stat-pipa-15-waiver].
127
+
128
+ Enforcement runs through the Attorney General — and that is the one place in Illinois privacy law where the AG, rather than a class-action plaintiff, holds the pen. Because a PIPA violation is deemed an unlawful practice under the Consumer Fraud Act [^stat-pipa-20-icfa], the AG can seek injunctions and civil penalties for late or omitted notice, with no cure period written into the statute. A private plaintiff, by contrast, has no liquidated-damages remedy here: a consumer suing over a breach must proceed under the Consumer Fraud Act, which requires actual damage from the violation [^stat-icfa-10a-actual] — a sharp contrast with BIPA and GIPA, where the statutory violation alone supports liquidated damages. Note the interaction for biometric incidents: a breach of authentication-grade biometric data triggers PIPA notice duties *and* invites scrutiny of the § 15(e) safeguards duty under BIPA, where the per-person liquidated-damages regime does apply.
129
+
130
+ ## What must your contracts with vendors say in Illinois? {#vendor-contracts}
131
+
132
+ **Short answer.** Illinois has no omnibus data-processing-agreement statute — no state law prescribes controller-processor terms, audit rights, or subprocessor flow-downs for general personal data. But two Illinois statutes put hard edges on vendor arrangements. Under BIPA, handing biometric data to a vendor is a *disclosure* that requires the subject's consent or another narrow statutory basis [^q9-stat-15d-disclosure], so the consent paperwork and the vendor contract have to be designed together. Under PIPA, a vendor that maintains or stores personal information it does not own must notify the owner of any breach immediately following discovery and cooperate in the response [^stat-pipa-10b-vendor].
133
+
134
+ The biometric-vendor scenario deserves specific attention because it is the standard BIPA fact pattern: an employer runs a fingerprint time clock, and a third-party vendor hosts and matches the templates. Both the employer and the vendor can face § 15 exposure — the employer for collecting and disclosing without the statutory disclosures and release, the vendor as a private entity obtaining biometric data itself — and the 2024 single-recovery amendment caps repeated disclosures only as to the *same recipient* [^q9-stat-20c-single-disclosure], so each additional vendor in the chain is a separate exposure line. A compliant program therefore names the vendor categories in the written consent, binds the vendor by contract to BIPA's storage, protection, no-sale, and destruction standards, and allocates defense and indemnity for biometric claims expressly.
135
+
136
+ Where a federal sectoral regime applies, it supplies the contract terms directly: the GLBA Safeguards Rule requires financial institutions to oversee service providers by contract — requiring your service providers by contract to implement and maintain appropriate safeguards [^fed-glba-safeguards] — and HIPAA requires a business-associate agreement with mandatory data-protection, breach-reporting, and subcontractor terms before protected health information moves [^fed-hipaa-baa]. Outside those verticals, carry the same architecture forward as best practice: processing limited to documented instructions, confidentiality, reasonable security, breach notification back to you on PIPA's immediate-notice clock [^stat-pipa-10b-vendor], return or deletion at the end of the engagement, and — for any Illinois-facing biometric or genetic data — express compliance with BIPA and GIPA by name.
137
+
138
+ [^about]: By Steven Obiajulu, J.D. Published by [openagreements.org](https://openagreements.org). Last reviewed 2026-06-11. License: CC BY 4.0. Steven Obiajulu, J.D. is admitted in New York, not Illinois. This article synthesizes Illinois primary law and is not legal advice from a Illinois-admitted attorney. This article is for informational purposes only and does not create an attorney-client relationship.
139
+
140
+ [^stat-bipa-5-findings]: **740 ILCS 14/5** — "The public welfare, security, and safety will be served by regulating the collection, use, safeguarding, handling, storage, retention, and destruction of biometric identifiers and information." *740 ILCS 14/5(g).* <https://www.ilga.gov/documents/legislation/ilcs/documents/074000140K5.htm>
141
+
142
+ [^stat-bipa-10-private-entity]: **740 ILCS 14/10** — "‘Private entity’ means any individual, partnership, corporation, limited liability company, association, or other group, however organized. A private entity does not include a State or local government agency. A private entity does not include any court of Illinois, a clerk of the court, or a judge or justice thereof." *740 ILCS 14/10.* <https://www.ilga.gov/documents/legislation/ilcs/documents/074000140K10.htm>
143
+
144
+ [^stat-gipa-15-confidential]: **410 ILCS 513/15** — "Except as otherwise provided in this Act, genetic testing and information derived from genetic testing is confidential and privileged and may be released only to the individual tested and to persons specifically authorized, in writing in accordance with Section 30, by that individual to receive the information." *410 ILCS 513/15(a).* <https://www.ilga.gov/documents/legislation/ilcs/documents/041005130K15.htm>
145
+
146
+ [^stat-pipa-5-data-collector]: **815 ILCS 530/5** — "‘Data collector’ may include, but is not limited to, government agencies, public and private universities, privately and publicly held corporations, financial institutions, retail operators, and any other entity that, for any purpose, handles, collects, disseminates, or otherwise deals with nonpublic personal information." *815 ILCS 530/5.* <https://www.ilga.gov/documents/legislation/ilcs/documents/081505300K5.htm>
147
+
148
+ [^stat-15a-written-policy]: **740 ILCS 14/15(a)** — "A private entity in possession of biometric identifiers or biometric information must develop a written policy, made available to the public, establishing a retention schedule and guidelines for permanently destroying biometric identifiers and biometric information when the initial purpose for collecting or obtaining such identifiers or information has been satisfied or within 3 years of the individual's last interaction with the private entity, whichever occurs first." *740 ILCS 14/15(a).* <https://www.ilga.gov/documents/legislation/ilcs/documents/074000140K15.htm>
149
+
150
+ [^stat-15a-comply]: **740 ILCS 14/15(a)** — "Absent a valid warrant or subpoena issued by a court of competent jurisdiction, a private entity in possession of biometric identifiers or biometric information must comply with its established retention schedule and destruction guidelines." *740 ILCS 14/15(a).* <https://www.ilga.gov/documents/legislation/ilcs/documents/074000140K15.htm>
151
+
152
+ [^fed-ftc5-deceptive]: **FTC Act § 5** — "Unfair methods of competition in or affecting commerce, and unfair or deceptive acts or practices in or affecting commerce, are hereby declared unlawful." *15 U.S.C. § 45(a)(1).* <https://www.law.cornell.edu/uscode/text/15/45#:~:text=Unfair%20methods%20of%20competition%20in,commerce%2C%20are%20hereby%20declared%20unlawful.>
153
+
154
+ [^stat-icfa-2-deceptive]: **815 ILCS 505/2** — "Unfair methods of competition and unfair or deceptive acts or practices, including but not limited to the use or employment of any deception fraud, false pretense, false promise, misrepresentation or the concealment, suppression or omission of any material fact, with intent that others rely upon the concealment, suppression or omission of such material fact, or the use or employment of any practice described in Section 2 of the ‘Uniform Deceptive Trade Practices Act’, approved August 5, 1965, in the conduct of any trade or commerce are hereby declared unlawful whether any person has in fact been misled, deceived or damaged thereby." *815 ILCS 505/2.* <https://www.ilga.gov/documents/legislation/ilcs/documents/081505050K2.htm>
155
+
156
+ [^stat-15b-consent]: **740 ILCS 14/15(b)** — "No private entity may collect, capture, purchase, receive through trade, or otherwise obtain a person's or a customer's biometric identifier or biometric information, unless it first: (1) informs the subject or the subject's legally authorized representative in writing that a biometric identifier or biometric information is being collected or stored; (2) informs the subject or the subject's legally authorized representative in writing of the specific purpose and length of term for which a biometric identifier or biometric information is being collected, stored, and used; and (3) receives a written release executed by the subject of the biometric identifier or biometric information or the subject's legally authorized representative." *740 ILCS 14/15(b).* <https://www.ilga.gov/documents/legislation/ilcs/documents/074000140K15.htm>
157
+
158
+ [^stat-10-biometric-identifier]: **740 ILCS 14/10** — "‘Biometric identifier’ means a retina or iris scan, fingerprint, voiceprint, or scan of hand or face geometry. Biometric identifiers do not include writing samples, written signatures, photographs, human biological samples used for valid scientific testing or screening, demographic data, tattoo descriptions, or physical descriptions such as height, weight, hair color, or eye color. Biometric identifiers do not include donated organs, tissues, or parts as defined in the Illinois Anatomical Gift Act or blood or serum stored on behalf of recipients or potential recipients of living or cadaveric transplants and obtained or stored by a federally designated organ procurement agency. Biometric identifiers do not include biological materials regulated under the Genetic Information Privacy Act. Biometric identifiers do not include information captured from a patient in a health care setting or information collected, used, or stored for health care treatment, payment, or operations under the federal Health Insurance Portability and Accountability Act of 1996." *740 ILCS 14/10.* <https://www.ilga.gov/documents/legislation/ilcs/documents/074000140K10.htm>
159
+
160
+ [^stat-15c-no-profit]: **740 ILCS 14/15(c)** — "No private entity in possession of a biometric identifier or biometric information may sell, lease, trade, or otherwise profit from a person's or a customer's biometric identifier or biometric information." *740 ILCS 14/15(c).* <https://www.ilga.gov/documents/legislation/ilcs/documents/074000140K15.htm>
161
+
162
+ [^stat-15d-disclosure]: **740 ILCS 14/15(d)** — "No private entity in possession of a biometric identifier or biometric information may disclose, redisclose, or otherwise disseminate a person's or a customer's biometric identifier or biometric information unless: (1) the subject of the biometric identifier or biometric information or the subject's legally authorized representative consents to the disclosure or redisclosure; (2) the disclosure or redisclosure completes a financial transaction requested or authorized by the subject of the biometric identifier or the biometric information or the subject's legally authorized representative; (3) the disclosure or redisclosure is required by State or federal law or municipal ordinance; or (4) the disclosure is required pursuant to a valid warrant or subpoena issued by a court of competent jurisdiction." *740 ILCS 14/15(d).* <https://www.ilga.gov/documents/legislation/ilcs/documents/074000140K15.htm>
163
+
164
+ [^stat-15e-safeguards]: **740 ILCS 14/15(e)** — "A private entity in possession of a biometric identifier or biometric information shall: (1) store, transmit, and protect from disclosure all biometric identifiers and biometric information using the reasonable standard of care within the private entity's industry; and (2) store, transmit, and protect from disclosure all biometric identifiers and biometric information in a manner that is the same as or more protective than the manner in which the private entity stores, transmits, and protects other confidential and sensitive information." *740 ILCS 14/15(e).* <https://www.ilga.gov/documents/legislation/ilcs/documents/074000140K15.htm>
165
+
166
+ [^stat-10-written-release]: **740 ILCS 14/10** — "‘Written release’ means informed written consent, electronic signature, or, in the context of employment, a release executed by an employee as a condition of employment." *740 ILCS 14/10.* <https://www.ilga.gov/documents/legislation/ilcs/documents/074000140K10.htm>
167
+
168
+ [^stat-bipa-25-glba]: **740 ILCS 14/25(c)** — "Nothing in this Act shall be deemed to apply in any manner to a financial institution or an affiliate of a financial institution that is subject to Title V of the federal Gramm-Leach-Bliley Act of 1999 and the rules promulgated thereunder." *740 ILCS 14/25(c).* <https://www.ilga.gov/documents/legislation/ilcs/documents/074000140K25.htm>
169
+
170
+ [^q3-stat-bipa-10-private-entity]: **740 ILCS 14/10** — "‘Private entity’ means any individual, partnership, corporation, limited liability company, association, or other group, however organized. A private entity does not include a State or local government agency. A private entity does not include any court of Illinois, a clerk of the court, or a judge or justice thereof." *740 ILCS 14/10.* <https://www.ilga.gov/documents/legislation/ilcs/documents/074000140K10.htm>
171
+
172
+ [^stat-bipa-25-contractors]: **740 ILCS 14/25(e)** — "Nothing in this Act shall be construed to apply to a contractor, subcontractor, or agent of a State agency or local unit of government when working for that State agency or local unit of government." *740 ILCS 14/25(e).* <https://www.ilga.gov/documents/legislation/ilcs/documents/074000140K25.htm>
173
+
174
+ [^stat-20a-damages]: **740 ILCS 14/20(a)** — "Any person aggrieved by a violation of this Act shall have a right of action in a State circuit court or as a supplemental claim in federal district court against an offending party. A prevailing party may recover for each violation: (1) against a private entity that negligently violates a provision of this Act, liquidated damages of $1,000 or actual damages, whichever is greater; (2) against a private entity that intentionally or recklessly violates a provision of this Act, liquidated damages of $5,000 or actual damages, whichever is greater;" *740 ILCS 14/20(a).* <https://www.ilga.gov/documents/legislation/ilcs/documents/074000140K20.htm>
175
+
176
+ [^case-rosenbach]: **Rosenbach v. Six Flags Entertainment Corp., 2019 IL 123186** — "Contrary to the appellate court’s view, an individual need not allege some actual injury or adverse effect, beyond violation of his or her rights under the Act, in order to qualify as an ‘aggrieved’ person and be entitled to seek liquidated damages and injunctive relief pursuant to the Act." *Rosenbach v. Six Flags Entertainment Corp., 2019 IL 123186, ¶ 40.* <https://www.courtlistener.com/opinion/4658484/rosenbach-v-six-flags-entertainment-corp/#:~:text=Contrary%20to%20the%20appellate%20court%E2%80%99s,relief%20pursuant%20to%20the%20Act.>
177
+
178
+ [^case-tims]: **Tims v. Black Horse Carriers, Inc., 2023 IL 127801** — "For the aforementioned reasons, we find that the five-year limitations period contained in section 13-205 of the Code controls claims under the Act." *Tims v. Black Horse Carriers, Inc., 2023 IL 127801, ¶ 42.* <https://www.courtlistener.com/opinion/9372460/tims-v-black-horse-carriers-inc/#:~:text=For%20the%20aforementioned%20reasons%2C%20we,controls%20claims%20under%20the%20Act.>
179
+
180
+ [^case-rosenbach-deterrence]: **Rosenbach v. Six Flags Entertainment Corp., 2019 IL 123186** — "When private entities face liability for failure to comply with the law’s requirements without requiring affected individuals or customers to show some injury beyond violation of their statutory rights, those entities have the strongest possible incentive to conform to the law and prevent problems before they occur and cannot be undone." *Rosenbach v. Six Flags Entertainment Corp., 2019 IL 123186, ¶ 37.* <https://www.courtlistener.com/opinion/4658484/rosenbach-v-six-flags-entertainment-corp/#:~:text=When%20private%20entities%20face%20liability,occur%20and%20cannot%20be%20undone.>
181
+
182
+ [^case-rosenbach-no-agency]: **Rosenbach v. Six Flags Entertainment Corp., 2019 IL 123186** — "Other than the private right of action authorized in section 20 of the Act, no other enforcement mechanism is available." *Rosenbach v. Six Flags Entertainment Corp., 2019 IL 123186, ¶ 37.* <https://www.courtlistener.com/opinion/4658484/rosenbach-v-six-flags-entertainment-corp/#:~:text=Other%20than%20the%20private%20right,other%20enforcement%20mechanism%20is%20available.>
183
+
184
+ [^q4-cothron-invitation]: **Cothron v. White Castle System, Inc., 2023 IL 128004** — "We respectfully suggest that the legislature review these policy concerns and make clear its intent regarding the assessment of damages under the Act." *Cothron v. White Castle System, Inc., 2023 IL 128004, ¶ 43.* <https://www.courtlistener.com/opinion/9413971/cothron-v-white-castle-system-inc/#:~:text=We%20respectfully%20suggest%20that%20the,of%20damages%20under%20the%20Act.>
185
+
186
+ [^case-cothron-per-scan]: **Cothron v. White Castle System, Inc., 2023 IL 128004** — "We hold that a separate claim accrues under the Act each time a private entity scans or transmits an individual’s biometric identifier or information in violation of section 15(b) or 15(d)." *Cothron v. White Castle System, Inc., 2023 IL 128004, ¶ 1.* <https://www.courtlistener.com/opinion/9413971/cothron-v-white-castle-system-inc/#:~:text=We%20hold%20that%20a%20separate,of%20section%2015(b)%20or%2015(d).>
187
+
188
+ [^stat-20b-single-recovery]: **740 ILCS 14/20(b)** — "For purposes of subsection (b) of Section 15, a private entity that, in more than one instance, collects, captures, purchases, receives through trade, or otherwise obtains the same biometric identifier or biometric information from the same person using the same method of collection in violation of subsection (b) of Section 15 has committed a single violation of subsection (b) of Section 15 for which the aggrieved person is entitled to, at most, one recovery under this Section." *740 ILCS 14/20(b), added by P.A. 103-0769 (eff. Aug. 2, 2024).* <https://www.ilga.gov/documents/legislation/ilcs/documents/074000140K20.htm>
189
+
190
+ [^stat-20c-single-disclosure]: **740 ILCS 14/20(c)** — "For purposes of subsection (d) of Section 15, a private entity that, in more than one instance, discloses, rediscloses, or otherwise disseminates the same biometric identifier or biometric information from the same person to the same recipient using the same method of collection in violation of subsection (d) of Section 15 has committed a single violation of subsection (d) of Section 15 for which the aggrieved person is entitled to, at most, one recovery under this Section regardless of the number of times the private entity disclosed, redisclosed, or otherwise disseminated the same biometric identifier or biometric information of the same person to the same recipient." *740 ILCS 14/20(c), added by P.A. 103-0769 (eff. Aug. 2, 2024).* <https://www.ilga.gov/documents/legislation/ilcs/documents/074000140K20.htm>
191
+
192
+ [^case-gregg-retroactive]: **Gregg v. Central Transport LLC (7th Cir. Apr. 1, 2026)** — "We hold that this amendment applies retroactively because it impacts only the statutory damages available to plaintiffs—it does not change BIPA’s substantive standards of liability." *Gregg v. Central Transport LLC, Nos. 25-2185, 25-2761, 25-2762 (7th Cir. Apr. 1, 2026).* <https://www.courtlistener.com/opinion/10831566/john-gregg-v-central-transport-llc/#:~:text=We%20hold%20that%20this%20amendment%20applies,BIPA%E2%80%99s%20substantive%20standards%20of%20liability.>
193
+
194
+ [^stat-gipa-25-employment]: **410 ILCS 513/25** — "An employer, employment agency, labor organization, and licensing agency shall not directly or indirectly do any of the following: (1) solicit, request, require or purchase genetic testing or genetic information of a person or a family member of the person, or administer a genetic test to a person or a family member of the person as a condition of employment, preemployment application, labor organization membership, or licensure; (2) affect the terms, conditions, or privileges of employment, preemployment application, labor organization membership, or licensure, or terminate the employment, labor organization membership, or licensure of any person because of genetic testing or genetic information with respect to the employee or family member, or information about a request for or the receipt of genetic testing by such employee or family member of such employee; (3) limit, segregate, or classify employees in any way that would deprive or tend to deprive any employee of employment opportunities or otherwise adversely affect the status of the employee as an employee because of genetic testing or genetic information with respect to the employee or a family member, or information about a request for or the receipt of genetic testing or genetic information by such employee or family member of such employee; and (4) retaliate through discharge or in any other manner against any person alleging a violation of this Act or participating in any manner in a proceeding under this Act." *410 ILCS 513/25(c).* <https://www.ilga.gov/documents/legislation/ilcs/documents/041005130K25.htm>
195
+
196
+ [^stat-gipa-40-damages]: **410 ILCS 513/40** — "Any person aggrieved by a violation of this Act shall have a right of action in a State circuit court or as a supplemental claim in a federal district court against an offending party. A prevailing party may recover for each violation: (1) Against any party who negligently violates a provision of this Act, liquidated damages of $2,500 or actual damages, whichever is greater. (2) Against any party who intentionally or recklessly violates a provision of this Act, liquidated damages of $15,000 or actual damages, whichever is greater. (3) Reasonable attorney's fees and costs, including expert witness fees and other litigation expenses. (4) Such other relief, including an injunction, as the State or federal court may deem appropriate. (b) Article XL of the Illinois Insurance Code shall provide the exclusive remedy for violations of Section 30 by insurers." *410 ILCS 513/40(a)-(b).* <https://www.ilga.gov/documents/legislation/ilcs/documents/041005130K40.htm>
197
+
198
+ [^stat-gipa-10-definitions]: **410 ILCS 513/10** — "‘Genetic testing’ and ‘genetic test’ have the meaning ascribed to ‘genetic test’ under HIPAA, as specified in 45 CFR 160.103. ‘Genetic testing’ includes direct-to-consumer commercial genetic testing." *410 ILCS 513/10.* <https://www.ilga.gov/documents/legislation/ilcs/documents/041005130K10.htm>
199
+
200
+ [^stat-gipa-25-pay-benefit]: **410 ILCS 513/25(d)** — "An agreement between a person and an employer, prospective employer, employment agency, labor organization, or licensing agency, or its employees, agents, or members offering the person employment, labor organization membership, licensure, or any pay or benefit in return for taking a genetic test is prohibited." *410 ILCS 513/25(d).* <https://www.ilga.gov/documents/legislation/ilcs/documents/041005130K25.htm>
201
+
202
+ [^stat-gipa-25-wellness]: **410 ILCS 513/25(e)** — "An employer shall not use genetic information or genetic testing in furtherance of a workplace wellness program benefiting employees unless (1) health or genetic services are offered by the employer, (2) the employee provides written authorization in accordance with Section 30 of this Act, (3) only the employee or family member if the family member is receiving genetic services and the licensed health care professional or licensed genetic counselor involved in providing such services receive individually identifiable information concerning the results of such services, and (4) any individually identifiable information is only available for purposes of such services and shall not be disclosed to the employer except in aggregate terms that do not disclose the identity of specific employees. An employer shall not penalize an employee who does not disclose his or her genetic information or does not choose to participate in a program requiring disclosure of the employee's genetic information." *410 ILCS 513/25(e).* <https://www.ilga.gov/documents/legislation/ilcs/documents/041005130K25.htm>
203
+
204
+ [^stat-gipa-25-workers-comp]: **410 ILCS 513/25(f)** — "Nothing in this Act shall be construed to prohibit genetic testing of an employee who requests a genetic test and who provides written authorization, in accordance with Section 30 of this Act, from taking a genetic test for the purpose of initiating a workers' compensation claim under the Workers' Compensation Act." *410 ILCS 513/25(f).* <https://www.ilga.gov/documents/legislation/ilcs/documents/041005130K25.htm>
205
+
206
+ [^stat-gipa-25-toxic-monitoring]: **410 ILCS 513/25(i)** — "Nothing in this Act shall be construed to prohibit an employer from requesting or requiring genetic information to be used for genetic monitoring of the biological effects of toxic substances in the workplace, but only if (1) the employer provides written notice of the genetic monitoring to the employee; (2) the employee provides written authorization under Section 30 of this Act or the genetic monitoring is required by federal or State law; (3) the employee is informed of individual monitoring results; (4) the monitoring is in compliance with any federal genetic monitoring regulations or State genetic monitoring regulations under the authority of the federal Occupational Safety and Health Act of 1970; and (5) the employer, excluding any health care provider, health care professional, or health facility that is involved in the genetic monitoring program, receives the results of the monitoring only in aggregate terms that do not disclose the identity of specific employees." *410 ILCS 513/25(i).* <https://www.ilga.gov/documents/legislation/ilcs/documents/041005130K25.htm>
207
+
208
+ [^q7-stat-15b-consent]: **740 ILCS 14/15(b)** — "No private entity may collect, capture, purchase, receive through trade, or otherwise obtain a person's or a customer's biometric identifier or biometric information, unless it first: (1) informs the subject or the subject's legally authorized representative in writing that a biometric identifier or biometric information is being collected or stored; (2) informs the subject or the subject's legally authorized representative in writing of the specific purpose and length of term for which a biometric identifier or biometric information is being collected, stored, and used; and (3) receives a written release executed by the subject of the biometric identifier or biometric information or the subject's legally authorized representative." *740 ILCS 14/15(b).* <https://www.ilga.gov/documents/legislation/ilcs/documents/074000140K15.htm>
209
+
210
+ [^q7-stat-15a-destruction]: **740 ILCS 14/15(a)** — "establishing a retention schedule and guidelines for permanently destroying biometric identifiers and biometric information when the initial purpose for collecting or obtaining such identifiers or information has been satisfied or within 3 years of the individual's last interaction with the private entity, whichever occurs first" *740 ILCS 14/15(a).* <https://www.ilga.gov/documents/legislation/ilcs/documents/074000140K15.htm>
211
+
212
+ [^q7-stat-gipa-30-disclosure]: **410 ILCS 513/30** — "No person may disclose or be compelled to disclose the identity of any person upon whom a genetic test is performed or the results of a genetic test in a manner that permits identification of the subject of the test, except to the following persons: (1) The subject of the test or the subject's legally authorized representative. This paragraph does not create a duty or obligation under which a health care provider must notify the subject's spouse or legal guardian of the test results, and no such duty or obligation shall be implied. No civil liability or criminal sanction under this Act shall be imposed for any disclosure or nondisclosure of a test result to a spouse by a physician acting in good faith under this paragraph. For the purpose of any proceedings, civil or criminal, the good faith of any physician acting under this paragraph shall be presumed. (2) Any person designated in a specific written legally effective authorization for release of the test results executed by the subject of the test or the subject's legally authorized representative." *410 ILCS 513/30(a)(1)-(2).* <https://www.ilga.gov/documents/legislation/ilcs/documents/041005130K30.htm>
213
+
214
+ [^stat-pipa-10-notice]: **815 ILCS 530/10** — "Any data collector that owns or licenses personal information concerning an Illinois resident shall notify the resident at no charge that there has been a breach of the security of the system data following discovery or notification of the breach. The disclosure notification shall be made in the most expedient time possible and without unreasonable delay, consistent with any measures necessary to determine the scope of the breach and restore the reasonable integrity, security, and confidentiality of the data system." *815 ILCS 530/10(a).* <https://www.ilga.gov/documents/legislation/ilcs/documents/081505300K10.htm>
215
+
216
+ [^stat-pipa-5-breach]: **815 ILCS 530/5** — "‘Breach of the security of the system data’ or ‘breach’ means unauthorized acquisition of computerized data that compromises the security, confidentiality, or integrity of personal information maintained by the data collector." *815 ILCS 530/5.* <https://www.ilga.gov/documents/legislation/ilcs/documents/081505300K5.htm>
217
+
218
+ [^stat-pipa-10e-ag]: **815 ILCS 530/10(e)** — "Any data collector required to issue notice pursuant to this Section to more than 500 Illinois residents as a result of a single breach of the security system shall provide notice to the Attorney General of the breach, including: (A) A description of the nature of the breach of security or unauthorized acquisition or use. (B) The number of Illinois residents affected by such incident at the time of notification. (C) Any steps the data collector has taken or plans to take relating to the incident. Such notification must be made in the most expedient time possible and without unreasonable delay but in no event later than when the data collector provides notice to consumers pursuant to this Section. If the date of the breach is unknown at the time the notice is sent to the Attorney General, the data collector shall send the Attorney General the date of the breach as soon as possible. Upon receiving notification from a data collector of a breach of personal information, the Attorney General may publish the name of the data collector that suffered the breach, the types of personal information compromised in the breach, and the date range of the breach." *815 ILCS 530/10(e)(2).* <https://www.ilga.gov/documents/legislation/ilcs/documents/081505300K10.htm>
219
+
220
+ [^stat-pipa-20-icfa]: **815 ILCS 530/20** — "A violation of this Act constitutes an unlawful practice under the Consumer Fraud and Deceptive Business Practices Act." *815 ILCS 530/20.* <https://www.ilga.gov/documents/legislation/ilcs/documents/081505300K20.htm>
221
+
222
+ [^stat-pipa-5-personal-info]: **815 ILCS 530/5** — "‘Personal information’ means either of the following: (1) An individual'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 elements are not encrypted or redacted or are encrypted or redacted but the keys to unencrypt or unredact or otherwise read the name or data elements have been acquired without authorization through the breach of security: (A) Social Security number. (B) Driver's license number or State identification card number. (C) Account number or credit or debit card number, or an account number or credit card number in combination with any required security code, access code, or password that would permit access to an individual's financial account. (D) Medical information. (E) Health insurance information. (F) Unique biometric data generated from measurements or technical analysis of human body characteristics used by the owner or licensee to authenticate an individual, such as a fingerprint, retina or iris image, or other unique physical representation or digital representation of biometric data. (2) User name or email address, in combination with a password or security question and answer that would permit access to an online account, when either the user name or email address or password or security question and answer are not encrypted or redacted or are encrypted or redacted but the keys to unencrypt or unredact or otherwise read the data elements have been obtained through the breach of security. ‘Personal information’ does not include publicly available information that is lawfully made available to the general public from federal, State, or local government records." *815 ILCS 530/5.* <https://www.ilga.gov/documents/legislation/ilcs/documents/081505300K5.htm>
223
+
224
+ [^stat-pipa-10-credential-notice]: **815 ILCS 530/10(a)(2)** — "With respect to personal information defined in Section 5 in paragraph (2) of the definition of ‘personal information’, notice may be provided in electronic or other form directing the Illinois resident whose personal information has been breached to promptly change his or her user name or password and security question or answer, as applicable, or to take other steps appropriate to protect all online accounts for which the resident uses the same user name or email address and password or security question and answer." *815 ILCS 530/10(a)(2).* <https://www.ilga.gov/documents/legislation/ilcs/documents/081505300K10.htm>
225
+
226
+ [^stat-pipa-15-waiver]: **815 ILCS 530/15** — "Any waiver of the provisions of this Act is contrary to public policy and is void and unenforceable." *815 ILCS 530/15.* <https://www.ilga.gov/documents/legislation/ilcs/documents/081505300K15.htm>
227
+
228
+ [^stat-icfa-10a-actual]: **815 ILCS 505/10a** — "Any person who suffers actual damage as a result of a violation of this Act committed by any other person may bring an action against such person." *815 ILCS 505/10a(a).* <https://www.ilga.gov/documents/legislation/ilcs/documents/081505050K10a.htm>
229
+
230
+ [^q9-stat-15d-disclosure]: **740 ILCS 14/15(d)** — "No private entity in possession of a biometric identifier or biometric information may disclose, redisclose, or otherwise disseminate a person's or a customer's biometric identifier or biometric information unless: (1) the subject of the biometric identifier or biometric information or the subject's legally authorized representative consents to the disclosure or redisclosure; (2) the disclosure or redisclosure completes a financial transaction requested or authorized by the subject of the biometric identifier or the biometric information or the subject's legally authorized representative; (3) the disclosure or redisclosure is required by State or federal law or municipal ordinance; or (4) the disclosure is required pursuant to a valid warrant or subpoena issued by a court of competent jurisdiction." *740 ILCS 14/15(d).* <https://www.ilga.gov/documents/legislation/ilcs/documents/074000140K15.htm>
231
+
232
+ [^stat-pipa-10b-vendor]: **815 ILCS 530/10(b)** — "Any data collector that maintains or stores, but does not own or license, computerized data that includes personal information that the data collector does not own or license shall notify the owner or licensee of the information of any breach of the security of the data immediately following discovery, if the personal information was, or is reasonably believed to have been, acquired by an unauthorized person. In addition to providing such notification to the owner or licensee, the data collector shall cooperate with the owner or licensee in matters relating to the breach. That cooperation shall include, but need not be limited to, (i) informing the owner or licensee of the breach, including giving notice of the date or approximate date of the breach and the nature of the breach, and (ii) informing the owner or licensee of any steps the data collector has taken or plans to take relating to the breach. The data collector's cooperation shall not, however, be deemed to require either the disclosure of confidential business information or trade secrets or the notification of an Illinois resident who may have been affected by the breach." *815 ILCS 530/10(b).* <https://www.ilga.gov/documents/legislation/ilcs/documents/081505300K10.htm>
233
+
234
+ [^q9-stat-20c-single-disclosure]: **740 ILCS 14/20(c)** — "For purposes of subsection (d) of Section 15, a private entity that, in more than one instance, discloses, rediscloses, or otherwise disseminates the same biometric identifier or biometric information from the same person to the same recipient using the same method of collection in violation of subsection (d) of Section 15 has committed a single violation of subsection (d) of Section 15 for which the aggrieved person is entitled to, at most, one recovery under this Section regardless of the number of times the private entity disclosed, redisclosed, or otherwise disseminated the same biometric identifier or biometric information of the same person to the same recipient." *740 ILCS 14/20(c), added by P.A. 103-0769 (eff. Aug. 2, 2024).* <https://www.ilga.gov/documents/legislation/ilcs/documents/074000140K20.htm>
235
+
236
+ [^fed-glba-safeguards]: **GLBA Safeguards Rule** — "Requiring your service providers by contract to implement and maintain such safeguards" *16 C.F.R. § 314.4(f)(2).* <https://www.law.cornell.edu/cfr/text/16/314.4#:~:text=Requiring%20your%20service%20providers%20by,implement%20and%20maintain%20such%20safeguards>
237
+
238
+ [^fed-hipaa-baa]: **HIPAA Business Associate Contracts** — "A contract between the covered entity and a business associate must: (i) Establish the permitted and required uses and disclosures of protected health information by the business associate. The contract may not authorize the business associate to use or further disclose the information in a manner that would violate the requirements of this subpart, if done by the covered entity, except that: (A) The contract may permit the business associate to use and disclose protected health information for the proper management and administration of the business associate, as provided in paragraph (e)(4) of this section; and (B) The contract may permit the business associate to provide data aggregation services relating to the health care operations of the covered entity. (ii) Provide that the business associate will: (A) Not use or further disclose the information other than as permitted or required by the contract or as required by law; (B) Use appropriate safeguards and comply, where applicable, with subpart C of this part with respect to electronic protected health information, to prevent use or disclosure of the information other than as provided for by its contract;" *45 C.F.R. § 164.504(e)(2).* <https://www.law.cornell.edu/cfr/text/45/164.504#:~:text=A%20contract%20between%20the%20covered,provided%20for%20by%20its%20contract%3B>