Customers using DLIDLib may periodically encounter a license that does not parse. This could be due to a new jurisdiction format, or due to something unusual and unexpected in the license data. The easiest way for us to analyze the problem and update the parser is to study the raw data in question. To this end, we have made several options available.

Types of data we accept

Raw Data: This is where the client sends us the raw data from the card reader (magnetic stripe or barcode). This gives us the most complete view of the data for analysis, but also exposes the license owner's information to us.

Barcode Photo: Clients may also submit hi-resolution, clear photos of the 2D barcode for us to read as raw data on our end. This may be helpful in situations where clients have a license that does not parse, but does not have a convenient way to capture or send us the raw data from that device.

Masked Data: We have provided a utility to clients which will read license data, and - even if it can't be parsed - save it to a data file for submission to us. This utility allows the user to mask personal information in the license with special characters which preserve the location and size of the data, but do not reveal the data itself. The user can mask the name, address, license/ID number, and if found, Social Security Number. Using this utility, we can still analyze the data as well as if we had the raw data, but without the license owner exposing any personal information to us.

What do we do with the data?

Whenever we receive any raw data, we immediately scrub it in a similar manner to the Masked Data procedure. Before anything else is done with the data, the owner's personal information is removed and replaced with dummy data. Specifically:

• We do not ever store any personal information from any real license or ID.
• We do not ever sell or share any such personal data with any other party, for any reason, period.

We do keep the masked, dummy data - which preserves the formatting itself, which is what's important to us - in our database for future testing, to ensure that our parser retains compatibility with all past data samples. Again, none of this data contains any real names, addresses, ID numbers, SSNs, etc.

Data Submission Procedure

1. First, especially if the data has not been masked already, consider using this method. It eliminates the concern over handling personal information.
2. Second, zip the file with a utility such as WinZip, 7-Zip, etc. and use a password to encrypt the contents.
3. Send the data, along with a description of any problems encountered with it, to either the developer you're working with or our general Data Submission email address. See our Developer Contacts page for a list of addresses.
4. Call us and give us the password to the file - DO NOT include it in the email! The contacts page above also has phone numbers.

The DLIDLib parser is available in several editions. If you have additional needs or requirements, please contact us so that we may address them for you. All versions of the parser include:

• Non-expiring usage - the parser license does not expire.
• Free technical support for 1 year
• Free maintenance updates within the same major version of the parser for 1 year
  
  • Includes updates to accommodate new or changed jurisdiction-specific formats

DLIDLib supports any jurisdictional format that adheres closely to the published AAMVA specification. However, not all jurisdictions do, and there may be some deviations that have not been addressed yet in the library. We are continuously updating the parser as new jurisdictions implement the AAMVA standard and as jurisdictions make changes to their formats. If you encounter a license that does not parse correctly, please This e-mail address is being protected from spambots. You need JavaScript enabled to view it . We have a secure, privacy-protected tool for reading these cards to decipher format deviations without exposing sensitive personal data. When such issues are reported,the parser is usually updated within 24-48 hours.