Redacting and combining ID cards (college ID, passport, license, 4 H club)

Question

I need a UI that will encourage privacy, and allow a user to selectively disclose information on a need-to-know basis, in real life and online. This can be ANY information, from a catalog of sorts including:

• Person - Age (date, or older or younger than X), state of residence
• College - StudentID, GPA, club membership & standing, alumni, graduation year
• etc....

Use cases

• A woman goes to a bar and shows her license. That contains her home address. The bartender or bouncer now knows where she lives, when all they needed was a photo and that she was > 21.
• A person needs to use their medical benefits, but must do so anonymously. All they need to know is that the person is valid under a current plan, and doesn't need the subscriber ID or to pinpoint that person in any way.
• A minor needs to access an age controlled website, reducing the risk that no online predators can access it.

I imagine implementing this on a mobile device (iOS, Android, etc) or on a website. Watch form factors (Apple/Android) will come later.

Question

What UI should I use to allow users to

• Redact / hide / cross out information they don't want others to see?
• Selectively disclose more sensitive information (home address, driver's ID number)
• Combine information from various sources to create a new ID card (passport, DMV, college ID)

Thanks for helping me figure out the correct UI for this. My current life passion is to share this amazing technology with as many people as possible, and I need to make sure that it's easy for all ages, on a variety of devices.

Edit - ideas

I was thinking of having a top row of frequently (context sensitive) ID cards that can be "favorited". These cards can be flippable

....with these swipes on the back:

New items (such as a photo from a passport) can be added through a search field or a hierarchal navigation that is done through a set of screens

To make things more intuitive, I think the bottom of the unflipped card needs to have an EDIT button, and a SEND button...Why? because it's not clear that flipping a card over allows you to redact. Then again I want this to be a material design...

Edit - data location

This data is not stored on your phone; it's password encrypted on a smartcard or downloaded from the internet with a SMS validation. This concept is more secure than logging into a website (IRS, DMV, College, Equifax, etc) and gaining full access to everything.

Additionally, the data can downloaded to your home computer via a private Bittorrent, or open source Syncthing.

The data is always encrypted - in air or at rest. Even if someone steals it. You can remote-wipe your device if you so choose.

Edit - How is it validated

The bartender validates it on his app using transparent cryptography, transmitted over Bluetooth, Wifi, or TLS

Answer 1

Considering the context of use and the user story, there must be a quick to deploy, yet routinely and robustly secure display of data.

A scene based approach would conceptually strongest UX. e.g. User selects a scene

• need to prove I am legal drinking age in this State
• need to prove level of medical cover
• need to prove I am in an age range
• need to prove I am a member of organisation X

how this is presented is secondary importance. Presentation must be driven out from the most common scenes and how they relate e.g. hierarchical? does a scene need secondary context input?

Note that

• Provide multiple default scenes
• Default scenes can pick best method of proof from the data available
• Scenes can merge data from different sources e.g. Hire a car has proof of drivers license and sufficient funds
• Lock phone when a scene is active (so user can hand to official without risk)
• Allow for custom scenes to be created

An additional low frequency use case may to extend amount of data revealed on current scene, BUT before you implement make sure this is a really required case.

Remember the official validating a stated claim is a user too, so any COMPLETE UX design must include their wider use cases too. Can they get independent proof of the claim made on applicants phone? e.g. Possibly scan a QR code on their phone and see verification message.

Answer 2

Your question does not stipulate how the user will deliver the desired information. I see 2 methods, physically delivering the card/ID to the recipient, and digitally providing the data. The latter doesn't fit your use cases, so I'll answer for the former.

The answer is challenging because there are multiple ways to accept information inputs, but the information comes in a physical form. Use case #1, for instance, makes no sense because bouncers aren't looking to see if the person is 21. Most new drivers licenses (their biggest use case) actually say when the person turns 21 by year. They care about the legitimacy of the card, which you cannot prove except by handing the card over. A photo and additional info, especially if it's digitized, can be declined as fake and fabricated.

Hurray physicality.

The other use cases fall under the same issues. So I answer with a question: what exactly are you trying to solve.

It sounds like you're looking for a way to collect "user" data that's relevant for the use case in question. If so, that's easy: map out all of the types of data inputs (drivers licenses, IDs, passports, etc.) in physical form, build an app that makes the camera scan that determines which input type it is, and then only display and highlight those data points.

Conceptually, it's easy. Technically...if you can find a team that can build it, give me the routing number for your company.

Assuming you have access to hundreds if not thousands of different government databases to answer the questions above in a simple fashion, awesome. But this is some Minority Report stuff.