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,174 @@
1
+ ---
2
+ jurisdiction: "New Mexico"
3
+ slug: new-mexico
4
+ countryCode: US
5
+ snapshotAsOf: "2026-06-19"
6
+ lastReviewed: "2026-06-11"
7
+ canonicalUrl: https://openagreements.org/practice-guides/privacy/us/new-mexico
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/new-mexico · **Snapshot as of:** 2026-06-19 · License: CC BY 4.0 · © openagreements.org
19
+
20
+ # New Mexico Consumer Privacy Law[^about]
21
+
22
+ New Mexico has no comprehensive consumer-privacy statute — the 2026 omnibus bill died despite aggregator claims it was enacted. The operative framework is the Data Breach Notification Act (NMSA 1978, §§ 57-12C-1 to -12), the Unfair Practices Act, and the federal overlay.
23
+
24
+
25
+ ## At a glance
26
+
27
+ | Question | New Mexico |
28
+ | --- | --- |
29
+ | **Law coverage** | No comprehensive law |
30
+ | **Summary** | New Mexico has not enacted a comprehensive consumer-privacy law — the Consumer Information and Data Protection Act (HB 214) died in the 2026 session, and aggregator pages reporting a July 1, 2026 effective date are describing a dead bill. What governs today is the Data Breach Notification Act (45-day breach notice, reasonable-security, disposal, and vendor-contract duties) plus the Unfair Practices Act, which can create private damages exposure when a covered privacy-policy or breach-response misstatement causes money or property loss. |
31
+ | **Main law** | Data Breach Notification Act, NMSA 1978, §§ 57-12C-1 to -12, plus the Unfair Practices Act, NMSA 1978, §§ 57-12-1 to -26 — New Mexico has no comprehensive consumer-privacy statute |
32
+ | **Privacy policy required?** | No New Mexico statute mandates a consumer privacy policy or fixes its contents; what you publish is policed by FTC Act § 5 and the Unfair Practices Act, so a knowing policy misstatement tied to a covered transaction can create private exposure if a person loses money or property |
33
+ | **Who does it cover?** | Any person that owns or licenses personal identifying information of New Mexico residents — no revenue or volume threshold; persons subject to GLBA or HIPAA are exempt from the breach act entirely |
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 Data Breach Notification Act — enforcement is Attorney General-only; but the Unfair Practices Act gives a private action to a person who loses money or property from an unlawful practice, with a $100 statutory floor, possible treble damages for willful conduct, mandatory fee-shifting, and class actions |
39
+ | **Who enforces it?** | New Mexico Attorney General (New Mexico Department of Justice) |
40
+
41
+ ## Which privacy laws apply to your business in New Mexico? {#which-privacy-laws-apply}
42
+
43
+ **Short answer.** There is no comprehensive New Mexico consumer-privacy law. The operative state statute is the Data Breach Notification Act, which applies to any person that owns or licenses personal identifying information of New Mexico residents — with no revenue or consumer-volume threshold — and imposes reasonable-security [^q1-dbna-security-duty], disposal [^q1-dbna-disposal-duty], vendor-contract [^q1-dbna-vendor-duty], and breach-notification duties [^q1-dbna-notice-duty]. Alongside it sits the Unfair Practices Act, the state's general consumer-protection statute, which makes unfair or deceptive and unconscionable trade practices unlawful and can reach data-practices misstatements tied to covered trade or commerce [^q1-upa-prohibition]. One unusual carve-out matters at the threshold: the breach act appears not to apply to a person subject to the federal Gramm-Leach-Bliley Act or HIPAA, but mixed lines of business should confirm coverage before treating the entire operation as outside the act [^q1-dbna-exemptions].
44
+
45
+ A correction is needed before anything else, because the secondary literature on New Mexico is contaminated. Several aggregator and compliance-vendor pages — many tracing back to the same database summaries — state that New Mexico enacted a comprehensive statute called the Consumer Information and Data Protection Act with an effective date of July 1, 2026. The primary legislative record refutes this. House Bill 214 (2026 Regular Session), which carried that name, is listed by the Legislature as *Died (API.)* and *Action Postponed Indefinitely* [^q1-hb214-status]. The July 1, 2026 date circulating online is simply an effective-date clause inside the dead bill's own text [^q1-hb214-effective-dates]. Had it passed, HB 214 would have created a controller-and-processor regime for businesses processing the personal data of at least 35,000 consumers, or 10,000 consumers plus more than 20% of gross revenue from selling personal data [^q1-hb214-scope]. It did not pass, nothing comparable is pending, and the Legislature does not convene again in regular session until January 2027. A compliance calendar built off the aggregator claim is preparing for a statute that does not exist.
46
+
47
+ Because no omnibus law exists, New Mexico residents have no general state-law rights to access, delete, or correct their personal data, no right to opt out of its sale, and no recognized universal opt-out signal; businesses face no notice-at-collection, consent, or data-protection-assessment duties under state law. What fills the gap is a layered framework. The Data Breach Notification Act supplies the statewide data-security spine. The Unfair Practices Act supplies the enforcement teeth for covered misrepresentation — including, unusually, a private right of action where a person loses money or property from the unlawful practice, covered in the consumer-lawsuit question below. The rest 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 the Children's Online Privacy Protection Act governs services directed to children under 13. This note is written to stay durable: if New Mexico enacts an omnibus law in a future session, a program built to this overlay upgrades rather than restarts.
48
+
49
+ ## What must your New Mexico privacy policy contain? {#privacy-policy-contents}
50
+
51
+ **Short answer.** No New Mexico statute requires a general consumer privacy policy or fixes what it must say. The binding rule is instead that whatever you publish has to be true. Under Section 5 of the FTC Act, a policy that misstates how you collect, use, share, retain, or secure data is a deceptive practice [^q2-ftc5-deceptive], and the Unfair Practices Act reaches the same conduct as a false or misleading written statement knowingly made in connection with the sale of goods or services [^q2-upa-deceptive-def]. Where a sectoral regime applies, that regime supplies the contents — a HIPAA covered entity, for example, must give individuals a notice of the uses and disclosures of their protected health information and of their rights and the entity's duties [^q2-hipaa-notice].
52
+
53
+ What makes New Mexico different from most no-omnibus states is the sharpness of the misrepresentation exposure. The Unfair Practices Act's definition of an unfair or deceptive trade practice expressly includes failing to state a material fact if doing so deceives or tends to deceive [^q2-upa-omission], and its private remedy reaches a person who loses money or property as a result of an unlawful practice [^q2-upa-private-remedy]. A privacy policy is a written statement a New Mexico claimant may test when the statement is knowingly made in connection with a covered sale, lease, rental, loan, credit extension, or debt collection, and when the claimant can tie the misstatement to money or property loss. The knowing-falsity element is a real pleading hurdle for plaintiffs, but the drafting lesson is the same: build the policy from the federal and sectoral overlay that actually binds you — GLBA privacy notices for financial institutions, the HIPAA notice for covered entities, a COPPA notice for child-directed services — describe your actual practices accurately, and then honor what you wrote.
54
+
55
+ One breach-act provision feeds directly into policy drafting. A person that maintains its own notice procedures as part of an information security policy, consistent with the act's timing requirements, is deemed compliant with the breach-notification requirements if it follows those procedures [^q2-dbna-own-procedures].
56
+
57
+ > [!CAUTION]
58
+ > **Drafting note.**
59
+ >
60
+ > An incident-response commitment in a privacy policy cuts both ways in New Mexico. A policy promising notification on a stated timeline can qualify as your own notice procedure and earn the statutory safe harbor if it is consistent with the act's timing requirements [^q2-dbna-own-procedures] — but it is also a written representation under the Unfair Practices Act, so promising faster notice than you can deliver can create deception exposure if the UPA's transaction and loss requirements are met [^q2-upa-deceptive-def]. Commit only to timelines your incident-response plan can actually meet.
61
+
62
+ ## What must your contracts with service providers say? {#vendor-contracts}
63
+
64
+ **Short answer.** New Mexico has one mandatory vendor-contract clause, and it is statutory, not best practice. A person that discloses personal identifying information of a New Mexico resident to a service provider under a contract must require, by contract, that the service provider implement and maintain reasonable security procedures and practices appropriate to the nature of the information [^q3-dbna-flowdown]. The duty attaches to any vendor that receives, stores, maintains, licenses, processes, or is otherwise permitted access to personal identifying information through its services [^q3-service-provider-def].
65
+
66
+ This is a narrower mandate than an omnibus-state data processing agreement — it requires a security flow-down clause, not processing instructions, deletion duties, audit rights, or subprocessor terms. But it is a real statutory floor: a New Mexico-facing vendor agreement that shares Social Security numbers, driver's license or government-ID numbers, payment-card credentials, or biometric data without a written reasonable-security commitment from the vendor violates the act. Where a federal sectoral regime applies, it supplies the fuller contracting obligations — the GLBA Safeguards Rule requires financial institutions to oversee service providers and bind them by contract to maintain appropriate safeguards [^q3-glba-safeguards], and HIPAA requires a business-associate agreement with mandatory data-protection, breach-reporting, and subcontractor flow-down terms before protected health information changes hands [^q3-hipaa-baa]. For everyone else, the prudent template still carries the omnibus-style protections forward — processing limited to documented instructions, confidentiality, breach notification back to your business, and return or deletion at the end of the engagement — because they cost little to include and your vendor stack rarely stops at the New Mexico border. The statutory minimum, though, is the reasonable-security clause, and it belongs in every New Mexico-facing services agreement that touches personal identifying information.
67
+
68
+ ## What data security and disposal duties does New Mexico impose? {#security-and-disposal}
69
+
70
+ **Short answer.** Two standing duties apply to any person that owns or licenses personal identifying information of New Mexico residents, breach or no breach. First, a reasonable-security duty: implement and maintain reasonable security procedures and practices appropriate to the nature of the information [^q4-dbna-security]. Second, a disposal duty: when records containing personal identifying information are no longer reasonably needed for business purposes, arrange for proper disposal — shredding, erasing, or otherwise modifying the information to make it unreadable or undecipherable [^q4-dbna-disposal].
71
+
72
+ Both duties are principles-based — the statute prescribes no specific controls, certifications, or frameworks, and no New Mexico regulator has issued implementing rules. The reasonableness standard scales with the sensitivity of the data: practices appropriate for marketing lists will not be appropriate for files of Social Security numbers or biometric records. Note a scope nuance in the text: the disposal duty speaks to *records* generally [^q4-dbna-disposal], while the act's breach-notification trigger is limited to computerized data — so paper files are inside the disposal and security duties even though a purely paper-record compromise does not trigger the notification provisions. The GLBA/HIPAA carve-out appears broad for a person subject to those federal regimes, but confirm coverage for mixed lines of business before treating every security and disposal function as outside the act [^q4-dbna-exemptions]. For everyone else, the practical program is a written security policy matched to the data you actually hold, a retention schedule that triggers disposal when business need ends, and documentation of both, since reasonableness is judged after the incident, with hindsight.
73
+
74
+ ## What must you do after a data breach in New Mexico? {#breach-notification}
75
+
76
+ **Short answer.** A person that owns or licenses personal identifying information of New Mexico residents must notify each resident whose information is reasonably believed to have been subject to a security breach — in the most expedient time possible and no later than 45 calendar days after discovery [^q5-dbna-notice-duty]. Notice is excused if an appropriate investigation determines the breach does not give rise to a significant risk of identity theft or fraud [^q5-dbna-risk-of-harm]. If a single breach requires notice to more than 1,000 New Mexico residents, you must also notify the office of the attorney general and the nationwide consumer reporting agencies on the same 45-day clock [^q5-dbna-ag-cra]. And a vendor holding data it does not own owes the data's owner notice of any breach within the same 45 days [^q5-dbna-maintainer-notice].
77
+
78
+ Start with what counts. A *security breach* is the unauthorized acquisition of unencrypted computerized data — or of encrypted data together with the key — that compromises personal identifying information; a good-faith acquisition by an employee or agent for a legitimate business purpose is carved out, so long as the information goes no further [^q5-dbna-breach-def]. The trigger is acquisition, not mere access, and it reaches only computerized data — a lost box of paper files does not start the notice clock. *Personal identifying information* means a resident's name combined with an unprotected Social Security number, driver's license number, government-issued ID number, financial-account or card number with its access credentials, or biometric data — and excludes information lawfully available from public sources [^q5-dbna-pii-def]. Encryption and redaction are built-in safe harbors: data elements that are encrypted or otherwise rendered unusable fall outside the definition unless the decryption key was compromised too.
79
+
80
+ The notice itself has statutorily fixed contents — your name and contact information, the types of information involved, the date or date range of the breach, a general description of the incident, the consumer reporting agencies' toll-free numbers and addresses, advice to review account statements and credit reports, and advice about the recipient's federal Fair Credit Reporting Act rights [^q5-dbna-contents]. Send it by U.S. mail, electronic notice where the statute allows, or substitute notice when the cost exceeds $100,000, the number of residents exceeds 50,000, or sufficient contact information is unavailable; substitute notice requires email where available, conspicuous website posting where the person maintains a website, and written notice to the attorney general and major New Mexico media outlets [^q5-dbna-methods]. When AG notice is triggered at the 1,000-resident threshold, you must also tell the attorney general how many residents were notified and provide a copy of the resident notice within the 45-day window [^q5-dbna-ag-cra]. Two timing escape valves exist: notification may be delayed if law enforcement determines it would impede a criminal investigation, or as necessary to determine the breach's scope and restore the system's integrity [^q5-dbna-delay]. Three practical notes round out the plan. First, 45 days is a ceiling, not a target — the operative command is the most expedient time possible. Second, the risk-of-harm determination that excuses notice must follow an *appropriate investigation* [^q5-dbna-risk-of-harm], so document the analysis contemporaneously. Third, the GLBA/HIPAA carve-out appears broad for a person subject to those federal regimes, but confirm coverage for mixed lines of business before treating all notification duties as displaced by federal breach rules [^q5-dbna-exemptions].
81
+
82
+ ## Who enforces these laws — and can consumers sue? {#consumer-lawsuit}
83
+
84
+ **Short answer.** The Data Breach Notification Act is enforced exclusively by the attorney general, who may sue on behalf of individuals and in the name of the state, with courts empowered to issue injunctions and award damages for actual costs or losses, including consequential financial losses [^q6-dbna-ag-enforcement]; for knowing or reckless violations, the court may add a civil penalty of the greater of $25,000 or, for failed notification, $10 per instance up to $150,000 [^q6-dbna-civil-penalty]. The act gives consumers no private right of action — but the Unfair Practices Act does: a person who loses money or property as a result of an unlawful deceptive or unconscionable practice may sue for actual damages or $100, whichever is greater, with up to treble damages for willful conduct and mandatory attorney fees for a prevailing complainant [^q6-upa-private-remedy]. The attorney general polices the Unfair Practices Act as well [^q6-upa-ag-action].
85
+
86
+ On the breach-act side, the enforcement posture is public and penalty-capped. The attorney general acts on a reasonable belief that a violation occurred, and the remedies run from injunction through actual-loss damages to the knowing-or-reckless civil penalty [^q6-dbna-ag-enforcement]. The penalty arithmetic rewards notification even when late: the per-instance exposure attaches to *failed* notification, capped at $150,000 [^q6-dbna-civil-penalty] — small against omnibus-state penalty schedules, but it stacks with the reputational and litigation costs that follow any publicized AG action.
87
+
88
+ The Unfair Practices Act is where private exposure lives. The private remedy carries a $100 statutory floor for a person who suffered money or property loss, discretionary treble damages (or $300 if greater) for willful practices, and one-way fee-shifting in the complainant's favor [^q6-upa-private-remedy] — and the statute expressly contemplates class actions, with class members recovering their actual damages [^q6-upa-class-action]. Applied to privacy, the theory is strongest when a privacy policy or breach-response promise is a false or misleading written statement knowingly made in connection with the sale, lease, rental, or loan of goods or services, an extension of credit, or debt collection [^q6-upa-deceptive-def], and the claimant can tie the misstatement to money or property loss [^q6-upa-private-remedy]. The knowing-falsity element — the main defense-side hurdle — does not require intent to deceive, but it does require a knowing representation [^q6-upa-intent]. On the public side, the attorney general may sue whenever proceedings would be in the public interest, seeking temporary or permanent injunctions and restitution without posting bond [^q6-upa-ag-action], plus a civil penalty of up to $5,000 per violation for willful conduct [^q6-upa-civil-penalty]. One enforcement claim circulating online deserves a final correction: there is no new comprehensive-privacy enforcement regime taking effect July 1, 2026 — that regime would have come from House Bill 214, which the Legislature lists as *Died (API.)* and *Action Postponed Indefinitely* [^q6-hb214-status]; July 1, 2026 was just an effective date in the dead bill text [^q6-hb214-effective-dates]. Until the Legislature acts, the enforcement map for New Mexico privacy is exactly this: AG-only under the breach act, and AG plus private UPA exposure where the statute's transaction, knowledge, and loss elements are met.
89
+
90
+ [^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 New Mexico. This article synthesizes New Mexico primary law and is not legal advice from a New Mexico-admitted attorney. This article is for informational purposes only and does not create an attorney-client relationship.
91
+
92
+ [^q1-dbna-security-duty]: **NMSA 1978, § 57-12C-4** — "A person that owns or licenses personal identifying information of a New Mexico resident shall implement and maintain reasonable security procedures and practices appropriate to the nature of the information to protect the personal identifying information from unauthorized access, destruction, use, modification or disclosure." *NMSA 1978, § 57-12C-4.* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
93
+
94
+ [^q1-dbna-disposal-duty]: **NMSA 1978, § 57-12C-3** — "A person that owns or licenses records containing personal identifying information of a New Mexico resident shall arrange for proper disposal of the records when they are no longer reasonably needed for business purposes." *NMSA 1978, § 57-12C-3.* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
95
+
96
+ [^q1-dbna-vendor-duty]: **NMSA 1978, § 57-12C-5** — "A person that discloses personal identifying information of a New Mexico resident pursuant to a contract with a service provider shall require by contract that the service provider implement and maintain reasonable security procedures and practices appropriate to the nature of the personal identifying information and to protect it from unauthorized access, destruction, use, modification or disclosure." *NMSA 1978, § 57-12C-5.* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
97
+
98
+ [^q1-dbna-notice-duty]: **NMSA 1978, § 57-12C-6(A)** — "Except as provided in Subsection C of this section, a person that owns or licenses elements that include personal identifying information of a New Mexico resident shall provide notification to each New Mexico resident whose personal identifying information is reasonably believed to have been subject to a security breach. Notification shall be made in the most expedient time possible, but not later than fortyfive calendar days following discovery of the security breach, except as provided in Section 9 [57-12C-9 NMSA 1978] of the Data Breach Notification Act." *NMSA 1978, § 57-12C-6(A).* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
99
+
100
+ [^q1-upa-prohibition]: **NMSA 1978, § 57-12-3** — "Unfair or deceptive trade practices and unconscionable trade practices in the conduct of any trade or commerce are unlawful." *NMSA 1978, § 57-12-3.* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
101
+
102
+ [^q1-dbna-exemptions]: **NMSA 1978, § 57-12C-8** — "The provisions of the Data Breach Notification Act shall not apply to a person subject to the federal Gramm-Leach-Bliley Act or the federal Health Insurance Portability and Accountability Act of 1996." *NMSA 1978, § 57-12C-8.* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
103
+
104
+ [^q1-hb214-status]: **New Mexico Legislature HB 214 (2026 Regular Session)** — "Current Location Died (API.)" *New Mexico Legislature, HB 214 (2026 Regular Session).* <https://www.nmlegis.gov/Legislation/Legislation?chamber=H&legType=B&legNo=214&year=26>
105
+
106
+ [^q1-hb214-effective-dates]: **HB 214 (2026), § 16** — "SECTION 16. EFFECTIVE DATES.-- A. The effective date of the provisions of Sections 1, 2 and 13 through 15 of this act is July 1, 2026. B. The effective date of the provisions of Sections 3 through 12 of this act is July 1, 2027." *HB 214 (2026), § 16.* <https://www.nmlegis.gov/Sessions/26%20Regular/bills/house/HB0214.HTML>
107
+
108
+ [^q1-hb214-scope]: **HB 214 (2026), § 3(A)** — "SECTION 3. [ NEW MATERIAL ] SCOPE OF ACT--EXEMPTIONS.-- A. The Consumer Information and Data Protection Act applies to persons that conduct business in New Mexico and persons that produce products or services that are targeted to residents of New Mexico and that during the preceding calendar year did any of the following: (1) controlled or processed the personal data of at least thirty-five thousand consumers, excluding personal data controlled or processed solely for the purpose of completing a payment transaction; or (2) controlled or processed the personal data of at least ten thousand consumers and derived more than twenty percent of its gross revenue from the sale of personal data." *HB 214 (2026), § 3(A).* <https://www.nmlegis.gov/Sessions/26%20Regular/bills/house/HB0214.HTML>
109
+
110
+ [^q2-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.>
111
+
112
+ [^q2-upa-deceptive-def]: **NMSA 1978, § 57-12-2(D)** — "‘unfair or deceptive trade practice’ means an act specifically declared unlawful pursuant to the Unfair Practices Act, a false or misleading oral or written statement, visual description or other representation of any kind knowingly made in connection with the sale, lease, rental or loan of goods or services or in the extension of credit or in the collection of debts by a person in the regular course of the person's trade or commerce, that may, tends to or does deceive or mislead any person" *NMSA 1978, § 57-12-2(D).* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
113
+
114
+ [^q2-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>
115
+
116
+ [^q2-upa-omission]: **NMSA 1978, § 57-12-2(D)(14)** — "(14) using exaggeration, innuendo or ambiguity as to a material fact or failing to state a material fact if doing so deceives or tends to deceive;" *NMSA 1978, § 57-12-2(D)(14).* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
117
+
118
+ [^q2-upa-private-remedy]: **NMSA 1978, § 57-12-10(B), (C)** — "Any person who suffers any loss of money or property, real or personal, as a result of any employment by another person of a method, act or practice declared unlawful by the Unfair Practices Act may bring an action to recover actual damages or the sum of one hundred dollars ($100), whichever is greater. Where the trier of fact finds that the party charged with an unfair or deceptive trade practice or an unconscionable trade practice has willfully engaged in the trade practice, the court may award up to three times actual damages or three hundred dollars ($300), whichever is greater, to the party complaining of the practice. C. The court shall award attorney fees and costs to the party complaining of an unfair or deceptive trade practice or unconscionable trade practice if the party prevails." *NMSA 1978, § 57-12-10(B), (C).* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
119
+
120
+ [^q2-dbna-own-procedures]: **NMSA 1978, § 57-12C-6(F)** — "A person that maintains its own notice procedures as part of an information security policy for the treatment of personal identifying information, and whose procedures are otherwise consistent with the timing requirements of this section, is deemed to be in compliance with the notice requirements of this section if the person notifies affected consumers in accordance with its policies in the event of a security breach." *NMSA 1978, § 57-12C-6(F).* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
121
+
122
+ [^q3-dbna-flowdown]: **NMSA 1978, § 57-12C-5** — "A person that discloses personal identifying information of a New Mexico resident pursuant to a contract with a service provider shall require by contract that the service provider implement and maintain reasonable security procedures and practices appropriate to the nature of the personal identifying information and to protect it from unauthorized access, destruction, use, modification or disclosure." *NMSA 1978, § 57-12C-5.* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
123
+
124
+ [^q3-service-provider-def]: **NMSA 1978, § 57-12C-2(E)** — "‘service provider’ means any person that receives, stores, maintains, licenses, processes or otherwise is permitted access to personal identifying information through its provision of services directly to a person that is subject to regulation." *NMSA 1978, § 57-12C-2(E).* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
125
+
126
+ [^q3-glba-safeguards]: **GLBA Safeguards Rule** — "(f) Oversee service providers, by: (1) Taking reasonable steps to select and retain service providers that are capable of maintaining appropriate safeguards for the customer information at issue; (2) Requiring your service providers by contract to implement and maintain such safeguards; and (3) Periodically assessing your service providers based on the risk they present and the continued adequacy of their safeguards." *16 C.F.R. § 314.4(f).* <https://www.law.cornell.edu/cfr/text/16/314.4#:~:text=(f)%20Oversee%20service%20providers%2C%20by%3A,continued%20adequacy%20of%20their%20safeguards.>
127
+
128
+ [^q3-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; (C) Report to the covered entity any use or disclosure of the information not provided for by its contract of which it becomes aware, including breaches of unsecured protected health information as required by § 164.410; (D) In accordance with § 164.502(e)(1)(ii), ensure that any subcontractors that create, receive, maintain, or transmit protected health information on behalf of the business associate agree to the same restrictions and conditions that apply to the business associate with respect to such information;" *45 C.F.R. § 164.504(e)(2)(i)-(ii)(D).* <https://www.law.cornell.edu/cfr/text/45/164.504#:~:text=A%20contract%20between%20the%20covered,with%20respect%20to%20such%20information%3B>
129
+
130
+ [^q4-dbna-security]: **NMSA 1978, § 57-12C-4** — "A person that owns or licenses personal identifying information of a New Mexico resident shall implement and maintain reasonable security procedures and practices appropriate to the nature of the information to protect the personal identifying information from unauthorized access, destruction, use, modification or disclosure." *NMSA 1978, § 57-12C-4.* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
131
+
132
+ [^q4-dbna-disposal]: **NMSA 1978, § 57-12C-3** — "A person that owns or licenses records containing personal identifying information of a New Mexico resident shall arrange for proper disposal of the records when they are no longer reasonably needed for business purposes. As used in this section, ‘proper disposal’ means shredding, erasing or otherwise modifying the personal identifying information contained in the records to make the personal identifying information unreadable or undecipherable." *NMSA 1978, § 57-12C-3.* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
133
+
134
+ [^q4-dbna-exemptions]: **NMSA 1978, § 57-12C-8** — "The provisions of the Data Breach Notification Act shall not apply to a person subject to the federal Gramm-Leach-Bliley Act or the federal Health Insurance Portability and Accountability Act of 1996." *NMSA 1978, § 57-12C-8.* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
135
+
136
+ [^q5-dbna-notice-duty]: **NMSA 1978, § 57-12C-6(A)** — "Except as provided in Subsection C of this section, a person that owns or licenses elements that include personal identifying information of a New Mexico resident shall provide notification to each New Mexico resident whose personal identifying information is reasonably believed to have been subject to a security breach. Notification shall be made in the most expedient time possible, but not later than fortyfive calendar days following discovery of the security breach, except as provided in Section 9 [57-12C-9 NMSA 1978] of the Data Breach Notification Act." *NMSA 1978, § 57-12C-6(A).* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
137
+
138
+ [^q5-dbna-risk-of-harm]: **NMSA 1978, § 57-12C-6(B)** — "Notwithstanding Subsection A of this section, notification to affected New Mexico residents is not required if, after an appropriate investigation, the person determines that the security breach does not give rise to a significant risk of identity theft or fraud." *NMSA 1978, § 57-12C-6(B).* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
139
+
140
+ [^q5-dbna-ag-cra]: **NMSA 1978, § 57-12C-10** — "A person that is required to issue notification of a security breach pursuant to the Data Breach Notification Act to more than one thousand New Mexico residents as a result of a single security breach shall notify the office of the attorney general and major consumer reporting agencies that compile and maintain files on consumers on a nationwide basis, as defined in 15 U.S.C. Section 1681a(p), of the security breach in the most expedient time possible, and no later than forty-five calendar days, except as provided in Section 9 [57-12C-9 NMSA 1978] of the Data Breach Notification Act. A person required to notify the attorney general and consumer reporting agencies pursuant to this section shall notify the attorney general of the number of New Mexico residents that received notification pursuant to Section 6 of that act [57-12C-6 NMSA 1978] and shall provide a copy of the notification that was sent to affected residents within forty-five calendar days following discovery of the security breach, except as provided in Section 9 of the Data Breach Notification Act." *NMSA 1978, § 57-12C-10.* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
141
+
142
+ [^q5-dbna-maintainer-notice]: **NMSA 1978, § 57-12C-6(C)** — "Any person that is licensed to maintain or possess computerized data containing personal identifying information of a New Mexico resident that the person does not own or license shall notify the owner or licensee of the information of any security breach in the most expedient time possible, but not later than forty-five calendar days following discovery of the breach, except as provided in Section 9 of the Data Breach Notification Act; provided that notification to the owner or licensee of the information is not required if, after an appropriate investigation, the person determines that the security breach does not give rise to a significant risk of identity theft or fraud." *NMSA 1978, § 57-12C-6(C).* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
143
+
144
+ [^q5-dbna-breach-def]: **NMSA 1978, § 57-12C-2(D)** — "‘security breach’ means the unauthorized acquisition of unencrypted computerized data, or of encrypted computerized data and the confidential process or key used to decrypt the encrypted computerized data, that compromises the security, confidentiality or integrity of personal identifying information maintained by a person. ‘Security breach’ does not include the good-faith acquisition of personal identifying information by an employee or agent of a person for a legitimate business purpose of the person; provided that the personal identifying information is not subject to further unauthorized disclosure" *NMSA 1978, § 57-12C-2(D).* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
145
+
146
+ [^q5-dbna-pii-def]: **NMSA 1978, § 57-12C-2(C)** — "‘personal identifying information’: (1) means an individual's first name or first initial and last name in combination with one or more of the following data elements that relate to the individual, when the data elements are not protected through encryption or redaction or otherwise rendered unreadable or unusable: (a) social security number; (b) driver's license number; (c) government-issued identification number; (d) account number, credit card number or debit card number in combination with any required security code, access code or password that would permit access to a person's financial account; or (e) biometric data; and (2) does not mean information that is lawfully obtained from publicly available sources or from federal, state or local government records lawfully made available to the general public;" *NMSA 1978, § 57-12C-2(C).* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
147
+
148
+ [^q5-dbna-contents]: **NMSA 1978, § 57-12C-7** — "Notification required pursuant to Subsection A of Section 6 [57-12C-6 NMSA 1978] of the Data Breach Notification Act shall contain: A. the name and contact information of the notifying person; B. a list of the types of personal identifying information that are reasonably believed to have been the subject of a security breach, if known; C. the date of the security breach, the estimated date of the breach or the range of dates within which the security breach occurred, if known; D. a general description of the security breach incident; E. the toll-free telephone numbers and addresses of the major consumer reporting agencies; F. advice that directs the recipient to review personal account statements and credit reports, as applicable, to detect errors resulting from the security breach; and G. advice that informs the recipient of the notification of the recipient's rights pursuant to the federal Fair Credit Reporting." *NMSA 1978, § 57-12C-7.* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
149
+
150
+ [^q5-dbna-methods]: **NMSA 1978, § 57-12C-6(D), (E)** — "D. A person required to provide notification of a security breach pursuant to Subsection A of this section shall provide that notification by: (1) United States mail; (2) electronic notification, if the person required to make the notification primarily communicates with the New Mexico resident by electronic means or if the notice provided is consistent with the requirements of 15 U.S.C. Section 7001; or (3) a substitute notification, if the person demonstrates that: (a) the cost of providing notification would exceed one hundred thousand dollars ($100,000); (b) the number of residents to be notified exceeds fifty thousand; or (c) the person does not have on record a physical address or sufficient contact information for the residents that the person or business is required to notify. E. Substitute notification pursuant to Paragraph (3) of Subsection D of this section shall consist of: (1) sending electronic notification to the email address of those residents for whom the person has a valid email address; (2) posting notification of the security breach in a conspicuous location on the website of the person required to provide notification if the person maintains a website; and (3) sending written notification to the office of the attorney general and major media outlets in New Mexico." *NMSA 1978, § 57-12C-6(D), (E).* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
151
+
152
+ [^q5-dbna-delay]: **NMSA 1978, § 57-12C-9** — "The notification required by the Data Breach Notification Act may be delayed: A. if a law enforcement agency determines that the notification will impede a criminal investigation; or B. as necessary to determine the scope of the security breach and restore the integrity, security and confidentiality of the data system." *NMSA 1978, § 57-12C-9.* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
153
+
154
+ [^q5-dbna-exemptions]: **NMSA 1978, § 57-12C-8** — "The provisions of the Data Breach Notification Act shall not apply to a person subject to the federal Gramm-Leach-Bliley Act or the federal Health Insurance Portability and Accountability Act of 1996." *NMSA 1978, § 57-12C-8.* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
155
+
156
+ [^q6-dbna-ag-enforcement]: **NMSA 1978, § 57-12C-11(A), (B)** — "When the attorney general has a reasonable belief that a violation of the Data Breach Notification Act has occurred, the attorney general may bring an action on the behalf of individuals and in the name of the state alleging a violation of that act. B. In any action filed by the attorney general pursuant to the Data Breach Notification Act, the court may: (1) issue an injunction; and (2) award damages for actual costs or losses, including consequential financial losses." *NMSA 1978, § 57-12C-11(A), (B).* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
157
+
158
+ [^q6-dbna-civil-penalty]: **NMSA 1978, § 57-12C-11(C)** — "If the court determines that a person violated the Data Breach Notification Act knowingly or recklessly, the court may impose a civil penalty of the greater of twentyfive thousand dollars ($25,000) or, in the case of failed notification, ten dollars ($10.00) per instance of failed notification up to a maximum of one hundred fifty thousand dollars ($150,000)." *NMSA 1978, § 57-12C-11(C).* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
159
+
160
+ [^q6-upa-private-remedy]: **NMSA 1978, § 57-12-10(B), (C)** — "Any person who suffers any loss of money or property, real or personal, as a result of any employment by another person of a method, act or practice declared unlawful by the Unfair Practices Act may bring an action to recover actual damages or the sum of one hundred dollars ($100), whichever is greater. Where the trier of fact finds that the party charged with an unfair or deceptive trade practice or an unconscionable trade practice has willfully engaged in the trade practice, the court may award up to three times actual damages or three hundred dollars ($300), whichever is greater, to the party complaining of the practice. C. The court shall award attorney fees and costs to the party complaining of an unfair or deceptive trade practice or unconscionable trade practice if the party prevails." *NMSA 1978, § 57-12-10(B), (C).* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
161
+
162
+ [^q6-upa-ag-action]: **NMSA 1978, § 57-12-8(A), (B)** — "Whenever the attorney general has reasonable belief that any person is using, has used or is about to use any method, act or practice which is declared by the Unfair Practices Act to be unlawful, and that proceedings would be in the public interest, he may bring an action in the name of the state alleging violations of the Unfair Practices Act. The action may be brought in the district court of the county in which the person resides or has his principal place of business or in the district court in any county in which the person is using, has used or is about to use the practice which has been alleged to be unlawful under the Unfair Practices Act. The attorney general acting on behalf of the state of New Mexico shall not be required to post bond when seeking a temporary or permanent injunction in such action. B. In any action filed pursuant to the Unfair Practices Act, including an action with respect to unimproved real property, the attorney general may petition the district court for temporary or permanent injunctive relief and restitution." *NMSA 1978, § 57-12-8(A), (B).* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
163
+
164
+ [^q6-upa-class-action]: **NMSA 1978, § 57-12-10(E)** — "In any class action filed under this section, the court may award damages to the named plaintiffs as provided in Subsection B of this section and may award members of the class such actual damages as were suffered by each member of the class as a result of the unlawful method, act or practice." *NMSA 1978, § 57-12-10(E).* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
165
+
166
+ [^q6-upa-deceptive-def]: **NMSA 1978, § 57-12-2(D)** — "‘unfair or deceptive trade practice’ means an act specifically declared unlawful pursuant to the Unfair Practices Act, a false or misleading oral or written statement, visual description or other representation of any kind knowingly made in connection with the sale, lease, rental or loan of goods or services or in the extension of credit or in the collection of debts by a person in the regular course of the person's trade or commerce, that may, tends to or does deceive or mislead any person" *NMSA 1978, § 57-12-2(D).* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
167
+
168
+ [^q6-upa-intent]: **NMSA 1978, § 57-12-2 annotations** — "Intent to deceive not element of ‘unfair or deceptive trade practice’ but a knowing representation is required." *NMSA 1978, § 57-12-2 annotations (Richardson Ford Sales, Inc. v. Johnson).* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
169
+
170
+ [^q6-upa-civil-penalty]: **NMSA 1978, § 57-12-11** — "In any action brought under Section 57-12-8 NMSA 1978, if the court finds that a person is willfully using or has willfully used a method, act or practice declared unlawful by the Unfair Practices Act, the attorney general, upon petition to the court, may recover, on behalf of the state of New Mexico, a civil penalty of not exceeding five thousand dollars ($5,000) per violation." *NMSA 1978, § 57-12-11.* <https://nmonesource.com/nmos/nmsa/en/4423/1/document.do>
171
+
172
+ [^q6-hb214-status]: **New Mexico Legislature HB 214 (2026 Regular Session)** — "Current Location Died (API.)" *New Mexico Legislature, HB 214 (2026 Regular Session).* <https://www.nmlegis.gov/Legislation/Legislation?chamber=H&legType=B&legNo=214&year=26>
173
+
174
+ [^q6-hb214-effective-dates]: **HB 214 (2026), § 16** — "SECTION 16. EFFECTIVE DATES.-- A. The effective date of the provisions of Sections 1, 2 and 13 through 15 of this act is July 1, 2026. B. The effective date of the provisions of Sections 3 through 12 of this act is July 1, 2027." *HB 214 (2026), § 16.* <https://www.nmlegis.gov/Sessions/26%20Regular/bills/house/HB0214.HTML>
@@ -0,0 +1,195 @@
1
+ ---
2
+ jurisdiction: "New York"
3
+ slug: new-york
4
+ countryCode: US
5
+ snapshotAsOf: "2026-06-19"
6
+ lastReviewed: "2026-06-11"
7
+ canonicalUrl: https://openagreements.org/practice-guides/privacy/us/new-york
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/new-york · **Snapshot as of:** 2026-06-19 · License: CC BY 4.0 · © openagreements.org
19
+
20
+ # New York Consumer Privacy Law[^about]
21
+
22
+ New York has no comprehensive consumer-privacy act. The SHIELD Act (GBL §§ 899-aa, 899-bb) imposes breach-notice and reasonable-safeguards duties, the Child Data Protection Act restricts processing data of users under 18, and GBL § 349 supplies the UDAAP rule and SHIELD safeguards hook.
23
+
24
+
25
+ ## At a glance
26
+
27
+ | Question | New York |
28
+ | --- | --- |
29
+ | **Law coverage** | Specific data types only |
30
+ | **Summary** | New York has not enacted a comprehensive consumer-privacy law, but the SHIELD Act already requires almost every business holding New Yorkers' private information — with no revenue or in-state-presence threshold — to run a reasonable data-security program, to report breaches within 30 days, and to expect Attorney General enforcement under separate SHIELD and breach-notice provisions. Since June 20, 2025 the Child Data Protection Act has added a default-deny regime for processing personal data of users under 18, including a sale ban subject to statutory exceptions. There is no general privacy-policy mandate, so the policy slice is governed by the rule that whatever you publish must be true; the moving piece to watch is the twice-passed Health Information Privacy Act, which would add a strict consumer-health-data regime if it becomes law. |
31
+ | **Main law** | SHIELD Act — N.Y. Gen. Bus. Law § 899-bb (reasonable-safeguards duty) and § 899-aa (breach notification) — plus the Child Data Protection Act (GBL art. 39-FF, in force since June 20, 2025) and GBL § 349; New York has no comprehensive consumer-privacy statute |
32
+ | **Privacy policy required?** | No general New York statute mandates a consumer privacy policy or fixes its contents; a published policy that misstates practices is actionable under GBL § 349 and FTC Act § 5, and GLBA, HIPAA, and COPPA supply required contents where they apply |
33
+ | **Who does it cover?** | Any person or business, wherever located, that owns or licenses computerized data including the private information of a New York resident — no in-state-presence, revenue, or volume threshold; small businesses get scaled (not waived) duties; the Child Data Protection Act covers operators of online services with New York users under 18 |
34
+ | **Can consumers sue?** | Limited path |
35
+ | **Privacy policy rule** | No state policy checklist |
36
+ | **Consent for sensitive data?** | Only for certain data types |
37
+ | **Browser opt-out signals?** | Not required |
38
+ | **Lawsuit detail** | Not under the SHIELD Act — § 899-bb expressly creates none and § 899-aa runs through the Attorney General; but GBL § 349(h) lets a consumer injured by a deceptive practice sue for actual damages or $50 (treble to $1,000) plus attorney's fees |
39
+ | **Who enforces it?** | New York Attorney General (Commissioner of Labor for employee personal-identifying-information violations under Labor Law § 203-d) |
40
+
41
+ ## Which privacy laws apply to your business in New York? {#which-privacy-laws-apply}
42
+
43
+ **Short answer.** New York has no comprehensive consumer-privacy statute, but it is far from unregulated — the state runs a layered, sector-by-sector framework with unusually broad practical reach. The SHIELD Act supplies the spine: any person or business that owns or licenses computerized data including the private information of a New York resident must develop, implement, and maintain reasonable safeguards to protect it [^q1-shield-duty], and must notify affected residents of a data breach in the most expedient time possible, with a hard outer limit of thirty days after discovery [^q1-breach-timing]. Since June 20, 2025, the Child Data Protection Act has barred operators of websites, apps, and connected devices from processing the personal data of New York users under 18 except on narrow statutory terms [^q1-cdpa-default]. And on the employment side, Labor Law § 203-d restricts what an employer may do with employee personal identifying information [^q1-labor-203d].
44
+
45
+ The structural point to absorb first is that the SHIELD Act's safeguards duty carries no in-state-presence, revenue, or data-volume threshold — it turns solely on holding a New York resident's *private information* — so a business with a handful of New York customers or employees is covered even if it has never set foot in the state. What New York does not have is an omnibus law of the California, Virginia, or Colorado type: residents hold no general state-law rights to access, delete, or correct their personal data, and no general right to opt out of its sale (the under-18 sale ban in the Child Data Protection Act is the exception). General Business Law § 349 supplies the UDAAP and deception rule and the SHIELD safeguards enforcement hook, but breach-notice violations, Child Data Protection Act violations, and employee personal-identifying-information violations run through their own statutory enforcement provisions. The federal overlay fills the remaining lanes: FTC Act § 5 polices deceptive or unfair privacy practices nationwide, GLBA governs financial institutions, HIPAA governs covered health entities and their business associates, and COPPA governs services directed to children under 13.
46
+
47
+ The landscape is also moving. A Health Information Privacy Act passed both houses in 2025 but was vetoed in December 2025; revised S9269/A10357 passed both houses on June 3-4, 2026 and would create the health-data regime if signed. Until signature, veto, or chapter amendment, it is not in force. The separate comprehensive New York Privacy Act lineage has not advanced in 2026, so New York remains a non-comprehensive state for now — but businesses handling health-adjacent consumer data should confirm the health bill's status before relying on the current sectoral-only picture.
48
+
49
+ ## What does the SHIELD Act require your data-security program to include? {#security-program}
50
+
51
+ **Short answer.** The SHIELD Act gives a business two ways to satisfy its reasonable-safeguards duty: be a compliant regulated entity under an enumerated regime (GLBA, HIPAA/HITECH, New York's financial-services cybersecurity regulation, or other federal or state data-security rules), or implement a data-security program with the statute's enumerated administrative safeguards [^q2-program-elements], technical safeguards [^q2-technical-safeguards], and physical safeguards [^q2-physical-safeguards]. Small businesses — fewer than fifty employees, under three million dollars in gross annual revenue in each of the last three fiscal years, or under five million dollars in year-end total assets [^q2-small-business-def] — comply with a program whose safeguards are appropriate to their size, complexity, activities, and the sensitivity of the data they hold [^q2-small-business-proviso].
52
+
53
+ This is the closest thing New York has to a general privacy-program mandate, and it is the prong most businesses should build to first. The statutory safeguard lists work as a program checklist: administrative safeguards (coordinator, risk identification, sufficiency assessment, training, vendor selection and contracting, program adjustment), technical safeguards (risk assessment in network and software design and in processing, transmission, and storage; attack detection, prevention, and response; testing and monitoring of key controls), and physical safeguards (storage and disposal risk, intrusion detection and response, protection during collection, transport, and destruction, and timely disposal by erasing media so the information cannot be read or reconstructed). The deemed-compliance path matters for regulated entities: a business already subject to and in compliance with GLBA, HIPAA, or the Department of Financial Services cybersecurity regulation does not need a second, parallel program for SHIELD purposes. The small-business proviso scales the duty but does not waive it — a five-person shop should be able to document a reasoned set of safeguards.
54
+
55
+ A safeguards failure is deemed a General Business Law § 349 violation, and the Attorney General may sue to enjoin violations and collect civil penalties [^q2-349-hook] — up to five thousand dollars per violation under the companion penalty section [^q2-350d-penalty]. Per-violation math across a large data set is what turns a paper duty into a board-level number.
56
+
57
+ ## What must your New York privacy policy contain? {#privacy-policy-contents}
58
+
59
+ **Short answer.** No New York statute requires a general consumer privacy policy or fixes what it must say. The governing rule is instead that whatever you publish has to be true: General Business Law § 349 declares unfair, deceptive, or abusive acts and practices in any business, trade, or commerce in the state unlawful [^q3-gbs-349], and FTC Act § 5 reaches the same conduct federally [^q3-ftc5] — so a privacy policy that misstates how you collect, use, share, retain, or secure data is itself the violation. Where a sectoral regime applies, that regime supplies the required contents; a HIPAA covered entity, for example, must give individuals notice of the uses and disclosures of their protected health information and of their rights and the entity's duties [^q3-hipaa-notice].
60
+
61
+ In practice the drafting question for a New York-facing policy is less what must be included than does the policy match actual practice. Build the contents from the overlay that applies to you — GLBA privacy notices for financial institutions, the HIPAA Notice of Privacy Practices for covered entities, HIPAA business-associate agreements where a business associate handles PHI, and a COPPA notice for services directed to children under 13 — and, 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, then honor every word of it. Two New York-specific notes sharpen the risk. First, § 349 was amended effective February 17, 2026 to reach *unfair* and *abusive* practices, not just deceptive ones, so the Attorney General can now pursue data practices that involve no affirmative misstatement at all — think onerous consent flows or data uses a consumer cannot reasonably avoid. Second, because § 349 carries a private right of action for deceptive practices (covered in the lawsuit section below), an inaccurate privacy policy is one of the few privacy failures in New York that consumers themselves can sue over.
62
+
63
+ ## Can you collect personal data from users under 18 in New York? {#minors-data}
64
+
65
+ **Short answer.** Only on the statute's terms. Since June 20, 2025, New York's Child Data Protection Act has flipped the default for minors' data: subject to the statute's express subdivision-six deletion/transition rule and § 899-jj exception, an operator may not process — or let a processor or third-party operator collect — the personal data of a covered user unless, for users 12 or younger, COPPA permits the processing, or, for users 13 through 17, the processing is strictly necessary for an enumerated activity or the user has given informed consent [^q4-cdpa-default]. A covered user is a New York user the operator actually knows to be a minor, or any user of a service primarily directed to minors [^q4-covered-user], and a minor is anyone under eighteen [^q4-minor-def]. Selling a covered user's personal data is prohibited except as provided in § 899-jj [^q4-sale-ban].
66
+
67
+ The strictly-necessary lane is narrow by design: it covers providing a service the user requested, internal operations (expressly excluding marketing, advertising, research and development, and re-engagement prompts), fixing technical errors, fraud and security, legal compliance and claims, and vital interests. Everything else for the 13-to-17 band requires informed consent collected the statute's way — the request must be separate from other transactions, free of interface design that obscures or impairs the choice, must state clearly that the processing is not strictly necessary and can be declined without losing the service, and must present refusal as the most prominent option [^q4-consent]; consent is freely revocable, and a declined or revoked request cannot be repeated for the following calendar year [^q4-revocation]. Operators also may not punish a non-consenting user by degrading or charging more for the service [^q4-no-degradation], must delete a covered user's non-permitted data within thirty days of learning the user is covered [^q4-deletion], and must honor device-level decline signals [^q4-device-signal].
68
+
69
+ Enforcement belongs to the Attorney General, who may sue any person within or outside the state for injunctions, restitution, disgorgement — including destruction of unlawfully obtained data — damages, and civil penalties of up to five thousand dollars per violation [^q4-remedies]. The Attorney General published implementation guidance in 2025 signaling enforcement discretion for good-faith compliance while formal rules under the act remain outstanding, but the statute itself is in force and per-violation exposure across a youth user base scales quickly. Note the act's relationship to federal law: for under-13 users it harmonizes with COPPA rather than displacing it, so a COPPA-compliant program is the starting point, not the finish line, for a New York audience that includes teenagers.
70
+
71
+ ## What privacy rights and opt-outs do New York consumers have? {#consumer-rights-opt-outs}
72
+
73
+ **Short answer.** New York does not give adult consumers a general state-law right to access, delete, correct, or port personal data, a general sale opt-out, or a general universal-opt-out-signal right. The state-specific choice regime is targeted to covered users under 18: for users 13 through 17, processing that is not strictly necessary requires informed consent collected through the CDPA's prescribed request or device-signal path [^q5-consent], and the sale of covered users' personal data is prohibited except as provided in § 899-jj [^q5-sale-ban].
74
+
75
+ For adults, the practical right is indirect: a deceptive privacy statement can support a consumer suit under General Business Law § 349(h), but that is a deception remedy, not an omnibus data-rights regime [^q5-349h-pra]. For minors, the CDPA gives the meaningful opt-out architecture. Consent must be separate from other transactions, free of mechanisms that obscure or impair the user's choice, and paired with refusal as the most prominent option [^q5-consent]. Once consent is declined or revoked, the operator generally cannot ask again for that processing for the following calendar year [^q5-revocation]; if the covered user's device communicates a decline signal, the operator cannot request informed consent for that processing [^q5-device-signal]. New York therefore has a strong minor-specific consent and signal rule, but no across-the-board adult universal-opt-out requirement.
76
+
77
+ ## What must your contracts with vendors say? {#vendor-contracts}
78
+
79
+ **Short answer.** New York has no omnibus data-processing-agreement statute, but two state-law contract duties do exist. Under the SHIELD Act, a compliant security program includes selecting service providers capable of maintaining appropriate safeguards and requiring those safeguards by contract [^q5-shield-vendor]. And under the Child Data Protection Act, no operator or processor may disclose a covered user's personal data to a third party — or allow a third party to process it — without a written, binding agreement setting out processing instructions and the parties' rights and obligations [^q5-cdpa-processor].
80
+
81
+ For general adult-consumer data, the SHIELD clause is the floor: a New York-facing business should be able to show that its vendor diligence and its contracts impose safeguards on everyone who touches *private information*, because a vendor-caused breach will be evaluated against that statutory element. Where minors' data is in scope, the Child Data Protection Act turns the contract into a gating requirement — the statute also obliges processors to follow the operator's instructions, to assist with the operator's deletion duties, to demonstrate compliance on request, to cooperate with assessments, and to give advance notice before handing data to further processors, so a compliant agreement should track each of those elements. The federal overlay supplies the rest where it applies: the GLBA Safeguards Rule requires financial institutions to bind service providers by contract to implement and maintain safeguards [^q5-glba-safeguards], and HIPAA requires a business-associate agreement with mandatory data-protection, breach-reporting, and subcontractor flow-down terms before protected health information changes hands [^q5-hipaa-baa]. Outside those lanes, carrying the same terms forward — documented instructions, confidentiality, reasonable security, breach notice back to you, return or deletion at the end of the engagement — is best practice that also evidences SHIELD compliance.
82
+
83
+ ## When must you notify people of a data breach in New York? {#breach-notification}
84
+
85
+ **Short answer.** Any person or business that owns or licenses computerized data including private information must notify every New York resident whose private information was, or is reasonably believed to have been, accessed or acquired without valid authorization — in the most expedient time possible, and in any event within thirty days after the breach is discovered [^q6-breach-trigger]. The trigger is broad: a breach includes unauthorized *access* to private information, not just its acquisition [^q6-breach-def]. And whenever any New York residents are notified, the business must also notify the Attorney General, the Department of State, the State Police, and — for covered financial-services entities — the Department of Financial Services [^q6-regulator-notice].
86
+
87
+ What counts as *private information* drives the analysis. It means personal information combined with an unencrypted (or key-compromised) data element — Social Security number, driver's license or non-driver ID number, financial-account or card numbers that permit account access, biometric information, medical information, and health-insurance information — or a username or email address combined with a password or security credentials permitting access to an online account [^q6-private-info]. The medical and health-insurance additions matter operationally: incident-response playbooks written before 2025 often classify those elements as non-triggering, and in New York they now trigger. A business that merely maintains data it does not own must alert the data's owner within thirty days of discovery [^q6-maintainer-notice], and notice to individuals may be written, electronic with express consent, telephonic with a log, or by substitute notice for very large or unreachable classes [^q6-notice-methods]. A narrow carve-out excuses notice for inadvertent disclosures by authorized persons that the business reasonably determines are unlikely to cause misuse or harm — but the determination must be documented in writing, retained for five years, and, if more than five hundred residents are affected, provided to the Attorney General within ten days [^q6-harm-carveout]. When more than five thousand residents are notified at once, the consumer reporting agencies must be notified as well [^q6-cra-notice].
88
+
89
+ Non-compliance is an Attorney General matter: in the Attorney General's action, the court may award damages for actual losses of persons entitled to notice [^q6-aa-damages], and for knowing or reckless violations may impose a civil penalty of the greater of five thousand dollars or up to twenty dollars per failed notification, capped at two hundred fifty thousand dollars [^q6-ag-penalty]. A late-notice case needs no underlying security failure, so the thirty-day clock deserves a hard-coded place in any incident-response plan. Businesses already notifying under GLBA, HIPAA/HITECH, or the Department of Financial Services cybersecurity regulation need not send duplicate individual notices, but the New York regulator and credit-agency notices still apply, and HIPAA-covered entities reporting a breach to federal health authorities must copy the New York Attorney General within five business days [^q6-hipaa-ag-copy].
90
+
91
+ ## Can a consumer sue your business in New York over privacy? {#consumer-lawsuit}
92
+
93
+ **Short answer.** Not under the SHIELD Act. The safeguards section says expressly that nothing in it creates a private right of action [^q7-shield-no-pra], and the breach-notification statute routes consumer redress through the Attorney General — in the Attorney General's action, the court may award damages for actual costs or losses of people who should have been notified but were not [^q7-aa-damages]. The consumer's own door is General Business Law § 349(h): any person injured by a deceptive act or practice may sue in their own name for actual damages or fifty dollars, whichever is greater, with discretionary treble damages up to one thousand dollars for willful or knowing violations and attorney's fees for a prevailing plaintiff [^q7-349h-pra].
94
+
95
+ The practical consequence is that New York privacy litigation by consumers is framed as deception, not as a statutory data-rights claim: a privacy policy or security promise that did not match reality is the classic § 349(h) theory, often pleaded alongside common-law negligence and implied-contract claims after a breach. Two limits keep that exposure bounded. The § 349(h) action reaches *deceptive* acts and practices — the statute's newer unfair and abusive prongs are the Attorney General's to enforce — and the modest statutory minimum means individual claims aggregate into class actions rather than standing alone. On the public side, the Attorney General is an active privacy enforcer, using the SHIELD safeguards hook, the breach statute, and § 349 directly, typically resolving matters by assurance of discontinuance with monetary payments and mandated security programs; the auto-insurer and notice-timing settlements described in the security-program and breach sections above show the pattern. Employee data has its own enforcement lane: the Commissioner of Labor may impose a civil penalty of up to five hundred dollars for a knowing violation of the employee personal-identifying-information rules, and a violation is presumed knowing if the employer has no safeguard policies in place — which makes a short written policy the cheapest compliance step in this entire note [^q7-labor-penalty].
96
+
97
+ One forward-looking caveat belongs here. Revised S9269/A10357 passed both houses on June 3-4, 2026 and would create a Health Information Privacy Act if signed; until signature, veto, or chapter amendment, it is not in force. In its passed form, it would keep enforcement exclusively with the Attorney General — no private right of action — at civil penalties of up to fifteen thousand dollars per violation.
98
+
99
+ [^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. This article synthesizes New York primary law and is not legal advice. This article is for informational purposes only and does not create an attorney-client relationship.
100
+
101
+ [^q1-shield-duty]: **N.Y. Gen. Bus. Law § 899-bb(2)(a)** — "Any person or business that owns or licenses computerized data which includes private information of a resident of New York shall develop, implement and maintain reasonable safeguards to protect the security, confidentiality and integrity of the private information including, but not limited to, disposal of data." *N.Y. Gen. Bus. Law § 899-bb(2)(a).* <https://www.nysenate.gov/legislation/laws/GBS/899-BB>
102
+
103
+ [^q1-breach-timing]: **N.Y. Gen. Bus. Law § 899-aa(2)** — "The disclosure shall be made in the most expedient time possible and without unreasonable delay, provided that such notification shall be made within thirty days after the breach has been discovered, except for the legitimate needs of law enforcement, as provided in subdivision four of this section." *N.Y. Gen. Bus. Law § 899-aa(2).* <https://www.nysenate.gov/legislation/laws/GBS/899-AA>
104
+
105
+ [^q1-cdpa-default]: **N.Y. Gen. Bus. Law § 899-ff(1)** — "Except as provided for in subdivision six of this section and section eight hundred ninety-nine-jj of this article, an operator shall not process, or allow a processor to process, the personal data of a covered user collected through the use of a website, online service, online application, mobile application, or connected device, or allow a third-party operator to collect the personal data of a covered user collected through the operator's website, online service, online application, mobile application, or connected device unless and to the extent: (a) the covered user is twelve years of age or younger and processing is permitted under 15 U.S.C. § 6502 and its implementing regulations; or (b) the covered user is thirteen years of age or older and processing is strictly necessary for an activity set forth in subdivision two of this section, or informed consent has been obtained as set forth in subdivision three of this section." *N.Y. Gen. Bus. Law § 899-ff(1).* <https://www.nysenate.gov/legislation/laws/GBS/899-FF>
106
+
107
+ [^q1-labor-203d]: **N.Y. Lab. Law § 203-d** — "An employer shall not unless otherwise required by law: (a) Publicly post or display an employee's social security number; (b) Visibly print a social security number on any identification badge or card, including any time card; (c) Place a social security number in files with unrestricted access; or (d) Communicate an employee's personal identifying information to the general public." *N.Y. Lab. Law § 203-d(1).* <https://www.nysenate.gov/legislation/laws/LAB/203-D>
108
+
109
+ [^q2-program-elements]: **N.Y. Gen. Bus. Law § 899-bb(2)(b)** — "A person or business shall be deemed to be in compliance with paragraph (a) of this subdivision if it either: (i) is a compliant regulated entity as defined in subdivision one of this section; or (ii) implements a data security program that includes the following: (A) reasonable administrative safeguards such as the following, in which the person or business: (1) designates one or more employees to coordinate the security program; (2) identifies reasonably foreseeable internal and external risks; (3) assesses the sufficiency of safeguards in place to control the identified risks; (4) trains and manages employees in the security program practices and procedures; (5) selects service providers capable of maintaining appropriate safeguards, and requires those safeguards by contract; and (6) adjusts the security program in light of business changes or new circumstances" *N.Y. Gen. Bus. Law § 899-bb(2)(b).* <https://www.nysenate.gov/legislation/laws/GBS/899-BB>
110
+
111
+ [^q2-technical-safeguards]: **N.Y. Gen. Bus. Law § 899-bb(2)(b)(ii)(B)** — "reasonable technical safeguards such as the following, in which the person or business: (1) assesses risks in network and software design; (2) assesses risks in information processing, transmission and storage; (3) detects, prevents and responds to attacks or system failures; and (4) regularly tests and monitors the effectiveness of key controls, systems and procedures" *N.Y. Gen. Bus. Law § 899-bb(2)(b)(ii)(B).* <https://www.nysenate.gov/legislation/laws/GBS/899-BB>
112
+
113
+ [^q2-physical-safeguards]: **N.Y. Gen. Bus. Law § 899-bb(2)(b)(ii)(C)** — "reasonable physical safeguards such as the following, in which the person or business: (1) assesses risks of information storage and disposal; (2) detects, prevents and responds to intrusions; (3) protects against unauthorized access to or use of private information during or after the collection, transportation and destruction or disposal of the information; and (4) disposes of private information within a reasonable amount of time after it is no longer needed for business purposes by erasing electronic media so that the information cannot be read or reconstructed." *N.Y. Gen. Bus. Law § 899-bb(2)(b)(ii)(C).* <https://www.nysenate.gov/legislation/laws/GBS/899-BB>
114
+
115
+ [^q2-small-business-def]: **N.Y. Gen. Bus. Law § 899-bb(1)(c)** — "‘Small business’ shall mean any person or business with (i) fewer than fifty employees; (ii) less than three million dollars in gross annual revenue in each of the last three fiscal years; or (iii) less than five million dollars in year-end total assets, calculated in accordance with generally accepted accounting principles." *N.Y. Gen. Bus. Law § 899-bb(1)(c).* <https://www.nysenate.gov/legislation/laws/GBS/899-BB>
116
+
117
+ [^q2-small-business-proviso]: **N.Y. Gen. Bus. Law § 899-bb(2)(c)** — "A small business as defined in paragraph (c) of subdivision one of this section complies with subparagraph (ii) of paragraph (b) of subdivision two of this section if the small business's security program contains reasonable administrative, technical and physical safeguards that are appropriate for the size and complexity of the small business, the nature and scope of the small business's activities, and the sensitivity of the personal information the small business collects from or about consumers." *N.Y. Gen. Bus. Law § 899-bb(2)(c).* <https://www.nysenate.gov/legislation/laws/GBS/899-BB>
118
+
119
+ [^q2-349-hook]: **N.Y. Gen. Bus. Law § 899-bb(2)(d)** — "Any person or business that fails to comply with this subdivision shall be deemed to have violated section three hundred forty-nine of this chapter, and the attorney general may bring an action in the name and on behalf of the people of the state of New York to enjoin such violations and to obtain civil penalties under section three hundred fifty-d of this chapter." *N.Y. Gen. Bus. Law § 899-bb(2)(d).* <https://www.nysenate.gov/legislation/laws/GBS/899-BB>
120
+
121
+ [^q2-350d-penalty]: **N.Y. Gen. Bus. Law § 350-d** — "Any person, firm, corporation or association or agent or employee thereof who engages in any of the acts or practices stated in this article to be unlawful shall be liable to a civil penalty of not more than five thousand dollars for each violation, which shall accrue to the state of New York and may be recovered in a civil action brought by the attorney general." *N.Y. Gen. Bus. Law § 350-d(a).* <https://www.nysenate.gov/legislation/laws/GBS/350-D>
122
+
123
+ [^q3-gbs-349]: **N.Y. Gen. Bus. Law § 349(a)** — "Unfair, deceptive, or abusive acts or practices in the conduct of any business, trade or commerce or in the furnishing of any service in this state are hereby declared unlawful." *N.Y. Gen. Bus. Law § 349(a).* <https://www.nysenate.gov/legislation/laws/GBS/349>
124
+
125
+ [^q3-ftc5]: **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.>
126
+
127
+ [^q3-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>
128
+
129
+ [^q4-cdpa-default]: **N.Y. Gen. Bus. Law § 899-ff(1)** — "Except as provided for in subdivision six of this section and section eight hundred ninety-nine-jj of this article, an operator shall not process, or allow a processor to process, the personal data of a covered user collected through the use of a website, online service, online application, mobile application, or connected device, or allow a third-party operator to collect the personal data of a covered user collected through the operator's website, online service, online application, mobile application, or connected device unless and to the extent: (a) the covered user is twelve years of age or younger and processing is permitted under 15 U.S.C. § 6502 and its implementing regulations; or (b) the covered user is thirteen years of age or older and processing is strictly necessary for an activity set forth in subdivision two of this section, or informed consent has been obtained as set forth in subdivision three of this section." *N.Y. Gen. Bus. Law § 899-ff(1).* <https://www.nysenate.gov/legislation/laws/GBS/899-FF>
130
+
131
+ [^q4-covered-user]: **N.Y. Gen. Bus. Law § 899-ee(1)** — "‘Covered user’ shall mean a user of a website, online service, online application, mobile application, or connected device, or portion thereof, in the state of New York who is: (a) actually known by the operator of such website, online service, online application, mobile application, or connected device to be a minor; or (b) using a website, online service, online application, mobile application, or connected device primarily directed to minors." *N.Y. Gen. Bus. Law § 899-ee(1).* <https://www.nysenate.gov/legislation/laws/GBS/899-EE>
132
+
133
+ [^q4-minor-def]: **N.Y. Gen. Bus. Law § 899-ee(2)** — "‘Minor’ shall mean a natural person under the age of eighteen." *N.Y. Gen. Bus. Law § 899-ee(2).* <https://www.nysenate.gov/legislation/laws/GBS/899-EE>
134
+
135
+ [^q4-sale-ban]: **N.Y. Gen. Bus. Law § 899-ff(5)** — "Except as provided for in section eight hundred ninety-nine-jj of this article, an operator shall not purchase or sell, or allow a processor or third-party operator to purchase or sell, the personal data of a covered user." *N.Y. Gen. Bus. Law § 899-ff(5).* <https://www.nysenate.gov/legislation/laws/GBS/899-FF>
136
+
137
+ [^q4-consent]: **N.Y. Gen. Bus. Law § 899-ff(3)** — "Requests for such informed consent shall: (i) be made separately from any other transaction or part of a transaction; (ii) be made in the absence of any mechanism that has the purpose or substantial effect of obscuring, subverting, or impairing a covered user's decision-making regarding authorization for the processing; (iii) clearly and conspicuously state that the processing for which the consent is requested is not strictly necessary, and that the covered user may decline without preventing continued use of the website, online service, online application, mobile application, or connected device; and (iv) clearly present an option to refuse to provide consent as the most prominent option." *N.Y. Gen. Bus. Law § 899-ff(3)(a).* <https://www.nysenate.gov/legislation/laws/GBS/899-FF>
138
+
139
+ [^q4-revocation]: **N.Y. Gen. Bus. Law § 899-ff(3)(b)-(c)** — "Such informed consent, once given, shall be freely revocable at any time, and shall be at least as easy to revoke as it was to provide. (c) If a covered user declines to provide or revokes informed consent for processing, another request may not be made for such processing for the following calendar year, however an operator may make available a mechanism that a covered user can use unprompted and at the user's discretion to provide informed consent." *N.Y. Gen. Bus. Law § 899-ff(3)(b)-(c).* <https://www.nysenate.gov/legislation/laws/GBS/899-FF>
140
+
141
+ [^q4-no-degradation]: **N.Y. Gen. Bus. Law § 899-ff(4)** — "Except where processing is strictly necessary to provide a product, service, or feature, an operator may not withhold, degrade, lower the quality, or increase the price of any product, service, or feature to a covered user due to the operator not obtaining verifiable parental consent under 15 U.S.C. § 6502 and its implementing regulations or informed consent under subdivision three of this section." *N.Y. Gen. Bus. Law § 899-ff(4).* <https://www.nysenate.gov/legislation/laws/GBS/899-FF>
142
+
143
+ [^q4-deletion]: **N.Y. Gen. Bus. Law § 899-ff(6)** — "Within thirty days of determining or being informed that a user is a covered user, an operator shall: (a) dispose of, destroy, or delete and direct all of its processors to dispose of, destroy, or delete all personal data of such covered user that it maintains, unless processing such personal data is permitted under 15 U.S.C. § 6502 and its implementing regulations, is strictly necessary for an activity listed in subdivision two of this section, or informed consent is obtained as set forth in subdivision three of this section" *N.Y. Gen. Bus. Law § 899-ff(6).* <https://www.nysenate.gov/legislation/laws/GBS/899-FF>
144
+
145
+ [^q4-device-signal]: **N.Y. Gen. Bus. Law § 899-ff(3)(d)** — "If a covered user's device communicates or signals that the covered user declines to provide informed consent for processing pursuant to the provisions of subdivision two of section eight hundred ninety-nine-ii of this article, an operator shall not request informed consent for such processing, however an operator may make available a mechanism that a covered user can use unprompted and at the user's discretion to provide informed consent." *N.Y. Gen. Bus. Law § 899-ff(3)(d).* <https://www.nysenate.gov/legislation/laws/GBS/899-FF>
146
+
147
+ [^q4-remedies]: **N.Y. Gen. Bus. Law § 899-mm** — "Whenever it appears to the attorney general, either upon complaint or otherwise, that any person, within or outside the state, has engaged in or is about to engage in any of the acts or practices stated to be unlawful in this article, the attorney general may bring an action or special proceeding in the name and on behalf of the people of the state of New York to enjoin any violation of this article, to obtain restitution of any moneys or property obtained directly or indirectly by any such violation, to obtain disgorgement of any profits or gains obtained directly or indirectly by any such violation, including but not limited to the destruction of unlawfully obtained data, to obtain damages caused directly or indirectly by any such violation, to obtain civil penalties of up to five thousand dollars per violation, and to obtain any such other and further relief as the court may deem proper, including preliminary relief." *N.Y. Gen. Bus. Law § 899-mm.* <https://www.nysenate.gov/legislation/laws/GBS/899-MM>
148
+
149
+ [^q5-consent]: **N.Y. Gen. Bus. Law § 899-ff(3)(a)** — "Requests for such informed consent shall: (i) be made separately from any other transaction or part of a transaction; (ii) be made in the absence of any mechanism that has the purpose or substantial effect of obscuring, subverting, or impairing a covered user's decision-making regarding authorization for the processing; (iii) clearly and conspicuously state that the processing for which the consent is requested is not strictly necessary, and that the covered user may decline without preventing continued use of the website, online service, online application, mobile application, or connected device; and (iv) clearly present an option to refuse to provide consent as the most prominent option." *N.Y. Gen. Bus. Law § 899-ff(3)(a).* <https://www.nysenate.gov/legislation/laws/GBS/899-FF>
150
+
151
+ [^q5-sale-ban]: **N.Y. Gen. Bus. Law § 899-ff(5)** — "Except as provided for in section eight hundred ninety-nine-jj of this article, an operator shall not purchase or sell, or allow a processor or third-party operator to purchase or sell, the personal data of a covered user." *N.Y. Gen. Bus. Law § 899-ff(5).* <https://www.nysenate.gov/legislation/laws/GBS/899-FF>
152
+
153
+ [^q5-349h-pra]: **N.Y. Gen. Bus. Law § 349(h)** — "In addition to the right of action granted to the attorney general pursuant to this section, any person who has been injured by reason of any deceptive act or deceptive practice made unlawful by this section may bring an action in such person's own name to enjoin such deceptive act or deceptive practice, an action to recover such person's actual damages or fifty dollars, whichever is greater, or both such actions. The court may, in its discretion, increase the award of damages to an amount not to exceed three times the actual damages up to one thousand dollars, if the court finds the defendant willfully or knowingly violated this section. The court may award reasonable attorney's fees to a prevailing plaintiff." *N.Y. Gen. Bus. Law § 349(h).* <https://www.nysenate.gov/legislation/laws/GBS/349>
154
+
155
+ [^q5-revocation]: **N.Y. Gen. Bus. Law § 899-ff(3)(b)-(c)** — "Such informed consent, once given, shall be freely revocable at any time, and shall be at least as easy to revoke as it was to provide. (c) If a covered user declines to provide or revokes informed consent for processing, another request may not be made for such processing for the following calendar year, however an operator may make available a mechanism that a covered user can use unprompted and at the user's discretion to provide informed consent." *N.Y. Gen. Bus. Law § 899-ff(3)(b)-(c).* <https://www.nysenate.gov/legislation/laws/GBS/899-FF>
156
+
157
+ [^q5-device-signal]: **N.Y. Gen. Bus. Law § 899-ff(3)(d)** — "If a covered user's device communicates or signals that the covered user declines to provide informed consent for processing pursuant to the provisions of subdivision two of section eight hundred ninety-nine-ii of this article, an operator shall not request informed consent for such processing, however an operator may make available a mechanism that a covered user can use unprompted and at the user's discretion to provide informed consent." *N.Y. Gen. Bus. Law § 899-ff(3)(d).* <https://www.nysenate.gov/legislation/laws/GBS/899-FF>
158
+
159
+ [^q5-shield-vendor]: **N.Y. Gen. Bus. Law § 899-bb(2)(b)(ii)(A)(5)** — "selects service providers capable of maintaining appropriate safeguards, and requires those safeguards by contract" *N.Y. Gen. Bus. Law § 899-bb(2)(b)(ii)(A)(5).* <https://www.nysenate.gov/legislation/laws/GBS/899-BB>
160
+
161
+ [^q5-cdpa-processor]: **N.Y. Gen. Bus. Law § 899-gg(1)** — "Except as provided for in section eight hundred ninety-nine-jj of this article, no operator or processor shall disclose the personal data of a covered user to a third party, or allow the processing of the personal data of a covered user by a third party, without a written, binding agreement governing such disclosure or processing. Such agreement shall clearly set forth instructions for the nature and purpose of the processor's processing of the personal data, instructions for using or further disclosing the personal data, and the rights and obligations of both parties." *N.Y. Gen. Bus. Law § 899-gg(1).* <https://www.nysenate.gov/legislation/laws/GBS/899-GG>
162
+
163
+ [^q5-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>
164
+
165
+ [^q5-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; (C) Report to the covered entity any use or disclosure of the information not provided for by its contract of which it becomes aware, including breaches of unsecured protected health information as required by § 164.410; (D) In accordance with § 164.502(e)(1)(ii), ensure that any subcontractors that create, receive, maintain, or transmit protected health information on behalf of the business associate agree to the same restrictions and conditions that apply to the business associate with respect to such information" *45 C.F.R. § 164.504(e).* <https://www.law.cornell.edu/cfr/text/45/164.504#:~:text=A%20contract%20between%20the%20covered,with%20respect%20to%20such%20information>
166
+
167
+ [^q6-breach-trigger]: **N.Y. Gen. Bus. Law § 899-aa(2)** — "Any person or business which owns or licenses computerized data which includes private information shall disclose any breach of the security of the system following discovery or notification of the breach in the security of the system to any resident of New York state whose private information was, or is reasonably believed to have been, accessed or acquired by a person without valid authorization. The disclosure shall be made in the most expedient time possible and without unreasonable delay, provided that such notification shall be made within thirty days after the breach has been discovered, except for the legitimate needs of law enforcement, as provided in subdivision four of this section." *N.Y. Gen. Bus. Law § 899-aa(2).* <https://www.nysenate.gov/legislation/laws/GBS/899-AA>
168
+
169
+ [^q6-breach-def]: **N.Y. Gen. Bus. Law § 899-aa(1)(c)** — "‘Breach of the security of the system’ shall mean unauthorized access to or acquisition of, or access to or acquisition without valid authorization, of computerized data that compromises the security, confidentiality, or integrity of private information maintained by a business." *N.Y. Gen. Bus. Law § 899-aa(1)(c).* <https://www.nysenate.gov/legislation/laws/GBS/899-AA>
170
+
171
+ [^q6-regulator-notice]: **N.Y. Gen. Bus. Law § 899-aa(8)(a)** — "In the event that any New York residents are to be notified, the person or business shall notify the state attorney general, the department of state, the division of state police, and the department of financial services as to the timing, content and distribution of the notices and approximate number of affected persons and shall provide a copy of the template of the notice sent to affected persons" *N.Y. Gen. Bus. Law § 899-aa(8)(a).* <https://www.nysenate.gov/legislation/laws/GBS/899-AA>
172
+
173
+ [^q6-private-info]: **N.Y. Gen. Bus. Law § 899-aa(1)(b)** — "(1) social security number; (2) driver's license number or non-driver identification card number; (3) account number, credit or debit card number, in combination with any required security code, access code, password or other information that would permit access to an individual's financial account; (4) account number, credit or debit card number, if circumstances exist wherein such number could be used to access an individual's financial account without additional identifying information, security code, access code, or password; or (5) biometric information, meaning data generated by electronic measurements of an individual's unique physical characteristics, such as a fingerprint, voice print, retina or iris image, or other unique physical representation or digital representation of biometric data which are used to authenticate or ascertain the individual's identity; or (6) medical information, meaning any information regarding an individual's medical history, mental or physical condition, or medical treatment or diagnosis by a health care professional; or (7) health insurance information, meaning an individual's health insurance policy number or subscriber identification number, any unique identifier used by a health insurer to identify the individual or any information in an individual's application and claims history, including but not limited to, appeals history; or (ii) a user name or e-mail address in combination with a password or security question and answer that would permit access to an online account." *N.Y. Gen. Bus. Law § 899-aa(1)(b).* <https://www.nysenate.gov/legislation/laws/GBS/899-AA>
174
+
175
+ [^q6-maintainer-notice]: **N.Y. Gen. Bus. Law § 899-aa(3)** — "Any person or business which maintains computerized data which includes private information which such person or business does not own shall notify the owner or licensee of the information of any breach of the security of the system immediately, provided that such notification shall be made within thirty days following discovery, if the private information was, or is reasonably believed to have been, accessed or acquired by a person without valid authorization." *N.Y. Gen. Bus. Law § 899-aa(3).* <https://www.nysenate.gov/legislation/laws/GBS/899-AA>
176
+
177
+ [^q6-notice-methods]: **N.Y. Gen. Bus. Law § 899-aa(5)** — "The notice required by this section shall be directly provided to the affected persons by one of the following methods: (a) written notice; (b) electronic notice, provided that the person to whom notice is required has expressly consented to receiving said notice in electronic form and a log of each such notification is kept by the person or business who notifies affected persons in such form; provided further, however, that in no case shall any person or business require a person to consent to accepting said notice in said form as a condition of establishing any business relationship or engaging in any transaction. (c) telephone notification provided that a log of each such notification is kept by the person or business who notifies affected persons; or (d) substitute notice, if a business demonstrates to the state attorney general that the cost of providing notice would exceed two hundred fifty thousand dollars, or that the affected class of subject persons to be notified exceeds five hundred thousand, or such business does not have sufficient contact information." *N.Y. Gen. Bus. Law § 899-aa(5).* <https://www.nysenate.gov/legislation/laws/GBS/899-AA>
178
+
179
+ [^q6-harm-carveout]: **N.Y. Gen. Bus. Law § 899-aa(2)(a)** — "Notice to affected persons under this section is not required if the exposure of private information was an inadvertent disclosure by persons authorized to access private information, and the person or business reasonably determines such exposure will not likely result in misuse of such information, or financial harm to the affected persons or emotional harm in the case of unknown disclosure of online credentials as found in subparagraph (ii) of paragraph (b) of subdivision one of this section. Such a determination must be documented in writing and maintained for at least five years. If the incident affects over five hundred residents of New York, the person or business shall provide the written determination to the state attorney general within ten days after the determination." *N.Y. Gen. Bus. Law § 899-aa(2)(a).* <https://www.nysenate.gov/legislation/laws/GBS/899-AA>
180
+
181
+ [^q6-cra-notice]: **N.Y. Gen. Bus. Law § 899-aa(8)(b)** — "In the event that more than five thousand New York residents are to be notified at one time, the person or business shall also notify consumer reporting agencies as to the timing, content and distribution of the notices and approximate number of affected persons." *N.Y. Gen. Bus. Law § 899-aa(8)(b).* <https://www.nysenate.gov/legislation/laws/GBS/899-AA>
182
+
183
+ [^q6-aa-damages]: **N.Y. Gen. Bus. Law § 899-aa(6)(a)** — "In such action the court may award damages for actual costs or losses incurred by a person entitled to notice pursuant to this article, if notification was not provided to such person pursuant to this article, including consequential financial losses." *N.Y. Gen. Bus. Law § 899-aa(6)(a).* <https://www.nysenate.gov/legislation/laws/GBS/899-AA>
184
+
185
+ [^q6-ag-penalty]: **N.Y. Gen. Bus. Law § 899-aa(6)(a)** — "Whenever the court shall determine in such action that a person or business violated this article knowingly or recklessly, the court may impose a civil penalty of the greater of five thousand dollars or up to twenty dollars per instance of failed notification, provided that the latter amount shall not exceed two hundred fifty thousand dollars." *N.Y. Gen. Bus. Law § 899-aa(6)(a).* <https://www.nysenate.gov/legislation/laws/GBS/899-AA>
186
+
187
+ [^q6-hipaa-ag-copy]: **N.Y. Gen. Bus. Law § 899-aa(9)** — "Any covered entity required to provide notification of a breach, including breach of information that is not ‘private information’ as defined in paragraph (b) of subdivision one of this section, to the secretary of health and human services pursuant to the Health Insurance Portability and Accountability Act of 1996 or the Health Information Technology for Economic and Clinical Health Act, as amended from time to time, shall provide such notification to the state attorney general within five business days of notifying the secretary." *N.Y. Gen. Bus. Law § 899-aa(9).* <https://www.nysenate.gov/legislation/laws/GBS/899-AA>
188
+
189
+ [^q7-shield-no-pra]: **N.Y. Gen. Bus. Law § 899-bb(2)(e)** — "Nothing in this section shall create a private right of action." *N.Y. Gen. Bus. Law § 899-bb(2)(e).* <https://www.nysenate.gov/legislation/laws/GBS/899-BB>
190
+
191
+ [^q7-aa-damages]: **N.Y. Gen. Bus. Law § 899-aa(6)(a)** — "whenever the attorney general shall believe from evidence satisfactory to him or her that there is a violation of this article he or she may bring an action in the name and on behalf of the people of the state of New York, in a court of justice having jurisdiction to issue an injunction, to enjoin and restrain the continuation of such violation. In such action, preliminary relief may be granted under article sixty-three of the civil practice law and rules. In such action the court may award damages for actual costs or losses incurred by a person entitled to notice pursuant to this article, if notification was not provided to such person pursuant to this article, including consequential financial losses." *N.Y. Gen. Bus. Law § 899-aa(6)(a).* <https://www.nysenate.gov/legislation/laws/GBS/899-AA>
192
+
193
+ [^q7-349h-pra]: **N.Y. Gen. Bus. Law § 349(h)** — "In addition to the right of action granted to the attorney general pursuant to this section, any person who has been injured by reason of any deceptive act or deceptive practice made unlawful by this section may bring an action in such person's own name to enjoin such deceptive act or deceptive practice, an action to recover such person's actual damages or fifty dollars, whichever is greater, or both such actions. The court may, in its discretion, increase the award of damages to an amount not to exceed three times the actual damages up to one thousand dollars, if the court finds the defendant willfully or knowingly violated this section. The court may award reasonable attorney's fees to a prevailing plaintiff." *N.Y. Gen. Bus. Law § 349(h).* <https://www.nysenate.gov/legislation/laws/GBS/349>
194
+
195
+ [^q7-labor-penalty]: **N.Y. Lab. Law § 203-d(3)** — "The commissioner may impose a civil penalty of up to five hundred dollars on any employer for any knowing violation of this section. It shall be presumptive evidence that a violation of this section was knowing if the employer has not put in place any policies or procedures to safeguard against such violation, including procedures to notify relevant employees of these provisions." *N.Y. Lab. Law § 203-d(3).* <https://www.nysenate.gov/legislation/laws/LAB/203-D>