MCDPA compliance for a mobile app
Minnesota Consumer Data Privacy Act. This page applies it to one kind of product (mobile app), so you get the obligations that are actually yours instead of a summary of the whole statute.
Does it apply to you?
100,000+ Minnesota consumers, or 25,000+ with revenue from selling data.
What a mobile app typically processes
- device identifiers and advertising IDs
- device permissions such as camera, location or contacts
- crash reporting and mobile analytics SDKs
- in-app purchases through the store
Each of these is processing you have to disclose. Adding an SDK later adds to this list — which is why a policy written once goes stale.
Documents you need
The intersection of what MCDPA requires and what a mobile app actually does:
- Privacy policy
Rights you must honour
MCDPA gives people in Minnesota the right to:
- Access a copy of their data
- Correct inaccurate data
- Have their data deleted
- Receive their data in a portable format
- Opt out of the sale or sharing of their data
- Opt out of profiling and targeted advertising
- Not be discriminated against for exercising a right
Cookies and trackers
Trackers may load by default, but the visitor needs a working way to opt out, and you must honour it.
MCDPA also requires you to honour a universal opt-out signal, so a browser sending Global Privacy Control must be treated as having opted out — without the visitor clicking anything.
On mobile, the store asks too
There is no cookie banner in a native app, but Apple App Privacy and Google Play Data Safety both make you declare the same processing — and a declaration that contradicts your privacy policy is the version reviewers notice. The policy has to be reachable at a public URL before you submit.
See what your site is actually missing
Paste your URL. We fetch the live page, detect the trackers, payments and AI calls that really ship to visitors, and tell you which documents and consent you need. No signup.
No signup · result in seconds
Primary sources
- MCDPA — Minnesota Consumer Data Privacy Act · official text
MCDPA for other kinds of product
Other frameworks for a mobile app
This page is an engineering summary of publicly available regulatory requirements, generated from LexVibe's framework registry — not legal advice. Every framework links to its official text so you can check it yourself. For decisions about your own compliance posture, consult the primary sources and a lawyer qualified in the relevant jurisdiction.