The problem PrintShield solves

So we all know that whenever we have to go to get a print of our confidential document(like passport, aadhar card etc.), there's a large amount of uncertainty associated with it. We never know when such documents can be used against us and without our knowledge.
Then it clicked me that Ethereum and BlockChain are all about privacy and decentralization. So i decided to build upon that idea and make this build my app, PrintShield.

In this app, after selecting document u can review the sensitive fields and then set a copy limit and an expiry limit, after this u get and QR which u can scan and then the files are sent to the printer without being locally saved on the Printer Shop's computer .

Challenges I ran into

1. Designing privacy without overclaiming security

The biggest challenge was figuring out what the MVP could actually guarantee. We didn't want to claim that a QR code alone makes a document secure, so we separated the current UX/prototype layer from the future encryption and backend enforcement layer.

2. Making temporary access meaningful

We had to think about how a print authorization should work: the user chooses a copy limit and an expiry time, then the QR becomes invalid after the selected window. Designing that flow while keeping it simple for a normal user was a challenge.

3. Designing the QR system without putting sensitive data inside it

A major design decision was keeping the actual document out of the QR code. The QR only carries things like the job reference and expiry information, while the document remains on the user's phone in the MVP.

4. Balancing security and UX

We wanted users to understand that shorter expiry times and fewer copies provide more control, without pretending that our “privacy score” is an actual security measurement. That led us to make the score explicitly a UX heuristic.

5. Building a convincing prototype without the complete infrastructure

A real system needs a backend, authenticated print-shop client, encryption, printer integration and secure deletion. Implementing all of that during an MVP would have significantly increased the scope, so we focused on proving the core user experience and QR authorization flow first.