No. HB 1477
Filed under Transportation.
Use of Driver License Information for Fraud Prevention; Authorizes DHSMV to provide state agencies & certain third parties with access to certain driver license information for specified purposes with licensee's consent; authorizes identity verification service providers to use DHSMV data under certain conditions; requires certain revenue be deposited into Highway Safety Operating Trust Fund; prohibits such providers from retaining certain information; prohibits third party from storing or selling certain information without licensee's consent.
Plain English Summary
AI-GENERATEDA new paragraph lets the department share a driver's license photo, signature, and data with a state agency or a contracted identity-verification provider, but only with that driver's consent.
That provider may not retain IP addresses, geolocation data, or other information about the device someone used to reach the verification system.
A separate rule bars any third party from storing or selling those images, signatures, or data unless the licensee agrees to it separately.
Revenue the department collects from these new agreements goes into the Highway Safety Operating Trust Fund, the same fund that finances the department's own operations.
AIAdds a new basis for the department to share a driver's license image, signature, and data with a private company under contract to perform identity verification, a recipient category the existing list does not include.
AIA contracted third party may not store or sell a driver's image, signature, or data used under this new authority, unless the driver separately consents to that specific use.
AIAny state agency with an interagency agreement can now receive this data for fraud prevention, identity verification, or protecting the integrity and security of individual identities, a broader standard than the law's older, agency-specific purposes.
AIThe state-agency and third-party disclosure channel only operates with the driver's consent, unlike the law's older, narrower recipient categories such as courts or child-support enforcement, which do not require it.
AIAn identity verification service provider may not keep Internet protocol addresses, geolocation data, or other information describing the location or device an applicant used to access the system.
AIA contracted identity-verification provider's use of this data is lawful only if the data remains in the department's possession, rather than being copied out to the provider's own systems.
AIMoney the department collects from these new interagency agreements or identity-verification contracts must go into the Highway Safety Operating Trust Fund instead of general revenue.