Digital Driver's Licenses: Privacy Tradeoffs in Mobile Wallets
How digital IDs offer selective disclosure but raise new tracking concerns
1Beyond plastic card digitization
Mobile driver's licenses (mDLs) use digitally signed information verified by issuing authorities, not just card images. The ISO/IEC 18013-5 standard enables selective data disclosure - like confirming age over 21 without revealing exact birthdates. This contrasts with physical IDs that expose all printed information during verification. Apple and Google implement additional protections including mandatory biometric authentication for in-person presentations and local phone storage rather than cloud syncing.
2Two data transfer methods
The ISO standard supports device retrieval (direct phone-to-reader transfer) and server retrieval (issuer-mediated transfer). Privacy advocates criticize server retrieval's 'phone home' capability, where issuers could track ID usage times/locations. In 2025, AAMVA banned server retrieval in North America, though regional rules still vary. Current implementations like Apple Wallet exclusively use device retrieval, but the debate continues as digital ID adoption grows globally.
3Post-sharing data concerns
While wallets control what leaves your device, they can't govern how recipients handle collected data. Apple and Google display retention intentions before sharing - whether requesters plan to store specific ID elements. Legal protections vary; New Jersey prohibits requiring device handover during verification. The ACLU warns broader digital ID adoption might normalize identity checks in currently anonymous online spaces, though current systems don't track web activity.
4Security vs accessibility tradeoffs
Lost digital IDs require stronger protections than plastic cards - Apple mandates biometric security for mDLs, Google requires screen locks. Both platforms allow remote credential deletion via Find My (Apple) or Google Account (Android). However, device dependency creates new vulnerabilities; dead/unsupported phones may prevent credential access entirely. Experts currently recommend treating digital licenses as supplements to physical IDs, not replacements.
5Selective disclosure mechanics
mDLs enable context-aware data sharing through verifier-specified requests. A bar needing age verification receives only an 'over 21' confirmation rather than full birthdate. This granularity extends to address, license number, and other fields. Both Apple and Google encrypt this data and require user approval per transaction. EU implementations now explore anonymous age verification without sharing personal identifiers at all.
6Implementation variances
Digital ID systems differ by region and wallet provider. Apple's implementation requires Face ID/Touch ID for in-person verification and shows requested fields pre-share. Google stores credentials locally on Android devices with similar preview functionality. The AAMVA's 2026 guidelines standardize certain North American practices, but global interoperability remains challenging due to differing national regulations and technical standards.
7Biometric authentication requirements
Adding mDLs to digital wallets mandates robust device security. Apple requires enrolled Face ID/Touch ID, while Google enforces screen lock mechanisms. Both platforms re-authenticate before each ID presentation attempt. This creates a higher baseline security than physical cards, as found devices can't immediately display ID information without bypassing these authentication measures first.
8The road ahead for digital IDs
While digital licenses offer privacy advantages through selective disclosure, their ecosystem faces standardization challenges. The prohibition of server retrieval addresses some tracking concerns, but data retention policies remain fragmented. As adoption grows in the EU and North America, the balance between convenience, privacy, and security will shape whether digital IDs can truly replace physical credentials or remain supplementary tools.