State Residency Verification | Zero-Knowledge Address Proof | MyProof
MyProof state residency verification proves that a user lives in an approved state without storing a full address. It helps regulated services check jurisdiction eligibility while minimizing location data exposure.
Never sent during verification
- Street address
- ZIP code
- License number
- Document image
Best for
- Policies based on a supported driver's-license state or address field.
- Regional eligibility checks that do not need the full address.
- Age-plus-state rules evaluated together on the user's phone.
Not for
- Proving the user's current physical location.
- Replacing geolocation, delivery-address validation, or legal residency review.
- Assuming every state document exposes identical fields and formats.
Legacy IDV vs MyProof
| Legacy IDV |
MyProof |
| Collect and retain the complete address to answer a state-level question. |
Evaluate the supported document-derived state policy on device and return the result. |
| Treat an ID address as proof of current physical location. |
Keep the claim narrow: document-derived residency, not geolocation. |
| Run separate age and state checks that duplicate identity data. |
Evaluate age and state predicates in the same configured policy when both are required. |
Frequently asked questions
How does state residency verification work?
MyProof reads supported state or address fields from a compatible driver's license on the user's phone and evaluates whether they satisfy the configured state policy. The requesting system receives the result rather than the full address.
Can MyProof confirm a state without collecting the full address?
Yes. The full address remains on the user's device during verification while the workflow receives the state-policy result and receipt reference.
Does this prove the user's current location?
No. A driver's-license address is a document-derived residency fact. MyProof does not geolocate the user or confirm where the user is physically located at the moment of verification.
Can a policy allow more than one state?
Yes. A policy can evaluate whether the supported document-derived state is within an approved set without returning the user's full address.
Can state and age requirements be evaluated together?
Yes. A policy can require both an age threshold and a supported document-derived state result in one verification when the workflow needs both facts.
Canonical page: https://myproof.ai/state-residency-verification