8 controls
132 frameworks share controls with it
United States - Minnesota
verified against its source document
Every control below is one this framework asks for. The right hand column counts how
many other frameworks in our corpus carry the same control, which is the difference between
doing this work once and doing it again for the next standard.
Minnesota Consumer Data Privacy Act Evidence & Implementation Kit
8 controls is the documentation set somebody has to write. This is that set,
already written: an adopt-ready artifact for every control in policy and procedure text you
edit rather than draft, and the evidence checklist an auditor asks for against each.
See what is in it, $249
The same set every buyer of this kit receives. Nothing here is produced on request.
What you already have
Frameworks whose controls overlap this one, most first. If you run any of them, the
count is roughly what you have already evidenced.
Every control
| Code | Control | Also in |
|---|
MN-CDPA-Chief-Privacy-Officer-Section-325O-06-MN-UNIQUE-Designation-Privacy-Programme-Training | Minnesota CDPA Chief Privacy Officer + Section 325O.06 + MINNESOTA-UNIQUE Designation + Privacy Programme + Training | 73 |
MN-CDPA-Consumer-Rights-Section-325O-04-Access-Correct-Delete-Portability-List-Third-Parties-Opt-Out-Appeal-AIQUEST-Profile | Minnesota CDPA Consumer Rights + Section 325O.04 + Access + Correct + Delete + Portability + List of Third Parties + Opt-Out + Appeal + AI Question Profile | 23 |
MN-CDPA-Data-Privacy-Assessment-DPIA-Section-325O-07-Sensitive-Targeted-Sale-Profiling-AI-Consumer-Health | Minnesota CDPA DPIA + Section 325O.07 + Sensitive + Targeted + Sale + Profiling + AI + Consumer Health | 72 |
MN-CDPA-Enforcement-AG-Ellison-Section-325O-10-USD-7500-Per-Violation-Data-Broker-Registration-325O-13-Sunset-25-Jan-2026 | Minnesota CDPA Enforcement + AG Ellison + Section 325O.10 + USD 7,500 Per Violation + Data Broker Registration + Sunset 25 January 2026 | 43 |
MN-CDPA-Privacy-Notice-Section-325O-05-Categories-Purposes-Rights-Email-Online-Mechanism-Appeal | Minnesota CDPA Privacy Notice + Section 325O.05 + Categories + Purposes + Rights + Email + Online + Appeal | 0 |
MN-CDPA-Processor-Contract-Security-Section-325O-08-Pseudonymisation-Section-325O-09-De-Identification | Minnesota CDPA Processor + Section 325O.08 + Security + Pseudonymisation + Section 325O.09 + De-Identification | 59 |
MN-CDPA-Scope-HF-1367-Chapter-325O-Walz-24-May-2024-Effective-31-July-2025-AG-Ellison-100K-25K-Threshold | Minnesota CDPA Scope + HF 1367 + Chapter 325O + Walz + 24 May 2024 + Effective 31 July 2025 + AG Ellison + 100K/25K | 0 |
MN-CDPA-Universal-Opt-Out-GPC-Sensitive-Data-Section-325O-02-Consumer-Health-Data-Children-Known-Child-Transgender | Minnesota CDPA Universal Opt-Out + GPC + Sensitive + Section 325O.02 + Consumer Health Data + Children + Known Child + Transgender | 46 |
Tell me when Minnesota Consumer Data Privacy Act files something new
One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.
What an auditor will ask you to produce
The artefacts named on the failure modes this framework speaks to.
- De-identification public commitment + contractual binding + technical safeguards
- Aggregated consumer information procedures
- Processor contracts with MCA 30-14-2809 mandatory clauses (instructions + confidentiality + security + return/delete + cooperate + subprocessor + ROPA)
- Reasonable security practices appropriate to risk + NIST CSF + ISO 27001 baselines + Montana Online Personal Information Theft Prevention Act parallel
- Pseudonymisation procedures per MCA 30-14-2811 with separation of identifier and additional information
- Processor contracts with Section 325O.08 mandatory clauses (instructions + confidentiality + security + return/delete + cooperate + subprocessor + ROPA)
How programmes fail on this
Failure modes named by this framework and others. Each opens the full record.
What this page is
A control-level reference for Minnesota Consumer Data Privacy Act, drawn from our framework corpus. Control codes and
titles are references to the standard, not reproductions of it. The overlap counts and the
auditor artefacts are our own work and are the part you will not find elsewhere.
Measure this against what you already run ·
All frameworks · Today's edition